WorkflowFinancial Close & Account Reconciliation

Intercompany Reconciliation

Intercompany reconciliation where every difference is explained, trued up at source and approved by both sides, with no top-side plug

See one case, screen by screen ↓
Watch with transcript →

Built forGroup controllersEntity controllersConsolidation accountantsTransfer pricing managers

The Problem Today

Group companies book each deal twice, and when the two sides disagree, the gap ends as an unexplained plug at the lock.

4 days
a quarter, chasing each break with two controllers our estimate

Exported to spreadsheets by hand

  • Ledgers
  • Rates
  • Agreements
  • Invoices
  • Two controllers, both sureEach believes their own books are right
  • Which side should change?Nobody can prove it before the books lock

The Solution

  1. Each pair matched overnightIntercompany lines from each ledger read and paired, side by side
  2. The cause found and provedExchange rate, timing, price or tax, proved from ledger and document
  3. The wrong side correctedThe agreement decides which side adjusts; the fix is drafted there
  4. Both controllers approveEach side approves with a reason code; the group signs off large ones

Built-in controls

  • Nothing posted or plugged automatically
  • Unclear causes go to a named person
  • Separated duties and a trail that cannot change

What You Get

Consolidation locks with fewer open differences, and each one left has its support ready when the auditor asks.

  • Eliminations proven before the lockAn independent re-check shows each pair nets, or who owns it
  • The big money firstThe few pairs that hold most of the gap are worked first
  • Treasury nets agreed balancesInvoices from open pairs held until both sides approve
In short

What is Intercompany Reconciliation?

Intercompany reconciliation is matching the balances and transactions two companies in the same group hold with each other (receivable against payable, revenue against cost, loan against borrowing) and resolving each difference so consolidation can eliminate them in full. Botminds Intercompany Reconciliation gives the work to eight agents that match each pair, find and cite why each one is out, and draft the true-up in the entity the agreement says is wrong, for both entity controllers to approve.

How to choose AI solutions for back-office and enterprise work →

Updated

The problem

Intercompany pairs that disagree, with no proof of which side is wrong

Each sale, recharge, loan and fee between two group companies is booked twice, once in each ledger, often in different ERPs and currencies. At close the receivable, the payable, the revenue and the cost must agree before consolidation can eliminate them in full. They rarely do. An accountant exports both ledgers to spreadsheets, finds the difference, and emails two entity controllers who each believe their own books are right.

The hard part is not finding that a pair is out; it is proving why, and which side should change. Was it the rate, goods or cash in transit, an invoice emailed and never loaded to the portal, the wrong trading partner, a markup amendment nobody put in the price list, withholding tax, a duplicate? When nobody can show which entity is wrong by the lock, the residual goes to a top-side adjustment in group reporting, and an unsupported plug is the first thing the auditor asks about.

typical9.2%of professionals polled call their intercompany framework leading
typical21.4%name disparate systems as the top barrier to intercompany accounting
typical6yearsor more that one group left its intercompany accounts unreconciled, in a 2008 SEC enforcement action
Where the intercompany close's working days goestimated
By hand10.5 days
With the solution1.5 days
  • Extracting intercompany balances from every ERP1 → 0.1 d
  • Matching receivable against payable, pair by pair3 → 0.1 d
  • Investigating each break with two controllers4 → 0.5 d
  • Agreeing which side adjusts and booking the true-up1 → 0.5 d
  • Eliminations and what is left at the lock1 → 0.2 d
  • Netting: sorting agreed from disputed invoices0.5 → 0.1 d

Estimated split for a quarter-end intercompany close in a group of about 60 entities, by hand and with the solution.

How it works

From a ledger line to a trued-up, eliminated intercompany pair

What comes in
Sources inevery group ledger · ERPs, portal, agreements, rates, banks
Agents at work
Ledger collectorread-only
Then
Matcherline by line
Break investigatorcause, cited
Then
Agreement readerwhich side is wrong
True-up drafternever posts
Then
Elimination checkernets to €0.00
Settlement planneragreed only
Close coordinatorasks and reminds
A person decides
Both entity controllersapprove with a reason code
What comes out
Approved true-up
Eliminations at €0.00
Evidence pack
One case, step by step

Intercompany reconciliation in the last two days before a quarter-end lock

The company closes the quarter across 62 entities. It is working day 10 of 11, and consolidation locks the next day at 12:00. Here is how the group controller and two entity controllers work with the agents, screen by screen, in the working solution.

A worked example on sample data. Names, IDs and figures on the screens and in this section come from the demo.

  1. 0107:00

    A morning briefing in place of a spreadsheet

    Group controller

    The group controller's home is a conversation with the agents. The close coordinator reports the night: 9,847 intercompany lines read from 18 ledgers and 9,611 matched; 354 pairs agree to the cent and 37 sit inside the €5,000 tolerance. 21 pairs are out: 16 with a true-up ready, 2 waiting on an answer, 3 that need a person. Below it, the break investigator puts the largest first, and each figure carries a numbered citation.

    “True-ups are due today at 17:00; consolidation locks tomorrow at 12:00.”

  2. 02Who is out with whom

    The pair map shows where the money is

    Group controller

    Each cell is one pair of group entities, net of everything both ledgers hold for the quarter: a tick when it agrees, “<5k” inside tolerance, or the difference with a dot sized by amount and colored by status. Three cells hold 63% of the money that is out. The group controller picks the pair of the US entity and the German entity (€212,025.89, FX rate, awaiting approval), and the agents' brief opens beside the map.

  3. 03Open the pair

    Two ledgers side by side, the break dashed

    Break investigator

    The US entity holds €14,576,181.92 against the German entity, which holds €14,364,156.03 against it. Five of six lines match to the cent (IT licenses, a travel recharge, a netting settlement), joined across the two ledgers. The sixth is the quarter's management fee: the US entity invoiced it on the quarter's last business day at 1.1640, €14,314,776.63; the German entity accrued it a week later at 1.1815, €14,102,750.74.

    Seven sources, one click each: the German journal, the intercompany agreement and its fee schedule, both rate tables, the US invoice and the group policy.

  4. 0404:47, overnight

    How it found the cause, step by step

    Break investigator

    The investigator shows its plan and lets anyone replay it: collect both ledgers, match line by line, look for the cause (the same US-dollar amount on both sides, so not a price or a missing booking), read the agreement, check the rate tables, draft the true-up in the German entity, the side that used the wrong rate, and ask the checker. Confidence 0.97.

    Its limit: below 0.80 confidence it does not guess. It hands the pair to a named person.

  5. 05One citation

    The clause that decides which side is wrong

    Agreement reader

    Each statement opens its source with the passage the agent relied on marked. The agreement's §5, Currency and rates: fees are invoiced in euros, and the US-dollar fee converts at the group closing rate for the last business day of the service period. That was the quarter's last business day, 1.1640 in Group Treasury's monthly rate table. The German entity used the daily rate of the day it accrued.

    “The US-dollar fee is converted at the group closing rate published by Group Treasury for the last business day of the service period. No other rate applies.”

  6. 0609:21

    The adjusting controller asks the agents back, in plain words

    German entity controller

    The true-up lands in the German entity's books, so its controller asks the question each entity controller asks: why my side? The investigator answers from the agreement and the invoice, with citations. Above it, the elimination checker has already re-performed the pair from its own copy of both ledgers, with the true-up applied: the pair nets to €0.00. The controller could also tell the agents to book it as group reporting only; they would argue against it and offer a version 2 that restarts the approvals.

    “Adjusting the US entity instead would break §5: its invoice already uses the rate the agreement sets.”

  7. 07The approval

    Approval with a reason code and the evidence read

    German entity controller

    The proposal is a real entry: in the German entity, Dr Intercompany management fees, Cr Intercompany payables to the US entity, €212,025.89, in the quarter's last period, reason code “FX rate set by the agreement”, version 1. The controller picks the reason code, may add a note for the auditor, and confirms having read the 7 sources the agents cited before approving.

    “Your approval is signed with your name and time. The entry is parked once the other approvers sign.”

  8. 08Both sides signed

    The US side signs too, and the entry is parked

    US entity controller

    The US entity's controller sees the same proof and approves, and the US books stay as booked. Under €250,000 the group controller is kept informed rather than asked, as §8 of the group policy sets. Only now does the true-up drafter park the entry in the German entity for posting. The pair moves to “Approved, posting”, and both approvals are on the audit trail with their reason code.

    “Approved by everyone. Parked in the German entity for posting.”

  9. 09The three it will not guess

    Where the agreement is silent, a person decides

    Group controller and transfer pricing manager

    The UK and US entities are out by €34,879.73: the US entity recharged 17.1% of the quarter's shared IT cost, the UK entity booked 16.4%, and neither version of Schedule D is signed by both parties. The investigator stops at 0.52 confidence and, under §11, hands it to the group controller with the transfer pricing manager. The group controller records the decision and why; the drafter turns it into a new version for both controllers.

    “3 I cannot explain. I will not guess; tell me what you decide and I will draft it.”

  10. 10Before the lock

    407 of 412 pairs net to €0.00, and nothing is plugged

    Elimination checker

    An independent agent copies all 18 ledgers, applies the 16 true-ups as drafted and eliminates all 412 pairs. Receivables and payables fall from €1,158,965.02 apart to €83,379.73, all of it in open pairs. Five pairs, €99,364.73, are carried open with an owner and a note. Unsupported top-side adjustments: €0.00. The check is the consolidation accountant's to sign before consolidation locks.

    “I do not reuse another agent’s numbers.”

Who it’s for

Group and entity controllers, consolidation and transfer pricing on one close

The same quarter-end close from five seats: the last days before the lock by hand, then with the agents.

Group controller
Signs the intercompany position
Before
Owns the intercompany position across 62 entities and signs it before consolidation locks, and will not lock on a plug that cannot be supported.
Now
Starts the day with a briefing that says what is out, why, and what needs a decision; decides only the pairs the agreements cannot settle.
Entity controller
Approves true-ups in their own books
Before
Will change the books only when shown the clause, and gets an email thread instead, days before the lock.
Now
Sees both ledgers, the cause and the clause, asks the agents back, and approves the true-up with a reason code.
Invoicing entity controller
Invoices fees to 20 entities
Before
Knows the invoice is right and still has to prove it, defending the same invoices to a dozen counterparties each quarter.
Now
The agents prove it to the other side with the invoice and the agreement; this controller signs the pairs that touch their own books.
Consolidation accountant
Clears small differences, signs the elimination check
Before
Knows each pair that does not net to zero is a question from the auditor, and finds out which ones at the lock.
Now
Gets an independent re-performance of each elimination with the true-ups applied, and signs it with the open pairs listed.
Transfer pricing manager
Confirms markups and allocation keys
Before
Treats a markup as a tax position to be asked about before it changes, yet hears about price differences after they are booked.
Now
Gets the pairs no clause can settle queued with the options and both versions of Schedule D cited, and confirms markups on the record.
The agents

Matcher, investigator, agreement reader and checker on each intercompany pair

Pairs are matched line by line and each break is traced and cited; the true-up is drafted in the right entity, both controllers approve, and the eliminations are re-performed.

Ledger collector

Pulls each intercompany line from 18 ledgers on 4 systems, the intercompany portal and the bank statement feeds, read-only.

  • Never writes to a ledger
Matcher

Pairs lines across the two ledgers by invoice reference, amount, date and partner (one to one, one to many, many to many) in group currency.

  • Never forces a match below 0.90 confidence
Break investigator

Finds why a pair is out (rate, timing, missing booking, wrong partner, price, tax, duplicate) and cites the lines and documents that prove it; asks a controller for missing evidence, such as a tax receipt.

  • Never guesses: below 0.80 confidence it hands the pair to a person
  • Shows its plan and confidence, and can replay its run
Agreement reader

Reads the intercompany agreements and the group policy (rates, markups, cut-off, who bears tax, who buys) and flags agreements that are missing, unsigned or expiring.

  • Never reads more into a clause than its words
  • Hands an unclear clause to the transfer pricing manager
True-up drafter

Drafts the true-up in the entity the agreement says is wrong, with accounts, amount, period and reason code, and writes a new version when a controller asks.

  • Never posts without every approval
  • Never proposes a top-side plug
Elimination checker

Re-performs the eliminations independently from its own copy of the ledgers, with the true-ups applied, and confirms each pair nets to €0.00.

  • Never trusts another agent’s numbers
  • A disagreement holds the pair
Settlement planner

Plans the monthly netting run from agreed balances only, and holds invoices from pairs still open until both controllers approve.

  • Never releases a payment — treasury approves the run
Close coordinator

Talks with people: the morning briefing, answers with citations, reminders and escalation against the close calendar, and the close report for the CFO.

  • Never approves anything
  • Never changes a proposal on its own
Both entity controllers

Approve true-ups on their books; the group controller above €250,000.

Ask in plain words

Pairs, causes and rates questioned in plain words, each answer cited

On each screen, ask about any pair, cause, rate, agreement or approval in plain words, or instruct the agents. Each answer cites its source.

Why is the US entity out with the German entity?

€212,025.89. The German entity accrued the quarter's fee a week after quarter-end at that day's rate, 1.1815. The agreement converts at the group closing rate of the last business day of the period, 1.1640. The drafter proposes the true-up in the German entity; both entity controllers approve.

Why not adjust the US entity instead?

Adjusting the US entity instead would break §5: its invoice already converts at 1.1640, the rate the agreement sets.

Book it as group reporting only

I can, but I would not recommend it. A group-reporting-only adjustment leaves the German entity's local books on the wrong rate, and the agreement sets the rate for both sets of books. It would also need the group controller's approval. Here is version 2 if you want it; approvals start again.

What is left before the consolidation lock?

Consolidation locks tomorrow at 12:00. Of 21 pairs with a difference: 1 approved, 15 awaiting approval, 2 waiting on a tax receipt, 3 need a person. 37 small differences wait to be cleared by rule. I have filtered the differences that need attention.

The screens

The pair map, two ledgers side by side and the elimination check

From the working solution, on its sample data. Pick one to see it large.

TodayThe agents' morning briefing: what was read and matched overnight, the largest break with its cause and proposal, what needs this person, and the close clock.
The pair mapWho is out with whom: each pair of group entities, the dot sized by amount and colored by status, with the agents' brief for the selected pair.
Two ledgers side by sideBoth entities' lines for the pair, matched lines joined across, the break dashed with its amount, and the sources the agents used.
How the agents found itThe investigator's plan, step by step and replayable, from collecting both ledgers to asking the checker.
The cited passageAny citation opens its source (here the agreement's currency clause) with the text the agent relied on marked.
Working with the agentsAn entity controller asks why their side is adjusted; the investigator answers from the agreement, and the checker confirms the pair nets to €0.00.
Approve with a reason codeThe true-up entry, the reason code, a note for the record and the confirmation that the cited evidence was read.
Both sides signedOnce both controllers approve, the entry is parked in the entity that was wrong and the pair moves to posting.
DifferencesEach pair that is out with its cause, amount, status, approvers and confidence; filter, sort, search and act on several at once.
A person decidesA pair the agents cannot prove: the options with their consequences, and the reason the decision needs.
The elimination checkAn independent re-performance of each elimination with the true-ups applied, step by step, by elimination type, before the lock.
AgreementsEach intercompany agreement with the terms and clauses the agents apply, how often each was used, and the ones that need attention.
Intercompany policy settingsTolerance, group approval threshold, hand-off and match confidence, the top-side ban and the reason codes, owned by the group controller.
Governance

Two-sided approvals and an independent elimination check on each pair

Each value cites its sourceEach cause, rate and amount links to the ledger line, document, rate table or clause it came from, and the passage the agent relied on is marked.
Both sides approve their own booksBoth entity controllers approve a true-up that touches their books, with a reason code and the evidence confirmed read; the group controller also approves above €250,000 and any group-reporting-only adjustment.
Agents do not post, plug or approveConnections are read-only. The drafter parks an entry only after the last approval, does not propose a top-side plug, and no agent approves a true-up or releases a payment.
No guessing below 0.80When the investigator cannot prove a cause, it hands the pair to a named person with the options and their consequences; a decision needs a reason and becomes a new version for both controllers.
An independent elimination checkA separate agent re-performs each elimination from its own copy of the ledgers and must reach €0.00; pairs that do not are carried open with an owner, not plugged. The consolidation accountant signs it.
Versions, separation of duties, a trail that cannot changeAn edit creates a new version and resets the approvals. Nobody approves both sides of a pair alone. Each agent step and human decision is on an audit trail that cannot be edited, with a fingerprinted evidence pack per pair.
Configuration

Tolerance, approval thresholds and the top-side ban in intercompany policy

The group controller owns the rules the agents follow. A change needs a reason, is on the audit trail and applies from the next run.

SettingDefaultChoose from
Tolerance per pair€5,000Any amount · below it a person may clear a difference by rule with a reason code (policy §6)
Group controller also approves above€250,000Any amount · plus every group-reporting-only adjustment (policy §8)
Agent hands a pair to a person below0.80 confidenceThe confidence the investigator needs to propose a true-up
Lowest confidence for a match0.90The matcher never forces a match below this
Top-side adjustments for intercompany differencesNot allowedPolicy §9: never without support
Reason codes8 true-up codes, TU-01 to TU-08Plus rejection codes RJ-01 to RJ-04 and tolerance codes TL-01 to TL-03
Rate sourceGroup Treasury closing rates, monthlyAn agreement may set its own rate for its invoices · daily rates read for reference only
Reminders and escalation12:00 and 15:00, escalate at 17:00Each on or off · email, chat and a weekly digest for the CFO
Connections

Ledgers on four ERP systems, agreements, rate tables and bank feeds

ERP and regional ledgerseach intercompany line from 18 ledgers on 4 ERP systems, read-only
Intercompany portalintercompany invoices and acceptances
Agreements and group policyservices, supply, tooling and loan agreements, schedules and amendments
Group rate tablesGroup Treasury closing rates and daily reference rates
Bank statements and in-house bankcash in transit, and the monthly netting run and payment files
E-mail and chatbriefings, questions to controllers, reminders and the CFO digest
What it changes

Intercompany differences corrected at source, as measured at the lock

Each figure carries its label: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
0
unsupported top-side plugs at the lock, the design goal for intercompany differences
Out at the lock21 sample pairs
Plugged0
demo
€1.14M
of differences fixed at source in one sample quarter
407 of 412 sample pairs
net to €0.00 after true-ups
target
Day 10
true-ups approved, a day before the consolidation lock
Lockday 11
Approvedday 10

“demo” = seen in the working solution, on its sample close data · “target” = the design goal, measured in the live solution · “estimated” = our estimate (the 4 days is the chart's estimated time investigating breaks with two controllers, for a quarter-end close in a group of about 60 entities) · “typical” = published figures (Deloitte, Intercompany accounting and process management, poll of more than 3,800 professionals, via Accounting Today — 9.2% call their framework leading, 21.4% name disparate systems as the top barrier; SEC Litigation Release 20547 (2008) — intercompany accounts unreconciled for at least six years). Elimination in full: IFRS 10 B86(c) and ASC 810. Names on the screens are sample data.

Questions

Intercompany reconciliation questions from group and entity controllers

What is intercompany reconciliation?

Intercompany reconciliation is matching the balances and transactions two companies in the same group hold with each other (receivable against payable, revenue against cost, loan against borrowing) and resolving each difference so consolidation can eliminate them in full. Botminds Intercompany Reconciliation gives the work to eight agents that match each pair, find and cite why each one is out, and draft the true-up in the entity the agreement says is wrong, for both entity controllers to approve.

How does it find why an intercompany pair is out of balance?

The break investigator works through the pair as an accountant would: both ledgers, line by line, then the cause, whether an FX rate, timing, a missing booking, the wrong counterparty, price or markup, withholding tax or a duplicate. It cites the ledger line, document, rate table or clause that proves it, shows its plan and confidence, and asks a controller when evidence such as a tax receipt is missing.

How does it decide which entity books the true-up?

The agreement reader turns each intercompany agreement and the group policy into the terms the agents apply: the rate clause, markup amendments, cut-off and title, who bears withholding tax, who is the buyer. The true-up drafter puts the entry in the entity those terms say is wrong and explains why the other side stays as booked.

What happens when the agents cannot explain a difference?

Below 0.80 confidence the investigator does not guess. It hands the pair to a named person, the group controller, with the transfer pricing manager where a price or allocation key is in question, along with the options and their consequences. The decision needs a reason, and the drafter turns it into a new version for both controllers to approve.

How are intercompany eliminations checked before the consolidation lock?

A separate elimination checker takes its own copy of each ledger, applies the true-ups as drafted and re-performs all eliminations by type: receivables and payables, revenue and costs, loans, borrowings and interest, cash in transit. Pairs that do not reach €0.00 are carried open with an owner and a note, not plugged, and the consolidation accountant signs the check.

Does it settle intercompany balances through netting?

The settlement planner plans the monthly netting run from agreed balances only and holds invoices from pairs that are still open; they join the next run once both controllers approve. It does not release a payment: the treasury analyst approves the run.

Can an agent post a true-up or plug a difference on its own?

No. The agents read ledgers read-only, park an entry only after the last approval, do not propose a top-side plug and do not approve anything. Both entity controllers approve a true-up that touches their books with a reason code, the group controller also approves above €250,000 or group-reporting-only adjustments, and each step is on an audit trail that cannot be edited.

What does the group provide to start on its own pairs?

Your intercompany policy, agreements, chart of accounts and a past quarter of intercompany lines. The Agentic Solution Engine builds and deploys it from these, and it goes live once each quality gate has passed. We will walk you through it on your own pairs first.

Run intercompany reconciliation
on a quarter of your own pairs.

We'll run Intercompany Reconciliation on a quarter of your own intercompany lines and the agreements behind them.