Pooling: offsetting balances without moving money

Pooling is the cash management service that lets a group offset the balances of several accounts against each other, for interest calculation, without physically moving the money between them. In a pool, a subsidiary with EUR 2 million in credit and a subsidiary with EUR 1 million in debit are treated as a net credit of EUR 1 million for interest purposes, so the group pays interest only on the net debit, or earns interest on the net credit, even though no money has moved. Pooling is therefore a calculation, not a movement, and it is the alternative to sweeping, which moves the money physically, and the choice between them is a legal, tax and operational decision, not just a preference. Balances are reported intraday by camt.052 and end of day by camt.053. Why pooling exists is that moving money between legal entities has consequences: it can be a loan, with tax and transfer pricing implications, it can breach exchange controls, and it can require regulatory approval, while offsetting balances for interest purposes does not move the money, so it avoids those consequences. A group with a subsidiary in France holding EUR 2 million and a subsidiary in Germany overdrawn by EUR 1 million can pool them, pay interest only on the net, and avoid a loan from France to Germany, which would have needed a loan agreement, an interest rate and a tax treatment. Pooling answers by letting the bank calculate interest on the net position, while each subsidiary keeps its own money in its own account, which is simpler legally and operationally. The parties are the treasurer, who sets up the pool, the subsidiaries, whose balances are pooled, the bank, which calculates the interest on the net position, and the tax and legal advisers, who must confirm the pooling is lawful in each country. The pool agreement is the key document: it names the accounts, the pooling method, the interest calculation, and the allocation of the interest benefit between the subsidiaries, because a subsidiary that contributes a credit balance must be compensated for it, and a subsidiary that uses the pool to cover a debit must pay for it, and the allocation must be fair and documented, or the tax authorities will challenge it. How pooling works is shown by a worked example with real numbers. A group has three accounts in a pool: France with EUR 2,000,000 in credit, Germany with EUR 1,000,000 in debit, and Spain with EUR 500,000 in credit, a net credit of EUR 1,500,000. Without pooling, the bank would charge interest on the EUR 1,000,000 debit at 6 percent, EUR 60,000 a year, and pay interest on the EUR 2,500,000 in credit at 2 percent, EUR 50,000 a year, a net cost to the group of EUR 10,000 a year. With pooling, the bank calculates interest on the net credit of EUR 1,500,000 at 2 percent, EUR 30,000 a year earned, so the group is EUR 40,000 a year better off, without any money having moved. The EUR 40,000 is the value of pooling, and it is measurable, which is why the treasurer can justify the fees. On success the group pays less interest, or earns more, without moving money, and each subsidiary keeps its own balance, which is operationally simple. On failure the pooling can be challenged by a tax authority, because the interest benefit must be allocated fairly between the subsidiaries, and an allocation that gives all the benefit to the parent, while the subsidiaries bear the cost, will be challenged as a hidden profit transfer. The recovery is a documented allocation, agreed in advance, with transfer pricing advice, and a pool agreement that is reviewed annually, because tax rules change, and a pool that was lawful last year may not be lawful this year. The data in pooling is the account balances, the net position, the interest rates for credit and debit, and the allocation of the interest benefit. The net position is the field that matters most, because the interest is calculated on the net, and a net position that is calculated on stale balances is wrong, so the balances must be reported on time, intraday by camt.052 or end of day by camt.053. A BA must specify the pool structure, the interest calculation, the allocation method, the reporting, and the legal review, because each of those is a customer promise and a source of errors. Edge cases show the depth. A pool across currencies needs an FX conversion to calculate the net, and the rate must be agreed, because a net calculated at a poor rate is wrong, and the interest will be wrong too. A pool that includes a subsidiary in a country that does not allow pooling must exclude that subsidiary, and the service must enforce the exclusion, not rely on the treasurer remembering it. A pool where one subsidiary is in deficit for a long time is effectively borrowing from the others, and the tax authority may treat it as a loan, so the pool agreement must set a limit on how long a deficit can persist. The effect on the bank is a service that earns fees and deepens the corporate relationship, because a treasurer who pools with one bank is unlikely to move. The effect on the customer is interest saved, which is measurable, and no money moved, which is legally simple. The effect on operations is a daily interest calculation on the net position, with a reporting feed that shows each subsidiary its balance and its share of the interest, and a manager who can see which pools are working and which are not. What a BA, PO or SME must understand is that pooling is a calculation, not a movement, and the value is the interest on the net position, not the money moved. The requirement must name the pool structure, the interest calculation, the allocation, the reporting and the legal review. The test is to take three accounts with known balances, calculate the net, calculate the interest with and without pooling, and state the saving, because if the saving cannot be stated, the service has no business case. Further reading: Bank for International Settlements, payment system glossaries; ISO 20022 camt.052 and camt.053. Last reviewed 7 November 2026.