Intercompany differences are often treated as a consolidation-team problem. In reality, they usually begin much earlier: a missing trading-partner code, an invoice posted in one entity but not the other, a different exchange-rate basis, a late goods receipt, an unrecorded service charge, or a correction entered after one entity has closed its books.
When these items remain unresolved until group close, Finance loses time investigating old transactions, posting manual adjustments and explaining why local ledgers do not agree. A disciplined intercompany reconciliation process moves the work upstream. It creates clear ownership between trading partners, identifies differences while there is still time to correct them, and gives the controller evidence that balances and eliminations are complete.
This guide sets out ten practical controls for US and Canadian groups, including organizations using SAP S/4HANA. It also explains why the reporting framework matters: US GAAP, IFRS and Canadian ASPE do not prescribe identical approaches to subsidiary reporting.
Why intercompany reconciliation matters
Intercompany activity can include product sales, management fees, shared-service charges, royalties, interest, loans, dividends, cost recharges and cash-pool transactions. Each transaction may create a receivable in one company and a payable in another, or income in one company and expense in its trading partner.
For consolidated financial statements, intragroup activity generally cannot remain as if the group had transacted with an outside party. Under US GAAP, ASC 810-10-45-1 requires intra-entity balances and transactions to be eliminated in consolidation. IFRS 10 requires a parent that controls subsidiaries to present the group as a single economic entity and its consolidation procedures include eliminating intragroup balances and transactions in full. The underlying accounting must still be correct in each entity before elimination entries are posted.
Understand the reporting framework
US GAAP
The FASB Accounting Standards Codification is the authoritative source of nongovernmental US GAAP. For entities preparing consolidated financial statements, ASC 810-10-45-1 addresses elimination of intra-entity balances and transactions, including open account balances, sales, purchases, interest and dividends. Intercompany profit remaining in assets such as inventory or fixed assets also requires attention; eliminating the receivable and payable alone does not remove unrealized profit from the group’s assets.
IFRS
IFRS 10 establishes control as the basis for consolidation. Consolidated statements present the parent and subsidiaries as one economic entity, and intragroup assets, liabilities, equity, income, expenses and cash flows are eliminated in full. Uniform group accounting policies and consistent reporting data are important before consolidation adjustments are run. See the IFRS Foundation’s IFRS 10 overview.
Canadian ASPE
Canadian private enterprises must consider the policy choices in Section 1591, Subsidiaries. Depending on the circumstances and the selected policy, an enterprise may consolidate subsidiaries or account for certain subsidiaries using the cost or equity method. If it prepares non-consolidated financial statements using the cost or equity method, Sections 3840 and 3856 apply to intercompany transactions that would otherwise have been eliminated on consolidation, as relevant. Section 3840 addresses related-party transactions, including measurement of certain non-financial items and disclosure. It is therefore important to identify whether the reporting package is consolidated or non-consolidated before applying an elimination workflow. See BDO’s Section 1591 summary and its Section 3840 summary, updated July 2026.
Ten controls to strengthen the intercompany close
1. Maintain a controlled trading-partner master
Assign a unique trading-partner identifier to every legal entity and maintain a centrally governed entity-to-entity mapping. Validate partner codes in customer, vendor, general-ledger and consolidation master data. Restrict who can create or change the mapping, require approval, and test the impact before changes move into production. A blank or incorrect partner code can make a valid transaction difficult to match.
2. Agree common transaction and reference standards
Define minimum data fields for intercompany documents: sending and receiving entity, transaction currency, invoice or agreement reference, document date, posting period, transaction type and relevant purchase-order or project reference. Use consistent naming and reference conventions across entities. Where systems differ, map source fields to a common group format and retain the original document identifier.
3. Reconcile before the group close deadline
Set an intercompany timetable that starts before local close. Require each entity to submit its trading-partner balances and transaction detail by an agreed date, then give counterparties time to confirm or dispute items. Run preliminary matching during the month where volumes justify it. Do not wait until consolidation is ready to discover that two entities have not communicated.
4. Match at transaction level, not only by net balance
Use invoice, document, purchase-order or settlement references to match the underlying items. A net balance comparison can conceal offsetting errors—for example, one missing invoice and one duplicate invoice. Retain the matched population, unmatched population, matching rule and reviewer evidence. Define tolerances carefully and investigate recurring small differences rather than allowing them to accumulate.
5. Investigate timing and cutoff differences
Common timing issues include goods shipped but not received, services delivered but not invoiced, invoices posted in different periods, and credit notes entered by only one side. Ask both entities for the supporting documents and establish which period should recognize the transaction under the applicable accounting policies. Use a controlled in-transit or accrual process where appropriate, with a named owner and automatic follow-up in the next period.
6. Separate transaction-currency matching from translation effects
For cross-border balances, compare the underlying transaction in its transaction currency where possible, then separately assess local-currency and group-currency translation. A US entity’s USD functional-currency ledger and a Canadian entity’s CAD ledger may show different translated amounts even when the original invoice is correctly recorded. Do not create an unexplained plug to force local-currency balances to agree. Document the exchange-rate source, rate date and any genuine settlement or remeasurement difference.
7. Reconcile income and expense as well as receivables and payables
Balance-sheet matching alone is not enough. Match intercompany revenue to the counterpart’s expense or inventory purchase, and match interest income to interest expense. Investigate differences caused by markup, freight, rebates, tax or service allocation. For inventory and fixed-asset transfers, identify whether an unrealized intercompany profit remains in the asset at period end and whether a consolidation adjustment is required under the reporting framework.
8. Control correction postings and eliminations
Require the entity that owns the error to correct its books where practical. Define when a group-level consolidation adjustment is appropriate and who approves it. Separate preparation and approval, attach the reconciliation and supporting evidence, and record the reason, period, entities and reversal or follow-up requirement. Prevent recurring manual journals from becoming a substitute for fixing source-system data.
9. Monitor aged differences and settlement items
Produce an aging report by entity pair, currency, transaction type, amount and age. Assign each material difference to an individual in the sending and receiving entities. Track whether the item is awaiting an invoice, credit note, cash settlement, accounting correction or management decision. Escalate items that exceed defined age or value thresholds and report repeat causes to the controller.
10. Lock the reconciliation only after review and approval
Before close certification, confirm that all material entity pairs have been reconciled, differences are resolved or formally accepted, and late postings are captured. Restrict reopening of a closed period or reconciliation cycle to authorized users. If new documents arrive after close, route them through a controlled late-adjustment process and assess whether the consolidation must be rerun.
How SAP can support the process
SAP documentation describes Intercompany Reconciliation functionality that supports G/L open-item reconciliation, G/L account reconciliation and customer/vendor open-item reconciliation. Its process includes data selection, data assignment, reconciliation, communication and correction posting. SAP also describes Intercompany Matching and Reconciliation capabilities in SAP S/4HANA Group Reporting, including configurable matching rules, line-item matching, status monitoring and workflows for differences.
These capabilities can improve visibility, but they do not replace control design. Confirm which product, release and scope your organization has licensed and implemented. Validate partner mappings, matching rules, tolerance thresholds, user roles, background jobs, exception queues and audit logs. Test whether a document posted after a reconciliation run is included in the next run, and whether closed periods prevent or flag late data as intended. See SAP’s Intercompany Reconciliation documentation and SAP S/4HANA Intercompany Matching and Reconciliation overview.
Example: a US–Canada inventory transaction
A US distribution company invoices its Canadian subsidiary for inventory in US dollars. The US entity records the sale and receivable. The Canadian entity records the purchase and payable, but the invoice is received after its local close and is posted in the next period. At group close, the receivable and payable do not match, and the inventory may already have been received or sold.
The reconciliation owner should identify the invoice using the trading-partner code and shipment or purchase-order reference, obtain proof of shipment and receipt, determine the appropriate cutoff in each ledger, and record any required correction in the correct entity and period. The team then assesses the inventory and any unrealized intercompany profit for consolidation. Only after these steps should the elimination be finalized. A manual consolidation plug would hide the timing issue without fixing the underlying records.
Month-end controller checklist
| Review item | Evidence |
|---|---|
| Entity and trading-partner master data are complete | Approved master-data change log and exception report |
| Material balances are matched by entity pair and currency | Transaction-level reconciliation and counterpart confirmation |
| Cutoff and in-transit items are assessed | Invoices, shipment/receipt evidence and accrual schedule |
| Income and expense differences are investigated | Revenue/expense matching report and variance explanations |
| Unrealized profit is evaluated | Inventory/fixed-asset rollforward and consolidation calculation |
| Corrections and eliminations are approved | Journal support, approval and posting reference |
| Aged differences and late postings are escalated | Aging dashboard, owner, due date and close certification |
Conclusion
Reliable intercompany reporting is built through disciplined transaction data, early matching, clear ownership and timely correction—not through last-minute elimination journals. Controllers should measure not only whether balances match, but also how quickly differences are resolved, how often the same causes recur and whether the final consolidation is supported by traceable evidence. With a controlled process and properly configured SAP capabilities, intercompany close can become more predictable, transparent and audit-ready.
Disclaimer: This article is for general informational purposes only and is not accounting, legal or tax advice. Apply the current authoritative guidance relevant to the reporting entity, reporting period and facts, and consult qualified advisers for complex arrangements.
Sources and further reading
- FASB — Accounting Standards Codification, the authoritative source of nongovernmental US GAAP.
- IFRS Foundation — IFRS 10 Consolidated Financial Statements.
- BDO Canada — Section 1591, Subsidiaries.
- BDO Canada — Section 3840, Related Party Transactions (updated July 2026).
- SAP Help Portal — Intercompany Reconciliation.
- SAP Learning — Intercompany Matching and Reconciliation overview.
