Intercompany netting offsets internal payables and receivables so each entity in a corporate group makes or receives one net settlement per cycle, instead of dozens of separate cross-border payments. That single change cuts payment volume, FX conversions, and bank fees at the same time. Groups typically run it one of two ways: bilateral netting between paired entities, or multilateral netting through a central netting hub covering the whole group. Either version depends on the same groundwork: accurate due-to/due-from ledgers, a published settlement calendar, and a signed governance agreement that says who nets what, when, and how disputes get resolved.
Before you build a program, know what you're committing to operationally:
- Agreed, reconciled due-to/due-from balances across every participating entity
- A fixed settlement calendar with holiday adjustments built in
- A netting agreement covering dispute resolution and fee allocation
- A currency policy: net first in transaction currency, then convert the net
Key Takeaways
Intercompany netting works because it replaces many gross cross-border payments with one net settlement per entity per cycle, cutting bank fees, FX conversions, and reconciliation effort simultaneously.
| Point | Details |
|---|---|
| Net in transaction currency first | Reconcile and calculate net positions in original currencies, then convert only the final net at one fixed run rate. |
| Match structure to entity topology | Use bilateral netting for a handful of paired entities; use multilateral netting once a netting center adds more payment reduction than governance cost. |
| Reconciliation is the hard part | Most implementation effort goes into getting both sides of every intercompany balance to agree before the net calculation locks. |
| Keep gross records for auditors | Retain invoice-level transaction history even after settling net, since tax and transfer-pricing reviews require it. |
| Feed netting outputs into hedging | Corphedge's VaR-based hedging tools use fixed net run dates and net notional figures to size and time currency hedges more precisely. |
Table of Contents
- How Intercompany Netting Works: Cycle Steps and Accounting Treatment
- Benefits and When Netting Actually Pays Off
- Bilateral vs Multilateral Netting: Which Fits Your Structure
- Implementation Checklist: From Agreement to Audit-Ready
- CorpHedge Perspective: Netting as an Input to FX Hedging Decisions
- Non-Cash Ways to Settle Intercompany Balances
- Reconciliation, Reporting, and Keeping an Audit Trail
- Common Challenges in Intercompany Netting and How to Fix Them
- Governance and Compliance Best Practices for Netting Programs
- What a Netting Program Looks Like in Practice
- Why Most Netting Programs Under-Deliver
- Corphedge: Turning Netting Data Into Hedging Decisions
- Sources
- FAQ
How Intercompany Netting Works: Cycle Steps and Accounting Treatment
Every netting cycle runs on the same raw material: AP and AR feeds from each entity's ERP, the group's due-to/due-from intercompany ledgers, and invoice-level detail that ties every balance back to a real transaction. Skip the invoice-level detail and you have nothing to reconcile against when an entity disputes a number, which happens more often than most treasury teams expect.
The mechanics follow a fixed sequence:
- Gather. Pull intercompany AP/AR positions from every participating entity as of the cutoff date.
- Reconcile. Match each entity's payable against its counterparty's receivable, line by line, in the original transaction currency.
- Calculate net positions. Sum what each entity owes and is owed across all its counterparties (multilateral) or against a single counterparty (bilateral).
- Confirm and agree. Circulate net statements for sign-off before the settlement date, not after.
- Settle. Move one net payment per entity through the settlement bank account or netting center.
- Post clearing entries. Book the settlement in each entity's general ledger against the intercompany control accounts.
Currency handling deserves its own rule, and it's the one companies get wrong most often: reconcile and net every balance in its original transaction currency first, then convert only the final net amount using a fixed run rate declared before the cycle starts. Netting before converting, rather than converting each invoice separately, is what keeps ledger balances from drifting apart between counterparties.
Settlement posts on both sides of the relationship: the paying entity clears its payable, the receiving entity clears its receivable, and the net amount hits each entity's cash account. None of this replaces the underlying transaction history. Auditors and transfer-pricing reviewers expect gross invoice-level records to remain available even though cash only moved once.
Pro Tip: Lock your FX run rate at the same moment you lock the net position, not the day you actually wire funds. A two-day gap between calculation and settlement is where most netting-related FX disputes originate.
Benefits and When Netting Actually Pays Off
The direct payoff is fewer wires. Instead of every entity paying every counterparty separately, each entity sends or receives one net amount per cycle, which immediately shrinks the number of cross-border transfers, the bank charges attached to them, and the number of FX conversions treasury has to execute.
That reduction in conversions has a second-order effect that matters more over time: treasury hedges a smaller, more precise notional because netting collapses dozens of gross exposures into one net figure per currency pair. Cleaner exposure data means tighter hedges and less over-hedging waste.
- Fewer gross payments, which lowers bank and correspondent fees
- Reduced FX conversion volume and tighter hedging notional
- Faster period close, since intercompany reconciliation happens continuously rather than at month end
- Cleaner audit trail because disputes get caught during the cycle, not during the close
A properly run program frequently cuts internal wire transfers by 70 to 80 percent and can save multiple millions of dollars a year in transaction costs and FX gains, depending on the group's size and transaction volume.
As a rough threshold, groups running more than a handful of active intercompany pairs, or settling more than monthly, usually see enough volume to justify the governance overhead. Below that, the administrative cost of running a formal netting cycle can outweigh the savings.
Bilateral vs Multilateral Netting: Which Fits Your Structure
Bilateral netting nets balances between two entities only, one relationship at a time. It's simple to set up, easy to explain to a controller who's never seen netting before, and requires no central netting infrastructure. It also caps its own upside: savings scale only with the number of paired relationships you bother to net, not with the group as a whole.
Multilateral netting runs every participating entity's balances through a central netting hub, producing one net position per entity across all its counterparties simultaneously. This is where the largest reduction in payment count shows up, because a subsidiary that owes three affiliates and is owed by two others ends up with a single net transfer instead of five.
- Bilateral: low setup cost, minimal governance, works for two or three high-volume entity pairs
- Multilateral: higher setup cost, needs a netting center and formal agreement, delivers the biggest reduction in gross settlements as entity count grows
- Governance gap: multilateral netting needs a documented netting center role, indemnities for the entity acting as hub, and clear authority over who can adjust a position before cutoff
- Decision driver: entity count and transaction topology matter more than total volume. Ten entities trading with each other in a web justify multilateral; two entities trading heavily with each other don't need it
Regulatory constraints in some jurisdictions also restrict how netting proceeds can be settled or reported, which is one more reason the legal review below isn't optional.
Implementation Checklist: From Agreement to Audit-Ready
Running a netting program well is less about software and more about sequencing. Skip a step here and you'll find out during your first disputed settlement, not before.
- Draft and sign a netting agreement. Name every participating entity, define fee allocation, and spell out a dispute resolution process before the first cycle runs, not during it.
- Publish the settlement calendar early. Set cutoff, confirmation, and settlement dates well in advance, and build in national holiday adjustments for every jurisdiction involved. A calendar published two weeks before go-live invites the exact disruptions it's supposed to prevent.
- Confirm reconciliation workflows per counterparty. Every due-to/due-from pair needs an agreed process for flagging and resolving mismatches before the net calculation locks.
- Choose and test your integration approach. Decide whether netting runs through your existing ERP intercompany module, a treasury management system, or a specialist netting tool, then run at least one parallel test cycle against live data before cutting over.
- Document tax and transfer-pricing treatment. Get tax and treasury in the same room. Optimizing purely for treasury efficiency without transfer-pricing alignment on fee structures and documentation can create liabilities that erase the savings you just generated. Retain gross transaction records regardless of how many settlements the net cycle produces.
- Define exceptions and shortfall handling. Decide in advance what happens when an entity can't fund its net payment obligation, and set operational SLAs for confirmation turnaround and dispute escalation.
The hardest part of most netting rollouts isn't the calculation logic. It's getting both sides of every intercompany balance to actually agree on the number before you try to net it, and most implementation effort goes into that reconciliation step rather than the netting math itself.
Pro Tip: Run your first two cycles in parallel with existing gross settlement, not as a full cutover. It costs you a month of extra work and saves you from discovering a reconciliation gap after real cash has already moved.
A month-end close checklist built for finance teams generally can double as a useful template when you're designing the reconciliation and sign-off cadence for your own netting calendar.
CorpHedge Perspective: Netting as an Input to FX Hedging Decisions
Netting and hedging solve related but different problems, and treating them as separate workstreams wastes the best data your netting cycle produces. Once you fix the run date for a net settlement, you also fix the moment your group's real, aggregated currency exposure becomes known, which is exactly the input a Value at Risk model needs to size a hedge properly.
- Fixed net run dates give hedging desks a predictable window to act on aggregated exposure rather than guessing at gross flows
- Net notional by currency pair, not gross exposure, is what should feed a VaR simulation
- Live position tracking and simulation tools help translate a netting output into a specific hedge size and timing decision
Netting outputs are some of the best inputs available for VaR-based hedging: fix the net run date, feed the net notional into a VaR simulation, and decide hedges based on the aggregated exposure that's left. Treasury teams that keep these two processes disconnected are hedging against numbers that no longer reflect their real position.
Corphedge's platform is built to take a net exposure figure and turn it into a sized, timed hedge rather than a rough estimate.
Non-Cash Ways to Settle Intercompany Balances
Not every net position has to move as cash. Groups with strong internal financing relationships often settle intercompany balances through routes that never touch a bank wire, each carrying its own legal and tax consequences that need sign-off before anyone posts an entry.
Offset against intercompany loans. If entity A owes entity B on trade balances and entity B already holds a loan payable to entity A, the net trade position can offset against the loan balance instead of settling in cash. This is common in groups that have evolved toward an in-house bank structure, where treasury keeps discretion over physical settlement timing rather than settling every net position immediately.
Capitalization. A parent can convert a subsidiary's net payable into additional paid-in capital instead of collecting cash, which is useful when a subsidiary is undercapitalized but raises company-law and tax questions about capital contribution rules in the subsidiary's jurisdiction.
Dividend offset. Where a subsidiary owes its parent a net intercompany balance and separately owes a dividend, the two can offset against each other, provided distributable reserves and local dividend law support it.
Assignment. A receivable owed by one entity can be assigned to a third party, inside or outside the group, effectively transferring who collects the balance.
Every one of these routes needs documentation and formal approval before posting, because each carries distinct legal and tax consequences that a simple cash settlement doesn't trigger.
Reconciliation, Reporting, and Keeping an Audit Trail
Reconciliation isn't a step you run once before the first netting cycle. It's a discipline you run every cycle, because intercompany balances drift the moment one entity books an invoice the other side hasn't recorded yet.
The baseline requirement is matching, at invoice level, what each entity's AP system shows against what the counterparty's AR system shows, before the net calculation locks. Mismatches get flagged, investigated, and resolved before confirmation, not folded into the net and sorted out later. Groups that skip this step end up chasing discrepancies through several cycles at once, which is far harder to untangle than catching one cycle's gap immediately.
Reporting needs to show three things clearly: the gross position each entity started with, the net amount actually settled, and the clearing entries posted on both sides of every relationship. That reporting output becomes your audit trail. Regulators and auditors reviewing transfer pricing or withholding tax exposure will ask for the underlying gross transaction history, not just the net settlement figure, so retaining invoice-level records alongside the net settlement data isn't optional.
A practical habit worth building: archive the confirmation statements each entity signs off on before settlement, alongside the final clearing entries. If a dispute surfaces months later, that signed confirmation is the document that settles it. Cross-currency transaction monitoring tools can help keep this reconciliation trail consistent across entities that don't share a single ERP instance.
Common Challenges in Intercompany Netting and How to Fix Them
The single biggest challenge isn't technical, it's behavioral: getting every participating entity to actually reconcile its balances before the cutoff, every cycle, without exception. Local controllers under time pressure will sign off on an approximate number rather than chase a discrepancy, and that habit compounds fast across a multilateral program with a dozen entities.
A second recurring problem is currency mismatch between systems. If one entity's ERP records a balance in its local currency and the counterparty records the mirror entry in a different currency without a shared, agreed exchange rate, the two ledgers will never tie out exactly. The fix is procedural: net in transaction currency first, and lock a single conversion rate for the whole cycle before anyone converts anything.
Governance drift is the third failure mode. Netting agreements get signed once and then ignored as entities join, leave, or change ownership structure. A netting center with authority that was accurate two years ago may no longer match the group's actual legal entity chart, which creates real exposure if a dispute ever goes to a regulator.
Liquidity timing is the fourth risk worth naming directly. An entity expecting to receive a net payment to fund local obligations can be left short if the settlement date slips or a counterparty disputes its position late. Building an exception process, and a small liquidity buffer for entities most dependent on netting proceeds, prevents a calendar slip from becoming a cash crisis.
Governance and Compliance Best Practices for Netting Programs
Strong governance starts with ownership, not policy documents. Someone specific, usually a treasury center lead, needs formal authority over the netting agreement, the calendar, and any exception approval. Diffuse ownership across multiple regional controllers is where compliance gaps open up.
Review the netting agreement annually against the actual legal entity structure, not just the finance org chart. Entities merge, get sold, or change tax residency, and a netting agreement that still lists a divested subsidiary is a compliance problem waiting to surface during an audit.
Tax and treasury need a standing review cadence, not a one-time sign-off. Fee structures and documentation for netting arrangements should get revisited whenever transfer-pricing policy changes or a new jurisdiction joins the program, because a structure optimized purely for payment efficiency can quietly create a transfer-pricing exposure.
Access controls matter more than most programs give them credit for. Whoever can adjust a net position before cutoff should be logged, and that log should be part of your audit package, not something reconstructed after the fact.
Finally, build compliance monitoring into the cycle itself rather than treating it as a separate quarterly exercise. A dashboard showing which entities confirmed on time, which disputes remain open, and which exceptions were granted gives a treasury lead early warning before a governance gap becomes a genuine control failure.
What a Netting Program Looks Like in Practice
A group with entities across a dozen countries, each trading heavily with several others in the network, is the textbook case for multilateral netting. Instead of forty or fifty separate cross-border wires each cycle, a netting center collapses that into one net payment or receipt per entity, and the group captures the reduction in bank fees and FX spreads that comes with fewer, larger conversions instead of many small ones.
Contrast that with a group of two entities, a US parent and a single European subsidiary, trading almost exclusively with each other. Bilateral netting fits here without any need for a netting center: the two sides agree a cycle, confirm the net figure, and settle once. Building multilateral infrastructure for two entities would add governance cost with no matching payment reduction, since there's only one relationship to net in the first place.
The pattern that shows up across both structures is the same. The savings that get reported publicly, like the 70 to 80 percent reduction in internal wire transfers some groups achieve, come almost entirely from entity count and transaction density, not from the sophistication of the netting math itself. A ten-entity web with dense trading nets far more value than a fifty-entity group where most pairs barely transact.
Why Most Netting Programs Under-Deliver
The conventional advice on intercompany netting treats it as a payments project: reduce wire count, cut bank fees, close the books faster. That's true, but it's the smaller win. The bigger one, and the one most treasury teams miss, is that a well-run netting cycle produces the cleanest currency exposure data a group generates anywhere in its finance function. Most programs never connect that data to a hedging decision, which means the group pays for the reconciliation discipline without collecting the FX benefit it should fund.
The research here supports a specific priority order: get reconciliation and governance solid first, because a netting program built on disputed numbers collapses under its own weight within a few cycles. Only once that foundation holds does the FX conversation matter, and it matters more than most programs assume. A net exposure figure sitting unused in a treasury report is a wasted asset. Feed it into a hedging decision instead, and the netting cycle starts paying for itself twice.
— Bartas
Corphedge: Turning Netting Data Into Hedging Decisions
Netting fixes your payment volume problem. It doesn't, on its own, tell you how much currency risk your group is actually carrying once the net settles, or when to hedge it. That's the gap Corphedge closes: a platform built to take your net exposure figures and turn them into a sized, timed hedge using Value at Risk simulation, rather than a rough estimate pulled together after the fact.
Corphedge's product tour walks through live position tracking and how net notional feeds directly into a VaR model. For teams that want to see the hedging methodology itself, the VaR-based hedging approach explains how position sizing works once a net exposure is known. Treasury teams building this skill set internally can also work through Corphedge's FX hedging course to train staff on turning netting outputs into hedging decisions. As Corphedge expands its coverage into Poland and Sweden, treasury teams in those markets managing multi-currency intercompany flows now have direct access to the same position tracking and hedging tools. Start with the product tour to see how your next netting cycle's output could become your next hedge decision.
Sources
This guide draws on treasury body guidance from the Association of Corporate Treasurers on netting centers and settlement calendars, practitioner cost-savings data from FTI Treasury Talks, transfer-pricing and legal guidance from LegalClarity, and mechanics explained by Ripple Treasury.
- A valuable tool for extracting net benefits | The Association of Corporate Treasurers
- FTI Treasury Talks: Intercompany Netting, Cutting Costs, Unlocking Liquidity and Streamlining Treasury - FTI Treasury
- How intercompany netting works for multinationals — LegalClarity
FAQ
What Is Netting in Intercompany Accounting?
Intercompany netting is the process of offsetting payables and receivables between entities in the same corporate group so each entity settles one net amount per cycle instead of many gross payments.
What Is an Example of Netting?
If Subsidiary A owes Subsidiary B a certain amount and Subsidiary B owes Subsidiary A another, netting offsets the two balances so only one net amount actually settles, instead of multiple separate payments.
What Does Netting Mean in Accounting?
In accounting terms, netting means recording a single net settlement entry against the intercompany control accounts on both entities' ledgers, while retaining the underlying gross invoice records for audit and transfer-pricing purposes.
What Is the Purpose of Netting?
The purpose is to reduce the number of cross-border payments, bank fees, and FX conversions a group makes, while producing cleaner currency exposure data that can also inform hedging decisions.
How Is Netting Different From Hedging?
Netting reduces the number and size of currency exposures a group has to manage; hedging protects against the remaining exposure that netting leaves behind, which is why the two work best when run together rather than separately.