Mon – Sat: 9:00 AM – 7:00 PM IST
ERP Basics

What is order to cash (O2C)?

From a customer order to money in the bank — the cycle, the breakpoints, and the measures that matter.

In short

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.

Why It Matters

Why this matters in practice

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.

Spans four functions, so the handovers are where it fails
Invoice accuracy drives dispute rate more than collection effort does
Credit checking at order entry prevents bad debt cheaply
Cash application speed affects available credit for the next order
How It Works

How it works in practice

Order capture and credit check

The order is entered or received by integration, and the customer's credit position is checked before it is accepted.

Fulfilment

Allocation, picking, despatch. The despatch confirmation is what should trigger invoicing, not a separate manual step.

Invoicing

Raised from the despatch, so what is invoiced matches what shipped. Where required, registered for e-invoicing before issue.

Collection

Statements, reminders and escalation driven by ageing rather than by whoever remembers to chase.

Cash application

Receipts matched to invoices, ideally automatically. Unapplied cash blocks credit and generates unnecessary chasing.

Worked example

A worked example: where the 54 days actually go

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.

Key terms

The vocabulary, briefly

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.
What Goes Wrong

Common mistakes worth avoiding

Invoicing decoupled from despatch

Manual invoicing after despatch introduces both delay and mismatch. Trigger it from the despatch document.

Credit checked after acceptance

Checking credit once goods are allocated or shipped means the decision has already been made.

Disputes with no root-cause tracking

If dispute reasons are not categorised, the same causes recur indefinitely.

Measuring DSO alone

It is a lagging summary. Invoice accuracy rate and time from despatch to invoice explain it.

What to measure

Numbers worth tracking

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.
FAQ

Questions we are asked about this

It depends entirely on your payment terms and sector, so compare against your own terms rather than a benchmark. The useful measure is the gap between agreed terms and actual collection.
At the despatch-to-invoice handover. Invoices raised late or not matching the delivery generate the disputes that then appear as a collections problem.
At the handoffs. Order entry to credit, credit to warehouse, warehouse to invoicing, invoicing to collections — each boundary is where something waits for someone. The characteristic symptom is that every individual department reports good performance while the end-to-end cycle is poor, because nobody owns the whole line. Measuring the cycle end to end, with one owner, changes more than optimising any single step.
In most businesses yes, and it is one of the highest-return configuration changes available. Invoicing at dispatch confirmation removes a delay that serves no purpose and eliminates the drift between what shipped and what was billed. The exceptions are genuine: consolidated monthly billing where customers require it, milestone billing on projects, and anything needing a customer acceptance step first. Those should be configured exceptions, not the default.
Find out what they are actually about, which usually means categorising a few months of them rather than guessing. The common causes are price differing from what was quoted, quantity differing from what was received, missing purchase order references, and documentation the customer's own process requires. All four are preventable at order entry, which is far cheaper than resolving them at collections where each one costs a conversation.
It depends so heavily on sector, customer mix and terms that cross-industry comparison is close to meaningless. The useful benchmarks are internal: DSO against your own stated terms, and the trend over time. A DSO of 45 on 30-day terms is a 15-day gap worth understanding regardless of what the industry average is, and that gap is the number to work on.
Related

Where to read next

What is ERP software?

Read more

What is period close?

Read more

Our ERP software solutions

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.