The Order-to-Cash Process: All 8 Stages, Where Cash Gets Stuck, and How to Automate It

Finance teams tend to think in functions: credit, billing, collections, cash application. Customers experience something entirely different — a single continuous flow from placing an order to paying for it.

Order to cash is the name for that flow. Treating it as one process rather than four departmental activities is what surfaces the real causes of slow cash conversion, because in most businesses the delay is not inside any stage. It is in the gaps: the two days an order waits for credit release, the four days between shipment and invoice, the week an invoice sits in a customer portal nobody monitors.

This guide walks through all eight stages of the O2C cycle, identifies where cash predictably gets stuck at each one, covers the metrics that tell you which stage is failing, and explains what automation realistically changes.

The 8 Stages of the Order-to-Cash Cycle

Stage 1: Customer Onboarding and Credit Assessment

Before a customer can order on credit, they must be onboarded and assessed: legal entity verified, credit application completed, references checked, a credit limit and payment terms set, and their invoicing requirements captured.

Where it breaks: Credit assessment is treated as a one-time formality, so limits are set at onboarding and never reviewed as the customer’s risk profile changes. Equally damaging, the customer’s invoicing requirements — which portal they use, whether a PO is mandatory, what e-invoicing format they need — are rarely captured properly here, which guarantees problems at Stage 5. Getting B2B credit management right at this stage prevents losses that are otherwise only discovered eleven months later.

Stage 2: Order Capture and Entry

The customer’s order arrives — by email, EDI, portal, phone, or increasingly WhatsApp — and is entered into the ERP as a sales order.

Where it breaks: Manual re-keying from PDFs and emails introduces errors in quantities, pricing, and product codes. A mismatch between the customer’s part number and your SKU produces an order that ships incorrectly, which becomes a disputed invoice at Stage 6. Errors introduced here are cheap to fix now and expensive to fix later — a wrong price on an order becomes a credit note, a re-issued invoice, and thirty extra days of DSO.

Stage 3: Order Fulfilment and Delivery

Goods are picked, shipped, and delivered, or services are performed and the delivery evidenced.

Where it breaks: The link between proof of delivery and the invoice. Many B2B customers will not pay without a signed POD, timesheet, or delivery note attached, and if that document lives in a separate operational system nobody connects to billing, the invoice is challenged and payment stalls. Partial shipments are a second common failure: invoicing the full order when only part shipped guarantees a short payment.

Stage 4: Invoicing

The invoice is generated from the order and fulfilment data and issued to the customer.

Where it breaks: Timing and accuracy. Batch-invoicing weekly instead of daily adds an average of three days of DSO for no reason at all. Accuracy matters even more — an invoice with a missing PO number, wrong tax treatment, or incorrect pricing will be rejected, and the clock restarts entirely. In markets with mandated e-invoicing, non-compliant format is an outright rejection. Which billing model you run also shapes what can go wrong here — see B2B billing models.

Stage 5: Invoice Delivery

The invoice reaches the person or system that can approve it — which is emphatically not the same as sending it.

Where it breaks: This is the single most underestimated stage in O2C. Enterprise customers require submission through their own portals — Ariba, Coupa, Tungsten, or bespoke systems — each with its own login, format, and business rules. AR teams log in manually, one portal at a time. Invoices are rejected for reasons discovered days later, if at all. The resulting invoice delivery gap commonly adds five or more days of DSO, and it is invisible in most reporting because the ERP shows the invoice as issued.

Stage 6: Collections and Dispute Management

Payment is followed up, and anything blocking payment is resolved.

Where it breaks: Follow-up that is inconsistent, starts too late, and never escalates beyond email. Equally, disputes and deductions handled inside the collections queue rather than as a distinct workflow — reminders keep going to a customer who is waiting on a credit note. A structured dunning process with defined tiers, owners, and a dispute off-ramp is what separates teams that collect from teams that chase.

Stage 7: Payment and Cash Application

Payment arrives and is matched to the correct invoices.

Where it breaks: Remittance data arriving separately from the payment, bulk payments covering dozens of invoices, short payments with unexplained deductions, and currency or bank fee variances. Unmatched cash means invoices show as open when the money is already in the bank — which triggers reminders to customers who have paid, distorts the aging report, and corrupts the bad debt provision built on it. Automated cash application and reconciliation removes this failure mode.

Stage 8: Reporting and Continuous Improvement

Performance is measured and fed back into the process.

Where it breaks: Reporting that describes outcomes without diagnosing causes. “DSO is 58 days” is not actionable. “Eleven of those days occur between shipment and invoice delivery” is. Most O2C reporting is a monthly AR aging report circulated as a spreadsheet, with no view of cycle time by stage.

Where the Days Actually Go

Mapping elapsed time by stage is the most useful diagnostic exercise in O2C, and the results routinely surprise people. A representative breakdown for a B2B business with Net 30 terms and a 58-day DSO:

The gap between the two columns is where DSO hides. Twelve days of the fifty-eight sit in stages that most finance leaders assume take no time at all — invoice generation lag, delivery lag, and cash application lag. None of these are collections problems, and none of them will be fixed by chasing customers harder.

The Metrics That Diagnose Each Stage

Portfolio-level metrics tell you whether O2C is healthy. Stage-level metrics tell you where it is failing.

Days Sales Outstanding (DSO) — the headline measure of how long revenue takes to convert to cash. Useful as a trend, but too aggregated to diagnose anything on its own.

Collection Effectiveness Index (CEI) — isolates collection execution from sales volume distortion. Where DSO worsens because sales grew, CEI shows whether the team actually performed. Best-in-class is above 80%.

Invoice-to-delivery lag — days between invoice generation and confirmed receipt by the customer. The most commonly missing metric in O2C and often the largest single source of avoidable delay.

First-pass invoice acceptance rate — the percentage of invoices accepted without rejection or query. Below 90% indicates a data quality problem originating at Stages 1, 2, or 4.

Dispute rate and average resolution time — volume of disputed invoices and how long they take to close. Rising dispute rates almost always trace back to order entry or fulfilment accuracy.

Cash application match rate — percentage of receipts matched automatically without manual intervention. Below 85% means the aging report and provision are both unreliable.

Bad debt as a percentage of revenue — the lagging indicator that tells you whether Stage 1 credit decisions and Stage 6 collections are working together.

Cash conversion cycle — the enterprise-level view of how long cash stays committed, covered in the cash conversion cycle guide.

Automating the Order-to-Cash Cycle

Automation delivers most where work is high-volume, rules-based, and currently manual — which in O2C means the handoffs.

Credit and onboarding. Live exposure views consolidated across entities, risk scored continuously from actual payment behaviour, automated review triggers, and rule-based credit holds with audited release.

Order capture. AI extraction from PDF and email orders directly into sales orders, with validation against pricing and product master data so mismatches are caught at entry rather than at dispute.

Invoicing and delivery. Automatic invoice generation on fulfilment rather than on a weekly batch, and automated delivery into customer portals. Browser-based agents log into portals that offer no API, submit invoices in the required format, and capture rejection reasons immediately rather than days later.

Collections. Tiered payment reminder automation triggered from aging buckets, disputes routed out to a resolution workflow, and AI voice agents extending consistent outbound contact across the entire portfolio instead of only the largest accounts.

Cash application. Automated matching of receipts to invoices including bulk payments, separately-arriving remittances, and short payments, with unmatched items queued for review rather than silently left open.

Reporting. Cycle time measured by stage rather than only at the portfolio level, so improvement effort goes where the days actually are.

The integration point matters as much as the automation. O2C spans the ERP, the CRM, fulfilment systems, banking, and customer portals. Automation that only works inside the ERP cannot address the handoffs, which is precisely where the delay lives. Teams weighing whether to build this capability internally or hand it to a provider should read AR outsourcing vs. automation. Native connections to NetSuite, SAP, Xero and QuickBooks keep the automated flow reconciled against the accounting record.

How to Improve Your Order-to-Cash Process

Step 1: Map elapsed time across all eight stages. Measured versus assumed is where the insight is.

Step 2: Measure invoice-to-delivery lag specifically. The most commonly missing metric in O2C.

Step 3: Fix data quality at order entry. Errors here become disputes months later.

Step 4: Capture invoicing requirements at onboarding. Portal, PO rules, format, AP contact.

Step 5: Separate dispute resolution from collections. Different problem, different workflow, different owner.

Step 6: Automate the handoffs, not just the stages. The seams are where the days are.

Our Verdict: The Days Are in the Handoffs, Not the Stages

The most useful thing a finance leader can do with order to cash is stop treating it as four departmental activities and measure it as one timeline. When teams do this, the result is almost always the same surprise: a large share of the elapsed days sit in transitions that everyone assumed were instantaneous — fulfilment to invoice generation, invoice generation to confirmed delivery, and payment receipt to cash applied.

This matters because it redirects effort. A company with a 58-day DSO and twelve days buried in those three handoffs will not fix it by chasing customers harder, yet collections pressure is the default response because collections is the stage that is visible and measured. The handoffs belong to no single function, which is exactly why they persist.

Process benchmarking from APQC and working capital research from Deloitte and PwC consistently identify cross-functional handoffs rather than individual stage efficiency as the determinant of cash conversion performance, and Gartner coverage of finance technology makes the same point about integration scope: automation confined to the ERP cannot address transitions that cross system boundaries. The practical instruction is to map elapsed days across all eight stages before selecting any tooling — the exercise usually takes about a week and reliably relocates the problem.

Conclusion

The order-to-cash cycle is only as fast as its slowest handoff. Teams that optimise collections alone tend to plateau, because the days they are trying to recover were lost before the customer ever saw the invoice.

Mapping elapsed time across all eight stages usually takes a week and almost always relocates the problem. Request a demo to see how Peakflo automates the full accounts receivable side of order to cash, or model the impact first with the savings calculator.

Frequently Asked Questions

What is order to cash?

Order to cash (O2C) is the end-to-end process that begins when a customer places an order and ends when payment is collected and reconciled. It spans customer and credit onboarding, order capture, fulfilment, invoicing, invoice delivery, collections, payment and cash application, and reporting — crossing sales, operations, and finance.

What are the stages of the order-to-cash cycle?

The O2C cycle has eight stages: customer onboarding and credit assessment, order capture and entry, order fulfilment and delivery, invoicing, invoice delivery, collections and dispute management, payment and cash application, and reporting with continuous improvement.

What is the difference between order to cash and accounts receivable?

Accounts receivable is a subset of order to cash. AR covers what happens after an invoice is raised — delivery, collections, and cash application. Order to cash is broader, starting at customer onboarding and credit assessment and including order capture and fulfilment, which is why many delays attributed to AR actually originate upstream.

How do you measure order-to-cash performance?

Use portfolio metrics such as DSO, Collection Effectiveness Index, and bad debt as a percentage of revenue to assess overall health, then stage-level metrics — invoice-to-delivery lag, first-pass invoice acceptance rate, dispute resolution time, and cash application match rate — to diagnose which specific stage is underperforming.

What is the difference between order to cash and procure to pay?

Order to cash is the revenue-side process covering customer orders through to collected payment. Procure to pay (P2P) is the mirror-image expenditure process covering purchase requisitions, purchase orders, goods receipt, supplier invoices, and outbound payments. One governs money coming in, the other money going out.

Where do most order-to-cash delays occur?

Most delays occur at the handoffs between stages rather than inside them — the lag between fulfilment and invoice generation, between invoice generation and confirmed delivery into the customer’s portal, and between payment receipt and cash application. These transitions are commonly assumed to take no time but often account for ten or more days of DSO.

How does order-to-cash automation reduce DSO?

Automation compresses the stages that pure collections effort cannot reach: generating invoices on fulfilment rather than in weekly batches, delivering them into customer portals same-day, escalating collections consistently across the whole portfolio, and applying cash automatically so balances close the moment payment arrives.

What is the difference between order to cash and quote to cash?

Quote to cash begins earlier, covering configuration, pricing and quoting before an order exists, and therefore includes the sales process itself. Order to cash begins once a customer places an order. Quote to cash is the broader commercial cycle; order to cash is the fulfilment and collection cycle inside it.

Which order-to-cash stage causes the most DSO?

In most B2B businesses the largest avoidable delays sit in invoice delivery and cash application rather than in collections. Invoices generated but not yet received in the customer’s approval workflow commonly add five or more days, and unapplied cash keeps settled invoices showing as open, both of which are invisible in ERP reporting.

Who should own the order-to-cash process?

Because O2C spans sales, operations and finance, it needs a single accountable owner with visibility across all eight stages — typically a finance operations or revenue operations leader. Without one, the handoffs between functions have no owner, and those transitions are where most of the elapsed time accumulates.