Intercompany payment netting: settle one group balance instead of dozens of cross-border invoices

Intercompany netting reduces the number of group payments by offsetting amounts companies owe each other and settling only the net balance. A multinational can replace dozens of cross-border transfers and FX conversions with one scheduled settlement per entity, but the underlying invoices and legal obligations still need to remain visible.

Netting offsets reciprocal intercompany obligations

If UK Co owes German Co €500,000 and German Co owes UK Co €350,000, a bilateral netting cycle can reduce the cash settlement to €150,000 from UK Co to German Co.

Multilateral netting extends the concept across several group companies through a treasury centre or clearing process.

The underlying invoices still exist

Netting changes how obligations are settled, not whether the sale, service or loan existed. Each company should still book the original intercompany invoice under transfer-pricing and accounting rules.

The net settlement clears several ledger items at once, supported by a netting statement.

Use a fixed monthly or weekly cut-off

Set a deadline for entities to submit approved intercompany invoices and disputes. Items after the cut-off move to the next cycle.

This gives treasury a stable net amount and prevents last-minute invoices from changing the payment after approvals are complete.

Centralise FX only where it improves economics

Groups can net invoices by currency and convert only the residual amount, reducing gross FX volume and bank fees.

Do not combine currencies without a controlled exchange-rate methodology. Each entity's local ledger needs a transparent conversion and settlement value.

Check local legal and exchange-control constraints

Some jurisdictions restrict set-off, cross-border payments or intercompany settlement. Tax and legal teams should confirm which entities can participate.

Do not force every subsidiary into one global process if local law requires gross settlement or special documentation.

Issue a netting statement to every participant

The statement should list invoices included, credits, exchange rates and final amount payable or receivable. Each company reconciles that statement to its ledger and bank entry.

Differences should be resolved centrally. The entire benefit of netting disappears if local teams post unexplained manual adjustments to force balances to zero.

Worked example: five group companies have 42 intercompany invoices totalling £6 million equivalent in both directions. Multilateral netting can reduce those gross flows to five or fewer net settlements, lowering bank fees and operational payment risk while preserving every invoice in the ledgers.

Use legal-entity approval before the treasury centre settles on behalf of subsidiaries. The central team can calculate the net, but each participating company still needs authority for its obligations and accounting.

Measure savings from fewer transfers and lower FX turnover, but also measure dispute rates. A poor intercompany invoicing process can delay the netting cycle and create more reconciliation work than it saves.

Establish dispute rules before the cycle. If Subsidiary A disputes one £50,000 invoice, the group should know whether that item is excluded while the other 40 invoices settle or whether the entire netting statement is blocked. Clear rules prevent one disagreement delaying group-wide cash efficiency.

Use consistent FX sources and timestamps for multi-currency netting. Entities should not calculate the same dollar invoice at different sterling rates and then spend days reconciling artificial differences.

Review local bank charges before forcing small balances through the central net. In some jurisdictions a tiny cross-border settlement can cost more than carrying the balance to the next cycle, subject to legal and tax rules.

Worked example: UK Co owes US Co $800,000, US Co owes German Co $500,000 equivalent, and German Co owes UK Co $350,000 equivalent. A multilateral netting centre can calculate each entity's single net pay or receive position instead of moving three gross amounts through several banks. The accounting ledgers still clear each underlying invoice individually.

Set entity funding deadlines before netting day. A subsidiary that must pay a £2 million net amount should know several days in advance so it can arrange local cash or intercompany funding. Netting reduces transactions but can concentrate a large cash requirement into one settlement date.

Keep tax and legal documentation for intercompany service and goods transactions independent from the netting system. The payment method does not prove arm's-length pricing or deductibility; it only settles amounts already recognised under the group's commercial arrangements.

Use one settlement bank account per legal entity where practical and verify changes through central treasury. A fraudulent change to a netting account can redirect a large group balance in one transaction, making beneficiary controls especially important.

Use a netting agreement that explains when obligations are treated as discharged. Accounting teams need to know whether the legal debt is settled on the netting calculation date, the bank settlement date or another contractually defined point. This matters when month-end falls between calculation and cash transfer.

Review participation after reorganisations. A sold subsidiary should be removed promptly, while a newly acquired entity should not enter the cycle until bank accounts, tax treatment and intercompany master data are ready. Group structure changes can otherwise route cash to companies that no longer belong in the network.