Make intercompany balances tie out before close, not during it.
Aurum pulls intercompany balances from every entity's ledger, matches both sides of each transaction across currencies and charts of accounts, and separates timing differences from genuine imbalances, so your entities stop arguing about whose number is right. Close faster, eliminate cleanly, and evidence every intragroup position.
52
separate reconciliations configured
4 hours
saved daily
>90%
decrease in time spent on reconciliation
Why now
Intercompany balances are now a tax and audit exposure, not just a close problem.
Three shifts have moved intercompany from a housekeeping task to a scrutinised one. OECD Pillar Two global minimum tax rules require reliable entity-level data. Transfer pricing scrutiny has intensified, with BEPS Action 13 Master File and Local File documentation expected to describe the legal arrangements behind each category of intragroup transaction. And e-invoicing mandates are expanding across jurisdictions, pulling intercompany invoicing into the tax reporting perimeter.
An unexplained intragroup difference used to be an inconvenience your team netted off at consolidation. Now it is a number a tax authority may ask you to defend, and a difference you cannot evidence is a difference you cannot defend.
Before and After
Manual Intercompany Reconciliation vs Automated with Aurum
Start now with 6000+ systems already integrated, including multiple ERPs and general ledgers



Why automate your intercompany reconciliation?
Intercompany problems are structural, not arithmetic. Entities post at different times, in different currencies, on different charts of accounts, in different systems, and the differences surface at exactly the moment you have no time to investigate them. Here's what changes when Aurum does it for you.


Stop chasing timing differences
Entity A posts an invoice this period, Entity B posts it next. That's not an imbalance, it's a calendar. Aurum holds known timing differences back until they mature, so your dispute list contains only differences that genuinely need explaining.

Reconcile across currencies without arguing about rates
Every balance carries its original, accounting and reporting currency amounts in parallel, with the rate applied recorded alongside. When two entities book the same transaction differently, the difference is visible and explainable rather than a mystery.


One structure for your whole group
Configure your group hierarchy once, from parent through subsidiaries and business units, and set matching rules, calendars, tolerances and exchange rates at whichever level makes sense. Everything below inherits it, so you override only where an entity genuinely differs.

Give every difference an owner in both entities
Imbalances become cases with named owners on each side, a full comment history and attached evidence. The conversation happens on the item rather than across two inboxes and a call, and what was agreed is recorded.


Arrive at close with balances that already agree
Run reconciliation continuously through the period rather than at the end of it, so intragroup balances tie out before consolidation begins and elimination becomes mechanical rather than investigative.
How does Automated Intercompany Reconciliation work?
Multi-entity groups see real value from automating intercompany reconciliation with Aurum.
“What does Aurum deliver? Data visibility, standardisation and centralisation of processes. Ultimately, what used to take a number of individuals a whole day to complete, now takes one person half a day at the end of the month.”
What Aurum reconciles between your entities
Intercompany is not one transaction type. Each carries its own matching obligation, and each has to reconcile to zero on elimination.
Due-to and due-from balances
Reconcile intercompany receivables in one entity against payables in the other, across every pair in the group, so the balance sheet nets cleanly.
Intragroup sales and purchases
Match sales recorded by the selling entity against purchases recorded by the buying entity, including differences created by cut-off and shipping terms.
Intercompany loans and interest
Reconcile principal balances and accrued interest between lender and borrower entities, across currencies and rate schedules.
Management fees and cost allocations
Match charges raised by a parent or shared service centre against the amounts recognised by receiving entities, so allocations don't sit unrecognised on one side.
Inventory transfers
Reconcile stock moved between entities at transfer prices, including quantities in transit at period end.
Dividends and capital contributions
Match distributions and capital movements between entities so equity and reserves reconcile at group level.
Why multi-entity groups choose Aurum

Every ERP, one reconciliation
Groups rarely run one system. Aurum reconciles across multiple ERPs, general ledgers and accounting platforms without requiring you to consolidate systems first, so acquisitions don't have to be migrated before their balances can be controlled.


Multi-entity and multi-currency by design
Separate legal entities, each with their own rules, calendars, charts of accounts and currencies, reconciled in a single run with one consolidated view across the group.

Built for multi level control
Configurable approval chains, reason codes and case routing mean intercompany sign-off follows your governance, with segregation of duties enforced and every action logged for SOX and statutory audit.


Adapts as the group changes
New entities, restructures and acquisitions are configuration rather than a project. Add an entity to the hierarchy and it inherits the group's rules from day one.
See Product in Action
Automate your intercompany reconciliation with Aurum.
Book a demo to see how Aurum matches both sides of every intragroup transaction, separates timing from trouble, and delivers balances that already agree when consolidation starts.
Close faster
Eliminate cleanly
Multi-entity and multi-currency
Immutable audit trail
See the product in action
Trusted by hundreds of companies including
Related resources
Frequently Asked Questions
Intercompany reconciliation is the process of matching transactions between legal entities that share common ownership or control, so that both sides of each intragroup transaction agree before the group's accounts are consolidated. Because these transactions are internal movements rather than economic activity with third parties, they must be eliminated on consolidation. If they don't agree, elimination leaves a residual difference that overstates or understates group revenue, expenses, assets or liabilities.
The causes are structural rather than arithmetic. The most common is a timing difference: one entity posts an invoice in one period and the counterparty posts it in the next, leaving the ledgers legitimately out of step. Others include currency translation mismatches, where two entities record the same transaction at different rates or on different rate dates; period cut-off differences; inconsistent charts of accounts or entity coding; differing accounting policies between entities; and straightforward data entry error.
An elimination is the consolidation entry that removes an intragroup transaction from the group accounts, so that internal activity doesn't inflate consolidated results. A sale from one subsidiary to another is revenue for the seller and cost for the buyer, but from the group's perspective nothing has been sold externally, so both sides are removed. Eliminations only work cleanly if both sides already agree, which is why reconciliation comes first.
No. Aurum does the reconciliation work that has to happen before consolidation: pulling balances from every entity, matching both sides, categorising differences and getting them resolved with an audit trail. Your consolidation or ERP system still performs the elimination and produces the group accounts. The value is that it receives balances which already agree, so eliminations are mechanical instead of a month-end investigation.
Aurum reconciles and evidences intercompany positions, and produces the adjustment journals that follow. It doesn't generate payment instructions or run multilateral netting across cash pools. If netting is a requirement, Aurum gives your treasury team reconciled, agreed balances to net from, which is usually the missing input rather than the netting itself.
Aurum reconciles intercompany transactions and surfaces variances between what was charged and what was recognised, including differences against the transfer price you expect. It doesn't calculate transfer prices or produce transfer pricing documentation. What it does provide is the evidenced, reconciled transaction record that transfer pricing documentation and Pillar Two reporting rely on.
Monthly is the common minimum, but the more useful answer is continuously. Reconciling through the period rather than at the end of it means differences are found while there is still time to correct them at source, so balances already tie out when close begins. Groups that only reconcile at period end tend to discover the same recurring differences every month.
It's the pair of balances recording an amount owed between two entities in the same group: a receivable, or due-from, in one entity's books and a corresponding payable, or due-to, in the other's. In a correctly reconciled group these are mirror images of each other and net to zero on consolidation.
Because it depends on other people. Most reconciliations are performed against an external source that simply arrives, whereas intercompany requires another entity, often in another country and time zone, to have posted the same transaction the same way. When it hasn't, resolution needs a conversation, and those conversations happen in the days you have least to spare.
Spreadsheets can hold the comparison but not the process. There's no automatic pull from each entity's ledger, no consistent mapping between charts of accounts, no record of who agreed what with whom, and no way to separate a timing difference from a real imbalance except by remembering. As entity count grows, the number of pairs to reconcile grows faster than the team, which is why intercompany is usually the first reconciliation to fall behind.
Single-ERP groups often can, at least while every entity is on the same instance and the same chart of accounts. The difficulty arrives with multiple ERPs, acquired entities on legacy systems, or local statutory ledgers, because the ERP can only reconcile what sits inside it. Aurum works across all of them without requiring system consolidation first, and extends your ERP rather than replacing it.





