Study guide
8.2 Order-Related vs. Delivery-Related Billing, Invoice Splits, and Collective Invoicing
SAP S/4HANA Sales C_TS462
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: SAP S/4HANA Sales Overview and Enterprise Structure
1.1 SAP Business Suite, SAP S/4HANA Sales, Deployment Options, and User Interfaces 1.2 Sales Organization, Distribution Channel, Division, and Sales Area Architecture 1.3 Sales Office, Sales Group, Plant, Storage Location, and Shipping Point Assignments 1.4 Cross-Company and Multi-Plant Sales Enterprise Setup & SD-FI Integration
2 Chapter 2: The Order-to-Cash Process and Sales Master Data
2.1 The Order-to-Cash Process: Sales Order, Shipping, Billing, and Finance Integration 2.2 Business Partner (BP) Approach, Customer Roles, and Partner Functions 2.3 Material Master / Product Master Sales Views, Tax Classifications, and Unit of Measure 2.4 Customer-Material Information Records (CMIR), Item Proposals, and Cross-Selling
3 Chapter 3: Sales Documents, Copying Control, Presales, and Outline Agreements
3.1 Sales Document Header Architecture and Customizing Sales Document Types 3.2 Special Functions in Sales Documents: Business Data, Blocks, and Reasons for Rejection 3.3 Copying Control and Document Flow Between Sales Documents 3.4 Pre-Sales Processing: Inquiries, Quotations, and Document Validity 3.5 Outline Agreements: Scheduling Agreements, Quantity Contracts, and Release Orders 3.6 Value Contracts: Releases, Partner Authorization, Contract Data, and Billing 3.7 Special Business Processes: Consignment, Rush Orders, Cash Sales, and Free-of-Charge Deliveries
4 Chapter 4: Item Categories, Schedule Line Categories, and Sales BOMs
4.1 Item Category Customizing Controls and Item Category Determination Logic 4.2 Schedule Line Categories and Determination Mechanics 4.3 Bill of Materials (BOM) Explosion in Sales Orders
5 Chapter 5: Pricing and the Condition Technique
5.1 Condition Technique Architecture: Field Catalogs, Tables, and Access Sequences 5.2 Condition Types, Calculation Types, Scales, and Condition Classes 5.3 Pricing Procedure Determination and Calculation Schema Configuration 5.4 Working with Condition Records: Maintenance Tools, Price Lists, Pricing Reports, and Manage Prices 5.5 Special Pricing Functions: Condition Exclusion, Group Conditions, Header Conditions, Condition Update, and Supplements 5.6 Special Condition Types: Manual Net Pricing, Minimum Values, Customer Hierarchy, Pallet Discounts, and Rounding 5.7 Statistical Condition Types and Tax Determination 5.8 Condition Contract Management: Contracts, Business Volume, Accruals, and Settlement
6 Chapter 6: Availability Check (ATP) and Delivery Scheduling
6.1 Availability Check Fundamentals: Checking Groups, Checking Rules, and Scope of Check 6.2 Delivery Scheduling & Routing: Transit Time, Loading Time, and Pick/Pack Time Calculations 6.3 Advanced ATP (aATP), Backorder Processing (BOP), and Transfer of Requirements
7 Chapter 7: Delivery Processing and Embedded EWM
7.1 Delivery Documents and Organizational Units for Delivery Processing, Including EWM 7.2 Shipping Point Determination and Route Determination Mechanics 7.3 Outbound Delivery Creation, Delivery Document Types, and Delivery Item Categories 7.4 Warehouse Execution: Picking, Packing, and Post Goods Issue (PGI) 7.5 Picking and Goods Issue with Embedded EWM 7.6 Inbound Deliveries with EWM and Special Functions in Deliveries
8 Chapter 8: Billing and Integration with Financial Accounting
8.1 Billing Document Types, Categories, and Billing Due List Processing 8.2 Order-Related vs. Delivery-Related Billing, Invoice Splits, and Collective Invoicing 8.3 Credit and Debit Memos, Down Payments, and Invoice Cancellation Workflows 8.4 Special Types of Settlement: Invoice Lists, External Billing Document Requests, and Preliminary Billing Documents 8.5 Billing Plans, Down Payment Agreements, and Installment Payments 8.6 Revenue Account Determination and FI-SD General Ledger Integration 8.7 The Interface Between Sales and Financial Accounting, Billing Output, and Technical Options
9 Chapter 9: Basic Functions: Partners, Incompletion, Texts, Material Determination, and Output
9.1 Partner Determination Procedures and Account Group Linkage 9.2 Incompletion Procedures, Status Groups, and Log Configuration 9.3 Text Control I: Text Objects, Text Types, Text Determination Procedures, and Manual Text Entry 9.4 Text Control II: Automatic Text Transfer, Text Determination Analysis, and Special Features 9.5 Material Determination, Material Listing, and Material Exclusion 9.6 Output Management: Modern BRFplus Architecture and Migration from Classical NAST 9.7 Output Parameter Determination with Decision Tables
10 Chapter 10: SAP Fiori, Sales Analytics, RISE with SAP, and Clean Core
10.1 SAP Fiori Sales Apps, Smart Business Monitoring, and Embedded Analytics 10.2 Working with the SAP Fiori Launchpad: My Home, Spaces and Pages, Help, Joule, Responsibilities, Situations, and Workflows 10.3 RISE with SAP Methodology: Standardized Framework, Transformation Preparation Service, Toolchain, Expert Guidance, and Dashboard 10.4 Clean Core: Definition, Benefits, the Five Principles, and Clean Core Levels
11 Chapter 11: Implementing SAP S/4HANA Cloud Private Edition
11.1 SAP S/4HANA Cloud Private Edition: Characteristics, Transition Paths, and the Implementation Team 11.2 System Landscapes, System Provisioning, and Release Upgrades 11.3 Setting Up the Project in SAP Cloud ALM and Preparing a System Conversion 11.4 Identity and Access Management: Users, Business Roles, Catalogs, Spaces, and Pages 11.5 Fit-to-Standard Workshops, Design Workshops, and Business Process Configuration 11.6 Extensibility in SAP S/4HANA Cloud Private Edition: Key User, Developer, and Side-by-Side 11.7 Integration: ISA-M, SAP Integration Suite, Prepackaged Content, and Monitoring 11.8 Data Migration with the SAP S/4HANA Migration Cockpit and Testing in SAP Cloud ALM
8.2 Order-Related vs. Delivery-Related Billing, Invoice Splits, and Collective Invoicing
Key Takeaways Explain This Topic AI
Item category billing relevance (TVAP-FKREL) dictates whether an item is billed based on delivery post goods issue (FKREL = A) or sales order confirmation (FKREL = B/C).
A single collective invoice can combine multiple deliveries or orders only if all VBRK header fields match identically, including Payer, Billing Date, Country of Destination, Payment Terms, and Currency.
Any divergence across VBRK header fields—originating from master data or introduced via Copy Control data transfer routines—forces an automatic invoice split.
The Split Analysis tool (VF01/VF04 Environment menu) provides an automated delta comparison between two invoices to identify the precise mismatched VBRK fields causing a split.
Copying control (VTFL for deliveries, VTFA for orders) governs copying requirements, the billing quantity, and the pricing type (for example, G keeps the order prices and redetermines taxes).
Last updated: October 2026
Order-Related vs. Delivery-Related Billing, Invoice Splits, and Collective Invoicing
In SAP S/4HANA Sales, an enterprise must bill diverse commercial offerings—ranging from tangible bulk goods and assembled machinery to intangible professional services, software licenses, warranties, and milestone-based construction contracts. To manage these operational variations, SAP provides two primary billing methods: Delivery-Related Billing and Order-Related Billing .
Furthermore, when processing hundreds of daily shipments to high-volume commercial buyers, enterprises seek to consolidate multiple shipments into a single Collective Invoice to reduce administrative costs and streamline payment processing. However, when transactional attributes differ, the billing engine automatically triggers an Invoice Split . Mastering billing methods, copy control routines, and split criteria is essential for configuring an efficient Order-to-Cash workflow.
Billing Relevance at the Item Category Level ( TVAP-FKREL )
The billing method applied to a sales line item is not configured at the sales document header level; rather, it is controlled at the Item Category level in database table TVAP through the Billing Relevance indicator ( FKREL ). Sales Document Header (OR)
- ├── Line 10: Material M-01 (Item Cat TAN) ──> FKREL = 'A' (Delivery-Related Billing)
- └── Line 20: Service S-01 (Item Cat TAD) ──> FKREL = 'B' (Order-Related Billing)
- Key Values of Billing Relevance ( FKREL )
Value Description Typical Item Categories Operational Workflow
A Delivery-related billing document TAN (Standard item) Billing after goods issue; the billed quantity is the delivered quantity.
B Order-related billing, status according to order quantity TAD (Service), REN (Returns), BVN (Cash sale) Billed directly from the sales document without a delivery.
C Order-related billing, status according to target quantity G2N , L2N (Credit/debit memo request items) Billed from the sales document based on the target quantity.
D Relevant for pro forma Free-of-charge items in export processes Item can be printed on a pro forma invoice without real billing.
F Order-related billing, status according to invoice receipt quantity TAS (Third-party) Customer billed for the quantity the vendor has invoiced.
I Order-relevant billing, billing plan Milestone billing ( TAO ), maintenance contract items Billed according to billing plan dates (see section 8.5).
K Delivery-related invoice for partial quantity Delivery items whose billed quantity may be changed Allows changing the quantity to be billed in delivery-related billing.
Deterministic Invoice Split Criteria
When a billing clerk runs transaction VF04 or an automated background job ( VF06 ) processes 50 outbound deliveries for the same customer, the business typically expects a single consolidated monthly or weekly invoice. However, the system often generates multiple distinct billing documents. This phenomenon is known as an Invoice Split .
The Fundamental Architectural Rule
An SD billing document is persisted in two primary database tables:
- VBRK : Billing Document Header
- VBRP : Billing Document Line Items
A billing document can contain thousands of line items in VBRP , but every line item within that billing document must share identical header fields in VBRK . If the deliveries selected for billing contain disparate header attributes, the database cannot physically store them under a single VBRK record. Therefore, the billing engine is mathematically compelled to initiate an Invoice Split .
Inviolable Header Split Fields in Table VBRK
The following header fields represent inviolable split criteria hardcoded into the SAP billing kernel. If any of these fields differ across preceding deliveries or orders, an invoice split is guaranteed:
Payer ( VBRK-KUNRG ) : The partner function Payer ( PY ) responsible for settling the invoice. Even if two deliveries share the identical Sold-to Party ( AG ), if their master data assigns different Payers, they must split.
Billing Date ( VBRK-FKDAT ) : The accounting date assigned to the invoice. If Delivery 1 is scheduled for billing on October 10th and Delivery 2 on October 15th, they will split unless the user overrides the date during batch execution.
Country of Destination ( VBRK-LAND1 ) : The destination country used for tax jurisdiction. Deliveries routed to domestic vs. international export destinations cannot be combined.
Terms of Payment ( VBRK-ZTERM ) : Payment terms (e.g., NT30 Net 30 days vs. 0002 2% 10 / Net 30). An invoice can have only one set of payment baseline dates and cash discount terms.
Billing Document Currency ( VBRK-WAERK ) : Transaction currency (e.g., USD vs. EUR). An invoice header can support only one commercial currency.
Sales Area ( VBRK-VKORG , VTWEG , SPART ) : Sales Organization, Distribution Channel, and Division. An invoice header is legally bound to a single Sales Area.
Incoterms ( VBRK-INCO1 , INCO2 ) : Delivery terms and location (e.g., FOB Chicago vs. DDP Munich ).
Exchange Rate for FI ( VBRK-KURRF ) : Fixed currency conversion rate between transaction currency and company code local currency.
Tax Classification / Destination VAT Registration Number ( VBRK-STCEG ) : Tax identification number required for statutory cross-border European Union reporting. Outbound Delivery 80001050 Outbound Delivery 80001051
- Sold-to: 100050 - Sold-to: 100050
- Payer: 100050 - Payer: 100050
- Terms: Net 30 (ZTERM: NT30) - Terms: 2% 10 Net 30 (ZTERM: 0002)
- Billing Date: 2026-10-15 - Billing Date: 2026-10-15
- │ │
- └──────────────────┬─────────────────────┘
- │
- ▼
- [ Billing Due List Execution ]
- │
Mismatched Field: VBRK-ZTERM!
- │
- ┌─────────────────┴─────────────────┐
- ▼ ▼
- [ Invoice 90000012 ] [ Invoice 90000013 ]
- Payer: 100050 - Payer: 100050
- Terms: NT30 - Terms: 0002
- Customizing Split Criteria via Copy Control Data Transfer Routines
In addition to the standard database header fields, an invoice split can be intentionally created—or prevented—through Data Transfer Routines configured in Copy Control (transactions VTFL and VTFA ).
When copying data from a delivery or sales order into an invoice, the system executes an ABAP data transfer routine (defined in transaction VOFM under Data Transfer → Billing Documents). This routine populates structure VBRK :
Routine 001 (Inv. Split Sample) : The standard routine. It populates VBRK with standard header values, permitting collective consolidation as long as baseline commercial fields match.
Routine 003 (Single Invoice) : Creates one billing document per reference document. According to the official course, data transfer routine 3 writes the number of the reference document into the split field VBRK-ZUKRI ; because that number differs for each document, the documents can no longer be combined.
Custom Data Transfer Routines (VOFM) : Enterprises can build bespoke routines to split invoices based on arbitrary business rules, such as customer Purchase Order number ( BSTKD ), manufacturing plant, or project WBS element.
Diagnosing Splits: The Split Analysis Tool
When a collective billing run unexpectedly generates multiple invoices for a customer, functional consultants do not need to perform manual table dumps. SAP provides an embedded diagnostic tool called Split Analysis .
How to Execute Split Analysis
In transaction VF01 (Create Billing Document) or VF04 (Maintain Billing Due List), enter or select the multiple deliveries/orders.
Execute billing simulation or navigate to menu path: Environment → Split analysis .
The system presents a side-by-side comparison matrix of the generated invoices.
Split Analysis compares table VBRK across both documents and explicitly highlights the differing fields in red, explaining exactly why consolidation failed (e.g., VBRK-FKDAT differs, or VBRK-INCO2 has divergent city names). +--------------------------------------------------------------------------+
- | Split Analysis Diagnostic Screen |
- +--------------------------------------------------------------------------+
- | Billing Document 90000045 <-> Billing Document 90000046 |
- |--------------------------------------------------------------------------|
- | Field Name Description Doc 90000045 Doc 90000046 |
- |--------------------------------------------------------------------------|
- | VBRK-KUNRG Payer 0001000050 0001000050 |
- | VBRK-VKORG Sales Organization 1010 1010 |
- | VBRK-ZTERM Terms of Payment NT30 0002 [SPLIT] |
- | VBRK-FKDAT Billing Date 2026-10-15 2026-10-15 |
- +--------------------------------------------------------------------------+
- | Result: Split caused by differing Terms of Payment (VBRK-ZTERM) |
- +--------------------------------------------------------------------------+
- Invoice Consolidation Strategies
To successfully achieve collective billing and combine multiple shipments into a single invoice, organizations employ three primary configuration strategies:
1. Overriding Billing Date in Collective Execution ( VF04 / Fiori)
Deliveries created on different days naturally carry different planned billing dates ( LIKP-FKDAT ). To prevent date-based splits, the billing user or background batch job can enter a unified Default Billing Date on the VF04 selection screen. The billing engine overwrites each delivery's individual date with this common date, aligning VBRK-FKDAT across all line items and enabling consolidation.
2. Invoicing Schedules via Factory Calendars ( KNVV-PERFK )
In the Business Partner master (role FLCU01 , Sales Area → Billing tab), enterprises assign an Invoicing Dates key ( PERFK ). This key points to a specialized factory calendar that designates specific commercial invoicing days (e.g., every Friday, or the 15th and last day of each month). All orders and deliveries created during the period automatically snap to the next scheduled calendar date, synchronizing VBRK-FKDAT .
3. Invoice Lists ( LR / LG )
If deliveries must be billed immediately upon shipment (generating separate F2 invoices for transportation documentation), the enterprise can consolidate those individual invoices at month-end into an Invoice List (document type LR ). The invoice list generates a collective financial summary sent to the payer for consolidated settlement.
Copy Control in Billing ( VTFL & VTFA )
Copy Control is the central customizing engine governing how data flows from preceding logistics documents into billing documents. Configured via:
- VTFL : Outbound Delivery to Billing Document (e.g., Delivery LF to Invoice F2 )
- VTFA : Sales Order to Billing Document (e.g., Sales Order OR to Invoice F2 , or CR to Credit Memo G2 )
Copy control is maintained at both Header Level and Item Level .
Key Parameters at the Item Level
Copy Control Parameter Level Purpose
Copying requirement Header and item A routine (maintained with VOFM ) checked before copying, for example that goods issue has been posted for a delivery-related item
Data transfer routine Header and item Controls how fields are filled in VBRK / VBRP , including split-relevant fields
- Billing quantity Item Which quantity is billed (see the table below)
- Pricing type and exchange rate Item Whether prices are copied or redetermined, and at which exchange rate
- Price source Item Where the conditions come from (for example, shipment costs from the shipment cost document)
The official course gives the standard billing quantities:
- Billing Document Billing Quantity
- Based on an order (for example, credit memo G2 ) Order quantity minus quantity already billed
- Based on a delivery (for example, F1 , F2 ) Quantity already delivered minus quantity already billed
- Pro forma invoice F5 Order quantity
- Pro forma invoice F8 Delivery quantity
For delivery-related billing, the quantities come from the delivery while the prices come from the underlying order.
The Pricing Type Parameter: Deep Dive
The Pricing Type parameter in copy control is one of the most vital customizing switches in SD, determining whether historical sales order prices are preserved or recalculated at billing time:
A (Copy pricing components and redetermine scales) : Copies base condition rates from the sales order but recalculates quantity scale tiers based on the total billed quantity.
B (Complete redetermination) : Completely wipes historical sales order pricing and re-reads all condition tables from scratch using the current billing date. Used when regulations require pricing to reflect spot-market commodity rates on the exact day of invoicing.
C (Copy manual pricing elements and redetermine the rest) : Retains manual discounts or surcharges entered by sales reps while recalculating base prices and taxes.
D (Copy pricing components unchanged) : Exactly copies all condition amounts, rates, and values from the preceding document without recalculation.
G (Copy pricing components unchanged and redetermine taxes) : Preserves the prices and discounts negotiated in the sales order but determines the tax conditions again, for example because the tax situation at billing differs from the order.
H (Redetermine freight conditions) : Preserves base prices and taxes but recalculates freight conditions ( KF00 ) based on actual shipped delivery weight.
Practical Scenario: Mixed Order Fulfillment
Consider an enterprise selling industrial machinery accompanied by an on-site installation service:
- Sales Order Item 10 : Assembly Robot ($80,000, Item Category TAN , FKREL = A )
- Sales Order Item 20 : Calibration & Training Service ($10,000, Item Category TAD , FKREL = B )
How Billing Unfolds:
Service Item 20 ( TAD ) : Because FKREL = B , this item does not enter the shipping delivery queue. It immediately appears on the Billing Due List ( VF04 ) under order-related billing. It can be invoiced immediately upon sales order confirmation.
Robot Hardware Item 10 ( TAN ) : Because FKREL = A , the system blocks invoicing until an outbound delivery ( LF ) is created, picked, packed, and posted with Goods Issue ( PGI ). Only after warehouse PGI moves the inventory does Item 10 enter the Billing Due List.
Result : Unless held by a billing block, the customer receives two invoices: an order-related invoice for the installation service and a delivery-related invoice for the physical robot.