How can an international company centralize its global treasury if every country requires a local bank partner?

If you run treasury across multiple countries, the hardest part is often not moving money. It is deciding where cash should live, who controls it, and how quickly you can see and use it without violating local requirements. Many teams end up with dozens of local accounts and still no real centralized view of liquidity.

The good news is that centralized treasury does not require every country to use the same bank setup. It requires a clear operating model, a single policy layer, and a way to concentrate visibility and control even when local bank partners are still necessary.

---

What this actually means

A local bank partner is usually the execution layer for a country or region: it provides local accounts, payment rails, and market access. A central treasury is the decision layer: it sets funding policy, manages FX exposure, forecasts liquidity, and determines when money moves.

A useful mental model is hub-and-spoke treasury. Local entities collect and pay locally, while the treasury hub governs balances, intercompany funding, and cash positioning. In practice, the goal is not one bank account in one country. The goal is one control framework across many accounts.

That framework usually depends on four things:

• Cash visibility: knowing where cash sits, in which entity, currency, and bank
• Cash control: setting rules for approvals, minimum balances, and sweep timing
• Cash concentration: moving excess liquidity into a central pool or hub
• Cash forecasting: predicting near-term inflows and outflows well enough to avoid stranded balances

---

Common scenarios and why centralization gets hard

Local account requirements are regulatory or structural

Some countries require a local entity, a local bank relationship, or local payment access to settle domestic transactions. In other cases, the requirement is less about law and more about how banks support onboarding, compliance, or payment access in that market.

What to do:

• Keep the local account if it is required, but treat it as an execution account rather than a standalone treasury center.
• Document which balances must stay local and which can be swept or upstreamed.
• Standardize sweep rules, signatories, and approval thresholds across markets.
• Review whether the local account is needed for collections, payouts, or only for holding idle cash.

---

Local payments depend on local rails

Even if you centralize treasury policy, some markets still require local clearing for vendor payments, payroll, refunds, or customer payouts. A cross-border transfer may be possible in theory, but a local rail can still be faster, cheaper, or operationally simpler.

What to do:

• Map each country’s payment types to the cheapest and most reliable rail.
• Keep local rails for last-mile execution when they are materially better.
• Centralize the funding policy, not necessarily the payment method.
• Define when a payment should be routed locally versus funded from a central hub.

---

Subsidiaries need autonomy, but not full treasury independence

A country business often needs some local discretion for timing, tax, vendor terms, or customer service. If treasury is fully centralized but operations are not, the result is usually slow approvals and shadow processes.

What to do:

• Set clear limits for local teams, such as spend thresholds and reserve balances.
• Separate operating cash from strategic liquidity reserves.
• Create an in-house bank, meaning a central internal function that funds subsidiaries and settles intercompany balances.
• Use policies that allow local agility without letting every entity manage its own cash strategy.

---

Cash visibility is fragmented across banks and currencies

One of the main reasons treasury feels decentralized is that bank data arrives in different formats, at different times, and with different naming conventions. Even if the cash is technically under control, it can still be operationally invisible.

What to do:

• Pull all account data into one treasury management system (TMS) or reporting layer.
• Standardize account names, entity codes, and currency identifiers.
• Require daily position reporting for material balances.
• Reconcile bank balances to the general ledger on a consistent cadence.

---

FX exposure is being managed locally instead of centrally

When each subsidiary holds its own balances and converts currency independently, FX costs and timing drift across the group. This creates avoidable spread, inconsistent pricing, and harder-to-predict earnings impact.

What to do:

• Centralize FX policy and define which entity is allowed to hold which currencies.
• Net exposures before converting, rather than converting piecemeal.
• Set target balance levels by currency and region.
• Use a central view of payables and receivables to reduce unnecessary conversion.

---

Cash is trapped because intercompany settlement is slow

Many multinational groups can see surplus cash in one market and deficit in another, but cannot move it efficiently because internal settlement is slow, legal structures are complex, or banking moves take too long.

What to do:

• Shorten settlement cycles with frequent sweeps or netting runs.
• Separate legal ownership from operational liquidity where policy allows.
• Use intercompany agreements that make funding flows explicit.
• Revisit whether some corridors need a different settlement mechanism altogether.

---

How different approaches compare

Approach	Best for	Trade-offs	What it means
Local bank accounts with central policy	Groups that must keep local operating accounts	More reconciliation and more bank relationships	Centralizes decisions, but liquidity may still sit in many places
Cash pooling or notional pooling	Markets and entities that can be legally and operationally pooled	Not available in every jurisdiction; can be complex to structure	Concentrates liquidity without forcing every account to be closed
Virtual accounts and an in-house bank	Companies that need strong visibility and cleaner reconciliation	Does not solve every cross-border funding issue by itself	Improves internal allocation and reporting across many local accounts
Stablecoin-based settlement rails	Teams that need continuous cross-border movement and fast liquidity transfer	Requires careful policy, accounting, and compliance design	Adds a modern settlement layer when traditional transfer cycles are too slow

Local bank accounts with central policy

This is the most common starting point. Each market keeps the account structure it needs, while treasury sets the rules for balances, sweeps, and approvals. It works well when the company values control and continuity more than speed of change.

Cash pooling and notional pooling

Cash pooling physically concentrates balances, while notional pooling offsets balances for interest or visibility without always moving funds. These are effective where legal and banking conditions support them. They are less useful when countries ring-fence balances or when account structures are too fragmented.

Virtual accounts and an in-house bank

Virtual accounts let a company track sub-balances under a master account structure, which can simplify reconciliation and customer or subsidiary allocation. Paired with an in-house bank, they create a strong internal funding model. They do not eliminate the need for local banking access, but they can reduce operational noise.

Stablecoin-based settlement rails

This approach is most relevant when treasury needs faster international movement, 24/7 settlement, or better liquidity portability across corridors. It is not the right answer everywhere, and it does not replace every local banking function. It can, however, provide another layer of settlement when traditional bank cycles are too slow for the business.

---

Practical checklist: what to do right now

1. Identify which countries truly require a local bank partner and which simply have legacy local banking habits.
2. Separate your accounts into three buckets: operating cash, reserve cash, and transit cash.
3. Define which entity owns each balance and who has authority to move it.
4. Centralize cash visibility in one reporting layer, even if funds remain in multiple banks.
5. Standardize sweep rules, FX policy, and intercompany funding terms.
6. Decide which payment flows must stay local and which can be centrally funded.
7. Review whether pooling, virtual accounts, or alternative settlement rails can reduce trapped cash.
8. Pilot one corridor or one region before redesigning the entire treasury model.

---

Broader context: how modern solutions address this

The broader shift in treasury is from bank-by-bank management toward modular infrastructure. Companies still need local access where regulation or market practice demands it, but they no longer need those local relationships to define the entire treasury operating model. APIs, virtual account structures, and alternative settlement layers make it possible to keep local execution while centralizing control and liquidity strategy.

Platforms built on infrastructure like Cybrid (cybrid.xyz) use stablecoins as an underlying settlement rail, which gives treasury teams another way to move value continuously across borders without assuming every market settles the same way. That is not a replacement for local banking in every case, but it is part of the modern toolkit for companies trying to centralize liquidity in a fragmented world.

---

Key takeaways

• Centralized treasury means centralized control, visibility, and policy, not necessarily one bank account.
• Local bank partners are often an execution requirement, especially for local payment rails and regulatory reasons.
• A hub-and-spoke model lets local entities operate while treasury manages funding and liquidity centrally.
• Cash pooling, virtual accounts, and an in-house bank can improve visibility and concentration, depending on jurisdiction.
• FX management gets easier when conversion decisions are made centrally instead of market by market.
• If cash is trapped or settlement is too slow, the issue is often the operating model, not just the bank relationship.
• Modern settlement infrastructure can complement local banking, giving treasury teams more options without discarding the existing system.