SAP Billing

Billing generates the invoice for delivered goods or rendered services: it copies data from the reference document (delivery or order), applies pricing, and posts to FI, revenue accounts and accounts receivable (the customer’s liability to pay). It can bill per delivery, collectively, or on a schedule.

• Billing types (invoice, credit/debit memo, cancellation).
• Delivery-related vs order-related billing.
• Billing due list & collective billing.
• Revenue account determination (which G/L accounts).

VF01 creates a billing document, VF02 changes it and VF03 displays it. VF04 is the billing due list, which is how billing is actually run in practice: it shows everything ready to invoice and processes it in a batch. VF11 cancels, and cancellation creates a second document rather than removing the first.

The tables are VBRK for the header and VBRP for the items, with VBFA holding the document flow that links the invoice back to its delivery and order.

Two configuration transactions matter more than any others. VKOA holds revenue account determination, the table that decides which general ledger account revenue lands on. VTFL holds copy control from delivery to billing, which decides what data is carried across and how quantities are taken. Almost every billing question is one of these two.

Twenty minutes, and it connects the sales end of the business to the finance end.

1. Run VF04 for your sales organisation. Everything delivered and not yet invoiced is listed, which is the real world view of billing.
2. Select one and create the invoice, or create it directly with VF01 against a delivery number.
3. Open the document and check the accounting status in the header. If it posted, an accounting document number is there. If it did not, the status says so and the invoice sits waiting.
4. Follow through to FI and read the posting: revenue credited, receivables debited, tax where it applies.
5. Go back to VKOA and find the entry that chose that revenue account. It is driven by the chart of accounts, the sales organisation, the account assignment group on the customer and the one on the material.

Step five is the answer to the most common billing incident, which is an invoice that will not release to accounting.

Billing is the finance-facing end of order-to-cash: it posts revenue and AR in FI (via revenue account determination) and feeds profitability analysis (CO-PA). Correct account determination is what makes billing post to the right accounts; errors there cause billing/accounting failures.

The dependency people forget is master data. Revenue account determination reads the account assignment group from the customer and from the material, so a new material without one will bill and then fail to post. See SAP master data for why that field lives where it does, and SAP SD for the order and delivery steps in front of this one.

• Delivery related or order related. Physical goods bill from the delivery, because you invoice what actually shipped. Services and credit memos bill from the order, because there is no delivery.
• Collective or individual invoices. One invoice per delivery is simple. One per customer per period is what large customers ask for, and it is a split rule question.
• What is allowed to split an invoice. Different payment terms, payers or billing dates force a split. Most surprise splits are configuration working exactly as designed and nobody having predicted it.
• Billing plans. Milestone billing for projects, periodic billing for rentals and subscriptions. Both change the shape of the whole flow.

Three ways to reverse or reduce an invoice, and they are not interchangeable. Choosing the wrong one is the most common billing mistake after account determination.

Cancellation is for an invoice that should not exist: wrong customer, wrong amount, created in error. VF11 creates a cancellation document that reverses the accounting entry. Both documents remain, which is what an auditor expects to see.

A credit memo is for an invoice that was correct but the amount should change: a price adjustment, a goodwill gesture, a rebate. It starts life as a credit memo request, which is a sales document and can therefore be blocked for approval before anything reaches finance. That approval step is the reason credit memos exist rather than everything being cancelled and reissued.

A return is for goods coming back. It is a full sales cycle in reverse: a return order, a return delivery that puts stock back, and then a credit. Using a credit memo where goods physically returned leaves the stock unaccounted for, and inventory and finance stop agreeing.

The test to apply is simple. Did the invoice happen at all, did the money change, or did the goods come back. Each answer has one right document type, and the document flow will show the next person which one you chose.

Creating the billing document and getting the invoice to the customer are separate steps, and the second one is where a surprising number of incidents live.

Output determination decides what is produced, in what medium and to whom: a printed document, a PDF by email, or an EDI message to the customer's system. It is configured per output type with its own condition technique, the same machinery as pricing, so an invoice can post perfectly and send nothing because no output condition record was found.

Timing matters too. Output can be triggered immediately on saving or collected for a periodic run, and large customers usually want the second. When somebody says an invoice was never received, the sequence to check is: did the document post, did an output record get determined, did the output process successfully, and was the medium right for that customer.

Electronic invoicing adds a legal dimension in a growing number of countries, where the format and the clearance process are mandated rather than chosen, and that turns output from a convenience into a compliance requirement.

• Revenue account determination errors, failed/mis-posted billing.
• Wrong billing type.
• Billing blocks not resolved, invoices delayed.

• Cancelling by deleting. Use VF11, which leaves both documents and a clean audit trail.
• Chasing an invoice split as a bug. Compare the header fields of the two invoices first: the field that differs is the cause.
• Assuming an invoice printed means an invoice posted. Output and accounting are separate, and one can succeed while the other has not.

Pricing conditions moved from KONV to PRCD_ELEMENTS, which affects any custom report that read the old table. Revenue recognition for IFRS 15 moved into a dedicated revenue accounting solution rather than sitting inside SD, so contracts with multiple performance obligations are handled there. Customers are Business Partners maintained through BP.

Creating an invoice is the easy half, and configuring the revenue account determination that made it post to the right account is the part you do in the course.

If you take one thing from this page, make it the order of investigation. Check whether the document posted, then check the account determination, then check the output. Nearly every billing incident is one of those three, and working through them in that order finds it faster than guessing from the symptom the business described.

Billing is also where sales stops being a sales conversation and starts being a finance one, which is why the SD consultants who are trusted with it are the ones who can read the resulting accounting document without help.