SD / O2Carchitect

SD Billing Part 10: Architecting Enterprise Billing — Scale, Governance and Migration

Key takeaway

Architect's view: billing type catalogue, invoice volume and performance, output and e-invoicing compliance, revenue account design with finance, intercompany automation, integration with external billing (SAP BRIM/convergent invoicing), month-end cut-offs and migration of open items and billing history.

Explanation

📌 KEY POINTS
✅ Keep a small billing type catalogue with fixed meanings; differences via output parameters or reason codes.
✅ Design revenue accounts and account assignment groups with finance as part of the template.
✅ E-invoicing and legal output requirements differ by country — plan them as a separate, governed layer.
✅ High-volume or subscription billing may need SAP BRIM/convergent invoicing instead of SD billing.
⚠️ Month-end revenue depends on PGI, billing and posting completing in time — design the cut-off chain.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Parts 1–9 covered billing end to end. This part is the landscape view.

━━━━━━━━━━━━━━━━━━━━
▶ 1. BILLING TYPE CATALOGUE

F2, G2, L2, RE, S1, IV, F5/F8, FAZ, LR — with documented purpose.
Country variants via output, not types.

━━━━━━━━━━━━━━━━━━━━
▶ 2. PERFORMANCE AND SCHEDULING

Background billing in parallel by sales org/payer ranges.
Sequence: PGI → intercompany → customer billing → output → FI checks.

━━━━━━━━━━━━━━━━━━━━
▶ 3. LEGAL AND OUTPUT

E-invoicing mandates (country formats, portals), document compliance solutions.
Output management in S/4HANA (BRF+ determination, forms).

━━━━━━━━━━━━━━━━━━━━
▶ 4. FINANCE INTEGRATION

Revenue account design, account assignment groups, tax.
Intercompany automation and reconciliation.
Revenue recognition requirements (see Revenue Recognition topic).

━━━━━━━━━━━━━━━━━━━━
▶ 5. MIGRATION AND SCALE-OUT

Migrate open items in FI; billing history kept in legacy/archive.
Open deliveries/orders migrated to be billed in S/4HANA.
Subscription/usage models → evaluate BRIM.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

Define billing type catalogue and account design.
Design the nightly chain and cut-offs.
Plan e-invoicing per country.
Decide SD billing vs BRIM for special models.
Plan migration of open items and documents.

✅ CHECKPOINT: month-end closes with all shipped goods billed and posted, and every country's legal invoice format is covered.

Code example

ABAP Code

===== STEP 1: nightly chain =====22:00 PGI jobs → 23:00 intercompany billing (IV) → 23:30 customer billing (VF06) → 00:30 output/e-invoicing→ 01:00 VFX3 check / alerts → month-end: cut-off checklist ===== STEP 2: catalogue =====F2 invoice | G2 credit | L2 debit | RE returns credit | S1/S2 cancel | IV intercompany | F5/F8 pro forma | FAZ down payment ===== STEP 3: decision: SD billing vs BRIM =====Low/medium volume, goods and services → SD billingHigh-volume usage/subscription, many billable events → SAP BRIM (convergent invoicing)

Real project scenario

A consumer goods company running a two-tier landscape had 18 billing types, country-specific e-invoicing implemented differently in each rollout, and nightly billing overrunning into the morning. The architect consolidated billing types to 9, introduced a common e-invoicing layer with country formats, parallelized billing by payer range after PGI and intercompany jobs, and added a month-end cut-off checklist. Nightly runtime halved and e-invoice rejections dropped.

Common mistakes

Billing types per country or print variant.
No defined nightly job chain.
Country e-invoicing built ad hoc.
Revenue accounts designed without finance.
Migrating closed billing history into S/4HANA unnecessarily.

Best practices

Keep a small billing type catalogue.
Design the job chain and cut-offs.
Treat e-invoicing as a governed layer.
Co-design accounts with finance.
Decide early on BRIM for special models.

Interview angle

Questions: "How would you design billing for a global template?", "How do you handle e-invoicing?", "When would you use BRIM?"
Strong answer: billing type catalogue, output-based variants, revenue accounts with finance, job chain and cut-offs, e-invoicing layer, intercompany automation, BRIM for high-volume usage models, migration of open items.

Practice this lesson

Quick check

1. Why must the nightly job chain be designed as PGI → intercompany billing → customer billing → FI checks?

2. Which business model most likely justifies SAP BRIM/convergent invoicing instead of SD billing?

3. A global template has billing types per country and per print layout. What should the architect recommend?

Interview questions

1. In a global template rollout, how do you design billing type strategy to correctly handle standard invoices, credit memos, debit memos, and cancellations while preserving clean FI-AR postings and audit traceability?

Answer it in your own words first, then compare.

2. You design billing for a global template covering goods sales, services, intercompany and country e-invoicing. What are your key design decisions?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.