Treasury used to mean cash management and paying invoices. At internationally active companies it now shapes outcomes at the level of the enterprise, across several currencies and several jurisdictions at once, and it has become a real difference between companies that otherwise look alike.
What changed
Three things moved at roughly the same time.
- Revenue dispersion. Companies now operate across forty-plus countries, each with its own currency, settlement window and regulatory requirements.
- Banking relationship contraction. Universal banks have narrowed their relationship-banking footprint, cutting services and pushing clients toward specialist fintech providers.
- New payments topology. Real-time domestic rails, faster correspondent networks, stablecoins and direct-to-clearing access all arrived together, and something has to hold them in one coherent, governed shape.
Treasury got harder, more specialised and more consequential in the same few years.
Four signs it has reached the board
- FX losses show up as recurring margin drag rather than as exceptional items.
- Working capital sits trapped in settlement delays, inflating cash requirements beyond what the business actually needs.
- Treasury gets bought service by service from different providers, and the architecture stops holding together.
- Compliance timelines lengthen every year as providers multiply and the reconciliation burden grows.
The consequences of an infrastructure choice are set years before they show up in the numbers, which is why it almost never feels urgent at the point where it is cheapest to fix.
How to think about the design
Coherence over coverage
Keep the number of provider relationships and moving parts down instead of chasing maximum capability and currency coverage. Breadth is easy to buy and expensive to operate.
Design for the operating model, not the org chart
Structure the architecture around how the business actually works: where revenue lands, where suppliers sit, how working capital moves through the year. Legal entity structure is rarely the right organising principle.
Treat liquidity as a strategic asset
Centralise visibility of liquidity, and make it movable across the whole operational footprint without friction.
Where we sit on this
Swiss financial tradition favours infrastructure discipline over feature accumulation, and that is the bias behind how Swiss Quantum Finance is built: payments, FX, merchant collection and digital assets as one coordinated platform rather than four products that happen to share a logo.
The work is cheaper before the constraints bind than after. If more than one of those four signs looks familiar, the case for opening it up has already made itself.
SQF Editorial · Treasury & Infrastructure