Billing Fundamentals: Purpose, Document Types, and Business Role
Introduces why billing exists in the SD process, the main billing document types, and how billing connects sales and delivery activities to finance.
Explanation
Billing is the final step in the classic Order-to-Cash chain where a company converts the value of goods delivered or services rendered into a financial claim against the customer. Without billing, a sales order or delivery has no financial consequence — no receivable is created, no revenue is recognized, and no VAT/tax obligation is triggered. This makes billing one of the most scrutinized areas in SD because errors here directly affect the general ledger, accounts receivable, and statutory tax reporting. In SAP SD, billing documents are generated using billing types, each representing a specific business transaction. The most common ones are: F2 (standard invoice, typically created with reference to a delivery), F1 (invoice created directly from an order, common in third-party or service scenarios), G2 (credit memo), L2 (debit memo), and F8 (pro forma invoice, used for customs or advance documentation without financial posting). Each billing type carries control settings that determine numbering, posting behavior, output determination, and whether it creates an accounting document. The billing document itself is structured like other SD documents: header level holds payer, billing date, pricing summary, and reference document links; item level holds material, quantity, net value, tax classification, and account assignment information inherited from the sales order or delivery. This layered structure allows billing to consolidate multiple deliveries into a single invoice (collective billing) or split a single delivery into multiple invoices based on differing terms (split billing), governed by header-level fields such as payment terms, incoterms, or billing date that must match for consolidation to occur. Billing relies heavily on preceding documents. A delivery-related invoice pulls quantities from goods issue postings, ensuring the customer is billed only for what physically left the warehouse. An order-related invoice bills directly from the sales order, common for services, or third-party/vendor drop-ship scenarios where no physical delivery is created in the selling company's system. Understanding this distinction is critical for a beginner because it determines which document flow to trace when investigating a billing block or a missing invoice. Billing also determines revenue account assignment, working through account determination logic (based on condition technique using access sequences tied to chart of accounts, sales organization, account assignment group of customer and material) to decide which G/L accounts receive the debit (customer receivable) and credit (revenue) postings. This is why billing configuration is jointly owned by SD and FI teams — a change in account determination configuration or master data (e.g., account assignment group) can silently misroute postings. From a process perspective, the billing due list is the primary tool used to identify sales orders and deliveries that are ready for billing based on billing relevance flags set in item categories. Understanding what makes a document appear or not appear in this list — billing blocks, incomplete deliveries, or billing plan dates not yet reached — is a foundational troubleshooting skill. Finally, beginners should understand that billing is not merely a print output. Even if invoice printing/output is suppressed, the billing document creates or is linked to critical downstream effects: FI accounting document creation, tax determination, revenue recognition triggers, and update of the document flow that ties sales order, delivery, and billing together for audit and reporting purposes.
Real project scenario
A retail distribution client implementing S/4HANA On-Premise wanted every delivery to automatically generate a customer invoice within the same day. During requirements workshops, the SD lead had to explain the difference between order-related and delivery-related billing to the client's finance team, who assumed billing happened automatically as soon as an order was placed. The team designed the billing type as F2, using delivery-related billing so invoices only fired after goods issue was posted, preventing premature revenue recognition before goods physically left the warehouse — a key control point flagged by external auditors during a subsequent SOX review.
Common mistakes
• Assuming billing document creation always triggers an FI posting; pro forma invoices (F8) do not post to accounting. • Confusing order-related and delivery-related billing when troubleshooting missing invoices, leading to wasted time checking the wrong preceding document. • Overlooking that billing blocks set at header or item level in the sales order will prevent documents from appearing in the billing due list. • Not recognizing that account assignment group on the customer and material master directly impacts revenue account determination, and treating incorrect postings purely as a technical config bug. • Believing invoice output (print/email) failure means the billing document itself was not created — the accounting effect and the output are separate processes.
Best practices
• Always confirm billing relevance settings on item category before assuming a billing block is the root cause of a missing invoice. • Use the billing due list regularly during cutover and go-live support to proactively catch documents stuck due to incomplete data. • Document for the client which billing types are delivery-related vs order-related, since this affects revenue timing and audit controls. • Coordinate account determination changes with FI counterparts; never modify SD account assignment groups without validating the G/L impact. • Treat pro forma invoices as non-financial documents in any reconciliation or revenue analysis.
Interview angle
Interviewers commonly probe whether a candidate can distinguish order-related vs delivery-related billing and explain what determines this at the item category level, plus ask candidates to describe what happens end-to-end when a billing document is saved (pricing copy, account determination, FI document creation, document flow update). Being able to articulate why pro forma invoices don't hit the ledger is a frequent differentiator between memorized configuration knowledge and real functional understanding.