For most of the last forty years, treasury was a function. Its remit was narrow: hold cash, pay invoices, hedge a small set of obvious exposures. It reported into the CFO. It rarely reached the board.
That arrangement made sense in a world where most enterprises operated in one or two currencies, banked with one or two relationships, and faced a payments landscape that, while not fast, was at least predictable. The job of treasury was to keep the lights on. It was unglamorous, and its absence from the boardroom reflected its place in the corporate imagination — useful, but downstream.
That world is gone. We are now operating in an environment where the average mid-market business with international ambition transacts in seven to twelve currencies, holds accounts with five or more financial institutions, and depends on a settlement infrastructure that can swing the company's working capital by full percentage points of revenue in any given quarter. Treasury, in other words, is no longer downstream of strategy. It is — increasingly — strategy itself.
This essay argues that the design of a company's financial infrastructure now belongs alongside strategy and talent as a board-level concern. We are not arguing that boards need to manage treasury. We are arguing they need to understand it, allocate to it, and treat its architecture as a load-bearing decision.
I. The shift
Three forces have moved treasury from the basement to the C-suite over the last decade.
The first is the dispersion of revenue. A company that, ten years ago, would have run a single domestic operation now runs four — and collects from forty markets. Each of those markets brings its own currency, its own settlement clearing window, its own regulatory permissions. The CFO who used to reconcile two bank statements now reconciles forty.
The second is the collapse of the assumption that "the bank will handle it." Universal banks, under sustained margin pressure, have systematically narrowed the surface area of relationship banking. Capabilities that used to be standard — multi-currency accounts opened in days, FX routing handled by a relationship manager, cross-border transfers settled at competitive prices — have become specialized services, often spun out to separate providers. The customer that asks for them at a traditional bank is, more often than not, told to use a fintech.
The third is the arrival of a new payments topology. Real-time domestic rails in dozens of jurisdictions, faster correspondent networks, stablecoin-based settlement, and direct-to-clearing access have expanded the menu of options dramatically. The good news is that these tools exist. The bad news is that integrating them — coherently, compliantly, and durably — is a non-trivial engineering and governance problem.
The combination of these forces is straightforward. Treasury has become harder, more specialized, and more consequential — at the same time.
II. Four signals it has reached the board
Most boards still treat treasury as an operational topic. We see four signals that it has, in practice, become a strategic one — and that boards which fail to recognize this are likely to find out the expensive way.
- FX losses are showing up in management discussion as a recurring, not exceptional, item. When the foreign exchange line moves from "headwind this quarter" to "structural drag on margin," the board has a treasury-architecture problem, not a market problem.
- Working capital is being held hostage by settlement delays. If the company carries materially more cash than its operating model requires, simply because money is in transit between jurisdictions, the architecture is taxing the balance sheet.
- Banking relationships are being managed as a procurement exercise. The moment treasury is RFP'ing for the cheapest provider on each line — payments here, FX there, accounts somewhere else — the company has already lost the architectural game. Coherence is worth more than line-item savings.
- Compliance and audit are taking longer each year, not shorter. Architectural fragmentation is the silent driver of compliance burden. A finance function that touches twelve providers will eventually buckle under the weight of reconciling them.
Any one of these signals deserves attention. Two or more, in combination, is a board-level matter.
Infrastructure is not a plumbing decision. It is a strategic one — and like all strategic decisions, its consequences are determined years before they show up in the numbers.
III. Three principles for designing treasury architecture
The companies that have moved fastest on this question are not, in our experience, the largest. They are the most deliberate. From observation across the institutional client base, three principles consistently separate well-architected treasury from the alternative.
Principle one: coherence over coverage
It is tempting, when assembling a financial stack, to chase coverage — the most providers, the widest currency list, the most exotic capabilities. This is almost always the wrong frame. The right frame is coherence: the smallest set of relationships through which the entire treasury function can be operated as one system. A well-designed architecture has fewer moving parts than its operators initially imagine they need.
Principle two: design for the operating model, not the org chart
Treasury architectures often replicate the company's legal entity structure — one bank per subsidiary, one set of accounts per jurisdiction. This is convenient for incorporation lawyers and almost always punitive for finance teams. The architecture should be designed for how the business actually operates: the flow of revenue, the location of suppliers, the rhythm of working capital. The legal structure can wrap around it.
Principle three: treat liquidity as a strategic asset
Most companies manage liquidity reactively — moving money where it is needed, when it is needed. The companies that outperform manage liquidity as a strategic asset: centralized in view, instantly mobile, deployed deliberately. This requires more than a good cash management product. It requires an architecture in which liquidity is visible across the full footprint and can be redirected without friction.
IV. The Swiss view
We come at this question from a particular vantage point. Switzerland's financial culture has, for more than a century, treated infrastructure as a discipline rather than a feature. The Swiss tradition of long-horizon institutional relationships, jurisdictional discipline, and architectural coherence is — we believe — a more useful starting point for treasury design than the prevailing fintech instinct toward feature accumulation.
That tradition is also why we built Swiss Quantum Finance the way we did: as a single, coordinated platform across four pillars — payments, FX, merchant collection, and digital assets — rather than as a constellation of products. The architecture is the product. The discipline is the moat.
For boards beginning to ask treasury-architecture questions, we offer one closing observation: the right time to redesign the architecture is before it begins to constrain the business, not after. The signals enumerated above are not warnings. They are confirmations that the redesign is already overdue.
Treasury is no longer downstream of strategy. The architecture that supports it deserves to be discussed in the same room, by the same people, with the same seriousness — as the strategy itself.