How to run the whole chain from a customer's order to cash in the bank — and hand your bookkeeper summarized numbers that still trace back to the exact lots and units behind them, without keying the same order into two systems by hand.
Real help from real food people
Chef Diego runs a real food plant. If this page didn't get you there, tell us — a person reads every message.
After this you can follow a single order from the purchase order that starts it to the payment that closes it, and put your finger on every point where someone is retyping the same numbers into a second system. You will know which parts of that chain belong to operations, which belong to whoever keeps your books, and how to pass clean summaries across the line so no order — and no lot — gets keyed twice.
Everything earlier in this course lived on one side or the other of a line: making the product and getting the cash. This lesson connects them. The whole run from a customer placing an order to the money clearing your bank has a name — the — and for a manufacturer it runs about like this:
Notice the chain crosses two worlds. Picking lots, packing cases, and shipping are operations — the floor. Invoicing, collecting, and booking the money are accounting — the books. The electronic documents from the last lesson ride along this same chain. The order-to-cash cycle is the seam where those two worlds hand work back and forth, and the seam is where a growing operation quietly loses hours and accuracy.
Watch what happens to one order in an operation that never wired the seam. The order comes in and someone types it into a spreadsheet to schedule production. The floor writes the lots and quantities it shipped on a paper pick sheet. Someone re-types those into the spreadsheet to draw down inventory. Someone types the invoice into QuickBooks by hand. When the payment lands short, someone reconciles it by squinting at a bank statement, the spreadsheet, and the invoice side by side. The same order has now been entered, by a person, four or five times.
That is the moment operators describe when they say their team has become the between systems that do not talk. Every hop is a chance to fat-finger a quantity, drop a lot, or convert a unit wrong, and every hop is time nobody is paid to spend. The cost is not one dramatic error; it is a steady tax of small ones, plus the hours spent making them. This is its own subject in the scaling track — the trap of being the human glue between tools that will not connect — but the order-to-cash chain is where most operations first feel it.
The fix is not a cleverer spreadsheet. It is deciding, on purpose, where each piece of the order lives, so it gets entered once and flows from there.
The clean way to run the seam starts with a simple split: operations owns the physical truth, accounting owns the financial record, and each keeps what it is best placed to know.
Operations owns everything about the actual goods and what they cost to make:
Accounting owns the money and the ledger — the — and everything the outside world reads:
The line between them is a hand-off point, not a wall. Operations knows a jar cost $2.37 to build and which lot it shipped from; accounting needs to know that the 4,500 jars behind one $18,000 chain-store order moved $10,665 of cost — 4,500 × $2.37 — from inventory to cost of goods sold this period. Same event, two altitudes. The skill is passing the right altitude across the line — and no more.
Here is where operations most often over-shares and gums up the books. It is tempting to push every lot, every unit, and every conversion straight into QuickBooks so the books "match" the floor. Do not. Your bookkeeper does not want 4,500 jar-level rows or a line for every lot; they want the totals that roll into the financial statements. The lot-level detail belongs on the operations side, where a recall or a customer complaint needs it. The books need summaries.
So push summaries across the seam:
The detail still exists — it just lives once, in the operations system, and only its summary crosses into the books. When a number comes up, ask who reads it. If the answer is your bank, your CPA, or the IRS, it belongs in the ledger as a summary. If the answer is the person tracing a lot, it belongs in operations at full detail.
A system built for food can hold that split for you: the lot-level truth on the operations side, summarized to the totals the books need at the seam. Bettr Manager, for one, keeps purchasing, receiving, inventory, production, and sales in one place, so the order, the lots that filled it, and the cost behind it are entered once on the operations side rather than re-keyed from a spreadsheet into production and then into inventory — and the lot genealogy stays there, at full detail, instead of being flattened into the books. However you wire it, the rule holds: detail lives once, and only its summary crosses to accounting.
Two things have to survive the trip from the floor to the invoice, and both are easy to lose: the unit and the lot.
Start with the unit. You buy tomato paste in one measure, make sauce in gallons, fill and count jars, and sell in cases. The is different at almost every step, and the invoice has to speak the customer's unit at the customer's price. The chain-store order for $18,000 is 375 cases to the customer — 375 cases at $48 a case — but it is 4,500 jars leaving your inventory (375 × 12), each drawing down finished-goods stock. If the conversion is off by a case here and there, the invoice quantity and the inventory relief stop agreeing, and the mismatch resurfaces later as a deduction or a stock count that will not tie out. Define the conversion once and exactly, so the same order reads as 375 cases on the invoice and 4,500 jars in inventory without anyone doing arithmetic on the fly.
Now the lot. When you ship those 4,500 jars, they came from specific lots. If the only surviving record of the order is an invoice that says "375 cases," you have severed the link between what you billed and which lots you shipped — and the day a customer calls about a bad jar, or an auditor asks which customers received a given lot, you are reconstructing it from packing slips. Keeping attached to the order through invoicing is what keeps the one-step-forward trace intact on the sales side. The invoice is a financial document; it should not be the only place your shipment is recorded.
Getting units of measure right across purchasing, production, and sales is a discipline of its own, and a companion lesson takes it on directly. Here it is enough to know the invoice has to carry the customer's unit while the lots stay attached behind it.
The order is not closed when you ship it, or even when you invoice it. It closes when the money lands and you have accounted for every dollar of the difference between what you billed and what arrived — which, on this course's running example, is a payment of $15,000 against that $18,000 invoice.
For a big EDI account, the payment does not arrive as a mystery deposit. It comes with a — in EDI, the 820 Payment Order/Remittance Advice, one more numbered document from the same ASC X12 standard behind the 850, 856, and 810 you met last lesson. Some retailers send the deduction itself as its own document, the 812 Credit/Debit Adjustment. Between them, the paperwork tells you the $3,000 broke into two parts — say $1,200 for the cases you shipped short, and $1,800 as an on-time, in-full chargeback for missing the in-full bar — the difference between a shortfall you owe back and a fee you might dispute.
Reconciling is matching the $15,000 that landed, and the $3,000 explained on the remittance, back to the $18,000 you billed, then telling accounting what to book: $15,000 to cash, and the $3,000 recorded against the sale — as a shortfall, a chargeback expense, whatever their chart of accounts calls it. That posting is your accountant's call, not yours. Your job on the operations side is to hand them a clean, itemized reason for every dollar of the gap, so the deduction gets recorded and — if it is disputable — disputed, instead of quietly written off. This is the same partial-payment discipline the model-versus-bank lesson insisted on, now closing the last link in the chain: enter what actually came in, keep the shortfall visible until it is collected or written off, and never let the books show $18,000 collected when $15,000 arrived.
Wire the seam this way and the order-to-cash chain stops leaking. An order is entered once and flows — production, inventory, invoice, and the summary to the books all reading from the same event. Operations keeps the lots and the units; accounting keeps the ledger; and the number that crosses between them is a summary that still traces back to the detail behind it. The team stops being the integration layer and goes back to running the operation.
That is the whole loop this track has walked — from what a batch truly costs, through the cash behind it, into stores, and back out as clean cash and clean books. The rest is running it well, one order at a time.
Do this in your operation