What makes intercompany reconciliation hard to automate
Intercompany reconciliation is the step most groups do by hand. What actually blocks automation, and what it takes to get past each one.
Intercompany reconciliation means ensuring that transactions between entities within a corporate group are accurately recorded and reconciled. Automating this process promises efficiency and accuracy, but it is not without its hurdles. At FINAHQ, we specialise in both itemised and summary-level reconciliation, and we have an established track record of navigating the complexities of ICO automation to support our clients effectively. Here are the practical challenges and considerations in implementing a fully automated ICO reconciliation process.
What ICO automation actually requires
Automating ICO reconciliation needs more than sophisticated software. It demands a structured approach covering the following:
Ledger-level integration with your ERP system. Effective automation hinges on the ICO reconciliation tool integrating smoothly with your existing ERP system, so data flows consistently and in real time across platforms.
A clearly defined GL structure for ICO transactions. A well-organised general ledger structure is essential. Each type of ICO transaction — whether the sale of goods, royalty income, or brand income — needs to be clearly identified and mapped to specific GL codes.
Identification and mapping of ICO transaction types. Differentiating and correctly mapping the various ICO transaction types to their respective GL codes is critical for accurate reconciliation.
Resolution of mismatches through the tool. The ability to identify and resolve mismatches is a cornerstone of automation, using rules capable of pinpointing discrepancies and suggesting resolutions.
Posting ICO journal entries at the end of the process. Once all transactions are reconciled, the system should automate the posting of ICO journal entries, so your financial records stay up to date and accurate.
Practical considerations in ICO automation
Take a typical scenario: a common cost recharge, such as executive salaries or brand expenses charged to subsidiary companies.
Clear GL structure. Success in ICO automation starts with a clear GL structure in both the entity incurring the expense and the subsidiary bearing it. If a non-unique GL code is used, automation becomes nearly impossible, since the system relies on understanding the nature of the GL to build matching rules.
Easiest transactions to match. Sale and purchase transactions are the easiest to reconcile — they have clearly identified counterparties and dates, which gives high confidence in the reconciliation.
Accrual transactions. The real challenge lies with accruals. Often the recharging entity posts a single consolidated accrual, while the receiving entities post accruals for their own portion of the charge. This causes mismatches unless accruals are posted at an itemised level, which lets the tool perform amount-based matches with moderate confidence.
Accrual reversals. Another issue arises with reversals: if accruals are posted itemised but reversed as a single consolidated adjustment, mismatches occur and complicate the reconciliation.
Identifying root causes. Even with itemised accruals, discrepancies can arise from unaccounted credit notes, incorrect GL codes, or unposted accruals. The next step is matching these unmatched transactions across ledgers, so ICO adjustments can be posted.
Structured resolution of mismatches. Resolving mismatches needs a structured approach: the tool flags them, and they are then reconciled by correcting the ledger or matching journals manually across group entities.
Generation of ICO journal entries. Once mismatches are resolved, the tool can generate ICO journal entries, for a streamlined and accurate reconciliation.
Full automation of ICO disclosures. Full automation also supports completing related-party disclosures for subsidiary financial statements, except for specific items such as managerial remuneration or corporate guarantees.
Understanding ledger integration, GL structure, transaction mapping and mismatch resolution is essential to a reliable, automated ICO reconciliation process — and gets you real gains in accuracy and efficiency in your intercompany transactions.
Why FINAHQ
At FINAHQ, we understand the intricacies of accounting systems and processes. What sets us apart is not just the infrastructure, but our ability to tailor our systems to your entity’s specific accounting practices. We work closely with you towards full automation, making ICO reconciliation a straightforward, low-effort process.
By addressing these practical considerations and drawing on our experience, you can navigate the challenges of ICO automation effectively. Reach out to us at FINAHQ to talk through your own intercompany reconciliation.
Part of Intercompany. Matching balances between group companies, the eliminations that follow, and the transactions that never match on the first pass.
Questions
Commonly asked
What does intercompany automation actually require?
More than software. It needs an agreed matching convention across entities, data arriving in a shape that can be matched, and a rule for what happens when two sides disagree — decided before the close, not during it.
What is the difference between itemised and summary-level reconciliation?
Itemised matches transaction to transaction; summary matches balances between counterparties. Itemised finds the cause of a difference, summary only finds that one exists. Most groups need both, at different points in the cycle.
What happens to a difference that will not reconcile?
It is parked in a control account and flagged, not hidden and not blocking. The close carries on; the difference stays visible and named until somebody resolves it.
Related
Living with a purchase price allocation after year one
Subsequent measurement of a purchase price allocation is underestimated: the entries carry for years, and each one has to be justified again.
Intercompany transactions in a group that keeps acquiring
Elimination entries are a key adjustment to consolidated statements, and an acquisitive group changes which ones are needed every year.
Unusual intercompany transactions: sub-leases and ESOPs
Two intercompany transactions that do not eliminate the way the others do, and what each one leaves behind in the consolidated numbers.