FI / FICOarchitect

FICO Accounts Receivable Part 4: AR Architecture Across S/4HANA Deployments

Key takeaway

Architect AR for cloud and on-premise: business partner and CVI, centralized receivables and collections, public cloud constraints (standard scope items, key-user extensibility), open item and customer migration with reconciliation, and governance for master data and cash application.

Explanation

📌 KEY POINTS
✅ Customers are business partners (CVI); master data quality drives billing, credit and collection.
✅ Central receivables and shared services standardize cash application and collections.
✅ Public cloud: use standard processes and apps; extend only with key-user or side-by-side options.
✅ Migration: open items per company code with terms and dunning data, reconciled to GL.
⚠️ Migrating open items without dunning levels and dispute status restarts collection from zero.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 3 covered payments. Now architecture.

━━━━━━━━━━━━━━━━━━━━
▶ 1. MASTER DATA

BP/CVI; customer hierarchy; credit segment.

━━━━━━━━━━━━━━━━━━━━
▶ 2. OPERATING MODEL

Shared services for cash application and collections.

━━━━━━━━━━━━━━━━━━━━
▶ 3. DEPLOYMENT OPTIONS

Private vs public cloud; extensibility limits.

━━━━━━━━━━━━━━━━━━━━
▶ 4. MIGRATION

Open items, dunning levels, disputes, reconciliation.

━━━━━━━━━━━━━━━━━━━━
▶ 5. GOVERNANCE

Master data owners, match-rate KPIs, DSO targets.

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

Assess customer data and open items.
Define operating model and deployment constraints.
Plan migration with reconciliation.

✅ CHECKPOINT: migrated AR equals legacy AR per company code and aging bucket.

Code example

ABAP Code

===== MIGRATION FLOW =====Customer cleansing → BP load (CVI) → open items (with due dates, dunning data) → GL reconciliation → aging comparison → sign-off ===== OPERATING MODEL =====Shared services: cash application (EBS), collections worklist, dispute handling | KPIs: DSO, match rate, overdue %

Real project scenario

A multinational retailer migrated open items but not dunning levels. Customers received first reminders for invoices already at final notice in the old system, causing complaints. A corrected load with dunning data fixed later waves.

Common mistakes

Migrating without dunning data.
Modifications in public cloud.
No aging reconciliation.
Duplicate customers.
No KPIs.

Best practices

Include dunning and dispute data.
Use standard features.
Reconcile aging.
Cleanse customers.
Track DSO.

Interview angle

Questions: "How do you migrate AR?", "What changes in public cloud?", "How do you design collections?"
Strong answer: BP/CVI, operating model, deployment constraints, migration with dunning/dispute data, governance.

Practice this lesson

Quick check

1. When migrating AR open items, what should be loaded to continue collections seamlessly?

2. A large customer has multiple branch offices that receive goods and invoices separately, but all payments and the balance should be consolidated under one central account. Which AR concept addresses this requirement?

3. What limits custom AR processes in S/4HANA Public Cloud?

Interview questions

1. In SAP Business Partner architecture, how is a customer master created and what is the relationship between the Business Partner, Customer, and the underlying roles required for Order-to-Cash processing?

Answer it in your own words first, then compare.

2. A multinational retailer is migrating AR to S/4HANA Public Cloud. What do you plan?