SAP order-to-cash process map

Where this fits

Use this map when a customer demand exists but the expected delivery, goods issue, invoice, accounting entry, or clearing result does not. The fastest starting point is the last correct business document—not the team that first received the ticket.

Process and evidence flow

1. DemandSales orderCustomer, material, quantity, requested date, partners, and commercial terms are valid.
2. CommitConfirmed scheduleAvailability, credit, pricing, incompletion, and delivery controls permit execution.
3. FulfilDelivery and goods issuePicking and shipping evidence exists, and goods issue records the inventory event.
4. BillBilling and accountingThe billable reference produces the intended invoice and financial posting.
5. SettleReceivable and clearingPayment, deduction, dispute, or clearing evidence resolves the open customer item.

Checkpoint-to-evidence map

Transition	Evidence that should exist	Typical reason it stops	Next route
Demand → commitment	Complete sales order item, confirmed quantity/date, pricing and credit status.	Incompletion, master data, pricing, credit, availability, or manual block.	Sales order block diagnosis
Commitment → fulfilment	Delivery-due schedule line and outbound delivery with executable status.	Delivery block, shipping-point or route data, due-date selection, stock, warehouse, or interface issue.	Delivery processing diagnostics
Fulfilment → billing	Goods issue or another valid billable reference, billing status, and complete billing data.	Billing block, copy control, split criteria, incomplete reference, or posting error.	Billing block analysis
Billing → accounting	Billing document plus the expected accounting transfer and customer open item.	Account determination, tax, posting period, partner, or interface failure.	Invoice split analysis
Receivable → settlement	Payment, clearing document, deduction, dispute, or dunning status.	Reference mismatch, underpayment, bank allocation, dispute, or payment-processing issue.	Payment and dunning diagnostics

How to trace a stopped O2C process

1. Capture the customer, sales document and item, material, requested date, expected outcome, and business impact.
2. Open the sales document flow and inspect item-level status. SAP document flow lists existing preceding and subsequent documents; absence of a document is different from an existing document in error.
3. Name the failed transition: order-to-delivery, delivery-to-goods-issue, reference-to-billing, billing-to-accounting, or receivable-to-clearing.
4. Check the control that owns that transition. Separate master data, configuration, application status, integration, timing, and approval before proposing a fix.
5. Confirm the next business proof after correction. A green technical status is not enough if the delivery, invoice, accounting entry, or clearing result is still absent.

Evidence to capture before routing

• Sales document and item, document type, customer, material, plant, requested and confirmed dates.
• Current header and item statuses, active block or incompletion reason, and document-flow screenshot or export.
• Last successful document, missing next document, exact error text, and time of the last processing attempt.
• Expected business outcome and owning team for the failed control.

Boundaries and non-goals

This is a standard diagnostic map, not a claim that every SAP sales process follows one document chain. Returns, third-party processing, intercompany sales, services, billing plans, EWM, transportation, tax engines, and external commerce platforms introduce additional documents and controls. Preserve the same method: identify the last correct evidence and the missing transition.

Official references

• SAP: displaying a sales document flow
• SAP: outbound delivery creation
• SAP: sales billing
• SAP: order-to-cash performance checkpoints