Billing
SD / O2Cbeginner

SD Billing Part 1: What Billing Does in Order-to-Cash

Key takeaway

Billing turns deliveries and orders into invoices, credit memos and debit memos, posts revenue and receivables to FI, and closes the order-to-cash loop. Learn the billing document structure, delivery-related vs order-related billing, the main billing types, and what billing hands over to accounting.

What this complete series covers

Learn Billing in a clear, practical sequence — from the basic idea to real project use, troubleshooting, and interview-ready understanding.

Who it is for
Best for SAP consultants, developers, and learners who want a practical understanding of Billing.
Prerequisites
Basic SAP S/4HANA navigation and an understanding of the business process are helpful. Configuration or transaction steps require suitable access to a practice or project system.
Final outcome
By the end, you should be able to explain Billing clearly, follow the main end-to-end flow, apply it in a project scenario, and troubleshoot the most common issues.
  1. Part 1: SD Billing Part 1: What Billing Does in Order-to-Cash

    Introduces why billing exists in the SD process, the main billing document types, and how billing connects sales and delivery activities to finance.

  2. Part 2: SD Billing Part 2: Billing Type Configuration and Copy Control

    Explains how copy control rules govern billing document creation, how the billing due list processes documents, and how billing integrates with FI through account determination and revenue posting.

  3. Part 3: SD Billing Part 3: Revenue Account Determination (VKOA)

    Understand how SAP determines the correct G/L accounts when a billing document is released to accounting, and how this configuration drives accurate revenue, tax, and cost of goods sold postings in FI.

  4. Part 4: SD Billing Part 10: Architecting Enterprise Billing — Scale, Governance and Migration

    Design considerations for billing solutions that must scale across markets, comply with statutory requirements, integrate cleanly with FI/CO, and migrate safely from ECC to S/4HANA

  5. Part 5: SD Billing Part 9: Troubleshooting Billing Blocks, Errors and Mass Processing Failures

    Learn how to systematically diagnose and resolve billing blocks, incompletion errors, and mass processing failures encountered during collective billing runs in production support.

  6. Part 6: SD Billing Part 6: Billing Plans — Milestone and Periodic Billing

    Use billing plans when invoicing is date- or milestone-driven rather than based on a single delivery, with controlled billing dates, percentages or values and block/release logic.

  7. Part 7: SD Billing Part 5: Cancellation, Credit Memos and Debit Memos

    Correct billing through the business process that matches the event: cancellation for reversing an incorrect invoice, credit memo for reducing customer liability and debit memo for increasing it.

  8. Part 8: SD Billing Part 7: Intercompany Billing and Internal Revenue/Cost Flow

    Understand intercompany billing when one company code's sales organization sells to the customer while a delivering plant belongs to another company code, creating both external an

  9. Part 9: SD Billing Part 4: Billing Due List, Collective Billing and Split Criteria

    Understand how billable sales or delivery documents enter the billing due list and how SAP combines them into one or multiple invoices according to mandatory and configurable split criteria.

  10. Part 10: SD Billing Part 8: Billing to FI — Accounting Transfer, Tax and Reconciliation

    Trace an SD billing document into Financial Accounting by checking revenue/account determination, tax, customer reconciliation account, posting status and any accounting-interface errors.

System and release assumptions: Examples focus on SAP S/4HANA. Exact apps, transaction codes, configuration paths, and field names can vary by release and deployment model.

Explanation

📌 KEY POINTS
✅ The billing document (VBRK/VBRP) is the last SD document: invoice, credit memo, debit memo, cancellation, pro forma.

✅ Delivery-related billing (after PGI) is the standard for goods; order-related billing is used for services, credit/debit memo requests and billing plans.

✅ Billing copies prices from the order (or reprices, per copy control) and posts revenue, deductions, taxes and the customer receivable to FI.

✅ Billing types (F2, G2, L2, S1, RE, F5/F8 pro forma…) control numbering, cancellation, posting and output.

⚠️ Pro forma invoices (F5/F8) are for customs/information only — they never post to accounting.

━━━━━━━━━━━━━━━━━━━━
▶ WHAT THIS SERIES COVERS

Part 1: What billing does

Part 2: Billing type configuration and copy control

Part 3: Revenue account determination

Part 4: Billing due list, collective billing and split criteria

Part 5: Cancellation, credit memos and debit memos

Part 6: Billing plans — milestone and periodic

Part 7: Intercompany billing

Part 8: Billing to FI — accounting transfer, tax and reconciliation

Part 9: Troubleshooting billing

Part 10: Architecting enterprise billing

━━━━━━━━━━━━━━━━━━━━
▶ 1. THE BILLING DOCUMENT

  • Header (VBRK): payer, billing date, billing type, currency, posting status.
  • Items (VBRP): reference to delivery/order item, quantity, net value, tax.
  • Document conditions (pricing) and partners.

━━━━━━━━━━━━━━━━━━━━
▶ 2. DELIVERY- VS ORDER-RELATED

  • Item category billing relevance A: delivery-related → invoice after PGI.
  • B/C: order-related → services, credit memo requests (CR → G2), debit memo requests (DR → L2).
  • I: billing plan dates.

━━━━━━━━━━━━━━━━━━━━
▶ 3. MAIN BILLING TYPES

  • F2 invoice, F1 order-related invoice, G2 credit memo, L2 debit memo, RE returns credit, S1/S2 cancellation, F5/F8 pro forma, IV intercompany, LR invoice list.

━━━━━━━━━━━━━━━━━━━━
▶ 4. CREATION

  • Individually (VF01) or via billing due list (VF04) and background jobs.
  • Several deliveries of one payer can be combined in one invoice if split criteria allow.

━━━━━━━━━━━━━━━━━━━━
▶ 5. HANDOVER TO FI

  • Accounting document: Dr customer receivable, Cr revenue, deductions, tax.
  • Posting status on the billing document; errors block the transfer.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

  1. Create an order, delivery and PGI.
  2. Create the invoice (VF01) and display the accounting document.
  3. Create a pro forma invoice and compare (no accounting).
  4. Check document flow.

✅ CHECKPOINT: you can explain every line of the invoice's accounting document.

Code example

ABAP Code
===== STEP 1: tables =====VBRK billing header (FKART type, KUNRG payer, FKDAT date, RFBSK posting status)VBRP billing items   | PRCD_ELEMENTS conditions (S/4HANA) | VBFA document flow ===== STEP 2: transactions =====VF01 create | VF02 change/release | VF03 display | VF04 billing due list | VF06 backgroundVF11 cancel | VFX3 blocked billing documents (release to accounting) ===== STEP 3: accounting document of an F2 invoice (example) =====Dr customer (reconciliation account)   1,190.00Cr revenue (ERL)                        1,050.00Dr sales deductions (ERS)                  50.00 (as negative revenue line)Cr output tax (MWS)                       190.00

Real project scenario

A distributor's customers regularly received invoices before goods arrived because billing was order-related for stock items (a copied item category with billing relevance B). Finance also saw revenue recognized too early. Changing billing relevance to A (delivery-related) meant invoices were created only after PGI; open orders were corrected and the billing due list run moved after the nightly PGI job.

Common mistakes

  • Order-related billing for goods that should be billed after delivery.
  • Expecting pro forma invoices to post revenue.
  • Billing before PGI in delivery-related processes.
  • Ignoring posting status (invoice created but not in FI).
  • Treating billing type names as behavior instead of configuration.

Best practices

  • Align billing relevance with the real billing trigger.
  • Run billing after PGI jobs.
  • Monitor documents not transferred to accounting.
  • Use pro forma only for information/customs.
  • Explain the accounting document to business users.

Interview angle

Questions: "What is delivery-related vs order-related billing?", "What does billing post to FI?", "What is a pro forma invoice?"
Strong answer: VBRK/VBRP billing document; billing relevance from item category; main billing types; VF01/VF04; accounting document with receivable, revenue, deductions, tax; pro forma without posting; posting status monitoring.

Practice this lesson

Quick check

1. Which statement correctly describes a key characteristic of a pro forma invoice in the billing process?

2. Which billing type is the standard customer invoice?

3. For which process is order-related billing typically used?

Interview questions

1. In a complex export scenario requiring pro forma invoices for customs clearance ahead of actual delivery, how should the pro forma billing type be configured to avoid unintended interference with credit management and revenue recognition?

Answer it in your own words first, then compare.

2. A customer requests a pro forma invoice before goods delivery so they can arrange import financing. Walk through how this is handled in SD and clarify what does and does not happen in FI-AR.

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.

More lessons in this topic

Interview questions on this topic

Related SAP topics