SAP Concepts: Order-to-Cash: How SD Hands Off to FI (PGI, Billing, Payment Clearing)

If Procure-to-Pay is the process that runs outgoing money, Order-to-Cash is the mirror image — the process that runs incoming money. Someone buys something from you, you deliver it, you invoice them, they pay. Every business on earth runs a version of this, and every SAP installation has it coded into the rhythm of its daily operations.

This is episode five of our SAP Concepts series. We're going to walk the full O2C flow, from the first customer enquiry to the moment the bank statement clears the receivable. Along the way you'll meet the movement types that trigger financial postings, see why revenue recognition is surprisingly mechanical in SAP, and get a clearer picture of how SD and FI integrate.

The five-step shape

Every O2C cycle has roughly the same five steps, and if you can name them, you can read any SAP sales report.

1. Quotation — the customer asks for a price, and we respond.
2. Sales order — the customer commits to buy; we commit to supply.
3. Delivery and goods issue — we pick, pack, and ship the goods.
4. Billing — we create and send the customer's invoice.
5. Incoming payment — the customer pays, and we clear the receivable.

SD drives steps one through four. FI is mostly passive, receiving postings at each stage. FI takes over at step five when payment processing happens in the treasury and collections teams.

Let's walk through with the postings.

Step one: the quotation

A customer contacts the sales team wanting to buy something. A sales rep creates a quotation in SD — essentially a formal price offer, valid for some period (often thirty days), listing the items, quantities, unit prices, and delivery terms.

The quotation is a statistical document. It doesn't commit the company to anything — if the customer never responds, it just expires. No financial posting happens.

Some companies skip this step entirely for repeat business. A standing customer with pre-agreed pricing might just place a direct sales order. Quotations are most common in project-based sales, large-ticket items, and new customer relationships.

Step two: the sales order

The customer accepts the terms and wants to proceed. Either the quotation is converted into a sales order, or a new order is created directly. Either way, a sales order in SD is the legal commitment: we agree to deliver these items, at these prices, by this date.

At order creation, SAP does a few automatic checks. Stock availability — does the warehouse have the requested items? Credit check — is the customer's outstanding balance within their approved credit limit? Pricing validation — do the prices on the order match the current price list and any customer-specific agreements?

If any of those fail, the order is held for review. Otherwise, it proceeds to the next step.

Still no financial posting. Like the purchase order in P2P, the sales order is a commitment, not a transaction. The commitment is visible in sales reports (you can see backlog, order book, forecasted revenue) but hasn't yet hit FI.

Step three: delivery and goods issue

The warehouse picks and packs the order, then ships it. In SAP terms, two things happen: a delivery document is created (a shipping document with pack lists, carrier details, tracking references), and a goods issue posts the movement of stock out of the warehouse.

The goods issue uses movement type 601 (outbound delivery), and this is the first step in O2C where FI gets a posting:

Dr  Cost of Goods Sold                €400
    Cr  Inventory                          €400

Inventory goes down by the cost value of the items shipped. Cost of Goods Sold goes up by the same amount. This is the accounting recognition that the inventory we used to have is now consumed, and its cost is now an expense against the revenue we're about to recognise.

Notice what's happening to the money spine here. The Universal Journal (ACDOCA, from episode three) now has a row showing CoGS hit for this specific customer, this specific product, this specific plant. Every dimension is captured. When the CFO wants to know margin by customer or by product line later, this row is where the answer comes from.

Step four: billing (the invoice)

Once the delivery is posted, the system is ready to generate the customer's invoice. In SAP terminology this is the billing document, and it references the sales order and the delivery.

Billing creates two important financial effects:

Dr  Accounts Receivable — Customer X  €500
    Cr  Revenue                            €500

Accounts Receivable goes up — we now have a €500 claim against the customer. Revenue is recognised on the P&L for the same amount.

This is where revenue recognition happens, and it's worth understanding the nuance. In SAP, revenue recognition is largely mechanical — tied to the billing document, which is tied to the delivery. You ship the goods, you bill the customer, revenue is recognised on that date. That's the default model, which covers the vast majority of sales transactions.

For more complex scenarios — multi-year contracts, subscription revenue, milestone-based project billing — SAP has additional functionality (SAP Revenue Accounting and Reporting, or RAR, handles these). But for standard product sales, the simple ship-and-bill flow captures revenue correctly at the moment of billing.

Also note: the billing document creates a customer invoice, which gets sent to the customer. That's a physical (or electronic) document that becomes the customer's source document for their own AP process. One company's invoice is another company's invoice-to-pay.

Step five: incoming payment

Finally, the customer pays. The payment arrives — bank transfer, credit card, cheque, depending on the terms. Finance (or increasingly, automated bank integrations) matches the incoming payment to the correct open receivable and posts:

Dr  Bank                              €500
    Cr  Accounts Receivable — Customer X   €500

Cash goes up, AR goes down. The receivable is cleared. The cycle is complete.

If you trace the whole flow, you can see every line of the P&L and balance sheet impact. Inventory dropped by cost. CoGS went up by cost. Revenue went up by selling price. AR went up by selling price. Cash went up by payment amount (= selling price), and AR cleared back to zero. Net effect on the balance sheet: inventory down, cash up, with a P&L margin equal to selling price minus cost.

That's the O2C loop. Starting with goods in the warehouse and ending with cash in the bank, with a clean margin line through the middle.

What can go wrong, and why it matters

Most O2C issues happen at the edges. The common ones:

• Credit holds — customer's order exceeds their approved limit, and the order is blocked until someone in credit management releases it. Usually a negotiation with the customer or an override by a senior manager.
• Picking shortfalls — the warehouse doesn't have enough stock to fulfil the order. The delivery is partial, and the billing has to reflect only what shipped.
• Pricing disputes — the customer thinks the price should be different. Either a master-data issue (stale price list) or a genuine disagreement that needs renegotiation.
• Unapplied cash — payment arrives but can't be matched to a specific invoice (often because the customer didn't include the invoice reference). Finance has to investigate and apply manually.
• Bad debt — customer doesn't pay. Eventually AR gets written off to bad debt expense.

Each of these corresponds to a specific SAP transaction and a set of workflows. Sales consultants spend a lot of time helping customers configure these edge cases to match their business practice.

Why this matters

O2C is how revenue enters the business. If it breaks, everything else breaks with it — revenue isn't recognised on time, AR balloons with unclear balances, cash flow forecasts become fictional, and the CFO stops trusting the data.

It's also one of the most-audited processes in any enterprise. External auditors almost always look at the O2C cycle during financial audits, because it's where revenue recognition happens, and revenue recognition is one of the highest-risk areas for misstatement.

And for SAP consultants, O2C is a huge specialisation on its own. An SD consultant who understands the revenue-recognition edge cases, the pricing conditions, the credit management configuration, and the integration with CO for margin analysis — that's a career-defining skillset.

What's next

That's Order-to-Cash. Quotation, sales order, delivery and goods issue (movement type 601), billing with AR and revenue, and finally incoming payment. Five SD steps, three FI postings, all flowing into the Universal Journal.

Episode six covers Plan-to-Produce — the third and final big process. If you're working in a manufacturing company, this is where most of the complexity lives. We'll walk through MRP, production orders, goods issue to production, confirmation, and finally the variance-to-standard posting at settlement.

See you there.