an overhead view of a team around a table with laptops
Intercompany · Reconciliation · Hub

AI Agents for Intercompany
Reconciliation

An intercompany difference has five causes and only three of them are errors. Clearing all five the same way destroys the information.

Key takeaways
  • An intercompany difference has five causes and only three of them are errors. Timing and rate differences are not wrong and should not be corrected.
  • Plugging the difference at group clears the balance and destroys the information about what caused it, which is why the same breaks recur.
  • Intercompany invoice matching is harder than external matching because there is usually no purchase order and the charge is often an allocation rather than a transaction.
  • Transfer pricing adjustments change agreed amounts retrospectively, sometimes after the receiving entity has already closed.
  • Nobody chases an intercompany invoice, because the counterparty has no incentive to, which is why these balances age differently from external ones.

AI agents for intercompany reconciliation classify every difference by cause before anything is cleared, match charges on the underlying agreement rather than on document references, and report calendar driven differences as expected rather than as breaks. ChatFin separates the three causes that are errors from the two that are not.

The recurring cost here is treating all differences as work. Most of a due to and due from break is a cut off or rate disagreement where both ledgers are correct, and plugging it at group clears the balance while guaranteeing the same break appears next period. ChatFin reports the cause so the response can be a policy rather than a correction.

Intercompany accountingDue to due fromIntercompany matchingGroup closeTransfer pricingMulti entityConsolidationAI agents for finance
01

Intercompany differences have five causes and one of them is not an error

A due to and due from difference is treated as a break to be cleared. It is more useful read as a classification problem, because the five things that cause it need completely different responses and only three of them are actually wrong.

CauseIs it an errorWhat resolves it
Different cut off datesNo, both books are rightA group cut off policy
Different FX rates appliedPartlyOne rate source per group
One side never bookedYesBook it
Different amounts agreedYesA commercial decision
Booked to the wrong counterpartyYesRecode it

Clearing all five the same way, which usually means plugging the difference at group, destroys the information. ChatFin classifies each difference by cause first, and the timing and rate categories typically account for most of the value while needing no correction at all.

In ChatFin

ChatFin classifies every intercompany difference by cause before anything is cleared, because timing and rate differences are not errors and should not be corrected.

02

Intercompany invoice matching is harder than external matching

Matching invoices between two entities of the same group sounds easier than matching to a third party. It is usually harder, and for structural reasons rather than technical ones.

Neither side has a purchase order. Intercompany charges are often raised on an agreement rather than an order, so the strongest matching key is absent.
The charge is an allocation, not a transaction. A management fee or a cost recharge has no natural line level detail to match against.
The billing entity decides the description. And the receiving entity codes it to whatever makes sense locally, so descriptions do not correspond.
Amounts change after the fact. Transfer pricing adjustments alter agreed figures retrospectively, sometimes after the receiving entity has closed.
Nobody is chasing. An external vendor chases an unpaid invoice. An intercompany counterparty has no such incentive.

ChatFin matches on the agreement and the amount pattern rather than on document references, and reports transfer pricing adjustments separately because they arrive after the fact by design.

an overhead view of a team around a table with laptops
Intercompany matching is harder than external matching, not easier.
In ChatFin

ChatFin matches intercompany charges on the underlying agreement and amount pattern, because document references between group entities rarely correspond.

03

Most of the balance difference is a calendar disagreement

Where entities close on different days, or where a charge is raised on the last day of a period and received on the first day of the next, both ledgers are correct and the group position does not net.

SituationEntity A showsEntity B showsGroup effect
Charge raised on the final dayA receivableNothing yetA difference
Entity B closes two days earlierA receivableNothing yetA difference
Credit issued after B closedA reduced balanceThe old balanceA difference
Both closed, both bookedA receivableA payableIt nets
Charge disputed by BA receivableNothingA real disagreement

Only the last row needs anybody to do anything. The others need a policy, not a correction, and treating them as breaks generates recurring work that never reduces. ChatFin identifies the calendar driven differences and reports them as expected rather than as exceptions.

In ChatFin

ChatFin reports calendar driven intercompany differences as expected rather than as breaks, so the exception list stops regenerating every period.

04

Where this underperforms

Three.

Counterparty is not recorded on the transaction. If intercompany is identified only by account, differences can be totalled but not attributed to a pair.
Agreements are not available. Allocation and management charges can only be matched on amount patterns, which is weaker evidence and should be labelled as such.
Group cut off is genuinely uncontrolled. Where entities close on materially different dates with no policy, the timing population dominates everything and the fix is governance rather than software.
Start by classifying one period of intercompany differences by cause. It corrects nothing, and it usually shows that most of the recurring work is not error correction.

Deeper in intercompany reconciliation

Use cases under this hub, shown rather than linked while they are in build.

In build
Due to and due from reconciliation · Intercompany invoice matching · Intercompany reconciliation

Covered as sections here
Difference classification · Allocation charges · Cut off timing · Transfer pricing adjustments

Questions group accountants ask first

Why not just clear intercompany differences at group?

Because it works and it never stops working. Plugging the difference balances the consolidation and removes the evidence of what caused it, so the same break returns next period. ChatFin classifies each difference into cut off, rate, unbooked, disputed amount and wrong counterparty, and only three of those need a correction at all.

Why is intercompany matching harder than matching a third party invoice?

Because the strongest keys are missing. There is usually no purchase order, the charge may be an allocation with no line detail, and each side describes and codes it differently. ChatFin matches on the underlying agreement and the amount pattern, and reports transfer pricing adjustments separately because they arrive after the fact by design.

What if entities close on different dates?

Then a large share of the difference is a calendar disagreement in which both ledgers are correct. ChatFin identifies those and reports them as expected rather than as exceptions, which stops the break list regenerating every period. The underlying fix is a group cut off policy, which is governance rather than software.

How ChatFin works on intercompany

Classify the difference before clearing it.

ChatFin splits intercompany differences into cut off, rate, unbooked, disputed and miscoded, and reports which of them are not errors at all.

Charges are matched on the agreement and amount pattern rather than on document references that rarely correspond between entities.

Bring one period of intercompany balances. The classification takes an hour.

Book a demo
AM
Ashok Manthena
CEO and co founder, ChatFin

Ashok Manthena is the CEO and co founder of ChatFin, an AI agent platform for enterprise finance that runs across NetSuite, Acumatica, JD Edwards, SAP and Dynamics 365. He works with CFOs and controllers on governed automation of the close, payables, receivables and reporting. Connect on LinkedIn.

Image credits. Header photograph: an overhead view of a team around a table with laptops, sourced from Pexels and used under the Pexels licence.
All images are served from the Pexels content network. No third party product screenshots, vendor logos or licensed media are used on this page.
Get started

Bring one period of intercompany balances.

We will classify the differences through ChatFin by cause and show you how much of your recurring break list was never an error.

✓Differences classified into five causes
✓Allocation charges matched on the agreement
✓Calendar differences reported as expected, not as breaks
Request a demo
Confidential & private