Cash Positioning

Cash positioning is the daily treasury task of working out how much cash a company has in each bank account today, what will come in and go out before the end of the day, and therefore whether each account will end the day short, on target or holding surplus funds. The result, the cash position, tells the treasurer whether to borrow, move money between accounts or invest the excess before banks' cut-off times.

Cash positioning is the shortest horizon of cash management. It differs from cash forecasting, which looks days, weeks or months ahead, and from cash reconciliation, which checks after the event that the books agree with the bank. It is one of the core routines of corporate treasury, and in a bank or payment company the same idea is applied to settlement and nostro accounts.

Picture checking your wallet and bank app first thing in the morning, then thinking through the day: your salary lands at noon, rent leaves this afternoon, and you promised to pay a friend back. If the sum says you will dip below zero, you move money from savings before lunch; if it says you will have plenty left, you might move some into savings instead.

A company does the same thing, but across many accounts, banks and currencies, and with payment deadlines set by each bank and payment system. The aim is simple: no account overdrawn by accident, no large balance sitting idle, and every decision made early enough in the day for the money to move.

The starting point is balance information from the banks. Treasury collects prior-day statements showing the closing ledger and available balances, and intraday reports showing what has already been received or paid today. This balance reporting arrives in standard formats: SWIFT MT940 statements and MT942 interim reports, BAI2 files in the United States, or ISO 20022 camt.053 statements and camt.052 intraday reports. Swift removed many legacy MT payment instructions from its cross-border service in November 2025, while statement messages such as MT940 remained in use with a later migration planned.

Treasury then adds the flows it knows about for the day: incoming customer receipts, outgoing supplier payments, payroll, tax, loan interest, maturing investments and foreign exchange settlements. A simple statement of the calculation is:

Here the opening available balance is the money the bank says can be used now, expected receipts are inflows due today, and expected disbursements are outflows due today. For example, an account opens with $2,000,000 available, expects $500,000 of customer receipts and has $1,800,000 of payments due, including payroll. The projected close is $2{,}000{,}000 + 500{,}000 - 1{,}800{,}000 = 700{,}000$. If the company's policy is to keep at least $1,000,000 in that account, treasury needs to bring in $300,000, perhaps by redeeming part of a money market fund or drawing on a credit line.

Once the position is known, treasury takes one or more of these steps before the relevant cut-off time:

• Fund shortfalls. Move cash from accounts with a surplus, draw on a revolving facility or, as a last resort, rely on an agreed overdraft.
• Invest surpluses. Place spare cash in overnight deposits, short-term investments or a fund within the limits of the investment policy.
• Concentrate balances. Use a cash pool or sweep accounts so that balances in many subsidiary accounts are gathered into a header account automatically.
• Settle currency needs. Buy or sell currencies so that each account in a foreign currency is funded, keeping an eye on foreign exchange risk.

Timing matters because each rail has its own windows. A high-value transfer through Fedwire or a European RTGS system can settle the same day, an ACH batch follows set settlement windows, and instant payment systems run around the clock. Banks may also grant intraday credit, which affects how tightly treasury needs to manage balances during the day.

Small companies often build the position on a spreadsheet each morning from bank portals. Larger ones use a treasury management system that pulls statements automatically through bank connectivity channels or a bank API, and takes expected flows from the ERP system's payables and receivables modules. Virtual accounts can reduce the number of physical accounts that need positioning.

The position is only as good as its inputs. Common problems are late or missing statements, payments released by business units without telling treasury, receipts that cannot yet be identified, and differences between the ledger balance and the available balance. Treasury therefore compares the morning projection with the actual closing balance the next day; persistent gaps point to a process issue, and the comparison feeds the wider liquidity management framework.

• Swift: ISO 20022
• Association for Financial Professionals (AFP)