Intercompany Agent
Intercompany differences are not usually errors. They are two entities booking the same transaction on different days, at different amounts, in different currencies, and both being right.
Both sides agree before either is posted.The counterparty entity confirms the entry before it lands, so eliminations at consolidation are arithmetic rather than negotiation.
What it checks
On every invoice, not a sample.
- Counterparty entity, amount and date agreed on both sides
- Currency and the rate applied on each side
- The entry exists in both books before consolidation
- Balances that will eliminate cleanly
What it reads, what it writes
Reads
Both entities' entries · Group structure and elimination rules · Exchange rates applied
Writes
The agreed entry in both books · A hold where the sides do not agree, showing the difference · The agreement trail
Where it sits in the team
Agents do not work alone. Each one hands its result to the next, so a finding raised here shows up as context downstream rather than being re-derived.
Hands to it
It triggers
When it isn't sure
Where the two sides disagree, neither is assumed right. The difference is quantified and put to both entity controllers, because the resolution is a decision about the transaction, not about the bookkeeping.
Any check that runs on every transaction will meet cases it cannot settle. What makes a control trustworthy is not that it never hesitates — it is that hesitation produces a named question for a person, rather than a silent pass or a silent block.
See what this one finds in your last 90 days.
One export. No connector. We come back within a working day.
$Check your savings→