Advanced Complex Billing in SAP S/4HANA SD: Milestone Billing, Periodic Billing, Pro Forma Invoicing, and Invoice Lists

Traditional Order to Cash (O2C) processes lend themselves to simpler delivery-related billing (F2 invoice generation following Goods Issue). However, complex enterprise models involving capital projects, subscription services, cross border trade, and consolidated corporate purchasing require billing to be more sophisticated.

In the area of SAP S/4HANA Sales, advanced configurations are required to manage complex revenue schedules and specialized documentation. Become proficient with the design, configuration and integration of financial aspects of the four major complex billing scenarios in SAP S/4HANA SD.

Configuration Roadmap for Complex SD Billing Scenarios

• Milestone Billing (Billing Plan 01 - Project/Phase-based)
• Periodic Billing (Billing Plan 02 - Recurring/Subscription)
• Pro Forma Invoices (F5/F8 - Non-financial Export/Customs)
• Invoice Lists (LR/LG - Consolidated Periodic Statements)

Scenario 1: Milestone Billing (Project-Based / Phase-Wise)

Billings for milestones consist of multiple installments and are invoiced against project stages (e.g., 20% milestone of the total contract value, 50% of the system built, 30% of the final acceptance).

Primary Use Cases: The manufacture of capital equipment, construction, and high-end professional services that integrate with the SAP Project System (PS).

Sales Order / WBS Element

• Milestone 10: Down Payment (20%) - Billing Block Removed -> VF01 Invoice
• Milestone 20: Delivery (50%) - Billing Block Removed -> VF01 Invoice
• Milestone 30: Acceptance (30%) - Billing Block Removed -> VF01 Invoice

Technical Configuration Steps:

1. Define Billing Plan Type (OVBO): Setup of Billing Plan Type 01 (Milestone Billing). Activate the Milestone Billing Indicator.
2. Configure Date Categories (OVBR): Rules for individual milestones can be set up (e.g category 01 for Down Payment and category 02 for Progress Payment). Default billing block IDs can be set to prevent billing before confirmation of a milestone.
3. Assign Billing Plan Types to Item Categories (OVB2): Assign Billing Plan Type 01 to either the standard item categories 'TAO' or the custom item Category 'ZTAO'.
4. Copy Control Setup (VTFA): Set up Order-to-Billing copy control for the Sales Order (OR) and the Billing Document (F2). Pricing Type is set to 'G' or 'H' to maintain the proper pricing logic.
5. PS/SD Integration: Through transaction CJM1, the billing plan dates can be linked to the Project System WBS Element and Milestone. A billing block will be released when a Project Manager confirms a Milestone in PS (CN25).

Scenario 2: Periodic Billing (Subscription & Rental Models)

Periodic Billing refers to billing a fixed amount over a defined contract period on a recurring basis (example $10,000 SaaS contract is billed on the 1st of every month).

Primary Use Cases: Equipment leasing, software subscriptions, recurring maintenance services, service level agreements (SLAs).

Technical Configuration Steps:

1. Define Billing Plan Type (OVBO): Configure Billing Plan Type 02 (Periodic Billing). Define start and end date rules using SAP calendar objects.
2. Define Invoicing Dates (OVBP): Define date determination logic (e.g., First day of a month, Last day of a quarter).
3. Assign to Item Categories (OVB2): Map Billing Plan Type 02 to either rental or service item categories (e.g., MVN).
4. Automated Batch Processing (VF04 / VF06): Run background billing using program SDBILLDL (VF06). The system checks open periodic billing dates for active contracts, and invoices are generated in the background within the batch.

Scenario 3: Pro Forma Invoices (Customs & Export Documentation)

A Pro Forma invoice is a commercial document issued to facilitate customs clearance, import licensing, or letter-of-credit processing without creating financial ledger postings.

• Standard Invoice (F2): Sales Order/Delivery -> Billing Document -> FI Accounting Document (FI Ledger Posted)
• Pro Forma Invoice (F5/F8): Sales Order/Delivery -> Billing Document -> NO Accounting Document Created

Primary Use Cases: International shipping, export customs declarations, free-of-charge sample deliveries (FD), and pre-payment documentation.

Key Operational Characteristics & Technical Comparison:

Parameter	Standard Invoice (F2)	Pro Forma Order-Related (F5)	Pro Forma Delivery-Related (F8)
Source Document	Sales Order / Delivery	Sales Order (OR)	Outbound Delivery (LF)
FI Posting Status	Posts directly to FI/G/L	No FI Posting	No FI Posting
Document Status Update	Closes order/delivery item	Leaves source doc open	Leaves source doc open
Re-billing Allowed	No (requires credit/debit)	Yes (can create multiple)	Yes (can create multiple)

Technical Configuration Steps:

1. Maintain Document Types (VOFA): Verify billing document types F5 and F8. Confirm the Transaction Group is set to 7 (Pro Forma) and the Accounting Block is active to prevent General Ledger updates.
2. Configure Copy Control (VTFA / VTFL):
   • VTFA (Sales Order OR -> Pro Forma F5)
   • VTFL (Outbound Delivery LF -> Pro Forma F8)
3. Pricing Procedure Rules: Ensure statistical condition types and export valuation rules populate without locking order processing status.

Scenario 4: Invoice Lists (Consolidated Periodic Statements)

• Individual Invoices (F2) -> Invoice List Run (VF21) -> Invoice List Document (LR) (Applies RL00 Factoring Discount)
• Credit Memos (G2) -> Invoice List Run (VF21) -> Invoice List Document (LR)

Primary User Scenarios: Large corporate buying groups or central purchasing organizations seeking consolidated payment input records for multiple subsidiary buying transactions.

Technical Implementation Steps:

1. Configure Billing Types (VOFA):
   • Set up Document Type LR (List of Invoice Debit Documents) and LG (List of Credit Memos).
   • Assign Document Type LR/LG to billing types F2/G2 under the field Invoice List Type in VOFA.
2. Assign Partner Role IL (VPA2): Add Partner Role IL (Invoice List Party) to the Sales Document and Customer Master (Payer) Partner Determination.
3. Factoring Discount Condition (RL00):
   • Define Condition Type RL00 (Invoice List Discount/Delcredere) in transaction V0/06.
   • Include RL00 in a statistical/absolute discount in the SAP SD Pricing Procedure (V/08) when the LR document is generated.
4. Output Determination (NACE / Output Control in Fiori): Configure Output Application V3 (Billing) with the assignment of Output Type LR00 for document transmission.
5. Execution (VF21 / VF24): Run VF21 (Generate Invoice List) or schedule batch execution in VF24 to consolidate open invoices for given customers and date ranges.

SD Billing Execution (VF01) leads into two parallel streams:

• Account Determination (VKOA):
  • Revenue Accounts (ERL)
  • Sales Deductions (ERS)
  • Factoring / Delcredere (RL00)
• SAP Revenue Accounting (RAR):
  • Performance Obligations (POBs)
  • Contract Asset / Liability Postings
  • IFRS 15 / ASC 606 Alignment

Account Determination (VKOA): Account determination ensures that billing items route using combination keys (Chart of Accounts + Sales org + Customer Account Assignment Group + Item Account Assignment Group + Account Key like RL00, ERS or MWS).

Revenue Recognition Integration (SAP RAR): IFRS 15/ASC 606 standards stipulate that billing timing and revenue recognition timing do not always align with milestone and periodic billing. S/4HANA integrates SD billing with SAP Revenue Accounting and Reporting (RAR) to manage contract liabilities and assets automatically via Performance Obligations (POBs).

Certification & Interview Prep: Preparation for the C_TS462 certification exams and technical mock interviews.

Build up your advanced SAP skills now! Check out the next cohorts at Best Online Career and hone your skills in SAP S/4HANA Sales!

FAQs

1. What is the primary difference between Milestone Billing and Periodic Billing?

For Milestone Billing, the total order value is distributed to individual milestones (either a percentage or a fixed amount), which sum to 100%. For Periodic Billing, the full order/contract value is repeated many times to bill a specific contract value for the duration of the contract at specific time intervals.

2. Does a Pro Forma Invoice (F5/F8) affect a customer's open item or the accounting ledger?

No. Pro Forma invoices are simply informative documents used for customs or export purposes and do not generate FI accounting documents, nor do they affect customer open items. They leave the sales order/delivery document open for actual billing (F2).

3. How do you address billing blocks in milestone billing plans?

In a billing plan, each milestone date line can be set to a billing block as a default. As individual project milestones are confirmed, either through PS integration or manually, the billing block for that line is removed and transaction VF01 or VF04 can load the line.

4. What partner role is required to process Invoice Lists in SAP SD?

Partner Role IL (Invoice List Party) must be entered in the Customer Master (Sales Area Data) and must participate in the partner determination for sales documents and billing headers.