Enterprises: the separate parts of your business
An enterprise is a part of your business you want to see separately. Corn against beans. Commercial against residential. The fleet against the shop.
You tag each transaction with the part it belongs to. The books then tell you what each part earned on its own.
That is the idea the rest of the software is built on.
The problem
Say you farm 320 acres of corn, run 150 head, and haul for a neighbor on the side.
That is one bank account, one tax return and one set of books. But it is three businesses, and they do not all make money.
Standard accounting software gives you a profit and loss for the whole operation. It tells you that you made $80,000.
It cannot tell you that the corn made $140,000, the cattle lost $30,000, and the hauling lost $30,000. That is the only version of the sentence you can act on.
The usual workarounds are a spreadsheet on the side, or classes and tags bolted onto a system that was not built for them. Both drift out of step with the books inside a season.
What an enterprise is
An enterprise is one of the businesses inside your business. Corn. Cattle. Hauling. The orchard. The shop.
You give each one:
- A name and number, so it can be referred to the same way every time
- A unit — acres, head, hours, tons — and how many of them
That second part is what most systems leave out. It is also what makes the numbers useful.
Once the software knows the corn enterprise is 320 acres, every dollar coded to corn has something to be divided by. You stop reading totals. You start reading dollars per acre and dollars per head. That is the language the decision gets made in.
Coding to an enterprise
Every line of every transaction can carry an enterprise. Not the invoice — the line.
One bill from the co-op can be seed on the corn, feed on the cattle, and a filter for the truck. Three lines, coded three ways, because that is what actually happened.
This runs through the whole ledger. Sales invoices, purchase bills, checks, deposits, journal entries, budgets, equipment, credit memos.
An enterprise is a dimension on the posting. It is not a second set of books you have to keep in step with the real one.
Which is why the enterprise numbers cannot drift from the financial statements. They are the same transactions, read two ways.
Direct, or overhead?
This is the part that catches people, so here it is exactly. A line can be coded two ways, and the difference is the whole model.
- Put an enterprise on the line and it is a direct cost to that enterprise. You knew who used it, so you said so. Seed for the corn. Feed for the cattle. A vet bill.
- Leave the enterprise blank and put an overhead on it instead. Now the cost goes into that overhead's pool, and gets spread across enterprises by percentages you set. Shop insurance. The accountant's fee. The office.
The blank enterprise is the switch. That is the whole rule.
So which is fuel? It depends on your operation, and the software does not decide for you.
If you know the tractor was on corn ground, split the bill by line and code it to corn. Direct, exact, no allocation.
Say it came out of a bulk tank that everything drew from. Nobody wrote down which machine took what. Then it is honestly an overhead.
Let the distribution do the work. Do not invent a split at the keyboard.
Both are right. Guessing at a line-level split you do not actually know is the wrong one. It looks precise and it is not.
Groups
Enterprises can be grouped. All the row crops. Everything on the home place. Everything the eldest son runs.
A group reports as a unit without losing the detail underneath. So you can look at "crops" as one number, then open it.
What you get out
- A profit and loss per enterprise, from the same ledger as the company one
- Per-unit economics — per acre, per head, per hour
- Comparisons across enterprises, and across years for the same enterprise
- Budgets set per enterprise, with actuals read against them
And when a field is drawn on the farm map and attached to an enterprise, the same figures land on the ground they came from.
The honest caveat
This only works if the coding gets done.
An enterprise left blank on a bill is a cost that lands on the company and on no enterprise. Your per-acre figure is then quietly wrong by that amount.
The software helps. Payees and accounts carry default enterprises, so most lines code themselves. Reporting will show you what went uncoded.
But nothing can work out which business a diesel bill belonged to. That part is yours.