Multi-Bank Cash Management

Multi-bank cash management is the practice of managing a company's cash held at several different banks as a single, coordinated position. It covers getting balance and transaction data from every bank each day, sending payments through each bank from one place, and moving surplus cash between banks to where it is needed. Most mid-sized and large companies need it, because they bank with several institutions for credit, geographic reach or risk reasons.

The discipline is part of corporate treasury. It contrasts with single-bank structures such as zero balance accounts and notional pools, which work smoothly only when all accounts are at one bank. Multi-bank set-ups rely on common message standards, including SWIFT formats and ISO 20022, and on a treasury management system (TMS) or ERP module that brings the data together.

Imagine a family whose money sits in four different banks: one for the mortgage, one near the grandparents, one for the children's savings and one with a better interest rate. Each bank has its own app and password. To know what the family really has, someone has to log in to all four and add up the numbers, then decide where to move money.

A business with accounts at twenty banks in ten countries faces the same problem at a larger scale. Multi-bank cash management is the toolkit that pulls all those balances into one screen, lets the finance team send payments through any bank from one place, and moves money between banks so that none of it sits idle.

The first problem is bank connectivity. Each bank must deliver statements and accept payment instructions in a way the company's systems can process. Common channels are:

• SWIFT for corporates. Companies can join SWIFT directly, under the corporate access model known as SCORE introduced in 2007, or through a service bureau. They receive MT940 or camt.053 statements and send MT101 requests for transfer or ISO 20022 pain.001 payment files to any participating bank.
• Host-to-host links. Direct secure file transfer between the company and each bank, often using bank-specific formats.
• Regional standards. EBICS is widely used for corporate-to-bank file exchange in Germany, France, Switzerland and Austria.
• APIs. Real-time API banking gives instant balances and payment status, but each bank's interface differs, so aggregation layers are often needed.

Standardising on ISO 20022 messages across banks reduces the number of formats to maintain, although banks still apply their own usage rules.

Because one bank cannot automatically sweep another bank's accounts, multi-bank structures use alternatives to a single-bank cash pool:

• Cross-bank sweeping. Treasury, or a bank acting on its instructions, sends daily MT101 or pain.001 transfers from local banks to a concentration account at an overlay bank.
• Overlay structures. Local operating accounts stay with in-country banks for collections and payments, and balances are moved each day to a regional or global header held at one international bank.
• In-house banking. A group treasury company acts as bank to its subsidiaries, settles their payments and keeps internal accounts, then holds only a few external accounts. Intercompany netting reduces the number of cross-border transfers further.

A consolidated daily position supports accurate cash forecasting, lets treasury reduce borrowing while cash sits elsewhere, and makes it easier to spread deposits across institutions to limit counterparty risk. Central control of payment initiation also strengthens fraud defences: approval rules, user rights and sanctions screening can be applied once rather than separately in every bank portal. Standard fee data, such as the camt.086 billing message behind an account analysis statement, allows banks' pricing to be compared directly.

• Cost and complexity. Each connection must be built, tested and maintained, and bank format changes can break it.
• Timing. Cross-bank sweeps depend on payment cut-off times and value dating, so cash may not reach the header on the same day.
• Legal and tax rules. Moving cash between group companies creates intercompany loans, and some countries restrict cross-border sweeps or require central bank reporting.
• Account administration. Tracking who can sign on hundreds of accounts across many banks is a control problem in itself; electronic bank account management (eBAM) standards aim to automate it.
• Security agreements. Lenders may require a bank account control agreement over key accounts, which can limit how freely cash is moved.

Many groups compromise by rationalising to a small number of core banks, using virtual accounts to keep sub-ledgers without opening more real accounts, and keeping local banks only where regulation or collections require them.

• SWIFT
• ISO 20022
• EBICS