Global Treasury: Managing Liquidity Across Multiple Jurisdictions Without Daily Firefighting

You have five legal entities across four jurisdictions, five bank accounts, and three currencies. Every day a payment requires manual approval, transactions are delayed in correspondent banking chains for two to three days, transfers between entities within your own group are processed as third-party payments, and currency losses erode your margin. This is not an operational problem — it is an architectural one.

Treasury architecture is the system that defines which accounts serve which purpose, how money moves between legal entities, how currency risk is managed at the structural level, and who makes payment decisions without the principal's daily involvement. When treasury architecture is absent, daily firefighting is the inevitable result.

The Global Architect does not resist operational chaos out of mere intolerance for disorder. Daily firefighting is a symptom. The root cause is the absence of a treasury architecture: the accounts exist, but the system for managing money within the group in a structured way does not.

What Is Treasury Architecture — and Why Does It Matter?

Treasury is not accounting, and it is not manual payment processing. It is architecture: which accounts serve which purpose, how money moves between legal entities, how FX risk is built into the structure, and who makes decisions without the principal's day-to-day involvement.

Financial chaos in international structures is always the result of a reactive account structure: each new jurisdiction brought an account but no logic for how money should flow. The result: funds exist everywhere, but are not always accessible when and where they are needed.

A well-designed global treasury rests on three principles:

Account architecture: every account has a defined function — operational, reserve, or contingency. No account is multipurpose.

Structured intercompany flows: money between group entities moves according to pre-agreed rules, not as external transactions.

FX policy: currency risk is built into the structure, not resolved manually with every payment.

A company that moves liquidity in hours rather than days consistently outpaces its competitors. This is not a consequence of size or resources — it is a consequence of architecture.

The Three Core Elements of International Treasury Architecture

Below are the three pillars of a well-structured treasury and the most common mistakes associated with each.

Which Role Should Each Bank Account Play?

The most common mistake is treating a bank account as merely a receptacle for incoming funds. An account is a functional node in the architecture — and each node has a distinct role.

Operational account — current payments, payroll, and operating expenses. Typically held at an e-money institution (EMI) or a local bank in the operational entity's jurisdiction. It should not hold more than two to three months of operating expenditure. EMIs offer speed, but come with limitations: transaction and balance limits, absence of deposit insurance in certain jurisdictions, and the regulatory risk of licence withdrawal. Their role in the architecture should be supplementary, not primary.

Reserve account — the group's primary liquidity held at a Tier-1 bank in a neutral jurisdiction. This is where the bulk of group liquidity accumulates. Typically this account is held by the holding company — the entity into which royalties and dividends are directed.

Contingency account — long-term reserves held at a different bank and in a different jurisdiction from the reserve account. Freeze scenarios differ: a sanctions block, a regulatory freeze, and bank insolvency each require a different response. Having one more account, without a well-designed contingency access plan, solves nothing.

Important: every account must be held by the legal entity it serves. A mismatch between the account-holding entity and the nature of transactions passing through it is the first thing a KYC officer looks for during an audit.

Self-assessment — Account Architecture: Does every account in the group have a clearly defined purpose? If one account is frozen tomorrow — under which scenario (sanctions, regulatory action, bank insolvency) and which operations would stop? Does the group hold accounts at banks in different jurisdictions, or is everything concentrated at one bank? If even one account serves as a catch-all, the architecture has not been built.

How Should Money Move Between Entities in Your Group?

One of the main sources of daily firefighting is payment delays caused by correspondent banking chains. An international payment passes through one to three intermediary banks, each of which conducts its own compliance review. In major EU corridors this takes two to three business days; in less liquid corridors such as UAE to Asia or Latin America — up to five to seven days. The solution: direct banking relationships in each jurisdiction, or high-speed payment rails that bypass multi-bank correspondent chains.

Royalties and service agreements — one of the primary mechanisms for internal flows. The operational entity pays licence fees to the IP holding company, or fees for management functions. Each flow is documented, structured, and recurring. An important caveat: royalty structures are under active scrutiny from EU and OECD tax authorities. The IP holding company must have substantive IP ownership and demonstrable economic substance, comply with BEPS Actions 8–10, and maintain transfer pricing documentation.

Intercompany loans — a tool for moving liquidity within the group without immediate tax leakage through dividends. They must be structured at a market rate consistent with the arm's length principle and supported by full transfer pricing documentation. Interest on intercompany loans may also be subject to withholding tax in the lender's jurisdiction — this rate must be verified before structuring, as it directly affects the economic rationale of the instrument.

Cash pooling — consolidating the balances of all group entities into a single master account eliminates the situation where one entity pays overdraft interest while another in the same group holds surplus liquidity. Physical pooling transfers funds to the master account via a sweep instruction. Notional pooling creates a virtual master account and calculates interest on the net position without physically moving funds. Critical caveat: notional pooling is prohibited or materially restricted in several EU jurisdictions, including Germany and France. The permissibility of this format must be confirmed legally before structuring.

Self-assessment — Intercompany Flows: Is there a documented legal basis for every intercompany flow? Are intercompany loan rates set on arm's length terms, and has withholding tax on interest been verified in the lender's jurisdiction? How many days does a transfer between your group entities currently take? If intercompany transfers are being processed as external payments — your intercompany documentation is inadequate.

How Do You Manage Currency Risk Without Eroding Your Margin?

A group with euro revenue, dirham operating costs, and a dollar-denominated payroll carries currency risk every day — often without recognising the exposure. Unmanaged FX risk consumes between 1% and 3% of annual revenue — not a one-off mistake, but a systemic vulnerability.

Natural hedging through structure means that if revenue is received in euros via the European holding company, and payroll is paid in dirhams via the operational centre, the conversion occurs once, at a predictable point. This is an architectural decision, not speculation.

FX hedging instruments apply where the currency mismatch is material and predictable in both volume and timing. A forward contract locks in the rate symmetrically, eliminating any benefit from favourable rate movements. An option grants the right but not the obligation to transact, and carries a premium. For most international structures in the €2–20M revenue range, natural hedging through structure is sufficient and instrument-based hedging adds unnecessary complexity.

Conversion policy — the frequency and terms of conversions are set at policy level, not determined ad hoc. When to convert, at which bank, and at what rate are policy decisions, not operational ones.

Self-assessment — FX Policy: Do you know, in absolute figures, how much currency exposure has cost your margin over the last 12 months? Do you have a documented conversion policy — or are decisions made situationally? If you use forwards or options, do you understand the difference in their risk profile and cost? Without an FX policy, every rate shift feeds through to your margin without control.

How to Start Building Your Treasury Architecture

Treasury architecture is not built in a single decision. The process follows a fixed sequence: first the account structure is designed to match the group's corporate architecture, then intercompany flows are documented and formalised, and finally the FX policy is established. Each step follows from the previous one — none of them is layered on top of existing chaos.

If you recognise your situation in this description, an initial consultation will review your current treasury architecture and identify the priority areas for restructuring. Companies with a well-designed treasury move liquidity in hours rather than days, and respond to opportunities rather than fighting fires.