Study guide
8.4 Special Types of Settlement: Invoice Lists, External Billing Document Requests, and Preliminary Billing Documents
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.4 Special Types of Settlement: Invoice Lists, External Billing Document Requests, and Preliminary Billing Documents
Key Takeaways Explain This Topic AI
An invoice list combines billing documents that have already been created and posted to accounting into one list for the payer; LR is the invoice list for invoices and debit memos and LG for credit memos.
When the invoice list is created, its reference number overwrites the reference numbers of the individual billing documents in accounting, so the payment can be posted with the invoice list number.
An external billing document request (EBDR) persists billing data from an external system in SAP S/4HANA; EBDRs appear in the billing due list and can be converged with sales documents into one invoice.
Preliminary billing documents require business function SD_BIL_PRELIMBILLINGDOC; creating one sets the preceding document to billed and removes it from the billing due list until the preliminary document is rejected.
Preliminary billing documents have the statuses In progress, Rejected, Finalized, and Completed, and are converted into final billing documents in the Manage Preliminary Billing Documents app.
Last updated: October 2026
Special Types of Settlement: Invoice Lists, External Billing Document Requests, and Preliminary Billing Documents
Standard billing creates one billing document from deliveries or orders and posts it to accounting. The S46150 lesson Understanding Special Types of Settlement covers three variations that change when , from what , and in how many steps customers are billed: invoice lists , external billing document requests (EBDRs) , and preliminary billing documents .
Invoice Lists
An invoice list is a list of billing documents sent to the payer at regular intervals, for example once a month, instead of or in addition to the individual invoices. Typical users are buying groups or head offices that pay centrally for many branches.
How Invoice Lists Work
You must first create the billing documents and post them to Financial Accounting . Only then can they be combined in an invoice list (official S46150 content).
Two billing types exist for lists: LR (invoice list for invoices and debit memos) and LG (credit memo list).
The billing type of the individual documents names the invoice list type to which it can be assigned.
The dates on which lists are created follow the invoice list schedule (a factory calendar) maintained for the payer in the customer master.
Invoice lists are created and processed with the invoice list functions of the billing menu. The transaction table of the official course lists VF24 (process the worklist for invoice lists) and VF25 (create, change, and display invoice lists).
Output and Reference Numbers
Output settings decide whether invoices are sent to the customer when each invoice is created or only when the invoice list is created.
The number saved as reference number in copying control is transferred to Financial Accounting with each billing document. When the invoice list is created, the reference number of the invoice list overwrites the reference numbers of the individual billing documents. This lets accounts receivable post the incoming payment with the invoice list number (section 8.7).
Note
Invoice lists commonly carry their own conditions, for example a factoring discount granted to the paying head office for central settlement. These are calculated in the invoice list, not in the individual invoices.
External Billing Document Requests (EBDRs)
Convergent billing means billing different types of SD documents together in a single customer invoice : sales orders, deliveries, and professional services. EBDRs extend this to data from outside the SAP S/4HANA sales documents.
The course's business example: an IT company sells a solution consisting of hardware (outbound delivery), a software license (sales order), consulting services (debit memo request), and cloud-based machine learning services billed by usage (external usage data persisted in an EBDR). At month end, all billing data is converged into one invoice that bills the customer for what they actually used.
The definition of an EBDR, according to the course:
A request object that persists billing data received from an external system in SAP S/4HANA.
It appears alongside other SD documents in the billing due list (the Create Billing Documents app).
A dedicated object page displays all of its attributes.
EBDRs can be billed on their own or converged with billable SD documents, such as deliveries and debit memo requests. SAP calls this omnichannel convergent billing : billable items from different channels (internal and external) and billing categories (one-time, project-based, usage-based) are combined, which reduces administrative effort and the number of invoices sent.
Creating EBDRs
Use the SAP Fiori app Manage Billing Document Requests .
Enter the external billing data in the pre-delivered Microsoft Excel template and upload the file ( *.xlsx ).
The data is processed and persisted as EBDRs, which then appear in the billing due list of the Create Billing Documents app and in Manage Billing Document Requests .
Preliminary Billing Documents
A preliminary billing document lets you prepare and review a billing document before the final invoice exists, for example to agree the invoice content with the customer or to run an internal approval.
Activation and Its Consequence
A configuration expert must activate the business function Functionality for Preliminary Billing Documents ( SD_BIL_PRELIMBILLINGDOC ) in Customizing; no further setup is needed. Before activating it, be aware of one consequence that the course highlights: once you create a preliminary billing document for a document in the billing due list (for example, a delivery), the billing status of the preceding document changes to billed . The document is removed from the billing due list, even though no final billing document exists yet. You can no longer bill it directly from the Create Billing Documents app unless you first reject the preliminary billing document, which reopens the preceding document. To create the final billing document from the preliminary one, you use the creation function in the Manage Preliminary Billing Documents app.
Statuses
Status Meaning
In progress Default status after creation; you can change the document, reject it, finalize it, or convert it into a billing document
Rejected Marked manually as unsuitable for billing; it cannot be converted. The preceding document (for example, a debit memo request) is reopened and can be changed
Finalized Marked manually as needing no further changes for now; it can be converted into a billing document but not changed. If changes become necessary, you can set it back to In progress
Completed Converted into a billing document; it can no longer be changed. If the successor billing document is cancelled, the status returns to In progress
SAP offers optional approval workflows for preliminary billing documents.
Comparing the Three Settlement Types
- Aspect Invoice List EBDR Preliminary Billing Document
- Purpose Periodic summary for a payer Bill external data, alone or converged Review before final billing
- Input Posted billing documents External billing data (Excel upload) Billing due list items
Effect on accounting Reference number of the list replaces those of the invoices Billed like other due list items No posting until converted
Key tool Invoice list functions ( VF24 , VF25 ) Manage Billing Document Requests , Create Billing Documents Manage Preliminary Billing Documents
Worked Example: Monthly Settlement for a Buying Group
A buying group pays centrally for 40 member stores. Each store receives goods several times a week.
Each delivery is billed with F2 and posted to accounting as usual; output is set so that the stores receive no paper invoice.
On the last working day of the month, according to the invoice list calendar of the payer (the buying group's head office), invoice list LR combines all posted invoices of the month.
The invoice list reference number replaces the reference numbers of the individual invoices in accounting. The head office pays one amount quoting the invoice list number, and accounts receivable clears all items with that number.
A separate credit memo list LG combines the month's credit memos for the same payer.