Cash management services: what a bank offers a corporate treasurer

Cash management services are the set of products a bank offers a corporate customer to control its money across many accounts, many entities and many countries, and the core idea is that a treasurer should see all the money, move it where it is needed, and earn or save interest on it, without logging into twenty different banking systems. The services include account information, payment initiation, sweeping, pooling, zero balancing, notional pooling, forecasting and reporting, and they are sold as a package, not as separate products, because a treasurer who can see the money but cannot move it has only half a service. Source: ISO 20022 camt.052, camt.053 and camt.054 for account reporting; Wolfsberg Correspondent Banking Principles. Why cash management exists is that a large corporate has money scattered across subsidiaries, countries and currencies, and without a service to bring it together, the corporate borrows in one place while it holds cash in another, and pays interest on the borrowing while earning nothing on the cash. A group with EUR 50 million in cash across ten subsidiaries, and EUR 20 million borrowed at 6 percent, is paying EUR 1.2 million a year in interest while its own cash earns nothing, and the treasurer who can see all ten balances can use the cash to repay the borrowing and save the interest. Cash management is therefore a service that saves the customer money, and the bank earns fees for providing it, which is why it is a commercial product, not just an operational convenience. The parties are the corporate customer, usually a group treasurer, the bank, which provides the service, the subsidiaries, which hold the accounts, and the bank systems, which report the balances and move the money. The treasurer is the decision maker, the subsidiaries are the account holders, and the bank is the operator, and the service agreement must name who can move money, who can see balances, and who approves a sweep, and a treasurer who can move a subsidiary cash without approval is a governance risk. The distinction between cash management for a corporate and liquidity management for a bank is important: the corporate manages its own cash, the bank manages its own liquidity, and the two must not be confused, because the rules, the systems and the risks are different. How the services fit together is shown by a worked example. A group has five subsidiaries, in France, Germany, Spain, Italy and the Netherlands, each with a euro account, and the balances on a Monday morning are EUR 2 million, EUR 800,000, EUR 300,000, EUR 50,000 and a deficit of EUR 400,000, a total of EUR 2. The treasurer sees all five balances on one screen, through camt.052 intraday reporting, sweeps the surplus from France, Germany and Spain into a header account, covers the Netherlands deficit, and ends the day with EUR 2. The reporting, the sweeping and the investment are three services, and the value is in using them together. On success the treasurer sees all the money, moves it where it is needed, earns interest on the surplus and pays no interest on a deficit that could have been covered, and the bank earns fees and holds the balances. On failure the service can mislead: a balance that is reported but not yet available, because the value date is tomorrow, will be swept as if it were available, and the header account will go overdrawn, and the subsidiary will blame the treasurer. The recovery is a sweep rule that respects value dates and payroll dates, and a reporting feed that distinguishes the ledger balance from the available balance, because the two are different, and a treasurer who sweeps on the ledger balance will be wrong. The data in cash management is the account balances, intraday and end of day, the value dates, the sweep rules, the pool structures, and the forecasts. The balance reporting, camt.052 for intraday and camt.053 for end of day, is the foundation, because a sweep that is based on stale balances is a sweep that moves the wrong amount, and a forecast that is based on stale balances is a forecast that is wrong. A BA must specify the reporting frequency, the value-date handling, the sweep rules, the approval workflow, and the distinction between the ledger balance and the available balance, because each of those is a customer promise and a source of errors. Edge cases show the depth. A subsidiary in a country with exchange controls cannot have its cash swept out of the country, and the service must respect that, or the bank will breach the control. A subsidiary that is a separate legal entity cannot have its cash pooled with another entity without a legal agreement, because pooling without agreement is a loan between entities, with tax and legal consequences. A sweep that moves money across currencies needs an FX conversion, and the rate must be agreed upfront, because a rate that is worse than the customer expected is a fee by another name. The effect on the bank is a fee-earning service that deepens the corporate relationship, because a treasurer who uses the bank cash management is unlikely to move to another bank. The effect on the customer is interest saved, fees reduced, and a single view of the money, which lets the treasurer make decisions in minutes instead of days. The effect on operations is a service that must run every day, with balances reported on time, sweeps executed on time, and exceptions, such as a failed sweep, worked the same day, because a sweep that fails on Monday and is not noticed until Wednesday has cost the customer three days of interest. What a BA, PO or SME must understand is that cash management is a package, and the value is in the package, not in any single service. The requirement must name the reporting, the sweeping, the pooling, the forecasting, the approvals and the value-date handling, and must distinguish corporate cash management from bank liquidity management. The test is to take one group with five subsidiaries, show the balances, sweep them, and state the interest saved, because if the interest saved cannot be stated, the service has no business case. Further reading: ISO 20022 camt.052, camt.053 and camt.054; Bank for International Settlements, payment system glossaries. Last reviewed 7 November 2026.