AI Agents for Intercompany
Settlement and Netting
Netting an unreconciled position moves the disagreement from a balance sheet account into cash, where it is far harder to unwind.
- Only agreed pairs should enter a netting run. Settling a timing difference moves cash out and back, and settling a dispute pays a claim nobody accepted.
- Direction is per relationship. A single entity is routinely a net receiver overall and a payer on four individual relationships, and only the second view funds anything.
- A cross currency settlement fixes a rate on a date. Where the two sides disagree on which rate and which date, both books are correct and the group has a difference.
- The funding question is what the centre needs on the settlement date, not the net position across the month.
- Netting cycles collide with local holidays, bank cut offs and entity close dates. Those collisions are entirely predictable and almost never modelled.
AI agents for intercompany settlement start from the reconciliation, not the payment. ChatFin excludes disputed and incomplete pairs from a netting run rather than settling them because they happened to be in the balance, and reports what it excluded so the exclusion is a decision.
For the pairs that do settle, it reports the position per relationship and per currency alongside the group total, fixes one rate basis for the whole run, records instruction and value date on every leg, and reconciles the cash that actually moved against the position that was netted.
Never net a position you have not agreed
Netting is sold as a treasury saving and it is one. The saving is only real if the underlying pairs are agreed, because settling an unreconciled balance moves the disagreement from a balance sheet account into cash, where it is far harder to unwind.
| Position state | What netting does to it | Cost of getting it wrong |
|---|---|---|
| Agreed both sides | Settles cleanly | None |
| Timing difference only | Settles a figure that reverses | Cash out, then cash back |
| Rate difference | Settles at one side's number | One entity absorbs the difference |
| Genuine dispute | Pays a claim nobody accepted | A recovery conversation |
| One side never posted | Settles half a transaction | An unexplained cash movement |
Only the first row should enter a netting run. ChatFin excludes anything classified as a dispute or an omission from the settlement set rather than settling it by default, and reports what it excluded and why, so the exclusion is a decision rather than a silence.
ChatFin excludes disputed and incomplete pairs from a netting run and reports the exclusions, rather than settling them because they were in the balance.
Direction is per relationship, not per entity
A netting statement that says an entity owes the group is describing a sum, and it is not what gets settled. Every pair has its own direction and a single entity is routinely a net receiver overall and a payer on four individual relationships.
ChatFin reports the position per relationship and per currency alongside the group total, and shows the funding requirement at the centre on the settlement date rather than the net position across the month.
ChatFin reports the position per relationship and per currency, and the funding needed at the centre on the settlement date rather than across the month.
Settling across currencies fixes a rate at a moment nobody recorded
This is where settlement creates the FX differences that treasury spends the next month explaining. A cross currency settlement converts at a rate on a date, and if the two sides do not agree on which rate and which date, both books are correct and the group has a difference.
Fix one rate basis for the run
Rate type and rate date, set once and applied to every leg. Most netting disputes are rate date disputes discovered after the payment has gone.
Say where the difference lands
A settlement rate that differs from the booking rate produces a realised gain or loss, and which entity absorbs it should be policy rather than an accident of who instructed.
Watch the value date, not the instruction date
A payment instructed before a bank cut off and valued the next day converts at whatever the bank applied. ChatFin records both dates.
Reconcile the settled amount to the position
The cash that moved should equal the position that was netted. Where it does not, the gap is bank charges, rate difference or an instruction that partially failed, and those need separating.
ChatFin holds the rate basis for the run, records instruction and value date on every leg, and reconciles cash moved against position netted. The revaluation side of the same problem is worked on multi currency revaluation and translation.
ChatFin fixes one rate basis for the whole netting run and reconciles cash actually moved against the position that was netted.
The settlement calendar is a real constraint and it is usually implicit
Netting cycles run on dates. So do period ends, tax filings, bank cut offs and public holidays in every jurisdiction a participant sits in. When those collide the settlement moves and the accounting does not.
| Collision | What happens | What it looks like afterwards |
|---|---|---|
| Cycle date is a local holiday | Settlement moves a day | Cash in the wrong period |
| Cycle falls after period close | Position settles next month | Balance sheet shows gross |
| Bank cut off missed | Value date moves | An unexplained FX difference |
| Participant closes early | Their balance is as at a different date | The pair will not agree |
| Quarter end and cycle collide | Everything at once | The month nobody can reconcile |
ChatFin holds the calendar per participant, including local holidays and each entity's own close date, and reports collisions before the cycle rather than after. That is a small piece of work that removes a recurring and entirely predictable month end problem.
Where this underperforms
Three.
Deeper in intercompany
Where the rest of the intercompany work sits.
The pillar above this
AI for intercompany accounting
Sibling hubs
Intercompany reconciliation · Eliminations · Multi entity
Treasury side
Treasury and cash management · FX and bank reconciliation · Cash position and liquidity
Questions treasury and group ask
Why not net everything in the balance?
Because netting an unreconciled position converts a balance sheet disagreement into a cash one. A timing difference settles a figure that reverses next month, and a genuine dispute settles a claim nobody accepted, which then needs recovering from a sister entity. ChatFin excludes both and reports the exclusions.
Why report the position per relationship?
Because that is what settles. A group total tells you an entity owes the group, which is a sum and not an instruction. The same entity can be a net receiver overall and a payer on several individual relationships, and where an in house bank sits in the middle its position against each participant is what has to be funded on the day.
Where do the FX differences come from?
From the settlement itself. Converting across currencies fixes a rate on a date, and if the two sides use different rate types or different dates, both books are right and the group has a difference. ChatFin fixes one rate basis for the run and records instruction and value date separately, because they are frequently not the same day.
Why does the calendar matter so much?
Because collisions are predictable and still surprise people. A cycle date landing on a local holiday moves the settlement, a cycle falling after a participant's close leaves the balance gross on their balance sheet, and a missed bank cut off moves the value date and with it the rate. ChatFin holds the calendar per participant.
Agree the pair, then settle it, on one rate basis.
ChatFin excludes disputed and incomplete pairs from the netting set and reports them, rather than settling whatever happened to be in the balance.
It reports position per relationship and per currency, fixes one rate basis for the run, and reconciles cash moved against position netted.
Bring your last four netting cycles.
Book a demoSection photograph: two people shaking hands across a desk with a laptop, 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.
Bring your last four netting cycles.
We will run them through ChatFin and show you what settled on the planned date, what was netted before it was agreed, and where the FX differences came from.