Intercompany Netting, From Gross Chaos to One Payment

Six entities that transact with each other can carry up to fifteen bilateral relationships. If each pair settles its invoices gross, a routine quarter can mean dozens of wire transfers, each one a bank fee, a reconciliation item, and a chance to key an amount wrong. Netting is the discipline that collapses that mess into a handful of predictable payments, and in some structures into no payments at all.

This guide covers what netting software actually does, how bilateral and multilateral netting differ in practice, how to run a netting cycle on a calendar, what to do about currency, and the non-cash routes for clearing balances that never should have been cash problems in the first place.

What Netting Software Actually Does

Strip the vendor language away and an intercompany netting system performs four functions:

1. Position calculation. For every pair of entities, sum what A owes B and what B owes A, and produce the net figure. For multilateral netting, produce each entity’s single net position against the group.
2. Agreement. Both entities (and in multilateral netting, the netting center) confirm the positions before anything clears. A netting run against disputed balances just spreads the dispute across more accounts.
3. Clearing entries. When the net amount is paid, or offset without cash, the system posts the settlement against the correct per-counterparty due-to/due-from accounts on both sides at once.
4. The audit trail. Every netted balance traces back to its source invoices, allocations, and loans, so any net figure can be decomposed after the fact.

Notice what is not on the list: reconciliation. In a system where both sides of every intercompany transaction post from a single entry, the positions are agreed by construction and netting is arithmetic. In a system of disconnected company files, “netting software” spends most of its life matching invoices that were keyed twice by different people. That is the real dividing line between tools, and it is set long before the netting run starts. The foundation is covered in depth in the intercompany settlement automation guide.

Bilateral Netting: One Pair, One Payment

Bilateral netting offsets the mutual balances of a single entity pair.

Suppose over a quarter:

• A management company invoiced an operating company $36,000 in management fees
• The operating company invoiced the management company $21,500 for office space and shared staff

Settled gross, that is $57,500 moving in two directions. Netted, the operating company pays $14,500 and both pairs of due-to/due-from accounts clear to zero.

The clearing entries mirror each other:

The practical requirements are modest: per-counterparty control accounts (a lumped “Intercompany” account cannot be netted per pair because the pairs are invisible), agreed balances, and a simple set-off understanding between the entities. Most groups can start bilateral netting in a single month-end.

Multilateral Netting: One Entity, One Position

Multilateral netting reduces each entity’s many pair positions to a single net figure against the whole group, cleared through a netting center, typically the parent or a treasury entity.

Gross settlement would move $93,000 across a dozen or more transfers. Multilaterally netted, three entities each make one payment into the netting center and the run is done. Every entity’s bank activity for the period is a single line.

The additional machinery over bilateral netting is real, though:

• A netting agreement. A written agreement among participating entities that mutual balances may be set off and settled through the center. Without it, the legal right of set-off between entities that are separate legal persons is not automatic.
• A netting center. The central entity carries the pair positions after the run, so its own intercompany ledger becomes the hub. That concentration is convenient and needs watching: the center’s balances with each entity should themselves be settled or reviewed on a cadence, not left to accumulate.
• A calendar. Multilateral netting works when it runs on fixed dates with a cutoff, a dispute window, and a settlement day. Ad hoc runs produce ad hoc disagreements.

The Netting Cycle

Groups that net successfully run the same loop every period. A workable monthly calendar:

1. Cutoff (business day 1). No new intercompany charges enter this cycle after the cutoff; late items roll to next month. Ambiguity about what is “in” the run causes more disputes than amounts do.
2. Position statement (day 2). The system produces each pair’s balance, or each entity’s net group position, from the ledger. If both sides post from one entry, this step is a report, not a project.
3. Dispute window (days 3 to 4). Entity controllers confirm or flag. In a linked-ledger system the flags are rare and specific: a coding disagreement, a contested allocation, not a missing $2,500.
4. Rate fixing (day 4, cross-currency groups). One declared rate per currency pair for the run, applied to net amounts.
5. Settlement (day 5). Payments move, or offsets are documented, and the clearing entries post to both sides of every affected pair.

The cycle is also the honest test of any tool you evaluate: ask a vendor to show you steps 2 and 5 live. Position statements that come from a spreadsheet export, or clearing entries that must be keyed into each entity separately, mean the “automation” is a label.

Currency Netting

Cross-currency pairs are where netting arithmetic goes wrong most often, because the two sides of the same balance legitimately differ once each entity remeasures into its own functional currency.

The order of operations that keeps the run defensible:

1. Reconcile in the transaction currency. A EUR-denominated balance between a USD parent and a EUR subsidiary is agreed in EUR first. In the transaction currency, the two sides must match exactly.
2. Net in the transaction currency. Offset the pair’s EUR items against each other before any conversion.
3. Convert the net at the fixed rate. The single net amount converts at the rate declared for the run, on the declared date.
4. Let remeasurement land where it belongs. The side holding a balance in a currency other than its functional currency carries FX gain or loss from remeasurement on its income statement (or in the translation adjustment in equity, for balances of a long-term-investment nature with no settlement planned). That difference is explained, not “reconciled away.”

Netting gross balances after conversion, at rates from different dates, produces net figures that tie to nobody’s books and dispute windows that never close. Groups with heavy cross-border flows eventually justify a treasury platform for this; the accounting-side requirement is the same either way, a ledger agreed in transaction currency.

Settling Without Cash

Some intercompany balances should never become payments at all. The recognized non-cash routes:

• Offset (set-off). The pure netting case: a due-to and a due-from between the same pair are cleared against each other under the set-off agreement, and only the remainder, if any, moves as cash.
• Capitalization. The parent converts its receivable from a subsidiary into equity. The subsidiary’s payable becomes a capital contribution, cleaning the balance sheet ahead of a financing or simply recognizing that the “loan” was always funding. Document the decision; auditors ask.
• Distribution offset. A subsidiary that owes its parent declares a dividend and offsets the payable against the distribution rather than round-tripping cash.
• Assignment. A balance owed to one group entity is assigned to another so it nets against an existing position in that pair. Useful for tidying triangular positions before a multilateral run; it needs the same legal care as any assignment of a receivable.

Each route clears the intercompany accounts and each changes the legal and tax picture, so the sequence is always: decide with advisors, document, then post, with both sides posting from the one decision so the pair stays agreed.

How the Tooling Options Compare

The pattern worth noticing: the further left a tool fails, the more expensive everything to its right becomes. A treasury system fed by disconnected ledgers spends its implementation budget on matching. A linked ledger makes every downstream step cheap, including the decision to skip a treasury system entirely because three net payments a month do not need bank-file automation.

Where EmLedger Fits

EmLedger is multi-entity accounting software, and its contribution to netting is the part every netting run depends on:

• Positions agreed by construction. An intercompany invoice, fee, shared bill, or loan is recorded once from either entity, and both sides post from the same record through inter-company transactions. A same-currency pair cannot drift apart through a missing or mis-keyed second side.
• Net positions on demand. The intercompany balance report shows every pair’s due-to/due-from position across the group with discrepancy detection, which is the position statement step of the netting cycle as a report rather than a workpaper.
• Settlement recorded once. When a net amount is paid or offset, the settlement is recorded as a transaction and clears the intercompany accounts on both sides.
• Eliminations follow automatically. Whatever remains unsettled at period end drops out of consolidated reports without manual elimination entries. Netting changes the cash; eliminations fix the reporting; see inter-company eliminations explained for that side.
• Pricing by capacity. One entity on Solo at $29/month, up to 3 at $49, up to 10 at $99, up to 25 at $199, custom above that. Adding an entity inside a tier adds no subscription.

Being precise about scope, as always: EmLedger is not a treasury workstation. It will not generate bank payment files, execute FX, or run a multilateral netting engine across fifty currencies. It produces agreed positions, records settlements, and eliminates in consolidation. Groups that outgrow that genuinely need a treasury system on top, and by then the linked ledger underneath is what makes that implementation cheap.

Getting Started

If your group settles gross today:

1. Split lumped intercompany accounts into per-counterparty due-to/due-from pairs. Netting requires seeing pairs.
2. Agree every pair once. Reconcile to a clean starting point and document what could not be substantiated.
3. Paper the set-off. A short netting agreement among the entities, reviewed by counsel, before the first offset.
4. Start bilateral, monthly. One pair, one net payment, on a fixed calendar. Add the netting center later if payment count justifies it.
5. Age the leftovers. Balances that survive every cycle untouched get a decision: offset, capitalize, distribute, or admit they are permanent funding and account for them that way.

Next: the intercompany settlement automation guide covers the full settlement process this sits inside, inter-company eliminations explained covers the reporting side with journal entries, and the intercompany accounting software buyer’s guide compares the platform options end to end.