Intercompany netting: settle group invoices without losing the reconciliation

Intercompany netting uses an agreed calculation to reduce the cash payments needed to settle eligible obligations within a group. The starting point is an invoice list accepted by both sides. A group spreadsheet showing that one company is owed money overall does not establish which individual debts have been settled.

Take a receivables export from one entity and compare it with the counterparty's payable records at the same cutoff. Match invoice number, issuing entity, customer entity, currency, original amount, open amount, and due date. Resolve missing invoices, credits, and withholding questions before including them. Keep disputed balances outside the settlement until someone has authority to resolve them.

Assign a cycle reference, such as the month and settlement date, to the agreed list. This gives both accounting teams a shared reference when their own software uses different customer codes or journal numbers. Keep an approved copy; a spreadsheet that changes after payment cannot explain what the payment settled.

Have the relevant finance and legal owners confirm the entities, debts, currencies, approval rights, and settlement terms covered by the arrangement. Group ownership alone does not answer whether particular obligations can be discharged by netting. Cross-border arrangements may also need a review of local settlement, withholding, and reporting requirements.

Document how the group chooses exchange rates, handles differences in due dates, and treats a participant that cannot fund its settlement. An invoice already assigned to an outside lender or subject to a dispute needs a separate decision. Do not assume the normal intercompany arrangement overrides another contract.

Microsoft's netting workflow illustrates a useful control: account pairs and effective dates belong in an active agreement before a journal is posted. Your system may work differently. The operating principle is to identify the approved parties and terms before the calculation reaches the payment queue.

For an illustrative same-currency cycle, Company A owes Company B $120,000, while B owes A $85,000. If every listed obligation is eligible and both parties approve the arrangement, A pays B $35,000. The settlement advice still needs to identify the $120,000 and $85,000 of invoices being discharged.

The $35,000 bank movement is insufficient support for clearing either ledger on its own. Each entity needs the approved invoice list, netting advice, payment evidence, and its own posting reference. Have the accountant set the postings for that entity's accounts and reporting policy; the example is a settlement calculation, not a universal journal entry.

For a multilateral cycle, include the settlement agent's allocation showing how each participant's agreed obligations connect to its final payment or receipt. Avoid entering only a group-level total. It may balance centrally while leaving an individual subsidiary with an unexplained receivable.

Mark the selected invoices so they cannot also be paid by the usual accounts payable process. Coordinate the freeze with whoever releases bank payments. An invoice can appear in two workflows even when each team's own spreadsheet is correct.

After posting, check both sides at the same date. Confirm that the agreed invoices have cleared, the cash settlement is recorded, and any clearing-account balance has an identified cause. A payment in transit should have bank evidence and an expected resolution date. An unexplained difference should remain visible rather than being absorbed into a miscellaneous expense account.

Keep any currency remeasurement or settlement difference separate from an invoice mismatch. A legitimate exchange difference does not explain why one company has an invoice the other never recorded. If the cycle must be reversed, coordinate both entities and the payment team before reopening the invoices.

Operational netting and financial-statement presentation answer different questions. Under IFRS, IAS 32 permits offsetting a financial asset and liability when there is a currently legally enforceable right of set-off and the entity intends net settlement or simultaneous realization and settlement. A plan to run a group payment exercise does not by itself establish those conditions.

Ask the reporting accountant to assess the applicable framework, enforceability evidence, and actual settlement process. US GAAP reporting requires its own analysis. Preserve the gross receivable and payable schedules even when the presentation conclusion allows an offset, because reviewers still need to understand the underlying balances.

Publish a short exception list with the excluded invoice, reason, owner, and next action. Distinguish a genuine dispute from a missing posting or a counterparty that missed the cutoff. This keeps the next cycle from inheriting an undifferentiated backlog.

At the following close, trace each exception to settlement, correction, or an updated decision. Review any aged clearing balance with the two entity controllers together. A dependable netting process ends with an explanation in every participating ledger, not merely a lower number of bank transfers.