Zero balancing: sweeping every account to zero each day

Zero balancing is the cash management service where every subsidiary account is swept to zero at the end of each day, so that all the cash ends the day in one header account, and each subsidiary starts the next day with a zero balance, funded only as it needs money. It is the most aggressive form of sweeping, and it gives the treasurer complete control: at 17:00 every day the group cash is in one place, and at 09:00 the next day the treasurer decides how much each subsidiary gets, based on what it needs to pay that day. Source: Bank for International Settlements, payment system glossaries; ISO 20022 camt.052 and camt.053 for balance reporting. Why zero balancing exists is that a treasurer who wants to invest the group cash overnight, or to repay borrowing, needs all the cash in one place, and a target-balance sweep leaves money in the subsidiaries, which is money that cannot be invested. A group with ten subsidiaries, each holding EUR 100,000 overnight, has EUR 1 million that cannot be invested, while a zero balancing arrangement sweeps all EUR 1 million to the header, invests it at 3 percent, and earns about EUR 83 for the night, which is EUR 30,000 a year, a measurable saving. Zero balancing is therefore the choice for a group that wants maximum concentration, and it is the most demanding on the bank, because the funding the next morning must be right, or the subsidiaries cannot pay. The parties are the treasurer, who decides the funding each morning, the subsidiaries, whose accounts are zeroed each night, the bank, which executes the sweep and the funding, and the header account holder, usually the parent, which holds the cash overnight. The funding is the critical service: each morning the bank must move money from the header to each subsidiary, based on the treasurer instruction or on a standing rule, so the subsidiary can pay its suppliers, its staff and its taxes. If the funding is late, or wrong, the subsidiary cannot pay, and the failure is visible immediately, because a supplier is not paid, so the funding service level must be defined in hours, not days. How zero balancing works is shown by a worked example with real numbers. The zero balancing sweep moves all EUR 1,180,000 to the header account, leaving each subsidiary at zero. The treasurer invests EUR 1,000,000 overnight at 3 percent, earning about EUR 83, and keeps EUR 180,000 in the header as a buffer. On Tuesday at 08:00 the treasurer funds the subsidiaries with EUR 400,000, EUR 200,000, EUR 100,000 and EUR 50,000, based on the payments each must make that day, a total of EUR 750,000, and the subsidiaries pay their suppliers, their staff and their taxes from the funding, ending Tuesday at 17:00 with new balances that are swept to zero again. On success all the cash is concentrated, invested, and funded back exactly as needed, and the interest earned is measurable. On failure the funding is wrong: a subsidiary that needs EUR 400,000 receives EUR 200,000, and its supplier payment of EUR 300,000 fails, and the supplier charges a late fee, and the subsidiary blames the treasurer, and the treasurer blames the bank. The recovery is an emergency funding, moving cash immediately, but the late fee has already been incurred, so the funding rule must account for known payments, not just a standing amount, and the treasurer must be able to change the funding on the day, not just the day before, because a payment due at 09:00 cannot wait for a funding decision at 10:00. The data in zero balancing is the end-of-day balances, the sweep amounts, the funding amounts, the funding time, and the value dates. The funding time is the field that matters most, because a funding that arrives at 10:00 is useless for a payment due at 09:00, and the service level must state the funding time, usually 08:00, and the bank must meet it. A BA must specify the sweep time, the funding time, the funding rule, the emergency funding process, the value-date handling, and the reporting, because each of those is a customer promise and a source of failure. Edge cases show the depth. A subsidiary in a different time zone may end its day at a different time, so the sweep must account for the time zone, or the sweep will run before the subsidiary has finished its payments. A subsidiary that receives a payment after the sweep, for example a customer payment at 18:00, will have a balance that is not swept until the next day, so the header account will not have all the cash, and the treasurer must know that. A zero balancing arrangement across currencies needs an FX conversion for the sweep and for the funding, and the rate must be agreed, because a rate that is worse than expected loses more than the interest saved. The effect on the bank is a service that moves money twice a day, every day, earns fees, and deepens the corporate relationship. The effect on the customer is maximum concentration, maximum interest earned, and complete control, which is the value, and maximum dependence on the funding, which is the risk. The effect on operations is a daily sweep and funding run that must execute on time, with a failure queue for sweeps and fundings that did not run, and a manager who can see which subsidiaries were not funded on time and why. What a BA, PO or SME must understand is that zero balancing is sweeping to zero, and the funding the next morning is the service, not the sweep. The requirement must name the sweep time, the funding time, the funding rule, the emergency funding, the value-date handling and the reporting. The test is to take four subsidiaries with known balances, sweep them to zero, fund them the next morning, and state the interest earned and whether every payment was made on time, because if a payment was late, the service has failed, however much interest was earned. Further reading: Bank for International Settlements, payment system glossaries; ISO 20022 camt.052 and camt.053. Last reviewed 7 November 2026.