Order-to-Cash Process: The Eight Steps, Where Cash Gets Stuck, and What to Automate First

Order-to-cash is the whole path a sale takes through a business: the customer orders, you check they are good for it, you deliver, you invoice, you collect, you sort out anything they dispute, you apply the payment to the right invoice and you report on it. It shortens to O2C. Quote-to-cash is the same process starting one step earlier, at the quote, and is the term sales software uses.

O2C is wider than accounts receivable. AR owns the second half, from the invoice to the cash. O2C adds the first half, because most late payments start there: a price agreed by the salesperson and never put on the order, a delivery charge the customer was told was included, an invoice sent to someone who left in the summer.

Every O2C process has the same eight steps, whatever the ERP. The owners below are typical for a business of 20 to 250 people with one credit controller or a small AR team.

Steps 5 and 6 are where cash sits. Steps 1 to 4 decide how much of it ends up there: an invoice with the right contact, the customer's PO number and the agreed price is paid on terms; one without them waits in somebody's inbox until it is chased.

In collections and disputes. Not because customers will not pay, but because nobody knows which invoices are blocked and why. Finance people describe it in their own words:

"My AR team is 3 people and they are absolutely drowning. We spend hours of emailing customers about overdue invoices, manually matching payments that came in overnight, chasing missing PO numbers, and dealing with short-pays."

r/ERP, finance lead at a $180M distributor, 2026

"A lot of AR 'collections work' is fake work. The invoice is 'overdue,' so everyone treats it like a payment problem."

r/Accounting, 2026; the thread argues most overdue invoices are blocked by disputes, missing POs or wrong contacts

"Track follow-ups in a spreadsheet? When they promised to pay?"

r/quickbooksonline, on what to do when automatic reminders fail, 2026

"The only issue I have with Upflow is that our customers/agents often perceive my emails as a spam, seeing that my address is different: reminders@upflow.io"

Software Advice, Upflow review, September 2020

Four ways cash gets stuck, then. Chasing from an aged-debt export, so nobody knows what was said last. Disputes that block payment while the chasing carries on regardless. Promises tracked by memory, so a broken promise is noticed a month late. And reminders that upset the customer: sent from a stranger's address, or a firm third reminder on an invoice the customer has already queried.

Days sales outstanding is the number that tells you how well order-to-cash is working. It is the average number of days between invoicing and being paid:

DSO = (accounts receivable ÷ revenue for the period) × days in the period

On €30M of annual revenue, one day of DSO is €30,000,000 ÷ 365, about €82,000 of cash sitting with customers instead of in your bank. Ten days is €820,000. That is why DSO is a board number.

The Irish figure is from the EU Payment Observatory source. Medians by sector, every one sourced, are on our DSO benchmarks by industry page. To see what cutting your own DSO would release, at your cost of capital, use the DSO calculator.

Automate the collections queue and reply reading first, steps 5 and 6. Not the customer payment portal: portals help customers who already intend to pay, and the cash that is stuck belongs to customers who have a reason not to. In order:

1. A queue, not an export. Every overdue invoice gets an owner, a next action and a date, read straight from your ERP each day. Nothing lives in a spreadsheet or a personal inbox.
2. Chases drafted, a person approves. The agent drafts each chase from the ledger and the history; the credit controller approves, edits or holds it, and it goes from your own mailbox.
3. Replies read and sorted. Every reply is read and filed as paid, promise to pay, dispute, query, contact change or bounce, and each one creates the next step.
4. Disputes routed, chasing stopped. A disputed invoice goes to the account owner with the thread attached, and nobody chases it until a person closes the dispute.
5. Promises dated. A promise to pay becomes a follow-up on the promised date, and a broken promise moves the account up the queue.

The safety points matter more here than in AP, because every mistake lands with a customer. Nothing is sent without a person approving it; auto-send exists only for templates an admin switches on, one at a time. The agent never promises a discount, extended terms or a write-off. A disputed invoice is never chased. Every email, reply, promise and note is logged against the invoice and the customer. Your ERP stays read-only, and escalation runs on rules you set to named people. The full list is on the accounts receivable automation page.

Every ERP can send a reminder. None of them runs a collections queue. What each does natively, read on the vendor's own help pages on 7 November 2026:

Dynamics 365 Business Central. Reminder terms with levels that set when each reminder is issued, what fee to charge and whether to add interest, with a grace period source, and a Reminders Automation page that creates, issues and sends them on a cadence source. What it leaves to people: reading the replies, pausing a disputed invoice, tracking promises and deciding who to call. More on AR automation on Business Central.

Sage 50 and Sage 200. Sage 50 Accounts Professional (v32.1 and above) has Automated Payment Reminders in Sage Copilot's debt management, sending invoices and statements on criteria you set source. Sage 200 has customer statements, aged debtors reports under Credit Control and Invoice Payments, which puts a Pay Now button on the emailed invoice source. What it leaves to people: replies, disputes and promises.

NetSuite. The Dunning Letters SuiteApp runs dunning evaluations on a schedule at customer, invoice or invoice-group level and emails or prints the letters; you buy it through your NetSuite account manager source. Oracle notes it cannot detect bounced emails source. What it leaves to people: everything after the letter is sent.

Xero. Invoice reminders for overdue invoices and for invoices coming due, with editable wording source. What it leaves to people: anything that depends on what the customer said back.

QuickBooks Online. Automatic invoice reminders scheduled up to 90 days before or after the due date, with a personalised message source. What it leaves to people: the same as Xero. If a reminder tool is enough for you, the AR automation software comparison covers the ones that sit on top of each ERP.

On a €30M rental group's ledger we found a €1,000 dispute holding up a €100,000 invoice. The other €99,000 was not in question, but nothing was paid until the €1,000 was settled. The same shape is in our public AR demo, on fictional data for Shannon Plant Hire, so you can open it and look:

1. Invoice. Kinsale Civil Engineering is invoiced €96,400 for a month's hire: three 20-tonne excavators, a dumper, 84 operator hours, and €1,150 for delivery and collection by low loader.
2. Chase. Once it is overdue, the queue drafts each reminder on the cadence and Niamh, the credit controller, approves it before it goes.
3. Reply read. The customer replies: "We are not paying a delivery charge we were told was included. The rest is fine." The reply is matched to the invoice by the email thread and read as a dispute.
4. Chasing paused, dispute routed. Chasing stops on that invoice. The dispute goes to Pádraig, the account manager for Munster, with the thread attached: reason delivery, €1,150 disputed of €96,400.
5. Settled. Pádraig checks what was quoted, and either a credit note for the €1,150 is raised or the quote is sent back. Once he closes the dispute, the chase resumes on what is left, and the €95,250 nobody argued about is asked for at once.
6. Logged. Every email, the reply, the dispute and the decision sit against the invoice and the customer, for whoever picks up the account next.

Without the queue, the third reminder goes out on a €96,400 invoice the customer has already said it will pay, less €1,150. That is how a reminder upsets a good customer, and how €95,250 sits for another month.

The financial controller should own it end to end, with the credit controller running steps 5 to 7 day to day. Sales owns the order and the price, operations owns proof of delivery, and account managers own disputes on their accounts. If nobody owns the whole thing, credit control chases what sales agreed and operations never wrote down.

Four numbers tell the owner whether it is working: DSO month on month, the share of overdue balance with a live next action, promises kept as a share of promises due, and disputes open by age and owner. If DSO does not move, look at steps 1 to 4 before blaming the chasing.