3 Best In-House Bank Software for Multi-Entity Treasury Teams

The three strongest in house bank software platforms for multi-entity treasury teams are Kyriba, Coupa Treasury, and TreasuryXpress. Each runs a virtual internal bank with dedicated accounts per legal entity, intercompany loan tracking, and automated funding with two-sided journal posting. Kyriba fits large multinationals with deep ERP integration needs. Coupa Treasury suits mid-market teams already on the Coupa spend platform. TreasuryXpress works for smaller multi-entity companies that need core in-house banking without an enterprise contract.


What Does In-House Bank Software Actually Do, and Why Does It Matter?

An in-house bank is a treasury structure where a central entity, usually a holding company or shared services center, acts as the internal bank for all other entities in the group. Each subsidiary holds a notional or physical account with the in-house bank instead of maintaining multiple external bank accounts in different countries. The in-house bank handles intercompany lending, cash concentration, and payment-on-behalf-of programs from one controlled center.

The software that runs this structure needs to do four specific things. It must open and maintain internal accounts per entity with running balances. It must book intercompany loans with interest accrual, maturity dates, and repayment schedules. It must execute funding sweeps and payment-on-behalf-of transactions, then post two-sided journal entries automatically. And it must enforce approval workflows so no intercompany transfer moves without the right authorization chain.

A spreadsheet can track some of these things historically, but it cannot enforce them in real time. When a subsidiary controller approves an intercompany draw in a spreadsheet, there is no system-level block stopping a second draw before the first is posted. That is the gap in-house bank software closes.

This distinction matters most when you have five or more legal entities, more than one currency, or regulatory environments where intercompany loans require documented arm’s length terms. At that point, the reconciliation burden on a manual process grows faster than the team can absorb it.


What Is the FintechSpecs Internal Bank Readiness Matrix?

Before evaluating any platform, treasury teams need to audit their own structure. The FintechSpecs Internal Bank Readiness Matrix is a four-column check that surfaces the structural prerequisites any in-house bank software will require you to have documented before go-live.

Entity Map: A complete list of legal entities in the group, their jurisdictions, their base currencies, and their intercompany relationships. No platform can build your internal account structure without this. If you do not have it, that is the first deliverable, not the software selection.

Funding Authority Matrix: Which entities can borrow from the in-house bank center, up to what amount, at what internal interest rate, and with whose approval. This becomes the approval workflow configuration in every platform reviewed here.

ERP Integration Depth: Where your chart of accounts lives, how intercompany journal entries are currently booked, and whether your ERP supports two-way API sync or requires file-based posting. Kyriba and Coupa Treasury both have direct connectors to SAP and Oracle. TreasuryXpress relies more on file-based integration for smaller ERP environments.

Regulatory Constraints: Whether any entities are in jurisdictions with thin-capitalization rules, transfer pricing documentation requirements, or restrictions on cross-border cash pooling. The software does not handle the tax analysis, but the structure it enforces needs to be pre-cleared with your tax counsel.

Running this matrix before demos saves significant time, because every vendor will ask for this information during scoping calls. Teams that arrive with it documented cut their implementation timelines noticeably.


How Do the Top In-House Bank Platforms Compare?

The table below maps the three platforms against the capabilities multi-entity treasury teams consistently ask about. All pricing is undisclosed publicly by these vendors; figures shown as contact-for-pricing reflect that position as of the date of this article.

PlatformInternal Accounts per EntityIntercompany Loan BookAutomated SweepsTwo-Sided Journal PostingERP ConnectorsBest Fit
KyribaYesYes, with interest accrualYes, rule-basedYes, real-timeSAP, Oracle, NetSuite, WorkdayLarge multinationals, 20+ entities
Coupa TreasuryYesYesYesYesSAP, Oracle, Coupa nativeMid-market, Coupa spend platform users
TreasuryXpressYesYesYesConfigurableFile-based, API for select ERPsSmaller multi-entity, 5-20 entities

Kyriba: What Does It Do for In-House Banking Specifically?

kyriba

Kyriba is the most fully realized in-house bank platform among the three. Its in-house banking module lets treasury teams open virtual accounts for each entity under a central in-house bank structure, track intercompany positions in real time, and execute funding requests with configurable approval chains before any transfer posts.

The intercompany loan book inside Kyriba records borrowing agreements with principal, interest rate, accrual method, maturity date, and payment schedule. When interest accrues, Kyriba generates the accounting entries automatically and passes them to the connected ERP. That two-sided posting is the feature most teams underestimate during evaluation, because booking the lender side and the borrower side simultaneously across two entities is exactly what a spreadsheet cannot enforce.

Kyriba also handles payment-on-behalf-of programs, where the in-house bank entity makes external payments on behalf of subsidiaries and nets the intercompany obligation internally. This is common in European treasury structures and reduces external bank account proliferation significantly. For teams already exploring Kyriba alternatives, the gap to close is usually whether the alternative can replicate this POBO functionality with the same ERP integration depth.

Pricing is enterprise-only and not publicly disclosed. Kyriba quotes based on entity count, transaction volume, modules selected, and integration complexity. Implementation is typically multi-month and usually involves a Kyriba-certified implementation partner.

Coupa Treasury: Who Is It Built For?

coupa

Coupa Treasury, formerly called Bellin TM5, was acquired by Coupa and integrated into the broader Coupa Business Spend Management platform. That history matters because Coupa Treasury’s in-house banking module is well-suited to organizations that already run procurement, AP, and expenses through Coupa. The data about payment obligations across entities is already in the system, which makes the in-house bank funding logic more accurate.

The platform supports notional pooling and zero-balance sweeping, intercompany loan management with documentation templates, and internal account statements that match what subsidiaries would receive from an external bank. Those internal statements are more than a reporting nicety: they are what subsidiary controllers use to reconcile their own books, and generating them automatically removes a manual reporting burden from the central treasury team.

Coupa Treasury is a reasonable choice for a Series C or post-Series C company in the 10 to 50 entity range that is already on Coupa’s platform and wants treasury functionality without adopting a separate TMS vendor. Standalone adoption, where Coupa is not already in place for spend management, is possible but loses the integration advantage that differentiates it from Kyriba at the enterprise tier.

As with Kyriba, pricing is contact-for-quote only. Coupa does not publish TMS module pricing publicly.

TreasuryXpress: When Does It Win?

TreasuryXpress positions itself as a cloud-native TMS built for mid-market companies that need real treasury management functionality without the implementation cost and timeline associated with Kyriba or Coupa Treasury. Its in-house banking module covers internal accounts, intercompany lending, and automated sweep rules, but the ERP integration story is narrower.

For a company with five to twenty entities, mostly in one or two currencies, and an ERP environment built on a mid-market platform like NetSuite or Sage Intacct, TreasuryXpress often delivers 80% of Kyriba’s in-house banking capability at a fraction of the total cost of ownership. The two-sided journal posting is configurable rather than automatic out-of-the-box, which means the finance team needs to invest time in the initial setup. After that configuration is done, it functions as expected.

TreasuryXpress does not publish pricing. Demo requests and scoping calls are the path to a quote. According to TreasuryXpress’s standard implementation documentation, go-live timelines for simpler entity structures can fall under 90 days, though this depends on how completely the customer’s entity map and ERP account mapping are documented before the engagement begins.

One trade-off worth naming: TreasuryXpress has a smaller partner network than Kyriba, which matters if your implementation requires significant custom integration work. Teams with an internal treasury systems team can often handle that scope. Teams without one may need to budget for consulting time regardless of which platform they choose.


What Features Should Every In-House Bank Platform Have?

Not every TMS that markets in-house banking capability actually delivers a full internal banking structure. Some platforms include intercompany loan tracking as a reporting feature without the posting controls that make it operationally sound. The checklist below is what separates a true in-house bank platform from a TMS that happens to have an intercompany module.

  • Virtual internal account per legal entity with a running balance that matches the ERP intercompany account
  • Intercompany loan agreement storage with terms, interest rate, accrual method, and maturity date
  • Automated interest accrual with journal entry generation on a configurable schedule
  • Funding request workflow with configurable approval levels and credit limit controls
  • Two-sided posting: every intercompany transaction posts to both the lending entity and the borrowing entity simultaneously
  • Internal account statements generated per entity on demand or on schedule
  • Payment-on-behalf-of module if the company runs centralized external payments
  • Audit trail on every funding event, approval, rate change, and account modification

If a platform being evaluated cannot demonstrate all eight of these in a live sandbox, the gap will surface during implementation. Asking for a live demo of a funded intercompany loan with the resulting journal entries is the most efficient way to test whether a vendor’s in-house banking claim is substantive. For teams building out a broader finance infrastructure, reviewing a treasury management system RFP question set before vendor calls gives the evaluation sharper teeth.


How Does In-House Banking Connect to Your Internal Ledger?

The internal treasury ledger is the accounting backbone of the in-house bank. Every intercompany funding event, every interest accrual, and every POBO payment needs to produce a journal entry that lands in the correct account in the correct entity’s books. This is where implementations most commonly fail: the in-house bank software generates correct transactions, but the ERP integration is configured incorrectly, so the intercompany accounts do not reconcile at month end.

The technical root of this problem is usually account mapping. Each entity has an intercompany payable or receivable account in the ERP. The in-house bank platform needs to know which internal account maps to which ERP account for each entity pair. For a five-entity company, that is a manageable matrix. For a 30-entity multinational with multiple currencies and multiple intercompany relationship types, that mapping table becomes a significant configuration artifact that needs to be built, tested, and maintained as the entity structure changes.

Kyriba handles this through its integration framework with direct connectors to SAP and Oracle. Coupa Treasury benefits from already having entity and account data inside the Coupa platform. TreasuryXpress requires the mapping to be configured during implementation and updated manually when the entity structure changes. None of these platforms auto-generate the mapping from scratch. That is a finance team deliverable, not a software feature.

For teams running NetSuite, the connection between treasury posting and the general ledger deserves specific attention. Tools built to automate reconciliation and close on NetSuite can reduce the manual work of clearing intercompany accounts at period end, but only after the account mapping is correctly configured in the TMS.


What Is the Real Implementation Timeline for In-House Bank Software?

Implementation timelines in this category are longer than procurement teams initially budget for, primarily because the work is not primarily technical. The technical integration between the TMS and the ERP typically takes four to eight weeks for a standard connector, based on typical vendor scoping calls with Kyriba and TreasuryXpress. The configuration work , mapping the entity structure, defining the funding authority matrix, setting up approval workflows, testing journal entries, and training subsidiary controllers , typically takes two to four times longer than the integration work, again based on vendor-reported scoping estimates rather than guaranteed timelines.

Consider a hypothetical company with 15 legal entities across four currencies. The ERP integration to SAP might be completed in six weeks. But documenting and configuring the intercompany loan terms for each entity pair, testing a full funding cycle with correct two-sided posting, getting subsidiary controllers to validate their internal account statements, and running a parallel close month before cutting over typically adds three to five months. That is a realistic timeline for a mid-market implementation, not an outlier.

The practical implication is that the internal project team, usually the VP of Finance or CFO plus one or two treasury analysts, carries most of the implementation burden. The software vendor provides the platform and an implementation playbook. The finance team provides the entity structure, the funding rules, the ERP account mapping, and the sign-off on every test case.


How Does In-House Banking Fit into a Broader Treasury Stack?

In-house banking is one module within a full treasury management system. The surrounding modules , cash visibility, bank connectivity, liquidity forecasting, FX management, and investment tracking , do not need to be in the same platform, but they need to share data. The in-house bank’s internal positions need to feed the liquidity forecast. The funding sweeps need to be visible in the cash position report. The interest income from intercompany loans needs to reach the investment portfolio tracking.

Teams building out treasury infrastructure sometimes adopt an in-house bank platform first and add forecasting and FX modules later. That sequence works if the platform is modular. Kyriba is designed that way; modules can be added after initial go-live. Coupa Treasury works similarly within the Coupa platform. TreasuryXpress is a more integrated product where the core treasury functions come bundled.

The alternative path is to use a lighter cash management or forecasting tool alongside a dedicated in-house bank structure, particularly at smaller entity counts. Teams evaluating the full range of cash flow forecasting platforms for treasury teams will find that most of those tools do not include in-house banking features. The two capability sets are genuinely distinct product categories, even when sold by the same vendor.

For finance teams running multi-entity close processes, the intercompany account reconciliation that in-house bank software automates is also one of the most time-consuming steps in a standard month-end close. Platforms that handle financial consolidation for multi-entity companies sit one step downstream from the in-house bank, consuming the intercompany eliminations that the treasury platform should already have clean.


Frequently Asked Questions

What is in-house bank software?

In-house bank software creates a virtual internal banking structure within a corporate group. A central entity, often a treasury center or holding company, opens internal accounts for each subsidiary, manages intercompany loans with documented terms, executes funding sweeps between entities, and generates two-sided journal entries so both the lending and borrowing entity’s books stay reconciled. It replaces manual spreadsheet tracking with system-enforced posting controls and approval workflows.

How is an in-house bank different from cash pooling?

Cash pooling is a bank-side service, where an external bank sweeps subsidiary balances into a master account to reduce net external borrowing. An in-house bank is an internal treasury structure that handles intercompany loans, internal payments, and payment-on-behalf-of programs independently of external bank mechanics. The two can coexist: the in-house bank manages internal positions while cash pooling manages the external bank structure. Most in-house bank platforms model both.

Can a TMS replace an in-house bank platform?

Some treasury management systems include in-house banking as a module, Kyriba and Coupa Treasury being the most complete examples among platforms widely deployed in North America. A generic TMS focused primarily on cash visibility or FX management may not include internal accounts, intercompany loan books, or two-sided posting. The key test is whether the platform can generate an internal account statement per entity and post both sides of an intercompany funding event simultaneously to the connected ERP.

What ERP integrations do in-house bank platforms support?

Kyriba supports direct connectors to SAP S/4HANA, SAP ECC, Oracle ERP Cloud, Oracle E-Business Suite, NetSuite, and Workday Financials. Coupa Treasury connects natively to SAP and Oracle and benefits from Coupa’s own spend platform data. TreasuryXpress supports file-based integration with most ERPs and direct API connections for a narrower set of platforms. For ERPs outside these lists, most platforms support flat-file or XML-based integration at higher configuration cost.

How much does in-house bank software cost?

None of the three platforms reviewed here publish pricing publicly. Kyriba and Coupa Treasury operate on enterprise contract terms, with pricing based on entity count, payment volume, modules selected, and integration complexity. TreasuryXpress is generally positioned as the lower total-cost option in this category, though still enterprise-priced. All three require a scoping call before any quote is generated. Budget cycles for this software category typically require board-level approval.

What is a payment-on-behalf-of program?

A payment-on-behalf-of program lets one entity, typically the in-house bank center, make external payments to third-party vendors on behalf of subsidiaries. The subsidiary’s payment obligation to the vendor becomes an intercompany obligation to the in-house bank instead. This reduces the number of external bank accounts the group maintains, centralizes FX risk, and simplifies compliance with banking mandates in certain jurisdictions. Kyriba and Coupa Treasury both support POBO programs. TreasuryXpress offers POBO functionality with configuration requirements that vary by entity structure.

How long does it take to implement in-house bank software?

Technical integration between the platform and an ERP with a supported direct connector typically takes four to eight weeks, based on vendor scoping estimates. The configuration work , documenting the intercompany funding matrix, mapping ERP accounts per entity pair, building approval workflows, testing journal entries, and running a parallel month-end close , typically adds three to six months depending on entity count and complexity. A 15-entity implementation with four currencies should be scoped at five to seven months total from contract signature to production go-live.


Conclusion

The core failure of a spreadsheet-based in-house bank is not that it lacks features. It is that it lacks enforcement. Any spreadsheet can record an intercompany loan. Only purpose-built in house bank software can block a second draw until the first is approved, post both sides of that draw to the right ERP accounts automatically, and generate the internal account statement that the borrowing entity’s controller actually needs to close their books. That gap is what distinguishes tracking from banking.

Kyriba is the right answer for large multinationals where the in-house banking module is one piece of a broader TMS deployment, particularly where SAP or Oracle integration depth matters. Coupa Treasury makes sense for mid-market teams already inside the Coupa platform who want treasury capability without a separate vendor relationship. TreasuryXpress is the practical choice for companies with five to twenty entities that need real in-house banking without a Kyriba-scale contract and timeline.

The most important thing any team can do before starting a software evaluation is complete the FintechSpecs Internal Bank Readiness Matrix: entity map, funding authority matrix, ERP integration depth, and regulatory constraints. Every vendor will ask for this information. Teams that arrive with it documented do not spend the first three months of implementation figuring out what they should have known before the contract was signed.

Sarah Whitmore
Sarah Whitmore

Sarah covers payment processing platforms and PayFac-as-a-service providers for FintechSpecs, digging into the residual splits and underwriting speed most vendors bury in the footnotes. She got interested in the space after watching a vertical SaaS company lose a deal over a five-day merchant onboarding delay, and she hasn't stopped asking vendors how fast is fast since.