How does Netting work with In-House Banking?
Netting calculates the confirmed settlement positions, while In-House Banking can settle positions for participating entities through internal mirror-account bookings instead of external bank payments. This can eliminate external banking fees for those internal settlements. Entities outside the in-house bank can still receive standard payment instructions, so both settlement methods can be handled within the same netting cycle.
A group can have sufficient cash overall and still create unnecessary payment activity inside its own structure. One entity pays another. A second entity owes money back in a different currency. Internal loans, management fees, royalties, trade balances and interest charges create additional obligations. Each item may be legitimate, but the settlement process can turn the group into its own network of counterparties.
For treasury, that creates a practical question: how much of the payment volume, FX activity and operational work exists only because internal obligations are being settled gross rather than coordinated centrally?
This is where intercompany netting becomes a liquidity topic, not just an administrative one. By offsetting obligations before settlement, treasury can reduce the number and size of payments that actually need to move between group entities.
The problem grows faster than the number of entities
Intercompany settlement often looks manageable when a group has only a few entities and currencies. The complexity changes quickly as the organisation grows.
More entities create more bilateral relationships. More currencies create more conversion points. Different local cut-off dates and reporting routines create timing differences. Disputed invoices or missing submissions delay the cycle. Treasury then becomes the coordinator between subsidiaries, ERP data, FX rates, payment execution and accounting.
A spreadsheet can calculate a net amount, but the calculation is only one part of the process. Treasury also needs to know who submitted data, which obligations are included, which items are disputed, when positions are confirmed, what FX rate is used and whether the final settlement has actually been executed.
Gross settlement hides the economic position
If each intercompany obligation is treated as a separate payment, the operational flow can be much larger than the group’s true net position.
That matters for both cash and FX. Two entities may have opposing obligations in the same currency. Several subsidiaries may owe and receive amounts across the same netting cycle. Settling each leg independently creates payment volume and, in multi-currency structures, can also increase the number of FX transactions treasury needs to manage.
Netting changes the starting point. Bilateral or multilateral obligations are calculated together, leaving the residual positions that actually need to be settled. Treasury can then focus payment execution and FX management on the net result rather than the full gross flow.
Local regulation can change how that settlement is handled. In jurisdictions such as India, South Africa, China or Brazil, restrictions may require gross settlement where receivables and payables cannot be offset, or a virtual netting approach that provides the netting view without settling the positions on a net basis.
A netting cycle needs more than a calculation engine
The strongest control comes when the entire cycle is structured.
A netting process needs defined participants, a settlement currency, cut-off dates and settlement timing. Obligations need to be collected from ERP systems or entered where necessary. Treasury needs visibility into missing submissions before the cycle closes. Entities need a way to review their statements, confirm their positions and dispute individual items. The calculation may need to be rerun as issues are resolved.
When those steps are coordinated through email and local files, the process depends heavily on personal follow-up. When they are part of one workflow, treasury gains a clearer view of the cycle before settlement is finalised.
The FX effect should be visible before settlement
Intercompany netting also changes the FX question.
In Nomentia, the previous day’s closing FX rate is applied to each invoice when it is uploaded into the netting cycle. Once opposing flows have been offset, the remaining currency exposure is the part that matters for settlement and potential hedging.
This allows treasury to work with residual net exposure instead of reacting to every gross bilateral flow. The result is a more focused basis for FX management and fewer internal transactions that require conversion.
Confirmation and dispute handling are part of liquidity control
An internal obligation does not become operationally reliable simply because it exists in an ERP.
Entities may disagree about an invoice, amount or timing. Data may arrive after the cut-off. A position can change before the final cycle is closed. Treasury needs to know where the disagreement sits and whether it affects the settlement result.
Structured statements and line-item dispute handling bring those questions into the cycle itself. Treasury can identify issues earlier, recalculate positions when necessary and close the cycle with a clearer record of what each participant has confirmed.
Settlement is where the netting result becomes useful
A netting process creates value only when the confirmed result reaches execution.
Once positions are finalised, settlement instructions can be generated and routed into the payment process or an in-house bank. Existing payment approvals still apply before funds move. This connects the calculation with the controls treasury already uses for execution. When netting and In-House Banking run on the same platform, confirmed net positions for entities inside the in-house bank can be settled through internal mirror-account bookings instead of external bank payments, avoiding the related external banking fees.
The settled result can then feed the wider liquidity and cash-positioning process, so the effect of the netting cycle is visible in the financial picture rather than remaining in a standalone workbook.
The audit trail matters because internal does not mean informal
Intercompany transactions may remain inside the group, but they still require control.
Treasury needs a history of imported obligations, calculation runs, confirmations, disputes, FX treatment and settlement. That history supports internal control, audit requirements and regulated environments where the organisation must be able to show how a settlement result was produced.
It also reduces reliance on individual knowledge. The cycle can be understood from the process record instead of reconstructed from inboxes and spreadsheet versions.
Netting is a working-capital and cash-deployment question
The conversation around intercompany netting is often framed around payment fees or process efficiency. Those benefits matter, but the treasury impact is wider.
A group that settles internal obligations inefficiently can move cash more often than necessary, create avoidable FX activity and make internal liquidity harder to interpret. Structured netting reduces that noise. It gives treasury a clearer residual position and a more controlled route from internal obligation to settlement. Depending on the group structure and transaction pattern, netting can reduce the number of intercompany payments by around 80–90%, lowering the volume of bank transactions and related processing costs.
For the CFO, the outcome is not simply fewer transactions. It is a better answer to a more important question: are we using the cash already inside the group as efficiently and transparently as we can?
