What is SAP Intercompany Reconciliation?
Definition
SAP intercompany reconciliation is the review of related-party balances and transactions recorded in SAP to confirm that internal receivables, payables, invoices, journals, allocations, and settlements match across company codes. It helps finance teams verify that both sides of an internal transaction are posted with the correct entity, counterparty, account, currency, document reference, and period. In practice, it is a SAP-focused form of Intercompany Reconciliation that supports accurate close, consolidation, and financial reporting.
How It Works
The reconciliation usually starts with SAP general ledger and subledger data. Finance teams extract intercompany open items, trading partner balances, vendor-customer records, journal entries, tax codes, and document references. The charging company code’s receivable or revenue entry is compared with the receiving company code’s payable or expense entry to identify matched and unmatched items.
Where multiple SAP instances, local ledgers, or reporting layers exist, the review also depends on Data Reconciliation (System View) so that balances can be compared consistently. If one company code posts a $58,000 intercompany receivable and the counterparty records only $56,750 as payable, the difference is reviewed by document number, tax treatment, exchange rate, posting date, and settlement status.
Core Reconciliation Checks
A strong SAP intercompany reconciliation checks both accounting accuracy and SAP master data quality. The goal is to make sure that internal activity can be matched, cleared, eliminated, and explained before group reporting is finalized.
Company code alignment: confirms that the originating and counterparty entities are correctly identified.
Trading partner coding: verifies that intercompany transactions include the correct partner details.
Account mapping: applies Chart of Accounts Mapping (Reconciliation) to align local and group accounts.
Currency review: checks document currency, local currency, group currency, and exchange rate treatment.
Document matching: compares invoice references, journal numbers, clearing documents, and settlement files.
Review evidence: confirms preparation and approval under Segregation of Duties (Reconciliation) controls.
Key Metrics and Example
A useful metric is: SAP Intercompany Match Rate = Matched Intercompany Items ÷ Total Intercompany Items × 100. Another common measure is: Manual Intervention Rate = Manually Corrected or Explained Items ÷ Total Intercompany Items × 100.
Assume SAP shows 9,500 intercompany items for May. If 8,930 items are matched through standard rules, the match rate is 8,930 ÷ 9,500 × 100 = 94%. If 380 items require user review, adjustment, or explanation, the Manual Intervention Rate (Reconciliation) is 380 ÷ 9,500 × 100 = 4%. A higher match rate usually indicates cleaner company code alignment and stronger posting discipline, while a higher manual intervention rate highlights where master data, coding, or cut-off rules can be improved.
Exception Handling and Monitoring
SAP intercompany reconciliation often uses Exception-Based Intercompany Processing to separate matched items from records that need review. Common exception categories include missing counterparty postings, unmatched invoices, duplicate documents, currency differences, tax coding gaps, late journals, and settlement differences.
With Continuous Monitoring (Reconciliation), finance teams can review open items before the close deadline and assign them to entity controllers, shared services, tax, treasury, or consolidation owners. This supports cleaner close execution because unresolved items are visible by company code, account, document reference, owner, and aging bucket.
Role in Close, Audit, and Consolidation
SAP intercompany reconciliation is important during month-end and quarter-end close because unmatched related-party balances can affect company code reporting, group eliminations, and consolidated financial statements. Clean matching helps ensure that internal receivables and payables offset correctly and that internal income and expense are eliminated during consolidation.
It also supports Reconciliation External Audit Readiness by preserving document history, approval evidence, clearing details, account mappings, and adjustment explanations. During SAP migrations or conversions, Data Reconciliation (Migration View) helps confirm that historical intercompany open items, trading partner data, and balance mappings remain accurate after the move.
Best Practices
Effective SAP intercompany reconciliation depends on clean master data, consistent posting rules, and clear accountability. Finance teams should define mandatory SAP fields, matching tolerances, ownership rules, exception categories, and escalation timelines before close begins. A Reconciliation Governance Committee can also help standardize policies across entities and review recurring control themes.
Require company code, trading partner, account, currency, tax code, and document reference on intercompany postings.
Review aged open items by company code pair, currency, account, and owner.
Apply Reconciliation Continuous Improvement to recurring mismatches and master data gaps.
Review Intercompany Profit in Inventory where inventory transfers require consolidation adjustments.
Document clearing entries, reclasses, timing items, and approved differences for close sign-off.
Summary
SAP intercompany reconciliation confirms that related-party transactions recorded across SAP company codes are matched, supported, approved, and ready for close and consolidation. It connects company code data, trading partner coding, account mapping, exception handling, and audit evidence into one controlled review. When managed consistently, it improves cash flow visibility, close quality, financial reporting accuracy, and consolidation confidence.
