Order to cash: the process, where it leaks, and what automation changes

Order to cash is the chain of steps that turns a customer's order into cash in the bank: order entry, a credit check, fulfillment, the invoice, collections, cash application, and the reporting that closes the loop. Each step is simple on its own, and the order to cash process still leaks, because every hand-off between sales, the warehouse and finance is a chance for a price, a quantity or a reference number to go wrong. The leak shows up as late cash. APQC's benchmarks put days sales outstanding at 30 days or less for top performers, 38 at the median and 46 or more for the bottom quartile, and Atradius, in its 2025 Payment Practices Barometer for North America, found that forty-three percent of credit-based B2B sales in the US were overdue. A company at the bottom of APQC's range waits more than two weeks longer for its cash than one at the top, on the same sales.

The order to cash process, step by step

The Hackett Group divides the work into credit management, order management, customer billing, cash application, collections, and dispute and deduction management. Followed in the order a transaction moves through them, the process has seven steps, and each one inherits whatever the step before it got wrong.

1. Order entry: the order arrives by EDI, a customer portal, email, a PDF or a phone call, and someone enters it into the ERP.
2. Credit check: the order is checked against the customer's credit limit and payment history, and held when it breaches either.
3. Fulfillment: the warehouse picks, packs and ships, or the service is delivered, and the shipment is confirmed.
4. Invoicing: the invoice is built from the order and the shipment, with the agreed prices and terms and the customer's own reference numbers.
5. Collections: overdue invoices are chased, disputes are logged and worked, and promises to pay are recorded.
6. Cash application: each payment is matched to the invoices it settles, using remittance details that often arrive separately from the money.
7. Reporting: the receivables aging, days sales outstanding and the cash forecast are updated, and the ledger is reconciled.

The sales order anchors the chain the way the purchase order anchors the buying side. It fixes what was sold, at what price, on what terms, and it is what the shipment and the invoice are built from. When the order is right, the rest of the chain is mostly mechanical. When it is wrong, the error travels: a wrong price becomes a short payment, a missing customer reference becomes an invoice the customer's accounts payable team can't match, and both become work for collections a month later.

One transaction seen from two sides

Order to cash and procure to pay are the same transaction seen from opposite ends. The customer's purchase order is the seller's sales order, the seller's invoice is the customer's supplier invoice, and the payment one company releases is the payment the other has to apply. We walked through the buying side in procure to pay, step by step, and the symmetry explains a good deal of what goes wrong on the selling side. A customer's accounts payable team runs a match before it pays, and an invoice that fails that match waits in the customer's exception queue. The seller sees the wait as a late payment. The cause is often an invoice that didn't carry the customer's order number, or billed a price the customer's system doesn't recognize.

So part of the collections workload is created upstream, on the seller's own side, at order entry and invoicing. Chasing the customer harder does nothing for an invoice the customer can't match.

Where revenue leaks before the invoice goes out

Order entry is the first leak. In a distributor or a manufacturer, orders arrive in every format the customers use, and a customer service team keys them into the ERP line by line, looking up item numbers, checking prices against contracts and noting special terms. Each line is a chance for a transcription error, and pricing is where the errors cost the most: a contract price not applied, a promotion applied after it ended, a quantity break missed. We walked a distributor's order-to-cash at the line level in process redesign inside a wholesale distributor, where order entry and pricing exceptions carry most of the labor.

Invoicing is the second leak. An invoice built from a wrong order is wrong, and an invoice built from a right order can still fail the customer's requirements: a missing purchase order number, a missing proof of delivery, a format the customer's portal rejects. APQC's data shows what that friction costs: what organizations spend to invoice customers ranges from 19 cents per $1,000 of revenue to 62 cents, and APQC attributes the gap to process friction such as mismatched data. Correcting a wrong invoice takes longer still, since the fastest quartile of organizations resolves billing adjustments in seven days or fewer while the slowest take three weeks or longer. These errors rarely appear in the seller's own reports as errors, and they surface a month later as days sales outstanding.

Where cash waits after the invoice goes out

Once the invoice is out, cash waits in three places. The first is the customer's approval process, which is where an invoice with a discrepancy stalls. The second is collections, where the question is which overdue invoices to work first, and where working the aging report from the top is the default even though the oldest invoice is not always the one a call will move. The Hackett Group's 2026 Working Capital Survey put the working capital gap among North America's largest companies at a record $1.94 trillion, with receivables deteriorating, and CFO.com's report on the same survey put the worsening in days sales outstanding at 2.1 days in 2025. We set out a redesigned collections workflow in working a receivables ledger down.

The third place is cash application, the step after the money arrives. Paper is shrinking but hasn't gone: the Federal Reserve Bank of Kansas City found that checks' share of the number of B2B payments fell from 32 percent in 2015 to 13 percent in 2024. Electronic payments carry their own problem. A payment often lands in the bank without the information needed to apply it: the remittance comes separately by email or through a portal, one payment covers many invoices, and short payments and deductions arrive without explanation. Until the payment is applied, the invoice still shows as open and the customer can be chased for money it has already paid. The Hackett Group's 2025 Digital World Class Matrix on cash application software found a median auto-match rate of 70% among end users, with a third exceeding 80%. The remainder is the manual work we describe in rebuilding cash application.

What order to cash automation changes

Order to cash automation has mostly meant tools for single steps: EDI for the customers who send structured orders, a collections tool that sends dunning emails, cash application software that matches the clean remittances. Each helps on its own step, and none of them sees the chain, so the errors that travel between steps keep traveling.

An agent working across the chain starts at order entry. It reads the order in whatever form it arrives, maps the customer's item descriptions to item numbers, checks prices against the contract and flags lines that disagree before the order is entered. Before an invoice goes out, it checks the invoice against the customer's known requirements: the reference number, the delivery proof, the format. In collections it ranks overdue invoices by amount, age and the customer's payment pattern, drafts the follow-up, and pulls the order and shipment records for any dispute so the collector starts with the evidence. In cash application it reads remittances from email and portals and proposes matches for the payments the rules can't clear, with the reasoning attached.

People keep the decisions that carry risk or a customer relationship: extending credit, settling a dispute, granting a deduction, writing off a balance. The agent's job is to make sure those decisions reach a person early, with the evidence in hand, rather than surfacing at month end as an aging problem.

A reasonable counter, answered

A reasonable counter is that late payment is the customer's doing: customers pay when their own cash allows, large customers dictate terms, and no amount of process work on the seller's side changes either. The evidence largely agrees. In Atradius's 2026 survey of North American suppliers, most attributed delayed payments primarily to their customers' liquidity rather than to disputes or administrative errors, and a seller can't fix a customer's cash flow. Disputes still count at the margin. In Atradius's 2025 survey of US suppliers, invoice disputes were the fourth most-cited reason customers paid late, named by 23 percent, though the 2026 edition's top four no longer includes them and Atradius warns that the two editions can't be compared. A disputed invoice is late for reasons that often start on the seller's side. An invoice that carries the right reference number, the right price and the proof of delivery clears the customer's match on the first pass; one that doesn't waits in the customer's exception queue until someone there asks about it. The work described above removes that second kind of delay, which is the part of days sales outstanding the seller's own process creates, and it leaves the credit decisions about customers who can't pay with the people who should make them.