SAP SD

What You'll Find Here

The articles in this category follow SD documents on their way into revenue accounting. They explain how sales orders, deliveries, and invoices become revenue accounting items and revenue contracts in RAR, how SD pricing conditions turn into the transaction price, the standalone selling price, and cost, and how fulfillment events such as goods issue relate to transfer of control. Further articles look at sales order changes and rejections, rebates treated as variable consideration, intercompany sales, consignment, third-party drop shipments, and free goods. Each article pairs the accounting question with the SD configuration that answers it, from item categories to pricing procedures and fulfillment event types.

Key Questions We Cover

• Which sales document types and item categories are relevant for revenue accounting?

• Which SD event fulfills which performance obligation: goods issue, customer acceptance, invoice, or the passage of time?

• Which pricing conditions belong in the transaction price, and who owns the SSP data?

• How do later changes to quantities, prices, or dates flow into existing revenue contracts?

• Which settings and monitoring steps act as SOX controls over revenue completeness and cutoff?

How We Approach SD and RAR

We design the SD-to-RAR handover from the ASC 606 perspective first and let the operational configuration follow, not the other way around. Our Agentic Finance approach relies on human-governed automation: agents triage exceptions such as items stuck in raw status or unexpected bundles and propose fixes, while revenue accountants approve them. The same RAR foundation also supports lessor leasing under ASC 842 and IFRS 16 without additional software, so equipment sold through SD and equipment leased out can follow one revenue process.

Start Here

• From Sales Order to Revenue Contract: How SD Feeds SAP RAR

• SD Pricing Conditions and Their Mapping to RAR

• Deliveries and Goods Issue: Fulfillment Events and Revenue Timing