3 Best Intercompany Netting Software for Corporate Treasury

Intercompany netting software calculates net positions across multiple legal entities within a corporate group, then settles only the residual amounts on a fixed cycle, typically daily, weekly, or monthly. The three platforms most commonly shortlisted by North American treasury teams are Kyriba, SAP In-House Cash, and Coupa Treasury. Kyriba suits multi-entity companies already running a standalone TMS; SAP In-House Cash is the natural choice if the group operates on SAP ERP; Coupa Treasury fits mid-market teams that want netting without a full enterprise TMS implementation.


What Is Intercompany Netting and Why Does It Differ From Reconciliation?

Reconciliation matches payments to invoices after money has already moved. Netting prevents most of those movements from happening at all. The distinction is architectural: a netting platform sits upstream of settlement, aggregates all intercompany payables and receivables across entities within a netting cycle, and calculates a single net position per entity before any bank instruction is issued.

Say a corporate group has five subsidiaries trading with each other. Without netting, those entities might generate 20 bilateral wire transfers in a month, each carrying an FX conversion, a bank fee, and a correspondent banking delay. With multilateral netting, the platform nets all 20 exposures into five net positions, one per entity, and settles only those residuals through a central treasury entity. The gross payment volume shrinks; the bank fees and FX costs shrink with it.

Reconciliation tools, accounts payable automation, and even some ERP modules use the word “netting” loosely to describe offset logic inside a ledger. That is not the same thing. True intercompany netting software maintains entity-level balance positions across a defined netting cycle, enforces cutoff rules, handles multi-currency netting with a settlement currency, and produces a netting statement each cycle that every entity confirms or disputes before settlement runs.


The FintechSpecs Netting Architecture Test: Three Questions Before You Shortlist

Before evaluating any intercompany netting platform, treasury teams should answer three structural questions. These define which architecture fits and eliminate platforms that look capable on a demo but fail on day two of implementation.

Where does your intercompany data live today?

Netting software must ingest intercompany invoices or balance positions from your ERP, your subsidiary ledgers, or both. If the group runs a single SAP instance, the netting module that shares the same data model is almost always cheaper to operate than a standalone platform that re-imports the same data via API or flat file. If the group runs multiple ERPs across subsidiaries, a standalone TMS with API-based ingestion becomes the more practical path.

How many currencies do you net, and what is your settlement currency?

Multi-currency netting requires the platform to apply mid-market or agreed FX rates to convert all positions into a single settlement currency before netting, then produce FX difference entries that post back to each entity’s ledger. Platforms differ significantly in how they handle rate sourcing, whether they pull live rates or allow treasury to upload a rate file, and how they book the FX differential. This is where demos tend to look similar and live implementations diverge.

What is your netting cycle frequency and do any entities need to opt out?

Monthly cycles are common for smaller groups. Weekly or daily cycles require a platform that can automate the confirmation workflow without manual intervention. Some platforms require all entities to confirm their balances before the netting run closes; others allow treasury to override unconfirmed positions. Groups with entities in countries that restrict outbound cash flows, or that have local minority shareholders, often need to exclude certain pairs from the multilateral pool entirely.


Kyriba: Best Intercompany Netting Platform for Multi-ERP Corporate Groups

kyriba

Kyriba is a cloud-native treasury management system that includes a dedicated intercompany netting module. The netting module supports both bilateral and multilateral netting, configurable netting cycles, multi-currency settlement, and an entity confirmation workflow that runs inside the platform rather than over email.

Kyriba’s netting architecture uses a central treasury entity as the settlement hub, which is the standard internal bank model. Each subsidiary nets its positions against the hub, not directly against counterpart entities. This means the hub entity carries a matched book after each cycle rather than accumulating bilateral exposure across the group. The settlement instructions generated by Kyriba can be transmitted directly to banks via SWIFT or file-based integration, which eliminates a manual step that many treasury teams still handle outside their TMS.

Where Kyriba netting stands out

Kyriba’s FX handling is more configurable than most alternatives in this segment. Treasury can define a netting rate for each cycle, apply that rate to all positions, and have Kyriba auto-generate the FX difference journals for each entity. The platform also supports intercompany loan tracking alongside netting, so groups that use a combination of intercompany trade netting and intercompany funding can manage both workflows in one place.

The confirmation portal is browser-based, meaning subsidiary finance teams do not need a Kyriba license to confirm their netting statements. That matters for groups where most entities are cost centers rather than active treasury participants.

Where Kyriba netting has limits

Kyriba is a full TMS, and its pricing reflects that. The company does not publish list pricing. Implementation for a mid-market group typically involves a consulting engagement in addition to the platform fee, and the total cost of ownership over three years is higher than a netting-only module. If the group already runs Kyriba for cash visibility and bank connectivity, adding the netting module is incremental. If the goal is netting only, buying a full TMS to access one module is hard to justify below a certain entity count and payment volume.

For a broader look at how Kyriba compares to other treasury platforms across more dimensions, the Kyriba alternatives comparison on FintechSpecs covers ten platforms with specific notes on netting capability.


SAP In-House Cash: Best Intercompany Netting for SAP-Native Corporate Treasury

SAP

SAP In-House Cash (IHC) is the netting and in-house banking module within SAP S/4HANA and the legacy SAP ERP suite. It is not a standalone product. If the group runs SAP, IHC provides multilateral netting, intercompany account management, and payment factory capabilities from inside the same system that runs the general ledger.

The architectural difference from standalone platforms is significant. IHC operates on the actual posted intercompany balances in SAP rather than on data imported from an external system. That eliminates an entire class of reconciliation problems that plague multi-system netting implementations, specifically the mismatch between what the netting platform thinks the balance is and what the ERP actually shows. When netting closes, the settlement entries post directly into the SAP ledger with no intermediate transformation step.

Where SAP IHC netting stands out

For groups already on SAP S/4HANA, IHC represents the lowest marginal data risk of any netting approach. The position calculation runs on live SAP data. Netting cycle cutoffs enforce a hard boundary in the same system that processes intercompany invoices, so subsidiary accountants cannot post transactions into a closed period from outside the netting workflow.

IHC also handles the internal account structure that many large groups use to track intercompany funding and cash pooling alongside trade netting. A subsidiary’s internal account balance reflects both its trade netting position and any intercompany borrowing, which gives group treasury a single view of each entity’s net position with the center.

Where SAP IHC netting has limits

SAP IHC is only available to groups running SAP. If even two or three significant subsidiaries run Oracle, Workday, or a local ERP, IHC cannot pull those positions natively, and the workaround of importing external data defeats much of the data integrity argument. The module also requires SAP Treasury consultants to configure properly, and misconfigured IHC implementations are common enough to generate a steady market for remediation projects. The user interface, particularly in older SAP ERP versions, is functional rather than intuitive for subsidiary finance teams unfamiliar with SAP transaction codes.


Coupa Treasury (Bellin): Best Intercompany Netting for Mid-Market Treasury Teams

coupa

Coupa Treasury, built on the Bellin treasury platform that Coupa acquired, targets mid-market to upper-mid-market corporate treasury teams. It includes a netting module that supports multilateral intercompany settlement without requiring the full SAP suite or a lengthy TMS implementation project.

The netting workflow in Coupa Treasury is designed around the entity confirmation step. Each subsidiary accesses a web portal to review its netting statement, dispute line items, and confirm before the cycle closes. Coupa Treasury then generates settlement instructions, which can be transmitted via its bank connectivity layer. The platform supports multi-currency netting with configurable rate sources, including automated rate feeds.

Where Coupa Treasury netting stands out

Coupa Treasury’s implementation timeline is typically shorter than Kyriba’s for a netting-only deployment, partly because the platform was architected as a treasury workstation rather than an enterprise TMS that accumulated modules over decades. For a corporate group with 10 to 50 entities running a monthly or weekly netting cycle, Coupa Treasury reaches a usable state faster than a full Kyriba deployment.

The platform’s ERP connectivity covers SAP, Oracle, and Microsoft Dynamics through standard file and API integrations, which makes it more practical than IHC for mixed-ERP environments. Groups that have subsidiaries on different ERP platforms can still feed intercompany balances into a single netting run.

Where Coupa Treasury netting has limits

Coupa Treasury does not publish list pricing. The platform sits in a mid-market positioning that makes it more affordable than Kyriba for smaller groups but less feature-rich for very large treasury operations with complex in-house banking requirements. Groups that need daily netting cycles with straight-through processing and deep SWIFT connectivity at scale may find Kyriba or a bank-provided netting service better suited.


Intercompany Netting Software Comparison: Netting Cycle, FX, and Settlement Controls

PlatformNetting TypeCycle FrequencyFX HandlingSettlement MethodBest FitERP Dependency
KyribaBilateral and multilateralDaily, weekly, monthly (configurable)Configurable rate per cycle; auto FX journal entriesSWIFT, file-based bank transmissionMulti-ERP corporate groups, full TMS buyersNone (standalone TMS)
SAP In-House CashMultilateral (internal account model)Configurable within SAP posting periodsNative SAP FX; posts FX difference to GL directlySAP Payment Factory or external bankGroups fully on SAP S/4HANA or SAP ERPRequires SAP ERP
Coupa TreasuryMultilateralDaily, weekly, monthlyAutomated rate feeds; configurable settlement currencyBank connectivity layer; file exportMid-market groups, mixed-ERP environmentsNone (connects to SAP, Oracle, Dynamics)

What Does Intercompany Netting Software Actually Cost?

None of the three platforms in this comparison publish list pricing. Kyriba, SAP In-House Cash, and Coupa Treasury all use contract-based pricing tied to entity count, transaction volume, and implementation scope. That is consistent with the broader treasury management software market, where pricing is negotiated rather than listed.

What treasury teams should budget for in addition to the platform fee is implementation. SAP IHC requires SAP-certified treasury consultants to configure the internal account structure, posting rules, and payment factory integration. For a group with 20 entities running SAP, an IHC implementation is a multi-month project. Kyriba implementations for netting deployments involve connecting each subsidiary’s ERP, configuring the netting rules, and training subsidiary finance teams on the confirmation portal. Coupa Treasury’s implementation scope is generally smaller for netting-only use cases, but still involves ERP connectivity work for each entity on a different system.

For a realistic view of total cost of ownership across treasury platforms, the treasury management system RFP guide on FintechSpecs includes a scoring matrix that separates platform fees from implementation and integration costs.


How Does Multilateral Netting Reduce Payment Volume in Practice?

Consider a corporate group with eight subsidiaries in four currencies: USD, EUR, GBP, and CAD. In a given month, each subsidiary has intercompany invoices payable to and receivable from several other entities. Without netting, the group processes 32 bilateral wire transfers, each requiring an FX conversion where currencies differ.

With multilateral netting through a central treasury entity, the platform aggregates all 32 exposures, converts them to USD at the netting rate, and calculates a single net position for each of the eight entities. Six entities end up net payors and two end up net receivers. The group executes eight settlement transfers instead of 32. For entities operating in different currency zones, FX conversion happens once per entity’s net position rather than on each individual invoice , consolidating what would otherwise be multiple conversion events per entity into a single conversion per cycle. The bank fee and FX cost reduction tracks directly with the reduction in payment count.

This is not a hypothetical benefit. It is the core mechanical value of netting, and it is why the decision to implement netting software is distinct from the decision to improve reconciliation. Reconciliation automation, like the tools covered in payment reconciliation software for finance teams, operates after cash has moved. Netting operates before it moves.


Intercompany Netting vs. Cash Pooling: Which Does Your Group Need?

Treasury teams evaluating netting software often encounter cash pooling as a competing or complementary option. The two serve different purposes. Intercompany netting reduces the number of settlement transactions by offsetting payables against receivables within the group. Cash pooling concentrates physical or notional cash balances from multiple entities into a central account to optimize interest and reduce external borrowing.

Many large corporate groups run both. Netting settles the intercompany trade flows on a fixed cycle. Cash pooling manages the resulting cash balances across bank accounts. SAP IHC supports both under the same in-house banking architecture. Kyriba and Coupa Treasury also support cash pooling alongside netting, though the specific features and connectivity requirements differ.

Groups that run only cash pooling without netting still process every intercompany invoice as a separate payment; the pool just concentrates the resulting balances. Netting reduces the transaction count. Cash pooling optimizes what is left.


How to Evaluate an Intercompany Netting Platform Before You Sign

The FintechSpecs Netting Proof-of-Concept Standard defines four checks every treasury team should run before committing to a platform:

  1. Live netting run with real data. Run one full netting cycle in a sandbox environment using actual intercompany invoice data from the previous month. Any platform that cannot demonstrate this in a proof of concept is not ready for your environment.
  2. FX rate sourcing and journal entry output. Ask the vendor to show how the platform sources its FX rates, what rate is applied to each entity’s position, and what the journal entry output looks like for the FX difference. This is where most implementation surprises originate.
  3. Entity confirmation workflow without full licenses. Confirm that subsidiary finance teams can confirm their netting statements through a portal without each needing a paid seat on the platform. Groups with 20+ entities cannot afford full licenses for every subsidiary controller.
  4. Settlement instruction format for your banks. Ask for a sample settlement file or SWIFT message in the format your banks actually accept. File format incompatibility with your banking group is a late-stage problem that delays go-live by weeks.

The fintech vendor evaluation framework on FintechSpecs covers the broader due diligence process for any financial infrastructure decision, including contract terms and security reviews that apply equally to treasury software.


Does Your Group Need Standalone Netting Software or a Full TMS?

This is the structural question most treasury teams avoid until they are already mid-RFP. The answer depends on what else treasury needs to manage beyond netting.

If the group already has a TMS for cash visibility, bank connectivity, and FX risk management, adding a netting module from the same vendor is usually the right call, because the data flows are already established. If the group has no TMS and the primary pain point is intercompany settlement volume, buying a full TMS to access netting is expensive. Some banking groups offer netting services directly, which is a third option worth evaluating before committing to a software platform.

Groups between $500M and $2B in revenue with 10 to 40 entities and a mix of ERP systems tend to find Coupa Treasury the most proportionate fit. Groups above $2B running SAP throughout the enterprise tend toward IHC. Groups above $1B with complex multi-bank, multi-currency treasury operations and an existing or planned TMS investment tend toward Kyriba.

For finance teams also managing multi-entity consolidation alongside netting, the financial consolidation software comparison on FintechSpecs separates the consolidation and netting decisions clearly.


Frequently Asked Questions About Intercompany Netting Software

What is the difference between bilateral and multilateral netting?

Bilateral netting offsets payables and receivables between two specific entities. If Entity A owes Entity B $100,000 and Entity B owes Entity A $60,000, bilateral netting produces a single net payment of $40,000 from A to B. Multilateral netting does this across all entity pairs simultaneously, using a central treasury hub to calculate each entity’s net position across the entire group. Multilateral netting reduces payment volume more aggressively than bilateral netting for groups with three or more intercompany trading entities.

How often should a corporate group run its netting cycle?

Monthly cycles are standard for smaller groups or those with low intercompany trade frequency. Weekly cycles suit groups with high intercompany invoice volumes or significant FX exposure that grows materially over a month. Daily netting is used by large multinationals with internal banks that process intercompany flows at high frequency. Cycle frequency should match the volume of intercompany invoices rather than a default setting, since more frequent cycles increase administrative overhead for entity confirmation.

Can intercompany netting software handle multiple settlement currencies?

Yes. All three platforms covered here support multi-currency netting with a defined settlement currency, typically USD or EUR for North American-headquartered groups. Each entity’s gross positions in local currencies are converted to the settlement currency using a netting rate before the net calculation runs. The FX difference is booked as a journal entry in each entity’s ledger. The specific rate sourcing method, live feed, treasury-uploaded rate, or central bank rate, varies by platform and by group policy.

What data does intercompany netting software need from each subsidiary?

At minimum, the platform needs each subsidiary’s intercompany payables and receivables by counterparty entity, in the invoiced currency, for the netting period. This data typically comes from the subsidiary’s ERP via API or file export. Some platforms also ingest intercompany loan balances and accrued interest if the group nets funding flows alongside trade flows. Data quality at the subsidiary level, specifically whether intercompany invoices are posted consistently and on time, is the most common operational constraint on netting cycle accuracy.

Is intercompany netting software the same as an in-house bank?

No, though the two concepts overlap significantly. An in-house bank is an organizational structure in which a central treasury entity acts as an internal bank for the group, managing intercompany funding, FX, and settlement. Intercompany netting is one specific function an in-house bank performs. Netting software can support an in-house bank structure, as SAP IHC does explicitly, but a company can run intercompany netting without a full in-house bank architecture. The in-house bank is the broader operating model; netting is one of its core workflows.

How long does it take to implement intercompany netting software?

Implementation timelines vary widely based on entity count, ERP complexity, and banking connectivity requirements. A Coupa Treasury netting deployment for a mid-market group with 10 to 15 entities on two ERP platforms typically takes three to six months from kickoff to first live netting cycle. SAP IHC implementations for larger groups often run six to twelve months, particularly when payment factory configuration is included. Kyriba implementations for netting-only scope fall between the two. The entity confirmation portal setup and subsidiary training are often underestimated in project plans.

Can intercompany netting software integrate with both SAP and Oracle?

Kyriba and Coupa Treasury both support mixed-ERP environments and connect to SAP, Oracle, Microsoft Dynamics, and other ERP platforms via API or file-based integration. SAP In-House Cash is native to SAP only and cannot pull data directly from Oracle or Dynamics without a custom middleware layer, which typically offsets much of the data integrity advantage of running netting inside SAP. Groups with Oracle-based subsidiaries and SAP headquarters should evaluate Kyriba or Coupa Treasury rather than relying on IHC to cover the full entity population.

Do any of these platforms support netting with entities in restricted currency countries?

All three platforms allow specific entity pairs to be excluded from the multilateral netting pool, which is the standard approach for subsidiaries in countries with capital controls or outbound payment restrictions. The excluded entities continue to settle bilaterally, or their positions are netted within the country’s regulatory constraints. Kyriba and Coupa Treasury both document this as a configuration option. Groups with significant exposure in markets such as China, India, or Brazil , where capital controls and outbound payment restrictions are common , should raise this requirement explicitly in vendor demonstrations and confirm how the platform handles excluded pairs in its cycle reports.


Conclusion

The core misconception treasury teams carry into an intercompany netting evaluation is that better reconciliation solves the same problem. It does not. Reconciliation cleans up after payments happen. Netting prevents most of those payments from happening in the first place, which is a structurally different intervention with structurally different economics. If your intercompany settlement cost is driven by transaction count and FX conversion events, reconciliation automation will not move those numbers.

Between the three platforms here, the architecture question is more important than the feature comparison. SAP IHC wins on data integrity for pure-SAP groups and loses badly in mixed-ERP environments. Kyriba wins on flexibility and bank connectivity at the cost of a larger implementation footprint. Coupa Treasury sits in the middle and is the most proportionate fit for mid-market groups that need multilateral netting to work without a multi-year TMS transformation project.

The netting cycle, FX controls, and settlement instruction format are the three variables that determine whether a platform actually works in your environment. Demos look similar across all three. The differences show up in the first live cycle with real data, real banks, and real subsidiary controllers who have never logged into a netting portal before.

Michael Carter
Michael Carter

Michael writes about fintech strategy and operations for FintechSpecs, covering pricing models, banking-as-a-service, payment infrastructure, and the tools fintech founders use to scale. He focuses on the decisions behind the stack, not just the stack itself.