SD / O2Carchitect

Advanced Intercompany Sales Part 2: Troubleshooting and Financial Reconciliation

Key takeaway

Keep intercompany processes reconciled: typical failure points (missing internal billing, failed automatic supplier invoices, price differences, tax), tracing documents across companies, month-end intercompany reconciliation, transfer pricing controls and governance.

Explanation

📌 KEY POINTS
✅ Most intercompany issues are missing or failed steps: no intercompany billing, failed automatic supplier invoice, or price/tax mismatches.
✅ Trace each transaction across both companies via document flow and interface monitors.
✅ Month-end intercompany reconciliation compares receivables/payables and revenue/cost pairs.
✅ Transfer pricing rules must be enforced by conditions and monitored.
⚠️ Unreconciled intercompany balances block consolidation and delay closing.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE
Part 1 described the flow. Now control and troubleshooting.

━━━━━━━━━━━━━━━━━━━━
▶ 1. FAILURE POINTS

Intercompany billing not run or failed.
Automatic supplier invoice failed (partner, tax, price).
Internal price missing or wrong.

━━━━━━━━━━━━━━━━━━━━
▶ 2. TRACING

Document flow per company; interface/IDoc monitors.
Match customer invoice → intercompany billing → supplier invoice.

━━━━━━━━━━━━━━━━━━━━
▶ 3. RECONCILIATION

IC receivables vs payables by partner company.
Differences by timing, price, currency, tax.

━━━━━━━━━━━━━━━━━━━━
▶ 4. TRANSFER PRICING

Condition maintenance and monitoring vs policy.
Documentation for tax authorities.

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

Owners, daily monitoring, month-end checklist.

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

List deliveries without intercompany billing.
Check failed supplier invoices.
Run IC reconciliation and classify differences.
Fix causes; repost.

✅ CHECKPOINT: IC balances reconcile at month-end with explained timing differences only.

Code example

ABAP Code

===== STEP 1: checks =====Deliveries/PGI without intercompany billing | failed automatic supplier invoices (interface monitor)Zero-value or wrong internal prices | tax code mismatches ===== STEP 2: reconciliation =====IC receivables (B) vs IC payables (A) by trading partner | revenue/cost pairs | differences: timing, price, FX, tax ===== STEP 3: governance =====Daily monitor | month-end IC checklist | transfer pricing review

Real project scenario

A selling company billed customers correctly but the delivering company's revenue was missing for some transactions because intercompany billing failed for a new plant. A daily list of deliveries without intercompany billing and an IC reconciliation step before close caught gaps within a day.

Common mistakes

No monitoring of missing IC billing.
Ignoring failed supplier invoices.
Reconciliation only at year-end.
Transfer prices not controlled.
No owners.

Best practices

Monitor IC steps daily.
Reconcile monthly by partner.
Control internal prices.
Document transfer pricing.
Assign ownership.

Interview angle

Questions: "How do you troubleshoot intercompany differences?", "How do you reconcile intercompany?", "What causes supplier invoice failures?"
Strong answer: missing/failed steps, tracing across companies, reconciliation by partner with difference classes, transfer pricing controls, governance.

Practice this lesson

Quick check

1. How do you trace a single intercompany transaction end to end?

2. Intercompany billing exists, but the selling company has no supplier invoice. Where should you look?

3. Intercompany receivables and payables differ at month-end. What is a structured approach?

Interview questions

1. You inherit an existing Advanced Intercompany Sales implementation covering Advanced Intercompany Sales in S/4HANA: Process and Document Flow. What would you review before changing it, and what would make you confident the change is production-ready?

Answer it in your own words first, then compare.

2. A project team is working on Advanced Intercompany Sales. Using the Advanced Intercompany Sales Troubleshooting and Financial Reconciliation scenario, how would you approach the requirement from design through validation?