Blog
Written by

Naman Mathur
Published on

Key Takeaways
Intercompany reconciliation agrees each entity pair at transaction level before consolidation, because eliminations can only remove balances that already agree.
To test an AI claim, rerun one match twice and expect identical output, with an explanation a reviewer can check behind every suggested match.
Shortlist by entity count, enterprise resource planning (ERP) landscape, controls regime and where your close days are lost.
If unmatched intercompany value at day 1 hasn't fallen after two closes, the tool isn't touching your real bottleneck.
The mistake we see most often with intercompany reconciliation software is buying an eliminations engine, when the days are lost upstream in matching. Eliminations take minutes once both sides of each entity pair agree.
For multi-entity companies, that turns one purchase into two decisions: which layer to automate, and which vendor to trust. Our guide on what to automate and how to choose covers the criteria, and this article covers who belongs on the shortlist.
Standard shortlist advice compares feature lists on clean demo data, where every reference matches. Your ledgers look different, so compare vendors on your own breaks.
Below, we cover what intercompany reconciliation is, why it breaks, which AI tools lead, and which software suits a multi-entity group.
What Is Intercompany Reconciliation and How Does It Work?
Intercompany reconciliation is the check that what one company in a group booked against another matches what the other booked in return. If the UK entity records a £50,000 receivable from its Swedish sister company, the Swedish entity should show the matching payable. Once both sides agree, consolidation removes them, so the group accounts show only dealings with outside parties.
Reconciliation and consolidation are separate jobs, and elimination under International Financial Reporting Standards (IFRS) depends on reconciliation finishing first. IFRS 10 paragraph B86(c) requires groups to "eliminate in full intragroup assets and liabilities, equity, income, expenses and cash flows relating to transactions between entities of the group". A consolidation tool performs that step, but it can't tell you why a pair disagrees.
The Five Steps: Recording, Matching, FX, Eliminations and Settlement
Each transaction passes through five steps, including a foreign exchange (FX) check, between booking and cash.
Step | What happens | Where it breaks |
|---|---|---|
Record | Entities book recharges, management fees and loans | One side books late, or to the wrong counterparty |
Match per pair | Each transaction is matched to its counterpart | Pairs agree in total while transactions disagree |
Apply FX tolerance | Differences within rate policy are accepted and adjusted | Entities translate the same item at different rates or dates |
Eliminate | Agreed balances are removed in consolidation | Differences are forced into suspense |
Net and settle | Balances are netted and paid | Cash moves before items agree |
Source: Stacks implementation practice, 2026.
Most groups lose their time at the matching step. A pair can net to zero while a missing recharge offsets an unrelated interest error, so match at transaction level.
Currency adds differences on intragroup monetary items, governed by International Accounting Standard (IAS) 21. Under IAS 21 paragraph 45, these "cannot be eliminated against the corresponding intragroup liability (or asset) without showing the results of currency fluctuations".
Transfer pricing is a separate tax lens on the same transactions, with guidance from the Organisation for Economic Co-operation and Development (OECD). The OECD Transfer Pricing Guidelines call the arm's length principle "the international consensus on the valuation of cross-border transactions between associated enterprises".
Why Does Intercompany Break Down for Multi-Entity Companies at Month-End?
In most groups we work with, intercompany still runs on comma-separated values (CSV) exports emailed to group and pasted into a spreadsheet matrix.
A recharge booked by the UK on 30 September and by the Netherlands on 2 October lands in different periods. Entities translate at different rates, some items are booked on one side only, and others carry the wrong counterparty code.
The work grows faster than the group: ten entities give 45 possible pairs, and 40 entities give 780.
Each acquisition adds a ledger with its own numbering. Recharges also flow outside the ERP, through payroll, Coupa purchase orders or Pleo expenses. Our guide to running reconciliations across entities at scale covers how to handle entity pairs across mixed ledgers.
What Are the Leading AI Tools for Intercompany Accounting?
The leading AI tools for intercompany accounting include AI-native platforms such as Stacks, and established suites that have added AI agents to their intercompany modules, such as HighRadius and BlackLine [VERIFY: whether Trintech, Lucanet and OneStream market AI for intercompany matching as of November 2026]. What separates them is whether they match on live ledger data, learn from reviewer decisions and log the audit trail as work happens.
Legacy suites and spreadsheets still depend on rules written for each pair.
Capability | Legacy suite or spreadsheet | AI-native platform |
|---|---|---|
Matching cadence | Batch, after month-end exports | Continuous, on live ledger data |
Exceptions | A list of unmatched items | Open differences shown down to the transaction, with an explanation for each suggested match |
Corrections | Journal keyed by hand | Adjustment pre-filled with the difference, posted to the ERP on approval |
Audit trail | Rebuilt from emails | Logged as work happens |
Source: Stacks implementation practice, 2026.
Test AI claims directly. Ask the vendor which outputs are deterministic, such as the match itself, and which are generated, such as an explanation or a draft journal.
Then rerun one match on the same data, because a control needs the same answer twice. To see how matching connects to creation, netting and eliminations, read our overview of the full intercompany automation lifecycle.
What Is the Best Intercompany Reconciliation Software?
The best intercompany reconciliation software depends on how many entities and ledgers you run, and on where your close days are lost.
Competitor capabilities come from each vendor's own pages, reviewed November 2026. The order is not a ranking, and the fit guidance is our view.
Stacks
Stacks is an AI-native close platform that matches intercompany transactions continuously on live ERP data, with balances shown in an entity matrix. Stacks Intercompany connects natively to NetSuite, Microsoft Dynamics 365 Business Central and SAP, with other ERPs on request.
BlackLine
BlackLine's intercompany page sets out a "centralized global intercompany subledger" across multiple ERPs. BlackLine organises the work into modules for create, balance and resolve, and net and settle. In our view, it suits large global groups with dedicated close teams.
Trintech Cadency
Trintech positions Cadency as an enterprise record-to-report suite. The Trintech Cadency Intercompany page brings together recording, reconciliation and elimination "within a single solution".
HighRadius
HighRadius lists AI agents for intercompany accounts receivable (AR) and accounts payable (AP), journals, netting and settlement. On its HighRadius intercompany management page, HighRadius states its agents "automate 80% of intercompany AR/AP reconciliations". That figure is vendor-reported.
Lucanet
Lucanet is a consolidation-led platform built around decentralised reconciliation by subsidiary. Its Lucanet intercompany reconciliation page covers matching "in group currency, transaction currency, or at the individual posting level".
OneStream
OneStream is a corporate performance management (CPM) platform. Its OneStream transaction matching page presents intercompany as one use case of a general matching engine. In our view, it suits groups that already run OneStream for consolidation.
ERP-Native Intercompany Modules
Native modules are the fair counterargument. On a single ERP instance, where both sides of each transaction are booked together, they often do the job.
They help less once the group is mixed, with NetSuite, SAP or Dynamics at head office and Sage, Exact, Visma, Unit4 or Fortnox in subsidiaries.
Vendor | Our view of best fit | What to check |
|---|---|---|
Stacks | Multi-entity groups on NetSuite, Dynamics 365 Business Central or SAP | Match rate on your last close |
BlackLine | Large global groups | Which modules your scope needs |
Trintech Cadency | Record-to-report suite buyers | Handling of references that differ by entity |
HighRadius | Heavy intercompany AR and AP volume | How the 80% figure was measured |
Lucanet | Consolidation-led groups | Subsidiary-level resolution before consolidation |
OneStream | Existing OneStream users | Intercompany workflow beyond general matching |
ERP-native modules | One ERP, one currency | What happens when a second ledger arrives |
Source: competitor product pages, November 2026; fit guidance is our view, 2026.
What Is the Best Intercompany Accounting Software for Multi-Entity Companies?
The best intercompany accounting software for multi-entity companies is the one that fits your entity count, ERP landscape, currency mix and control requirements. A five-entity group on one ledger needs far less than a 40-entity group on four.
A group on one ERP and one currency is usually well served by its native module. Once a second ledger or currency arrives and close days go on agreeing pairs, shortlist a dedicated matching layer such as Stacks. Large global groups with a dedicated close team tend to look at BlackLine or Trintech Cadency, and groups whose bottleneck is consolidation at Lucanet or OneStream.
Provision 29 of the UK Corporate Governance Code 2024, which applies to financial years beginning on or after 1 January 2026, asks boards to declare whether material controls were effective. The Financial Reporting Council (FRC) sets out the scope in its FRC Provision 29 mythbuster. US-listed groups face a related requirement under the Sarbanes-Oxley Act (SOX). Either way, the evidence behind each intercompany match and correcting journal is in scope, which is what the last two tests below check.
Test | How to run it | What good looks like |
|---|---|---|
Own last close with known breaks | Load a closed period with breaks you already know | Every known break found and explained |
Match rate without new rules | Run matching before the vendor writes rules | Most pairs match, and every open difference traces to its transactions |
Two ERPs live | Connect two different ledgers | Both sides of each pair in one view, without exports |
FX break outside tolerance | Book one item outside policy tolerance | Flagged for review, with the difference ready to adjust |
Audit trail export | Export the trail for one entity pair | Preparer, reviewer and timestamp on every match |
Segregation of duties on corrective journals | Prepare and approve one journal as the same user | The system blocks it |
Source: Stacks implementation practice, 2026.
Why the Standard Advice Fails
The standard advice is to standardise your intercompany policy, then buy an eliminations module. Agreed cut-off dates and rate sources do remove a class of breaks, but neither step touches the mismatches upstream.
An eliminations module removes balances that agree, and when they don't, the close date waits for someone to explain the difference. We regularly meet groups that bought this layer and still spend the first week agreeing pairs by email.
Rules-based matching also decays. Rules key on references, which change when an entity switches bank or joins with its own numbering. Match rates then slide until someone rewrites the rules.
Outside the single-ERP case, fix matching first. Track unmatched intercompany value at day 1 of the close, because in our experience that number tells you how long agreement will take.
How to Pilot Intercompany Software on Your Own Close
Prove the tool on your own breaks over two closes. Our guide to piloting an agentic close platform covers the wider set-up.
Record a baseline of unmatched intercompany value at day 1, working days to agree balances and breaks aged over 30 days.
Connect read-only to the ledgers in scope, so nothing posts to the ERP during the pilot.
Run a parallel close for two consecutive periods alongside your current process.
Run the FX break and audit trail export tests from the table above on live data, and have your auditor sample the trail.
Compare baseline measures after two closes and decide on the numbers.
Why Choose Stacks for Intercompany Reconciliation
Stacks is built for the matching layer that sets your close date. Stacks intercompany automation software shows every balance in a real-time entity matrix and suggests matches with an explanation.
When a pair differs, Stacks flags differences that may come from exchange rates for review and pre-fills the adjustment with the difference. Your team selects the accounts and posts the adjustment back to the ERP. Both entities' teams work the same item.
Our AI matching for account reconciliations reaches match rates above 95%, against the 70–75% we typically see from rules-based tools (Stacks product data, 2026). Stacks Intercompany uses the same matching approach [VERIFY: confirm with product].
Volt reached 95%+ auto-matching of transactions in its first month and 97% by its third close, with its monthly close 3 days shorter [VERIFY: year]. Read how Volt reached 97% auto-matching.
Nivoda runs 13 entities and more than 130 bank accounts on NetSuite. Nivoda's close went from more than 20 days to 12 [VERIFY: year].
Epidemic Sound signed with us on 29 August 2025 and ran its first close in Stacks on 6 October 2025: 713 tasks across 102 bank accounts and 13 legal entities, at 100% completion [VERIFY: case study URL].
We ran an intercompany masterclass with Sara Scott, Group Accounting Lead at Bloom & Wild, on why totals can balance while individual accounts still differ.
Stacks holds a System and Organization Controls (SOC) 2 Type II report and ISO 27001:2022 certification. It complies with the General Data Protection Regulation (GDPR) and runs SOX-ready controls, set out in the Stacks close management security controls.
FAQs for Intercompany Reconciliation Software
What Is the Difference Between Intercompany Reconciliation and Consolidation?
Reconciliation agrees each entity pair's bookings during the close, and consolidation then combines the entities and eliminates the agreed balances.
Can AI Handle Intercompany Reconciliation Matching?
Yes, provided each match is repeatable and carries evidence a reviewer can check, with your team approving exceptions and journals.
How Does Intercompany Reconciliation Software Reduce Audit Risk?
It logs preparer, reviewer and timestamp on every match and journal as work happens, so auditors sample live evidence instead of rebuilt spreadsheets.
How Much Does Intercompany Reconciliation Software Cost?
Pricing generally scales with entities, accounts and modules, so ask each vendor to quote against your real numbers.
Can Xero or QuickBooks Handle Intercompany Transactions?
In our experience, groups on Xero or QuickBooks set up one organisation per entity and handle intercompany manually or through add-ons. That holds up for a few entities and breaks down as pairs multiply.
When Should a Group Invest in Intercompany Reconciliation Software?
Invest when a second ERP or currency enters the group, or when agreeing balances regularly delays the close.
See How Stacks Maps to Your Close Process
Book a 30-minute walkthrough. We'll discuss your close process, show you which tasks run automatically, and outline the next step from there.
"Stacks has transformed how our finance team operates... it's saved us time and reduced frustration."
Graham B., SVP of Finance at Volt
Trusted by fast-growing companies including: Datavant, Future, Cleo, Motorway, Nivoda, Yoto and Epidemic Sound.

