Article map
An in-house bank is sometimes described as a central treasury team with an intercompany loan spreadsheet. A mature model is much more: it is an internal financial-services operating platform through which subsidiaries can fund, invest, pay, collect, hedge and settle with the group treasury centre. The arrangement can reduce external balances and transaction costs, improve netting and strengthen policy execution, but it also concentrates operational, liquidity and governance responsibilities.
The central question is not whether the group can create internal accounts. It is whether those accounts, services and prices can be governed with the discipline expected of material financial relationships. Participating entities need clear entitlements, statements, interest calculations, dispute processes and evidence. Central treasury needs reliable cash, exposure and settlement information across currencies and legal entities.
This article presents a practical TMS-centred blueprint for designing an in-house bank that is scalable, transparent and controllable.
1. Define the service catalogue and participation perimeter
An in-house bank should have an explicit service catalogue. Without one, different entities develop different expectations and central treasury becomes responsible for activities that were never designed or resourced. Participation may also vary by country, currency, entity type and regulatory constraint.
The operating boundary should define:
- internal current accounts for operating balances and settlements
- short-term deposits, overdrafts, term funding and committed internal facilities
- payments-on-behalf-of, collections-on-behalf-of and intercompany netting
- central FX execution, hedge allocation and settlement services
- internal guarantees, bank-fee allocation, liquidity pricing and management reporting
The perimeter should identify exclusions as clearly as inclusions. An entity may use central FX but retain local payments, or participate in netting while remaining outside cash pooling. The TMS should represent those service entitlements by entity and effective date.
2. Model internal accounts as real financial records
Internal accounts need the same core attributes that make external instruments governable: owner, currency, value date, balance, rate, limit, maturity, settlement status and accounting mapping. Treating them as memo fields creates inconsistencies between subsidiary books and central treasury.
The governed data record should capture:
- unique internal account number linked to participating legal entity and currency
- opening balance, value-dated movements, available balance and overdraft limit
- interest basis, reference rate, spread, day-count convention and compounding rule
- transaction source, purpose, counterparty entity and underlying external event
- due-to and due-from ledger mappings with statement and confirmation references
The central and subsidiary views should be mirror images derived from one transaction record. Separate spreadsheets maintained by each party invite breaks in value date, rate, currency and classification.
3. Connect subsidiary requests to central execution
The operating model should translate business needs into controlled internal transactions. A subsidiary funding request, payment proposal or hedge requirement should be captured, tested against policy and entitlement, approved, executed externally where necessary and posted to internal accounts without manual reconstruction.
The end-to-end workflow should make visible:
- entity request or automated trigger with amount, currency, date and purpose
- policy, limit, documentation and authorised-requestor validation
- central decision on internal funding, external funding, investment or netting action
- execution, confirmation and settlement linked to the originating request
- automatic internal-account movement, interest schedule and entity accounting output
Status visibility matters. Participating entities should know whether a request is submitted, approved, executed, settled or rejected, and central treasury should see pending internal obligations alongside external liquidity.
4. Govern credit, liquidity, pricing and conflicts
Centralisation does not eliminate risk; it relocates it. The in-house bank may become the largest counterparty to every subsidiary and the largest internal user of group liquidity. Governance should therefore cover internal credit limits, liquidity buffers, pricing approval, service continuity and conflicts between group optimisation and entity solvency.
The control architecture should address:
- entity borrowing and deposit limits linked to approved internal credit assessment
- minimum liquidity and external facility headroom for the central treasury entity
- arm’s-length or policy-supported pricing with tax review and effective dates
- independent approval of rate overrides, write-offs and limit breaches
- documented escalation when group optimisation conflicts with local cash requirements
Legal, tax, exchange-control, transfer-pricing and regulatory analysis is jurisdiction-specific. The TMS can enforce the approved model, but it cannot determine whether a service is permissible or how it should be documented in each country.
5. Give participants statements, limits and self-service visibility
An in-house bank gains credibility when subsidiaries can see their positions and understand charges without relying on central treasury to prepare ad hoc reconciliations. The TMS should provide participant-level views while preserving central control over configuration and execution.
The TMS configuration should support:
- entity portal for balances, movements, requests, statements and confirmations
- real-time limit utilisation and projected interest or fee information
- automated internal statements and bilateral reconciliation
- workflow for disputes, rejected requests and missing documentation
- consolidated external and internal liquidity, FX and counterparty views
Access should follow entity boundaries. A local user may view and initiate for its own legal entity but should not see another entity’s confidential positions unless the role is explicitly authorised.
6. Evaluate value across the group, not only the centre
An in-house bank can appear successful at central level while imposing friction or hidden costs on participants. Measurement should cover external savings, internal service quality, risk concentration, funding efficiency and reconciliation quality.
Management reporting should measure:
- external debt avoided, surplus cash mobilised and bank balances reduced
- intercompany netting volume and gross payment reduction
- weighted internal and external funding cost by currency
- request turnaround, straight-through processing and dispute ageing
- internal-account breaks, limit breaches and overdue settlements
Service-level metrics should be visible to participating entities. Transparency helps distinguish a genuine operating issue from resistance to centralisation and gives management evidence for refining the model.
7. Build the in-house bank in service increments
A complete in-house bank is rarely delivered safely in one step. A practical sequence starts with visibility and internal accounts, then adds netting, funding, payments or FX as data and governance mature. Each service should have a defined owner and operational acceptance criteria.
The implementation plan should sequence:
- establish entity and currency internal accounts with opening-balance reconciliation
- introduce intercompany netting and internal statements
- add short-term deposits and funding with controlled interest calculation
- extend to POBO, COBO or central FX where legal and technical readiness exists
- formalise service levels, issue management and periodic participant review
The implementation should include close and stress scenarios, not only normal processing. Treasury must know how internal accounts, external liquidity and participant communications will operate when a bank, currency or system is disrupted.
Management questions before approval
Before management approves in-house bank operating model, the discussion should test the boundary described by define the service catalogue and participation perimeter, the reliability of unique internal account number linked to participating legal entity and currency, and whether entity borrowing and deposit limits linked to approved internal credit assessment remains effective when an exception occurs. It should also ask how external debt avoided, surplus cash mobilised and bank balances reduced will reveal whether the decision delivered its intended treasury result.
- Is the in-house bank service catalogue formally defined?
- Is participation configured by entity, country, currency and service?
- Are internal accounts complete financial records rather than memo balances?
- Do subsidiary and central entries derive from the same transaction?
- Are internal limits, pricing and approvals governed?
- Have tax, legal and exchange-control implications been reviewed?
The TMS record should connect those answers to connect subsidiary requests to central execution and to the action 'establish entity and currency internal accounts with opening-balance reconciliation'. Where judgement changes the normal route for in-house bank operating model, the evidence, approver, effective date and next review should remain visible beside entity portal for balances, movements, requests, statements and confirmations.
Evidence a controlled TMS should retain
The operating record for in-house bank operating model should show how unique internal account number linked to participating legal entity and currency became an approved action under govern credit, liquidity, pricing and conflicts. It should retain source identity, calculation or transformation, workflow status, exception treatment and approval, together with the downstream result represented by entity portal for balances, movements, requests, statements and confirmations.
- entity borrowing and deposit limits linked to approved internal credit assessment
- minimum liquidity and external facility headroom for the central treasury entity
- arm’s-length or policy-supported pricing with tax review and effective dates
- entity portal for balances, movements, requests, statements and confirmations
- real-time limit utilisation and projected interest or fee information
- automated internal statements and bilateral reconciliation
Version history for unique internal account number linked to participating legal entity and currency should preserve the information used when the decision was taken, even if later correction changes the current view. Comparing that history with external debt avoided, surplus cash mobilised and bank balances reduced and the practical outcome in 'turning scattered intercompany loans into an internal liquidity market' allows management to evaluate process discipline and decision quality without hindsight rewriting.
Practical illustration: turning scattered intercompany loans into an internal liquidity market
A multinational group has subsidiaries placing deposits with local banks while other entities draw expensive overdrafts. Intercompany funding is arranged through emails and month-end spreadsheets, creating inconsistent rates and overdue confirmations. The group creates an in-house bank for five major currencies.
Each entity receives internal current accounts and limits. Daily surplus cash is swept or notionally reflected, funding requests are approved through workflow, and the TMS applies approved reference rates and spreads. External borrowing and investment remain with central treasury, while entity statements and ledger entries are produced automatically.
Within several cycles, the group reduces external overdrafts and avoids unnecessary deposits, but it also identifies two entities whose liquidity cannot legally be transferred. Those constraints remain visible rather than being hidden by a group total.
Implementation checklist
A treasury team preparing to operationalise this topic should be able to answer yes to the following questions:
- Is the in-house bank service catalogue formally defined?
- Is participation configured by entity, country, currency and service?
- Are internal accounts complete financial records rather than memo balances?
- Do subsidiary and central entries derive from the same transaction?
- Are internal limits, pricing and approvals governed?
- Have tax, legal and exchange-control implications been reviewed?
- Can participants view balances, statements and request status?
- Are external and internal liquidity positions connected?
- Are breaks and disputes owned through workflow?
- Has disruption and liquidity stress been tested?
Common design failures
In-house bank programmes underperform when they centralise transactions without creating a service and control model.
- maintaining internal balances in disconnected spreadsheets
- using one generic interest rate regardless of currency, tenor or policy
- allowing central treasury to override entity limits without independent approval
- failing to provide entities with statements and transaction transparency
- ignoring local restrictions because the group appears liquid in aggregate
- adding services faster than accounting and operational capacity can support
The centre earns trust by producing accurate, timely and explainable services. Central authority without reliable service is not an in-house bank; it is merely dependency.
Closing perspective
An in-house bank can convert fragmented group liquidity into an internal market for cash, funding, payments and risk management. Its success depends on modelling internal financial relationships with the same seriousness applied to external ones.
A TMS provides the operating spine when requests, execution, internal accounts, limits, pricing, statements, accounting and evidence remain connected. The resulting value is both financial and organisational: less external friction and clearer accountability inside the group.
Frequently asked questions
What is an in-house bank?
An in-house bank is a central treasury operating model that provides defined financial services to group entities, such as internal accounts, funding, investments, payments, collections, netting and FX execution.
Does an in-house bank require physical cash pooling?
No. It may use physical pooling, notional pooling, virtual accounts, intercompany netting or internal accounting structures depending on legal, tax, banking and operational constraints.
What TMS capabilities are important for an in-house bank?
Key capabilities include internal accounts, entity entitlements, limits, interest and fee calculation, request workflow, external execution, netting, statements, accounting, reconciliation and complete audit history.