From a customer order to money in the bank — the cycle, the breakpoints, and the measures that matter.
Order to cash is the end-to-end process from receiving a customer order through fulfilment, invoicing and collection to cash applied against the invoice. It spans sales, warehouse, finance and credit control, which is exactly why it breaks: each function optimises its own step and the handovers between them are nobody's responsibility.
O2C is where working capital is won or lost. Every day between despatch and cash is financed by you, and the delays are rarely in collections — they are upstream, in invoices raised late, raised wrongly, or disputed because the delivery did not match the order. Measuring only days sales outstanding looks at the end of a process whose problems started much earlier.
The order is entered or received by integration, and the customer's credit position is checked before it is accepted.
Allocation, picking, despatch. The despatch confirmation is what should trigger invoicing, not a separate manual step.
Raised from the despatch, so what is invoiced matches what shipped. Where required, registered for e-invoicing before issue.
Statements, reminders and escalation driven by ageing rather than by whoever remembers to chase.
Receipts matched to invoices, ideally automatically. Unapplied cash blocks credit and generates unnecessary chasing.
A business measures DSO at 54 days against payment terms of 30 and assumes it has a collections problem. Decomposing the cycle shows something else.
Order to dispatch averages 3 days. Dispatch to invoice averages 6 — invoices are raised in a weekly batch, so a parcel leaving on Monday is invoiced the following Monday. Invoice to payment averages 45, against terms of 30. Within that 45, around 9 days is attributable to invoices disputed and reissued, most commonly for pricing that did not match the order.
Three fixes, in order of return. Invoice at dispatch confirmation rather than weekly, which removes 6 days immediately and costs nothing but configuration. Fix the pricing errors causing disputes, which removes most of the 9. Only then is what remains an actual collections issue, and it is 30 days rather than 54. The general point is that DSO is a composite, and attacking it without decomposing it means working on the longest-looking segment rather than the most tractable one.
| Term | What it means |
|---|---|
| Credit check | Validating a customer's limit and exposure before confirming an order. |
| Allocation | Reserving stock against an order so it cannot be sold twice. |
| Billing block | A hold preventing invoicing until something is resolved, usually pricing or approval. |
| DSO | Days sales outstanding — how long cash takes to arrive after the sale. |
| Dispute | A customer-raised reason for non-payment, which is an invoice-quality problem more often than a cash one. |
Manual invoicing after despatch introduces both delay and mismatch. Trigger it from the despatch document.
Checking credit once goods are allocated or shipped means the decision has already been made.
If dispute reasons are not categorised, the same causes recur indefinitely.
It is a lagging summary. Invoice accuracy rate and time from despatch to invoice explain it.
| Metric | What it tells you | What distorts it |
|---|---|---|
| DSO, decomposed | Order-to-dispatch, dispatch-to-invoice, invoice-to-cash. The single figure hides which one is broken. | |
| Invoice accuracy | Share of invoices paid without query. Disputes are usually a pricing or data problem. | |
| Orders on credit hold | Whether credit control is blocking revenue or protecting it. Ageing holds mean nobody is working the queue. | |
| Perfect order rate | Complete, on time, correctly invoiced. The composite customers actually experience. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.