A cash sweep is the automated transfer of funds between bank accounts based on rules, typically moving end-of-day excess balances up to a master concentration account or funding shortfalls down to operating accounts. It is the mechanism that operationalises cash pooling and Zero Balance Account structures.
A cash sweep is a rule-based, automated transfer of funds between bank accounts. The trigger is almost always a balance condition at a defined point in the day, most commonly the bank's end-of-day cut-off. When the condition is met, the bank or treasury platform executes a transfer without manual intervention. Sweeps are the operational engine behind cash pooling and Zero Balance Account structures: pooling defines the architecture, sweeps move the money.
There are two directions. A sweep up, often called a concentration sweep, moves balances above a target threshold from subsidiary or operating accounts up to a master account. A sweep down, or funding sweep, transfers cash from the master account down to an operating account that has fallen below its target. In practice most treasury teams run bidirectional sweeps: the target balance in the operating account is held constant, typically at zero, and the master account absorbs all variance.
A concentration sweep is the workhorse of multi-entity treasury. The trigger is straightforward: if end-of-day balance is greater than the target threshold, transfer the surplus to the designated master account. The direction flows from operating, collection, and lockbox accounts into a single concentration account, usually held by the parent entity or an in-house bank.
Frequency varies by volume. High-turnover accounts may sweep intra-day, often two or three times before the cut-off, to put working capital to use sooner. Lower-volume accounts typically sweep daily, and some non-core accounts only weekly. The mechanism is one of three options: ACH for domestic same-currency transfers, SWIFT MT101 request-for-transfer messages where the master bank instructs other banks to move funds, or an internal bank book transfer when all accounts sit at the same banking partner. The third option is fastest and cheapest, which is why treasury teams concentrate banking relationships.
When the target balance is set to zero, the concentration sweep is operating a ZBA structure. The operating account ends every day at zero, with surpluses concentrated and shortfalls funded automatically.
The second major use of the term shows up in leveraged finance and private equity deals. A covenant cash sweep, also called an excess cash flow sweep, is a clause in a credit agreement that requires the borrower to redirect a defined percentage of excess cash flow to debt repayment, typically annually.
The credit agreement defines excess cash flow with precision. The common formula is operating cash flow minus mandatory debt service minus capital expenditure, with adjustments for working capital movements and permitted distributions. The sweep percentage is usually tiered: 50% or 75% of excess cash flow above a defined leverage ratio, stepping down to 25% or zero as leverage falls below thresholds. The trigger is the audited leverage ratio at year-end.
This is not the same operational mechanism as a treasury concentration sweep. There is no daily bank transfer. It is a contractual obligation that drives a single large repayment, calculated and executed once a year against the term loan or senior notes. Treasury teams managing leveraged balance sheets need to forecast covenant sweeps inside their cash position and working capital models to avoid liquidity surprises.
A sweep programme touches banking, tax, legal, and accounting at the same time. Each transaction carries a bank fee, so frequency directly affects cost. Sweeping ten low-balance accounts hourly can erase the interest gain from concentration.
Every sweep between legal entities is an intercompany loan. The transfer creates a payable on the funded entity and a receivable on the concentration entity. This requires loan documentation, an arm's-length interest rate for transfer pricing, and routine settlement to keep intercompany balances from drifting. Cross-border sweeps add withholding tax on intercompany interest in many jurisdictions, and multi-currency sweeps introduce FX exposure that needs to be hedged or accepted as P and L volatility.
Finally, cut-off timing is non-negotiable. Each bank publishes a cut-off for outbound transfers. Miss it by a minute and the sweep moves to the next business day, which can leave an operating account exposed to overdraft fees overnight or block a scheduled payment.
Four problems show up repeatedly when sweep programmes are deployed without strong controls. Missed cut-offs are the most common: a late receivable lands after the sweep has run, leaving the funds idle for a day. Under-funded operating accounts happen when the sweep-down logic does not account for in-flight payments scheduled to settle after cut-off, triggering returned payments and supplier penalties. Fee bleed creeps in when sweep frequency is set without modelling the cost-benefit; a daily fixed fee on twenty small accounts can outpace the interest earned. Tax events arrive quietly: a routine cross-border sweep can be reclassified as a deemed dividend if intercompany loan documentation is missing or stale, triggering withholding tax and corporate income tax exposure.
Most sweep programmes still run on static rules set when the structure was first built. AI-native treasury changes the inputs. Intra-day balance forecasts pulled from AR collection feeds, AP scheduling, and historical settlement timing give a probabilistic view of where each account will end the day, hours before the cut-off. The system recommends sweep timing dynamically: pull the sweep forward when high-confidence inflows have landed, delay it when an expected payment is still in transit.
An agentic treasury workflow validates that no scheduled outflow will be left short before executing a sweep up, and triggers a sweep down automatically when a forecast shortfall crosses the threshold. Intercompany journal entries are generated and posted to the GL the moment the sweep settles, with the correct interest accrual already calculated. Reconciliation between the bank transaction, the intercompany loan, and the GL entry happens in the same workflow, removing the month-end clean-up that traditionally consumes treasury accountant time.
Cash pooling is the structural arrangement that consolidates the liquidity of multiple accounts or entities, either through physical movement of funds or notional offsetting of balances. A cash sweep is the operational mechanism that physically moves the money in a pooling structure. Pooling defines the design; sweeps execute it. Notional pooling, by contrast, achieves a similar interest result without any actual transfer, so no sweep takes place.
Frequency depends on transaction volume, balance volatility, and the cost per sweep. High-volume operating accounts often justify intra-day sweeps because the interest gain or borrowing offset exceeds bank fees. Lower-volume accounts typically sweep once daily at end of day. Some non-core or low-balance accounts only need weekly sweeps. The right test is whether the marginal interest benefit covers the marginal fee plus the operational risk of missing a cut-off.
A covenant cash sweep is a clause in a credit agreement, typically in leveraged finance or private equity transactions, that requires the borrower to apply a defined percentage of excess cash flow to debt repayment. Excess cash flow is defined inside the credit agreement, usually as operating cash flow minus debt service minus capital expenditure with working capital adjustments. The sweep percentage is normally tiered by leverage ratio and is triggered annually based on audited financials.
They can. A cross-border sweep between legal entities is an intercompany loan, and the interest charged on that loan is usually subject to withholding tax in the funding entity's jurisdiction. Sweeps without proper loan documentation or arm's-length interest rates can be recharacterised by tax authorities as deemed dividends, triggering both withholding tax and corporate income tax. Treasury teams running cross-border sweep structures need standing transfer pricing documentation and active intercompany loan agreements for every funded entity pair.
The transfer rolls to the next business day. For a sweep up, this means surplus cash sits idle overnight, foregoing one day of interest or one day of debt offset. For a sweep down, the consequences are more serious: the operating account may be left below its target, triggering overdraft fees or, worse, causing scheduled outbound payments to be returned for insufficient funds. Treasury teams typically build a buffer of fifteen to thirty minutes before the published cut-off into their sweep scheduling.
Yes, in three ways. First, intra-day balance forecasts built from AR and AP feeds let the system recommend dynamic sweep timing rather than running a fixed schedule, capturing more value per sweep. Second, agentic workflows validate that no in-flight payment will be left short before executing a sweep up, eliminating a common cause of returned payments. Third, intercompany journal entries, interest accruals, and bank-to-GL reconciliation are generated automatically the moment the sweep settles, removing the month-end clean-up burden that manual sweep programmes create.
