8.1 Billing Document Types, Categories, and Billing Due List Processing

Key Takeaways

  • Billing represents the final operational stage of Order-to-Cash, creating the SD billing document while simultaneously posting accounts receivable in FI and profitability segments in CO.

  • Billing types (table TVFK, transaction VOFA) control the SD document category, the FI document type, the account determination procedure, the cancellation billing type, and an optional posting block.

  • Pro forma invoices (F5 for sales orders, F8 for deliveries) provide export customs and commercial documentation without posting financial entries or closing preceding document billing status.

  • A posting block in the billing type stops the automatic transfer to accounting (posting status 'A', blocked for forwarding) until the documents are released, for example with VFX3.

  • The billing due list (VF04, background billing with VF06, or the Create Billing Documents app) collects all items due for billing and can create individual or collective billing documents.

Last updated: October 2026

Billing Document Types, Categories, and Billing Due List Processing

In the SAP S/4HANA Order-to-Cash (O2C) processing chain, Billing represents the definitive commercial culmination of the sales cycle. Logistics execution—consisting of sales order processing, delivery creation, warehouse picking, packing, and posting goods issue (PGI)—moves goods and transfers physical custody. Billing translates those logistical fulfillment events into legal commercial claims, establishing customer receivables, recognizing sales revenue, calculating statutory tax liabilities, and updating managerial profitability accounting.

When a commercial billing document is saved in Sales and Distribution (SD), the system automatically triggers an accounting interface that creates an integrated financial accounting document in the Universal Journal (ACDOCA). This seamless integration between SD and Financial Accounting (FI) / Controlling (CO) ensures that logistical inventory movements and commercial sales transactions remain completely synchronized in real time.


The Role of Billing in the Order-to-Cash Lifecycle

Billing serves three fundamental business functions within the enterprise:

  1. Customer Invoicing and Receivables: It produces the legal customer invoice document (in print, PDF, or electronic data interchange formats such as EDI 810, Peppol, or SAF-T) and records the open debit on the customer's accounts receivable subledger in FI-AR.
  2. Revenue and Tax Recognition: It credits the appropriate revenue general ledger accounts and credits sales tax liability accounts according to the statutory tax jurisdiction of the transaction.
  3. Managerial Profitability Analysis (CO-PA): It passes detailed revenue, sales deduction, freight, and cost-of-goods-sold (COGS) figures into CO-PA profitability segments, providing real-time margin visibility by customer, product, sales organization, and distribution channel.
[ Sales Order (VA01) ] 
         │
         ▼
[ Outbound Delivery (VL01N) ] 
         │
         ▼
[ Post Goods Issue (PGI) ]  ---> (Material Document / Inventory Credit)
         │
         ▼
[ Billing Document (VF01/VF04) ] (Table VBRK Header / VBRP Item)
         │
         ├───────────────────────────────┐
         ▼                               ▼
[ FI Accounting Document ]     [ CO-PA Profitability Segment ]
(Universal Journal ACDOCA)     (Margin Analysis by Dimensions)
- Dr. Customer AR               - Revenue (PR00)
- Cr. Sales Revenue             - Discounts (K004/K007)
- Cr. Output Tax (MWST)         - Freight / Surcharges

Billing Document Types and Customizing (Table TVFK / Transaction VOFA)

Just as sales document types (VBAK) and delivery document types (LIKP) structure orders and shipments, the Billing Document Type governs the structural properties, number ranges, partner determination, and accounting behaviors of billing documents. The configuration of billing types is stored in database table TVFK and maintained via transaction VOFA.

Standard Billing Document Types

SAP delivers predefined billing document types tailored to standard commercial processes:

Billing TypeDescriptionReference SourcePrimary Output / Accounting Impact
F2InvoiceOutbound Delivery (LF) or Sales Order (OR)Generates customer invoice; posts debit to Customer AR and credit to Revenue.
G2Credit MemoCredit Memo Request (CR)Reimburses customer; posts credit to Customer AR and debit to Sales Deductions.
L2Debit MemoDebit Memo Request (DR)Supplementary customer charge; posts debit to Customer AR and credit to Revenue.
RECredit for ReturnsReturns Order (RE)Credits the customer for returned goods; created with reference to the returns order once the billing block is removed.
S1Invoice CancellationCommercial Invoice (F2)Reverses original invoice and creates offsetting FI journal entry.
S2Credit Memo CancellationCredit Memo (G2)Reverses credit memo and creates offsetting FI entry.
BV (CS)Cash SaleCash Sale Order (BV / CS)Order-related billing created after goods issue; posts to a cash settlement account. The receipt (output RD03) was already printed from the order.
F5Pro Forma Invoice for OrderSales Order (OR)Customs and export documentation; no FI posting; preceding order status unaffected.
F8Pro Forma Invoice for DeliveryOutbound Delivery (LF)Customs documentation based on actual delivery packing; no FI posting.
IVIntercompany BillingOutbound Delivery (LF)Cross-company code sales; generates internal intercompany receivable and payable.
IGIntercompany Credit MemoBilling documentCredit between the company codes in an intercompany process.
LR / LGInvoice List / Credit Memo ListBilling documentsCombine posted billing documents into one list for the payer (see section 8.4).
FAZDown Payment RequestSales Order Milestone (OR)Statistical billing document; creates noted item in FI without revenue impact.

Key Customizing Parameters in Table TVFK (Transaction VOFA)

Transaction VOFA houses the control parameters that dictate how the billing engine interacts with logistics, pricing, output, and general ledger accounting:

1. SD Document Category

The SD Document Category is the foundational classification that informs the SAP kernel of the document's legal identity:

  • M = Invoice (e.g., F2, BV)
  • O = Credit Memo (e.g., G2, RE)
  • P = Debit Memo (e.g., L2)
  • U = Pro Forma Invoice (e.g., F5, F8)
  • N = Invoice Cancellation (e.g., S1)
  • 5 = Intercompany Invoice (e.g., IV)
  • 6 = Intercompany Credit Memo (e.g., IG)

2. Document Type in FI

Defines the FI document type created when the billing document is transferred to Financial Accounting. If the field is left blank, the system transfers document type RV (billing document transfer) for every billing type; maintaining a different document type per billing type allows separate number ranges and evaluations in accounting. This setting enables financial accountants to segregate automated sales invoicing entries from manual journal vouchers (SA) or vendor invoices (KR).

3. Posting Block

The Posting Block checkbox controls whether the billing document immediately releases its financial entries to General Ledger accounting upon creation:

  • Unchecked (Standard): Saving the billing document in VF01 or VF04 automatically generates the FI document (ACDOCA) in real time.
  • Checked ([X]): The billing document is created with posting status A (blocked for forwarding to accounting, field VBRK-RFBSK). No FI document is generated until the document is released, individually with VF02 or collectively with VFX3. The official course notes that this lets you create and print billing documents first and transfer them later, and that the system creates either all accounting documents (FI, CO) or none.

Note

Enterprises frequently activate the posting block for specialized billing types—such as high-value credit memos, scrap billings, or complex export shipments—where commercial supervisors or tax auditors must review pricing, VAT numbers, and customs codes before general ledger updates take place.

4. Account Determination Procedure

Specifies the Condition Technique procedure evaluated to determine general ledger accounts for revenue, sales deductions, freight charges, and tax accruals (standard procedure KOFI00, with condition types KOFI and KOFK).

5. Document Pricing Procedure

Defines the document pricing key assigned to the billing type. When combined with the customer pricing procedure (from the Business Partner record) and the sales area, it identifies the pricing procedure used if pricing is recalculated or redetermined during billing.

6. Cancellation Billing Type

Specifies the billing document type that the system must automatically instantiate when a user cancels the billing document in transaction VF11. For example, standard invoice F2 points to cancellation billing type S1, and credit memo G2 points to S2.

7. Invoice List Type

Controls whether the billing document can be combined into an invoice list: LR for invoices and debit memos, LG for credit memos.


Deep Comparison: Pro Forma Invoices (F5/F8) vs. Commercial Invoices (F2)

One of the most frequently tested concepts on SAP certification exams is the structural and accounting distinction between Pro Forma Invoices and Commercial Invoices.

A Pro Forma Invoice is an informational document generated to facilitate international trade, customs inspection, import licensing, export declarations, or letters of credit before the financial transaction actually occurs. Because it carries no financial obligation, it does not represent an accounting receivable.

Operational CharacteristicCommercial Invoice (F2)Pro Forma Invoice (F5 / F8)
SD Document CategoryM (Invoice)U (Pro Forma Invoice)
Reference Preceding DocumentDelivery (LF) or Sales Order (OR)F5 references Order (OR); F8 references Delivery (LF)
FI Accounting Document Generated?Yes — Generates real-time journal entry in ACDOCA / BKPF.No — Generates zero financial or cost accounting entries.
Impact on Preceding Document StatusUpdates Billing Status — Sets status from 'Open' (A) to 'Completed' (C).No Status Change — Preceding order or delivery billing status remains 'Open' (A).
Quantity Invoiced TrackingConsumes delivery/order quantity; prevents duplicate billing.Does not consume quantity; can be generated repeatedly.
Prerequisite for ExecutionDelivery-related F2 requires Post Goods Issue (PGI) to be completed.F8 can be generated before PGI to provide paperwork for customs clearance.
Revenue Account DeterminationMandatory (KOFI00 must resolve valid G/L accounts).Bypassed completely; no G/L accounts are determined.
Cancellation MechanismMust be formally reversed via transaction VF11 (creates S1).Not posted, so no accounting reversal is needed.

Tip

In export logistics, an outbound delivery often requires customs paperwork before the freight carrier departs the warehouse loading dock. Because the physical goods have not yet left the facility, posting goods issue (PGI) has not occurred. Warehouse personnel create an F8 Pro Forma Invoice for Delivery, print the export declaration, hand it to the carrier, and perform PGI later. When the carrier departs, the standard F2 Commercial Invoice is generated.


Billing Due List Processing Mechanics

In high-volume enterprise operations, billing is rarely executed document by document. Instead, organizations run automated batch jobs or collective worklists known as the Billing Due List.

How Documents Enter the Billing Due List

A logistics document enters the Billing Due List automatically when its processing status meets specific criteria:

  1. For Delivery-Related Billing (Item Category FKREL = A):
    • Outbound delivery item exists.
    • Post Goods Issue (PGI) has been completed (LIKP-WBSTK = 'C').
    • Billing status is not completed (LIKP-FKSTK <> 'C').
    • No billing block exists in the delivery.
  2. For Order-Related Billing (Item Category FKREL = B or C):
    • The sales order item is complete and not rejected.
    • No header billing block (VBAK-FAKSK) or item billing block (VBAP-FAKSP) exists.
    • Billing status is not completed (VBAK-FKSAK <> 'C').

Execution Modes: Interactive vs. Mass Processing

SAP provides three execution tiers for billing processing:

+-------------------------------------------------------------------------+
|                        1. Interactive Billing (VF01)                    |
|  - Direct document entry for single invoices, testing, or exceptions.   |
|  - Displays split analysis and allows manual adjustment before saving.  |
+-------------------------------------------------------------------------+
                                     │
                                     ▼
+-------------------------------------------------------------------------+
|                 2. Collective Billing Due List (VF04)                   |
|  - Foreground mass processing with rich selection criteria.             |
|  - Provides simulation mode and collective processing with split logs.  |
+-------------------------------------------------------------------------+
                                     │
                                     ▼
+-------------------------------------------------------------------------+
|                  3. Background Mass Billing Jobs (VF06)                 |
|  - Program SDBILLDL scheduled as a recurring batch job during off-peak. |
|  - Automatically processes thousands of shipments without user locking. |
+-------------------------------------------------------------------------+

Transaction VF04: Maintain Billing Due List

Transaction VF04 allows billing specialists to review and process pending shipments and orders across customizable filter parameters:

  • Billing Date: Restricts the selection to items due on or before a specified date.
  • Billing Type: Targets specific document types (e.g., only F2 or only G2).
  • Organizational Filters: Sales Organization, Distribution Channel, Division, Shipping Point.
  • Partner Filters: Sold-to Party, Payer, or Destination Country.
  • Selection Toggles: Delivery-related items, order-related items, and intercompany items.

In VF04, the official course distinguishes three options:

  • Individual billing documents: one billing document per selected document, no combination; the system branches to VF01 for each.
  • Collective billing documents: all selected documents are billed in the background and combined as far as possible; icons in the list show success or errors.
  • Collective billing documents online: the system branches to VF01 and combines the documents according to the usual criteria.

You can also run the due list in simulation mode, which shows the billing documents without saving them and marks documents with errors. Billing on request (VF01) also offers item selection, but in delivery-related billing the item quantity can only be changed for item categories with billing relevance K. A whole collective run can be cancelled: its billing documents are combined under a collective processing number of type S, and the preceding documents can then be billed again (Billing → Information system → Billing documents → Log of collective run, then Reverse all).

Transaction VF06: Background Mass Invoicing

Transaction VF06 schedules billing in the background, either periodically (for example, every Monday at 2 a.m.) or at a specific time. The system can split the billing due list into several jobs that run in parallel. SAP recommends switching off the log and detailed list if you do not need them, because this improves performance considerably.

SAP Fiori Billing Apps

  • Create Billing Documents - Billing Due List Items: offers more filters than VF04 and billing settings that decide whether the system asks for a billing date and type, creates separate billing documents per item, posts billing documents to accounting automatically (and triggers output), and displays temporary billing documents after creation. Temporary documents can be saved as final documents or discarded, which avoids cancellations and gaps in the number range. Custom fields can also be used to filter and sort the due list.
  • Manage Billing Documents: displays, edits, posts, and cancels invoices, cancellations, credit memos, and other billing documents, and generates PDF print previews.
Loading diagram...
SAP S/4HANA Billing Generation and Financial Integration Architecture
Test Your Knowledge

What happens when a posting block is set in customizing for a billing type (transaction VOFA)?

A

The billing document generates an FI document, but general ledger account posting lines are held in temporary cash management tables.

B

The system cancels the billing document right after it is created.

C

The customer master record is automatically placed on credit hold, blocking subsequent delivery creation until payment is received.

D

The document is saved with posting status A, and nothing is posted until release (VFX3 or VF02).

Test Your Knowledge

Which statement correctly distinguishes a Pro Forma Invoice (document type F5 or F8) from a standard Commercial Invoice (document type F2)?

A

A pro forma invoice updates customer accounts receivable but posts to a statistical revenue account rather than primary operating revenue.

B

It creates no accounting entries and does not change the billing status of the order or delivery.

C

It can be created only after goods issue has been posted.

D

A pro forma invoice cannot be created more than once for the same outbound delivery to prevent export documentation fraud.

Test Your Knowledge

Under what specific condition does an outbound delivery line item for physical goods (item category TAN) become eligible for selection in the Billing Due List (transaction VF04 / VF06)?

A

Only after Post Goods Issue (PGI) has been successfully posted for the delivery and the billing status remains open.

B

Immediately upon creation of the outbound delivery document in transaction VL01N, regardless of warehouse picking status.

C

Only when the customer payment terms expire and the commercial credit limit check is re-executed.

D

As soon as warehouse picking and packing have achieved status 'Completed', even if transportation planning remains in progress.

Sections you finish are checked off in the contents.