Study guide
8.5 Billing Plans, Down Payment Agreements, and Installment Payments
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.5 Billing Plans, Down Payment Agreements, and Installment Payments
Key Takeaways Explain This Topic AI
A billing plan stores several billing dates for an item (or for the whole document when assigned at header level) instead of a single billing date; the system proposes periodic or milestone billing depending on the business transaction.
Periodic billing bills the full amount at regular dates, typically for rental and service contracts; new dates are created in the plan or with report RVFPLA01, which should run regularly.
Milestone billing distributes the total value over several dates; dates can be blocked until a project milestone is confirmed, and each date creates an entry in the billing index for order-related billing.
A billing rule per date defines whether a fixed amount or a percentage is billed and whether the date is a final invoice; down payment agreements use billing rules 4 (percentage) and 5 (value).
Down payment items use condition type AZWR (condition category E, calculation type B); in partial invoices, down payments can be cleared in full or proportionally by changing AZWR.
Last updated: October 2026
Billing Plans, Down Payment Agreements, and Installment Payments
Not every sale is billed once after delivery. Rental contracts are billed every month, construction projects in stages, and capital goods often require a down payment before production starts. The S46150 unit Exploring Special Business Processes (135 minutes) covers the tools for these cases: billing plans , down payments , and installment payments .
Billing Plans
When processing an order, instead of storing a single billing date, you can store a billing plan with several billing dates at item level . You can also define a billing plan at header level ; it is then valid for all items assigned to it, and header billing plans are assigned to sales document types . Depending on the business transaction, the system automatically proposes one of the two billing plan types :
- Billing Plan Type Typical Use How the Value Is Billed
- Periodic billing Rental and service agreements The full amount is billed periodically on fixed dates
- Milestone billing Plant engineering and construction The total value is spread over several dates
Items with a billing plan have billing relevance I (order-relevant billing according to the billing plan), so billing is order-related : each due date appears in the billing due list.
Periodic Billing
Periodic billing suits rental contracts :
The start and end dates define the duration of the billing plan and are taken from the contract data where possible.
If the duration is unlimited, you may set no end date. New dates are then created up to the horizon , which specifies the number of settlement periods in the billing plan.
You create new dates directly in the billing plan or with report RVFPLA01 . Schedule the report regularly, because new dates are not created automatically when you bill individual periods.
The billing dates define when and how often billing happens, for example on the first or last day of every month.
Special condition types with monthly prices let you price rental costs month by month.
Milestone Billing
In milestone billing, the total value is distributed among the individual dates according to rules:
You can enter as many dates per billing plan as required, and dates can be blocked for billing .
If amounts change after some milestone billing documents have been created, the changes are distributed among the remaining dates , and any amount still to be billed for documents already created is included in the final invoice .
The system creates an entry in the billing index for each billing date , so the date appears in the billing due list when it is reached; billing is order-related.
When you create a billing document, the system updates the status of the billing plan dates . Billed dates can no longer be changed; existing billing documents are visible in the document flow.
Link to Project Milestones
A typical case is a project in plant engineering. In SAP S/4HANA, milestones are stored in a project network with planned and actual data. Milestones are assigned to billing plan dates, which stay blocked for billing until the milestone is confirmed as completed. For each billing date you can control:
Whether it is a fixed date .
Whether it is updated with the actual date of the milestone.
Whether it is updated with the actual date only if the milestone is completed before the planned billing date.
The Billing Rule
A billing rule can be created for each billing plan date. It defines how the value to be billed on that date is determined: a fixed amount or a percentage of the total amount. It also determines whether the amount counts as a final invoice , for which unbilled dates must also be taken into account.
Customizing Billing Plans
Billing plan Customizing defines the billing plan types, the date categories (with their billing rule and billing block proposal), date proposals, and the assignment of billing plan types to item categories and, for header billing plans, to sales document types.
Down Payment Agreements in the Billing Plan
Down payments are usually agreed for plant engineering, construction, or capital goods. They are created in the sales order , and down payment processing is carried out with the billing plan function :
You store one or more down payment agreements as dates in a billing plan .
You enter the agreed value either as a fixed amount or as a percentage of the item value.
Control is through the billing rules: billing rule 4 (down payment for percentage milestone billing) and billing rule 5 (down payment for value-related milestone billing).
The agreement can be assigned to a single item or be valid for all items of the order.
Down payment items use the special condition type AZWR instead of PR00 . AZWR has condition category E and calculation rule B (fixed amount). When AZWR is determined, all other condition types are set to inactive.
At the due date, the system creates a down payment request (billing type FAZ ). In Financial Accounting it is posted as a noted item with special G/L indicator F , which is statistical and posted to a different reconciliation account. The customer's payment is posted with special G/L indicator A and assigned to the down payment request and to the sales order (section 8.3).
Partial and Final Invoices
In partial and final invoices, the down payments made are transferred as down payments to be cleared :
Full settlement : during partial invoicing, the down payment amount due for clearing is displayed and deducted from the receivable automatically.
Proportional settlement : you can change the amount of the down payment to be cleared by changing the AZWR amount on the item's pricing screen. The maximum is the down payments received minus the down payments already cleared.
During final invoicing , all pending down payments are taken into account.
In Financial Accounting, the cleared down payments are moved from the special reconciliation account to the standard reconciliation account, where they appear as open items for the customer and reduce the receivables total.
Installment Payments
An installment payment splits one invoice amount into several partial amounts with different due dates, for example 40% after 30 days, 30% after 60 days, and 30% after 90 days. It is controlled by terms of payment for installment payments in Financial Accounting Customizing. The billing document itself is created once, with the installment payment terms; when it is posted, accounting creates one receivable line item per installment , each with its own due date. Installment payments therefore spread the payment , while a billing plan spreads the billing over several billing documents.
- Requirement Tool
- Bill a rental contract every month Periodic billing plan
- Bill a project in stages as milestones are reached Milestone billing plan linked to project milestones
- Collect money before delivery Down payment agreement in the billing plan (billing rule 4 or 5, FAZ , AZWR )
- Let the customer pay one invoice in parts Installment payment terms
- Worked Example: Machine Order with Down Payment and Milestones
A machine is sold for 100,000 EUR with this agreement: 20% down payment at order, 50% on acceptance of the design, and the rest after delivery.
The item has a milestone billing plan with three dates: a down payment date with billing rule 4 (20%), a milestone date (50%) blocked until the design milestone is confirmed, and a final invoice date.
At the first date, down payment request FAZ for 20,000 EUR is created and posted as a noted item (special G/L indicator F ). The customer pays; the payment is posted with indicator A .
When the design milestone is confirmed, the block on the second date is removed and a partial invoice for 50,000 EUR is created. With full settlement, the 20,000 EUR down payment is cleared, so the customer owes 30,000 EUR.
After delivery, the final invoice bills the remaining 30,000 EUR. All down payments have already been cleared, and the billed dates can no longer be changed.