Intercompany netting offsets mutual obligations among group entities so only a net amount is paid or received. It is a settlement design, not a bank account product. The goal is fewer wires, less FX conversion, and cleaner intercompany books — without pretending cash magically appears at a header the way cash pooling does.
Netting and pooling often sit in the same treasury program, but they solve different problems. Pooling concentrates balances. Netting reduces gross settlement of invoices, loans, royalties, and other IC claims.
What gets netted
Typical candidates:
- Intercompany trade payables / receivables
- Intercompany loans and interest
- Management fees, royalties, and shared-service charges
- FX settlements between entities (when policy allows)
Multilateral nets run through a netting center (often the treasury center or in-house bank): each entity reports obligations, the center computes a single net payable or receivable per participant, and only those nets settle on the cycle date.
Shapes treasurers actually use
1. Bilateral netting
Two entities offset mutual claims and settle one remainder. Simple legally; limited scale.
2. Multilateral payment netting
Many entities, one cycle, one net per entity. Highest payment-volume reduction when invoice and FX calendars align.
3. Netting + concentration hybrid
Nets settle first; residual cash still feeds domestic or cross-border cash pooling. Common when the center needs real cash for investing or a payment factory.
Netting does not replace POBO or entity-level payment legal models for third-party vendors. It mainly cleans intercompany settlement.
When it helps
- High gross IC invoice volume with recurring opposite flows
- Multi-currency groups that want fewer FX conversions per cycle
- Centers that want a predictable settlement calendar before pool sweeps
- Groups building toward an in-house bank with formal IC ledgers
When it breaks
- Local rules that restrict netting, set-off, or require gross settlement for certain claim types
- Missing master netting / set-off agreements or unclear governing law
- Transfer-pricing or VAT/GST treatments that assume gross invoicing
- Entities on incompatible ERP cutoffs so positions cannot be frozen for the cycle
- Corridors where cash still cannot move cross-border after the net is calculated — see cross-border cash pooling and country notes such as China
Minimum design package
- Legal master netting / set-off framework and participant accession docs
- Scope matrix (which claim types, currencies, and entities are in)
- Cycle calendar, freeze rules, and dispute window
- ERP–TMS posting: gross for accounting where required, net for cash
- Tax / TP review of interest, FX gains, and settlement characterization — including whether residual pool sweeps create taxable interest (do cash pool sweeps create taxable interest?)
- Funding path for net payers (pool header, IHB books, or prefund)
Settle early whether netting is a payment-volume tool, a FX tool, or both — then size the center and bank rails around that answer.