Cash management versus bank liquidity management: two different jobs

Cash management and bank liquidity management are two different jobs, and confusing them is one of the most common mistakes a payments professional can make, because they use similar words, similar systems and similar data, but they serve different customers, follow different rules, and fail in different ways. Cash management is a service a bank provides to a corporate customer, to help the corporate control its own money across its own accounts. Source: Bank for International Settlements, Principles for Financial Market Infrastructures; Bank for International Settlements, payment system glossaries; Basel Committee on Banking Supervision, liquidity coverage ratio. Why the distinction matters is that the two jobs have different owners, different risks and different regulators. In bank liquidity management, the owner is the bank treasurer, the risk is that the bank cannot settle its payments and fails, which can bring down the payment system, and the regulator sets strict rules, including the liquidity coverage ratio, which requires the bank to hold enough high-quality liquid assets to survive 30 days of stress, and the net stable funding ratio, which requires stable funding for a year. A corporate that runs out of cash misses a supplier payment; a bank that runs out of liquidity can fail, and the consequences are not comparable. The parties are different too. In cash management the parties are the corporate, its subsidiaries and the bank as service provider. In bank liquidity management the parties are the bank, its treasury, its central bank, which provides intraday liquidity and overnight facilities, and its regulator, which sets the rules and monitors compliance. The systems overlap: both use balance reporting, camt.052 and camt.053, and both use forecasting, but the data is different, because the corporate forecast is about its own receipts and payments, while the bank forecast is about its settlement obligations, its nostro balances, its collateral and its central bank account, and the two forecasts must never be mixed, because a corporate balance is not a bank balance. How the two differ is shown by a worked example with real numbers. A corporate group has EUR 10 million in cash across its accounts, and its treasurer sweeps EUR 8 million to a header account and invests it overnight at 3 percent, earning about EUR 667 for the night. The bank that holds the header account has EUR 10 million of corporate deposits, which are liabilities, and must hold liquid assets against them, and must also manage its own settlement: on the same day the bank must settle EUR 500 million of payments through T2, and it holds EUR 50 million in its central bank account, borrows EUR 200 million intraday from the central bank against collateral, and queues the rest. The two jobs are on different scales, with different consequences. On success, cash management saves the corporate interest and gives the treasurer control, while liquidity management lets the bank settle every payment on time and meet its regulatory ratios, and the two succeed independently. On failure, a cash management failure costs the corporate interest and a missed payment, which is serious but recoverable, the regulator intervenes, and the bank fails, which is not recoverable. The recovery is also different: a cash management failure is fixed by a reverse sweep or a corrected forecast, while a liquidity failure is fixed by borrowing from the central bank, selling assets, or, in extremis, by resolution, and the BA must never propose a cash management fix for a liquidity problem, or vice versa. The data is similar but the meaning is different. A balance in liquidity management is the bank money at the central bank, and the bank treasurer can use it to settle, but it is constrained by regulation, by collateral, and by the need to hold a buffer. A forecast in cash management predicts the corporate receipts and payments; a forecast in liquidity management predicts the bank settlement obligations, and the two forecasts have different inputs, different owners and different horizons, usually days for the corporate and intraday for the bank. A BA must specify which job each requirement serves, because a requirement that says the system must show the balance, without saying whose balance and for what purpose, is ambiguous. Edge cases show the distinction. A corporate that sweeps its cash to a header account reduces the bank deposits at the subsidiary banks, which changes the banks liquidity, so the two jobs interact, but they are still different jobs, and the bank must manage its own liquidity after the sweep, not assume the corporate will manage it. A bank that offers notional pooling to a corporate must not confuse the notional net with its own liquidity, because the notional net is a calculation for the corporate, while the bank liquidity is the actual money at the central bank, and the two are not the same. A regulatory report on bank liquidity must not include corporate cash management balances as if they were the bank own funds, because they are liabilities, not assets. The effect on the bank is that it must run both jobs well, with separate teams, separate systems and separate controls, and a manager who can see both, but who never confuses them. The effect on the customer is a cash management service that saves interest, and a bank that settles reliably, which is the foundation of trust. The effect on operations is two queues, two forecasts and two sets of controls, and a discipline that every requirement, every report and every balance is labelled with whose money it is and what job it serves. What a BA, PO or SME must understand is that cash management is a product for the corporate, liquidity management is survival for the bank, and the two must be specified, built and tested separately. The requirement must name the customer, the owner, the risk, the regulator and the data for each job, and must never use the same balance for both. The test is to take one balance, state whose money it is, what job it serves, and what happens if it is wrong, and if the answer is the same for both jobs, the distinction has not been understood. Further reading: Bank for International Settlements, Principles for Financial Market Infrastructures; Basel Committee, liquidity coverage ratio; ISO 20022 camt.052 and camt.053. Last reviewed 7 November 2026.