SAP SD Order-to-Cash Process Explained With an Example
The SAP SD order-to-cash process connects a customer’s order with delivery, invoicing and payment. Understanding this process helps you see how sales, warehouse and finance teams work together.
This guide follows a straightforward sale of physical goods from available stock. Other scenarios, such as services, returns and third-party sales, can follow different steps.
A Practical Order-to-Cash Example
Imagine a distributor selling 10 office chairs to a customer at ₹5,000 each.
The basic order value is ₹50,000 before applicable taxes, discounts or additional charges. The customer wants all 10 chairs delivered to one location.
The business must record the order, confirm what it can supply, prepare the shipment, issue an invoice and record the customer’s payment.
1. Customer Enquiry and Quotation
The customer may first ask about price, availability and delivery dates.
The business can record an enquiry and prepare a quotation describing its offer. A quotation may include products, quantities, prices and a validity period.
These documents are optional in many sales scenarios. A sales order can also be created without a preceding enquiry or quotation.
In our example, the distributor offers 10 chairs at the agreed price, and the customer accepts.
2. Create the Sales Order
The sales order records the customer’s request and the commercial details needed to process it.
Typical information includes:
- Customer and delivery address
- Products and quantities
- Requested delivery date
- Prices, discounts and applicable taxes
- Payment terms
- Delivering plant
For our example, the order contains 10 chairs. The system can perform checks and determine information based on the master data, configuration and process being used.
A requested delivery date is not automatically a promise that the business can meet it. Availability and scheduling must also be considered.
3. Create the Outbound Delivery
The outbound delivery supports the preparation and execution of the shipment.
It contains information needed by the shipping team, such as the goods to deliver, quantities and delivery destination.
In our example, the business creates an outbound delivery for the 10 chairs that are ready to ship.
A sales order does not always result in exactly one delivery. Partial deliveries or different shipping requirements can create multiple deliveries.
4. Pick and Pack the Goods
Picking means taking the required goods from their storage location. Packing means preparing them for transport.
The warehouse team picks the 10 chairs and packs them according to the business’s shipping requirements.
The exact activities depend on the warehouse setup. Some businesses use additional warehouse management processes and documents.
Before continuing, users should check that the relevant quantities and processing statuses are correct.
5. Post Goods Issue
Posting goods issue records the goods leaving the business.
For a typical sale of valuated stock, this step reduces inventory and creates relevant accounting postings, including the inventory and cost-of-goods-sold effects.
Goods issue is different from billing. It records the movement of goods; it does not create the customer’s invoice.
In our example, the business posts goods issue for the 10 shipped chairs.
6. Create the Billing Document
The business now creates the customer’s invoice.
For this delivery-related billing example, the billing document refers to the delivery. Other scenarios may use order-related billing.
The invoice includes the relevant quantities, prices and charges. When successfully transferred to financial accounting, it creates the corresponding financial posting, including the customer receivable.
The invoice amount is not necessarily identical to our ₹50,000 basic order value because taxes, discounts and other applicable charges must be considered.
7. Receive and Clear the Payment
The customer pays according to the agreed payment terms.
The finance team records the incoming payment and clears the appropriate customer open item. Payment differences or partial payments may require further processing.
This financial accounting activity completes the payment part of the wider order-to-cash cycle.
Creating an invoice alone does not mean that the customer has paid.
Why Document Flow Is Important
Document flow helps users follow the relationship between sales documents and their subsequent documents.
For example, you can investigate whether an order has a delivery, whether goods issue has been posted and whether billing has taken place.
When a process stops, identify the affected document and read the relevant status or error message before changing anything.
Useful questions include:
- Is the order complete?
- Is there a delivery block?
- Are the required quantities available and confirmed?
- Has the delivery been processed?
- Is the document relevant and ready for billing?
- Has the billing document transferred successfully to accounting?
How to Practise This Process
Use a training system and follow one complete example. Record each document number and explain the purpose of every step.
Then practise a variation, such as delivering only part of the order. Compare the quantities and statuses with your original example.
This builds a stronger understanding than memorising transaction codes without knowing the business purpose.
Build Your SAP SD Process Knowledge
The order-to-cash process is a useful foundation for learning SAP SD. Start with the relationship between the sales order, delivery, goods issue, billing and payment.
SAP Experts Academy offers SAP SD online training and interview preparation support. Contact us to discuss practical learning options for your goals.
