Intercompany reconciliation
Intercompany reconciliation software: closing the gap at source
Intercompany reconciliation software matches receivables and payables between group entities, explains every difference by counterparty and period, and clears the mismatches before consolidation. Done properly it removes one of the most persistent and least valuable sources of manual effort in the monthly and annual close process.
Intercompany differences rarely come from one dramatic error. They accumulate from timing differences, currency translation, partial postings, credit notes booked on one side only, and charges that were agreed in policy but never invoiced. Each is small, but together they create a balance that nobody can explain under audit pressure.
Automating the match changes the economics of the close. Instead of two teams emailing schedules back and forth, the system pairs transactions, isolates the unmatched residue, attributes it to a cause, and hands finance a short, actionable list. The work moves from finding differences to deciding what to do about them.
What automated intercompany reconciliation actually removes
The value is not simply speed. Automating the match removes categories of work and categories of risk at the same time, because differences are surfaced in the period they arise rather than being carried forward and compounded into a year-end balance that requires forensic effort to unwind and explain.
Manual schedule exchange
Entities stop sending each other spreadsheets. Both sides read from the same matched dataset, so the discussion starts from an agreed position rather than from two versions of the truth that first have to be aligned before anyone can even begin to identify where the genuine difference actually sits.
Unexplained closing balances
Every remaining difference carries a reason: timing, currency, missing invoice, or posting error. That turns a single opaque number in the consolidation into a short list of specific items with owners, which is exactly what an auditor expects to see when they test intercompany balances at year end.
Year-end surprises
Differences are caught in the period they arise, when the underlying documents are still fresh and the people involved still remember the transaction. Resolving a mismatch two weeks after it happens costs a fraction of resolving the same mismatch eleven months later during a statutory audit.
Consolidation rework
Because balances agree before they reach the consolidation, elimination entries stop generating late adjustments. Group reporting runs on a clean intercompany position, which shortens the close calendar and reduces the number of last-minute journals that need review, approval and separate explanation to auditors.
Checklist
Signs your intercompany reconciliation needs automating
- Entities exchange reconciliation spreadsheets by email every period
- The consolidation carries an intercompany difference nobody can fully explain
- Differences are only investigated seriously at year end
- Currency and timing effects are untangled manually each month
- Auditors routinely raise intercompany balances as a review point
- Nobody can say how much finance time the process consumes
Use cases
Where reconciliation automation pays back fastest
Groups with many entities transacting bilaterally in several currencies
Shared service centres invoicing a large number of receiving entities
Groups tightening the close calendar after an acquisition
Finance teams preparing for a first statutory group audit
Frequently asked
Common questions
How is this different from our ERP's intercompany module?+
ERP modules typically match on document reference and stop there. The remaining residue, which is where the effort actually sits, is left to finance. Dedicated tooling matches on multiple attributes, attributes each unmatched item to a cause, and gives you the explanation rather than simply confirming that a difference exists.
Do both entities need to use the same system?+
No. The reconciliation runs on ledger extracts from each side, so entities can remain on different systems or charts of accounts. That matters for groups that have grown through acquisition, where harmonising ERP platforms is a multi-year programme and the reconciliation problem needs solving well before then.
Does it handle currency differences?+
Yes. Translation differences are identified and separated from genuine posting mismatches, so a balance that only differs because of rate movement is not investigated as an error. That single distinction typically removes a large share of the items finance teams currently chase manually every reporting period.
What does it need from us to get started?+
A ledger extract of intercompany transactions from each entity and your entity structure. From there the matching logic is configured to your posting conventions, and you get a first reconciliation run to review, which usually surfaces long-standing differences that had been quietly carried forward for several years.
Run a first reconciliation on your own data
We can take an extract of your intercompany transactions and show you the matched position, the unexplained residue, and what is driving it. Most groups find something in that first run that had been carried forward unnoticed for years, and it takes a short call rather than a full implementation project.