Intercompany Netting: How It Works

Intercompany netting is a process that offsets the amounts group entities owe each other so only the net positions are settled — instead of every intercompany invoice being paid in full and separately. A netting centre gathers all intercompany payables and receivables, works out who owes whom on net, and settles just those net amounts. The effect is dramatic: a web of dozens or hundreds of gross cross-border settlements collapses into one net figure per entity, cutting payment volumes, FX conversions, bank fees and float all at once. It's one of the cleanest efficiency wins in group treasury — and it lives or dies on the quality of the intercompany data behind it.

What netting is

Groups are full of internal trade: entities buy from and sell to each other constantly, generating a dense web of intercompany payables and receivables. Settled gross, every one of those is a separate payment — often cross-border, often in different currencies, each with a conversion and a fee. Netting recognises that many of these offset, and settles only the difference.

Why net

• Fewer payments. Many gross settlements become one net position per entity.
• Less FX. Offsetting exposures before converting means fewer, smaller currency conversions and less spread paid.
• Lower fees. Every payment avoided is a transaction fee avoided.
• Less float and risk. Less money in transit means less float cost and less settlement risk.

"

Settling intercompany gross is paying a bank fee and an FX spread to move money the group already owes itself. Netting settles only what's genuinely left over after the group's internal claims cancel out.

Bilateral vs multilateral

Two forms, very different in power:

Multilateral netting — run through a central netting centre — is where the real value is: instead of resolving each pair, every entity ends up with a single net position against the centre. A tangle of many-to-many flows becomes one number each.

How a netting cycle works

Netting runs on a cycle, usually monthly:

1. Collect all intercompany invoices — payables and receivables — from every entity, by an agreed cut-off.
2. Match and agree. Reconcile the two sides of each intercompany balance and resolve disputes before the run.
3. Calculate net positions — each entity's single net payable or receivable against the centre, converting to the netting currency at agreed rates.
4. Settle the net — each entity pays in or receives its net amount only.
5. Repeat next cycle, on a predictable calendar everyone plans around.

Where it sits with the in-house bank and payment factory

Netting is part of the same centralization family as the in-house bank and the payment factory. In fact a netting centre is often run by the in-house bank, and the net settlements may flow through the payment infrastructure. Pooling concentrates external cash; netting concentrates internal obligations; the payment factory centralizes external payments — different problems, one centralization programme.

What usually goes wrong

• Poor intercompany data. The whole thing depends on both sides agreeing what they owe. Mismatched or unreconciled intercompany balances break the netting run — data quality is the number-one failure point.
• Disputes handled in-cycle. Trying to resolve disagreements during the settlement window instead of before the cut-off, jamming the cycle.
• FX rate disagreements. No agreed source or timing for the rates used to convert, so entities argue over their net figure. Fix the rate policy up front.
• Regulatory blind spots. Some countries restrict or prohibit netting for certain flows or currencies. Confirm what's permitted per jurisdiction before including it.
• Undisciplined timing. A cycle that slips or varies, so entities can't plan their cash around it.

Collect and agree the intercompany balances, run a disciplined multilateral cycle on agreed rates, settle only the net, and respect local restrictions — and intercompany netting turns a costly web of internal gross payments into one clean net settlement per entity. It's the group refusing to pay banks to move money it already owes itself.

Part of the Cash & Liquidity Management guide. See also what is a payment factory and what is an in-house bank. The newsletter sends one finance-systems pattern, product decision or build lesson every two weeks.