Cross-border cash pooling sounds simple: gather the group's money in one place, let a surplus in one currency cover a shortfall in another, and stop paying for idle balances scattered across a dozen accounts. In practice, most groups end up with a patchwork of local accounts, separate banking relationships and treasury spreadsheets that never quite agree. The obstacle is rarely ambition. It is structure.

Why pooling breaks across borders

Conventional pooling depends on a legal right of set-off — the ability to treat a balance held by one entity as available to another. That right is defined by local law and does not travel across borders automatically. Add to that a bank, a cut-off time and a reporting format for every corridor, and the operating cost of coordination rises faster than the benefit of consolidation. Prefunding each corridor compounds the problem: balances sit in every currency and country, working for the bank rather than for the group.

Netting instead of one more sweep

The alternative is to cancel offsetting flows before they leave the network. In a single order book, approved operations are matched, opposite flows cancel internally, and only the remainder is routed to an external path. A bank sending €10m while other participants receive €8.5m leaves just €1.5m to move on outside rails. Fewer external transactions, and liquidity that stays inside the network rather than flowing out and back.

What good looks like

A workable structure gives treasury one consolidated view while keeping each business unit legally isolated — in SUPA's case a segregated portfolio, where one unit's assets answer only to its own liabilities with no cross-recourse. Operations are validated once, recorded in a double-entry ledger attributable to principal, agent and policy version, and reported per unit. Balances remain with licensed partners; SUPA is not a bank and does not hold client money in its own name.

In short

  • Cross-border pooling usually fails on legal set-off, not on software.
  • Netting cancels opposite flows before they reach external rails.
  • Consolidation and legal isolation can coexist.
  • Balances sit with licensed partners until a banking licence exists.

See how netting and routing fit together in the protocol → /protocol/