Summarise the article with your AI
Here you can read:
For groups with multiple subsidiaries, managing intercompany loans, transfers and debt can become an ongoing, manual headache during month-end closing. Manual intercompany accounting can also create financial reporting risks, tax compliance exposure, and unnecessary bank fees. But intercompany netting can automate settlements, reduce transaction volume, and ensure group-wide transparency through modern treasury automation.
The hidden cost of intercompany complexity at month-end
It is the last week of the month. Your finance team is manually reconciling countless intercompany balances across six subsidiaries in three currencies. The issue isn't one of speed, it's about the systemic unreliability these manual reconciliations create.
Intercompany transactions now account for a substantial portion of global trade flows with some estimates suggesting that 30% to 50% of world trade takes place within multinational enterprise structures. Yet most organisations still manage them through spreadsheets and manual reconciliation. The problem only grows as entities multiply: a five-entity group generates up to 20 bilateral intercompany pairs. It’s like ricegrains on a chessboard multiplying with each new subsidiary added or company merged into a group. Every settlement that clears through external bank rails again generates unnecessary FX conversion costs and bank fees. All back-and-forward.
Why do finance teams struggle with intercompany management at scale? Two structural problems create the bottleneck. First, bilateral transaction volume increases significantly as the group expands. Second, each bilateral pair that settles externally triggers CHAPS or BACS payments, FX conversions, and bank charges that erode working capital.
When entities maintain their own records without a single source of truth, month-end becomes an exercise in explaining differences the system itself created.
What is intercompany netting and why it's misunderstood
Intercompany netting is the process by which a group's finance function offsets mutual payables and receivables between subsidiaries, settling only the net balance through a single payment rather than executing multiple gross bilateral transfers.
Despite its simplicity, netting can still be misunderstood in mid-market treasury operations. It’s easy to and many finance leaders are confusing netting with cash pooling, or assume it requires complex legal structures. In reality, netting is one of the most accessible tools for groups with centralised treasury functions, delivering immediate transaction cost savings.
To clarify: Cash pooling concentrates liquidity to optimise interest. Netting reduces settlement volume to minimise transaction costs.
Best-in-class treasury teams use both: netting to reduce the number of external payments, and pooling to optimise the cash position that remains.
Bilateral vs multilateral netting
Understanding the difference between bilateral and multilateral netting determines how your treasury operation can save money and reduce complexity:
Bilateral netting pairs two entities and offsets their mutual obligations. If a UK subsidiary owes the German parent €50,000 and the German parent owes the UK £40,000, bilateral netting reduces this to one net payment instead of two gross transfers (after adjusting for a base currency).
Multilateral netting involves three or more entities settling through a central netting centre. Think of four subsidiaries: UK, Germany, Netherlands, and Spain. Under gross bilateral settlement, this creates 12 potential payment pairs. With multilateral netting through a treasury centre, the group executes just four net settlements.
| Approach | Transaction pairs | Bank fees | FX conversions | Settlement risk |
| Gross bilateral | 12 | High | Multiple | High |
| Multilateral netting | 4 | Reduced | Centralised | Reduced |
Example with 4 entities and a central netting center vs. bilateral netting
The cost difference is structural, not marginal. Every eliminated transaction removes bank fees which can cost between £20 and £35 for a single CHAPS transaction, FX spreads, and settlement timing losses from money in transit. For groups processing hundreds of intercompany transactions monthly, multilateral netting can thus significantly reduce costs compared to gross settlement.
Cash pooling vs netting: what's the difference?
Cash pooling and netting solve different treasury problems, though they're often conflated as already mentioned.
Notional pooling calculates interest on aggregated balances without physically moving cash.
Zero-balance pooling sweeps cash from subsidiary accounts to a master account daily.
Both techniques optimise interest income and borrowing costs.
Netting, on the other hand, reduces the number of external settlements by offsetting payables against receivables before any payment executes. It's a volume reduction strategy, not a liquidity concentration strategy.
The two techniques complement each other. A multinational might use multilateral netting to reduce intercompany operations settlement volume from 200 transactions to 40, then use zero-balance pooling to sweep the resulting net balances into a central liquidity account.
Modern treasury platforms typically integrate both capabilities, allowing finance teams to configure netting cycles and automated settlement instructions that feed directly into cash pooling structures.
The operational risks of managing intercompany loans manually
Intercompany loans create four specific risks that practitioners in multi-entity groups immediately recognise.
Interest calculation drift occurs when Euribor or other benchmark-referenced rates are recalculated manually across subsidiaries with slightly different outcomes. Inconsistencies between the entities then create transfer pricing exposure. HMRC and other tax authorities may scrutinise undocumented or mis-priced intercompany loans as potential evidence of transfer pricing non-compliance, which can trigger enquiries and potential adjustments.
Amortisation schedule misalignment emerges when loan terms tracked in Excel across subsidiaries diverge over time. One entity may record a five-year term; another records seven years. By year three, principal balances no longer reconcile.
Audit trail gaps appear when drawdowns, repayments, and interest accruals lack complete time-stamped records. IFRS 9 requires entities to recognise expected credit losses for intercompany loans, which demands a forward-looking assessment of borrower creditworthiness, a difficult task without systematic documentation.
Regulatory exposure intensifies as groups scale. The OECD's BEPS framework requires that intercompany loan pricing reflect arm's length principles, including consideration of implicit parental support. Spreadsheet-based tracking may not adequately demonstrate compliance when tax authorities challenge loan pricing during audits.
How intercompany reconciliation breaks down at scale
When entities maintain separate records, discrepancies arise from structural causes: timing differences, currency revaluation, and invoice coding inconsistencies, symptoms of decentralised record-keeping, which is why intercompany accounting best practices are critical to master.
The architectural solution is a single intercompany ledger: one source of truth for all bilateral balances, updated in real time from ERP entries. When both entities post to the same central register, timing differences become visible immediately rather than surfacing weeks later during close.
Groups using modern treasury platforms report significant reductions in days-to-close. According to industry benchmarks, automation can bring month-end close forward by several days, reducing the time per transaction from minutes to seconds. Results vary based on transaction complexity and system maturity.
What a modern intercompany netting process looks like
A robust intercompany netting process comprises five core components that eliminate manual intervention while maintaining audit control.
First, a centralised intercompany register that maintains entity-level positions updated in real time from ERP entries. Each transaction posts to both entities simultaneously, creating automatic two-sided entries that eliminate reconciliation discrepancies.
Second, automated Euribor- (or other benchmark) referenced interest calculations that apply rate updates at each fixing date without manual formula changes. Variable-rate loans track reference indices daily, recalculating interest accruals automatically across all outstanding periods.
Third, netting cycle management that operates on weekly or monthly windows with automated settlement instructions. At cycle close, the system calculates net positions, generates payment files, and posts general ledger entries without separate journal entry steps.
Fourth, a documentation engine that produces loan agreements, repayment schedules, and audit-ready interest accrual records with full timestamp and user attribution.
Fifth, ERP writeback which posts reconciled positions to the general ledger automatically. Settlement confirmations flow back from banks, match against original instructions, and update document statuses without manual verification.
This framework serves as the evaluation standard: any treasury management system (TMS) claiming to automate intercompany management should deliver all five components.
How modern treasury platforms automate intercompany loan and netting management
Leading treasury management systems deliver the five-component framework through integrated modules that connect bank feeds, ERP systems, and payment rails.
Modern treasury platforms provide intercompany modules with benchmark-referenced interest calculation engines that update rates automatically at reset dates. Cash pooling and netting hubs centralise settlement instructions across all group entities.
Bidirectional ERP integration with SAP, Business Central, and NetSuite and other ERPs maximised through connectors like the SAP integration, reflects position changes in near real time, eliminating overnight batch delays.
The result is measurable operational improvement. Groups report significant reductions in manual treasury tasks, often 75% or more, with daily management consuming substantially less time after automation.
As an example, thePower, an education company operating in more than 60 countries, significantly accelerated their month-end close and reduced payment execution time from minutes to seconds per transaction after implementing treasury automation.
The audit trail captures every action: who validated each netting bundle, when settlement instructions were transmitted, and which rule triggered each GL posting. Compliance teams demonstrate regulatory adherence without reconstructing histories from email archives and spreadsheet versions.
For treasury teams managing complex group structures, automation transforms intercompany management from a monthly bottleneck into a continuous background process.
