Order-to-cash process map

The O2C cycle as a swimlane map, from the customer's order through credit control, delivery, invoicing and cash application to collections, across the customer, sales, credit control, the warehouse, accounts receivable and the finance controller. Most of its twenty-six steps sit after the invoice, because that is where the cash actually gets stuck.

Open this map in the editor

Opens a copy in the editor and saves it in this browser. No account, nothing sent anywhere.

What is in this map

26 steps across 6 swimlanes and 5 phases, with 9 decision points.

Swimlanes (who does the work)
Customer, Sales and customer service, Credit control, Warehouse and logistics, AR and cash application and Finance controller
Phases (left to right)
Order capture, Credit and confirmation, Fulfil and deliver, Invoice and cash and Collections and closure

Why map this process

Order-to-cash is usually described as a sales process with an invoice at the end. Mapped honestly it is the opposite: the order and the delivery take a handful of steps, and everything after the invoice (short payments, disputed deductions, dunning, referral to collections, write-off) takes the rest. Teams trying to reduce days sales outstanding without a map tend to work on the visible front half, when the days are lost in the back half.

The credit hold is the other reason to draw it. An order on hold sits in the credit control lane, not with sales, and it can leave three ways: released, released after prepayment, or refused. When those three exits are on one page, sales and credit stop arguing about whose delay it is.

Every step in the map

This is the spreadsheet behind the diagram. The numbers in “Goes to” are row numbers, which is exactly what the editor’s “Line to” column holds — so you can read the flow here and retype any part of it.

Every step in the Order-to-cash process process map, in the order the editor numbers them.
#StepShapeSwimlanePhaseGoes to
1 Customer order received Start Customer Order capture 2
2 Order and *master data* complete? Decision Sales and customer service Order capture 4 (Complete), 3 (Missing)
3 Supply the missing order details Process Customer Order capture 2 (Corrected)
4 Credit exposure **within limit?** Decision Credit control Credit and confirmation 8 (Within limit), 5 (Over limit)
5 Place the order on credit hold Process Credit control Credit and confirmation 6
6 Credit hold released? Decision Credit control Credit and confirmation 8 (Released), 7 (Prepay first), 9 (Refused)
7 Prepay or provide extra security Process Customer Credit and confirmation 6 (Re-check)
8 Confirm the order and release it Process Sales and customer service Credit and confirmation 10
9 Order cancelled on credit refusal Reject Credit control Credit and confirmation End
10 Pick, pack and dispatch the goods Subprocess Warehouse and logistics Fulfil and deliver 11
11 **Proof of delivery** received? Decision Warehouse and logistics Fulfil and deliver 13 (Received), 12 (Missing)
12 Chase the carrier for proof Process Warehouse and logistics Fulfil and deliver 11 (Obtained)
13 Create and issue the **invoice** Document AR and cash application Invoice and cash 14
14 **Paid in full** by the due date? Decision AR and cash application Invoice and cash 15 (Paid in full), 17 (Short-paid), 21 (Unpaid)
15 Apply the cash and clear the invoice Process AR and cash application Invoice and cash 16
16 Invoice cleared and order closed Success AR and cash application Collections and closure End
17 Code the deduction and open a dispute Process AR and cash application Invoice and cash 18
18 Investigate against the order and POD Process Sales and customer service Invoice and cash 19
19 Deduction valid? Decision Sales and customer service Invoice and cash 20 (Valid), 21 (Invalid)
20 Raise a **credit note** and clear the line Compensation AR and cash application Invoice and cash 16
21 Work the *dunning ladder* Process Credit control Collections and closure 22
22 Customer response? Decision Credit control Collections and closure 15 (Pays), 18 (Disputes), 23 (No response)
23 Refer to collections or legal Process Credit control Collections and closure 24
24 Balance recovered? Decision Credit control Collections and closure 15 (Recovered), 25 (Irrecoverable)
25 **Approve** the write-off? Decision Finance controller Collections and closure 26 (Approved), 23 (Keep pursuing)
26 Balance written off Reject Finance controller Collections and closure End

The decision points

Every branch in the map, with the label on each outgoing line. These are the questions the process has to be able to answer.

  • 2. Order and *master data* complete?

    Owned by Sales and customer service · Order capture

    • Complete → step 4
    • Missing → step 3
  • 4. Credit exposure **within limit?**

    Owned by Credit control · Credit and confirmation

    • Within limit → step 8
    • Over limit → step 5
  • 6. Credit hold released?

    Owned by Credit control · Credit and confirmation

    • Released → step 8
    • Prepay first → step 7
    • Refused → step 9
  • 11. **Proof of delivery** received?

    Owned by Warehouse and logistics · Fulfil and deliver

    • Received → step 13
    • Missing → step 12
  • 14. **Paid in full** by the due date?

    Owned by AR and cash application · Invoice and cash

    • Paid in full → step 15
    • Short-paid → step 17
    • Unpaid → step 21
  • 19. Deduction valid?

    Owned by Sales and customer service · Invoice and cash

    • Valid → step 20
    • Invalid → step 21
  • 22. Customer response?

    Owned by Credit control · Collections and closure

    • Pays → step 15
    • Disputes → step 18
    • No response → step 23
  • 24. Balance recovered?

    Owned by Credit control · Collections and closure

    • Recovered → step 15
    • Irrecoverable → step 25
  • 25. **Approve** the write-off?

    Owned by Finance controller · Collections and closure

    • Approved → step 26
    • Keep pursuing → step 23

Notes on specific steps

These notes travel with the map. In the editor they live in the Notes column and appear when you open a box.

2. Order and *master data* complete?
Most ERP order failures are master-data failures rather than judgement calls: a ship-to that no longer exists, a pricing condition that expired last quarter, a missing tax classification, incoterms nobody filled in. Decide which fields block the order and which merely warn, because an order that passes here with a blank field stops later at delivery or at billing, where it costs far more to unpick and the customer is already waiting.
4. Credit exposure **within limit?**
Exposure is not the posted ledger balance. It is open orders, goods delivered but not yet invoiced, invoices outstanding, and the one most policies forget: amounts currently in dispute, which are still money you have not got. Write down which of those your ERP genuinely includes in the check, because the answer is usually fewer than you think, and a limit calculated on posted invoices alone will wave a large order straight through.
6. Credit hold released?
This loop decides whether credit control is a control or a bottleneck. Name who may release a hold and up to what value, set a response time in hours rather than days, and state what customer service is allowed to tell the customer while the order sits. Record a reason for every release, because a hold released with no recorded reason is indistinguishable from a hold that was never applied at all.
10. Pick, pack and dispatch the goods
One box here stands for an entire process. Stock allocation, backorders and partial shipments belong to order fulfilment; the pick route, short-pick branches, pack verification and the weight check belong to picking and packing below it. Keep it collapsed unless the problem you are solving is inside the warehouse. It appears at all because dispatch is what produces the delivery evidence the next decision bills against, and because a part shipment here becomes a part invoice later.
11. **Proof of delivery** received?
Billing is blocked here deliberately. An invoice raised before delivery is evidenced is the commonest cause of a deduction three months later, because the customer disputes receipt and nobody can produce the signed note. Decide how long you will chase before the order is treated as a delivery failure rather than a paperwork one, and where proof of delivery is filed so that AR can find it without asking the carrier all over again.
13. Create and issue the **invoice**
The invoice is built from the delivery, not from the order, which is why a part-shipped order produces a part invoice and why quantity changes made after picking have to reach billing. Check the invoice address, the customer's purchase order number and any portal reference before it goes: an invoice rejected by a customer's accounts payable portal for a missing PO number never enters their approval queue, and the payment clock never starts.
17. Code the deduction and open a dispute
A short payment is not a late payment, and treating it as one starts a dunning ladder against a customer who believes they have already paid. Code the reason at the moment the remittance is applied (price, quantity, shortage, damage, promotion, freight, returns) because the reason code is the only thing that later tells you whether the problem sits in pricing, in the warehouse, or in a rebate agreement nobody in finance has seen.
25. **Approve** the write-off?
Keep the person chasing the debt separate from the person approving the write-off, and set the authority level against the value of the balance rather than its age. Record the amount, the reason and the recovery steps already taken, because this is the entry an auditor samples. If you accounted for VAT or sales tax on the invoice, check the bad-debt relief conditions in your jurisdiction before clearing the balance.

Making it yours

Start with the payment decision after the invoice: 'Paid in full by the due date?' has three branches (paid, short-paid, unpaid), and each one leads into its own sub-process. In the spreadsheet these are just rows with a Line to pointing at the right step, so you can delete the deduction handling if your customers never short-pay, or add a branch for partial payments, without redrawing anything. If your ERP is SAP, Oracle, Dynamics 365 or NetSuite, keep this vendor-neutral map for the business conversation and use the system-specific version for the people configuring it.

What to watch out for

  • Do not put the credit check in the sales lane. Sales can see the result, but the hold is released by credit control, and moving the step hides who the order is waiting for.
  • Proof of delivery is a real step, not an assumption. Invoicing before you can prove delivery is the most common source of the deductions that appear three boxes later.
  • Write-off needs an approver and an amount. A map that ends with 'write off the balance' and no approval step describes a process where anyone can make bad debt disappear.

Frequently asked questions

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

Quote-to-cash starts earlier, with pricing, quoting and contract negotiation before the order exists. Order-to-cash starts when the customer order arrives. If your sales cycle involves configured quotes or contract approval, map that as a separate quote process that hands an accepted order to this one.

Where does cash application belong: AR or treasury?

In the lane of whoever matches incoming payments to invoices, which in most companies is accounts receivable. Treasury owns the bank account and the cash position, not the matching. If the two are the same team in your company, merge the lanes rather than inventing a handover that does not happen.

Is there a version of this map for SAP, Oracle or Dynamics 365?

Yes. QueryChart publishes order-to-cash process flows with the transactions and screens of SAP S/4HANA, Oracle Fusion, Dynamics 365 and NetSuite. This map is deliberately system-neutral, which makes it the better starting point for a workshop with the business before anyone talks about configuration.

Open the map and start editing

The editor loads this chart with the spreadsheet underneath it. Change a cell and the diagram redraws — no drawing, no signup.