Cash pooling for international SMEs: A practical guide

A subsidiary has a supplier payment due on Friday. Its account is short of cash, while another entity in your group holds a surplus. You can see enough money across the group to cover the payment. But the invoice belongs to the subsidiary, and its finance team needs to know how the account will be funded before the payment goes out.

Can you move the surplus? How much needs to stay local? Would cash pooling make the next funding gap easier to handle?

A recurring mismatch between surpluses and short-term funding needs can make pooling worth investigating. The practical route depends on which balances you can access, when you need them and the terms governing their use.

If you lead finance for an international SME group, this guide will help you understand the mechanics and prepare a useful feasibility brief. The key distinction is whether a structure moves money between accounts or combines balances for an interest calculation. Those mechanisms leave your entities in different positions.

We'll work through:

• Where cash sits after each type of pool operates
• How currencies, borders and local needs affect participation
• How to assess a pool and organise the visibility, transfers and controls around it

First, return to Friday's payment. Is the subsidiary's shortfall a one-off, or part of a funding pattern across your group?

When does cash pooling make sense for your group?

Cash pooling is worth assessing when your group has recurring, forecastable surpluses in certain entities and short-term funding needs in others, plus the capacity to manage the arrangement.

A cash pool balances group liquidity through physical cash concentration or notional interest aggregation. The economic opportunity is to reduce external borrowing or improve the return on surplus cash under the agreed terms. Any benefit needs to justify the cost and work involved.

Start with five checks:

• Pattern: Do surpluses and deficits overlap repeatedly, or are you solving an isolated payment need?
• Forecast: Does your rolling forecast show when each entity needs cash and when surplus funds could be available?
• Participation: Can you identify the entities, accounts and currencies you want to include?
• Ownership: Is a named finance owner able to coordinate the bank and participating teams?
• Economics: Can you compare the expected benefit with bank charges, implementation work and ongoing controls?

If you can't see current balances or near-term obligations reliably, establish that cash position first. With iBanFirst, you can view balances across your entities' iBanFirst accounts by entity, group or currency. Read that view alongside your forecast to identify where cash sits and which entity has an upcoming need. A missing balance report and a recurring funding mismatch require different responses.

Once the mismatch is visible, you can ask what a pool would actually change.

Physical vs notional cash pooling: What changes?

Physical pooling moves money between accounts. Notional pooling leaves balances in place and combines them for an agreed interest calculation. The ECB's explanation of cash pooling distinguishes the structures on that basis.

The pool leader is the entity coordinating the arrangement. A physical design uses a central account, also called a header account, to collect and distribute funds.

As you compare structures, follow the cash, the entity's access to funding and the obligations attached to participation.

Physical pooling moves cash to a central account

In a physical pool, surplus cash moves from participating accounts into the header account. Funds then move from the header to bring deficit accounts up to their agreed targets.

With zero balancing, the target is zero. A different agreed target can leave operating cash in the participant's account. Sweep frequency and limits form part of the design, so you need to understand when each movement happens and what balance remains afterwards.

Where does the subsidiary's next payment come from?

If its surplus has been swept away, the arrangement needs an agreed way to fund its next cash requirement. Keeping a local account can still serve a purpose even when the group concentrates cash centrally.

Actual transfers may create intercompany positions between the entities. Your team needs records that explain who supplied funds, who received them and which terms apply. The central cash balance tells only part of that story.

Notional pooling offsets balances for interest

In a notional pool, the bank combines participating balances for the interest calculation specified in the agreement. The pooling mechanism makes no corresponding physical transfer between those accounts.

An entity with a surplus keeps its account balance. An entity with a debit balance still needs the agreed credit terms supporting it. A positive group net position doesn't, by itself, give the second entity access to the first entity's cash for payments.

Separate balances can still carry shared obligations:

• Cross-guarantees can expose one participant to another participant's obligations.
• Set-off rights concern the bank's ability under the agreement to offset balances or obligations.

Ask the bank and legal team to establish the scope of both before assessing the arrangement's effect on each entity. Leaving money in separate accounts doesn't settle the question of who bears the risk.

Hybrid pooling combines structures across currencies

A hybrid arrangement can combine physical pools organised by currency with a notional layer across those pools, where the bank supports that design. You might concentrate balances within each currency while the bank applies an agreed interest calculation across them.

But a EUR surplus and a USD supplier payment still create a currency problem.

You need to establish whether conversion is required, when the USD must be available and how settlement timing affects the payment. Combining balances for pooling purposes doesn't itself remove FX exposure or make every currency accessible in every market.

To see the underlying account mechanics clearly, start with an example that keeps the currency the same.

How a €350,000 net position works under each pooling structure

Consider a hypothetical group with three wholly owned EU entities, each holding a EUR account with the same bank. Assume participation is permitted, the bank offers both structures, and a written agreement and the relevant credit terms are in place.

Entity A holds €300,000, B holds €200,000 and C has an authorised €150,000 debit position. The physical pool's header starts at zero.

Here's where the money ends up:

Under physical zero balancing, €500,000 moves from A and B to the header. A €150,000 transfer from the header brings C to zero, leaving €350,000 centrally. The group still needs the corresponding intercompany records.

Under notional pooling, A, B and C retain their starting balances. The bank uses the net €350,000 position for the agreed interest calculation, while C's debit remains subject to its credit terms.

Same group total. Different access to cash.

The €350,000 figure alone doesn't tell you where funds sit or which entity can spend them. To apply the example to your group, you need to replace its assumptions with confirmed participation, funding and operating terms.

Build a cash-pooling feasibility brief for your finance team

Turn those participation, funding and operating questions into a brief your finance team can use with the bank, payment providers and relevant professional teams. You can start before choosing a pooling method.

Give the brief three parts:

• An entity and currency map showing candidate balances and local cash needs
• A list of funding, interest and intercompany terms to confirm
• Named owners for approvals, records, reconciliation and exceptions

The order matters. First establish what cash can participate and what needs to stay local. Then clarify the terms governing its use. Finally, test whether your teams can operate the arrangement and explain the resulting balances.

Map the entities, currencies and local cash needs

Build the participation map around legal entities. A country label or office location won't tell you which entity owns an account or can enter the arrangement.

For each account, capture:

• The account-owning legal entity, country and bank or payment provider
• The currency and current balance
• The forecast funding need and cash to retain locally

Check whether payroll, collections or other local activity gives you a reason to keep an account in place.

Then separate the questions by who can answer them:

• Bank operating the pool: Which entities and currencies can participate, what documentation is needed, and how do cut-offs, settlement and retained local accounts affect the design?
• Local legal and tax teams: What participation, convertibility, cross-border transfer, repatriation or account restrictions need to be resolved?

The IMF's review of exchange arrangements and restrictions illustrates why those country questions belong in the assessment. Your group's answers need to reflect the relevant local rules.

Visible cash isn't necessarily available cash.

Mark each item confirmed, excluded or unresolved, and name an owner for every unresolved check. Count only accessible, participating cash as potential funding for another entity.

Establish the funding, interest and intercompany terms

Identify the pool leader, participants and expected direction of cash flows.

List the terms to confirm with the bank and relevant professional teams:

• Each participant's proposed credit limit, local balance target and access to funding
• How interest and any pooling benefits would be allocated
• The guarantees and set-off provisions

Then look at how long the funding lasts. Does the same entity remain in deficit month after month?

If so, review whether the funding requirement is still short term. The OECD's transfer pricing guidance calls for a facts-and-circumstances assessment of longer-term cash-pool balances. The appropriate treatment depends on that assessment.

For physical movements, prepare traceable intercompany transaction records. Capture transaction type, entity pair, amount, currency, business reason and supporting record so both sides can identify the flow.

Give each part of the terms-and-questions list a clear owner:

• Bank: Confirm the proposed facility and interest mechanics.
• Legal teams: Review obligations.
• Tax teams: Assess tax and transfer-pricing treatment.
• Accounting teams: Confirm recording and classification.

Keep unanswered questions attached to the person responsible for resolving them.

Assign approvals, reconciliation and exception ownership

Give each control a named owner and a record that shows the work was done. Agree who will:

• Approve movements and limits through the group's payment approval workflow, separating creation from approval where the control design requires it
• Retain shared references and supporting records across participating entities
• Match both entities' records to statements by amount, reference, date and currency
• Investigate differences and document resolution and sign-off
• Review recurring balances for changes in the funding pattern

For transfers through iBanFirst, you can configure entity-level access rights, payment limits and multi-level approvals. You can also bring transaction data, statements and proof of payment into your accounting software to support the matching work. Your team sets the approval policy and resolves exceptions.

Consider a transfer recorded by the sending entity that the receiving entity can't match. A shared reference gives the exception owner a starting point for tracing the movement across statements and internal records. They can investigate a timing difference, an FX difference or a missing entry, then record how the mismatch was resolved.

Who owns the difference until it's closed?

Name the exception owner in your payment reconciliation process. A transfer appearing on a statement doesn't finish the accounting work. Your finance team retains responsibility for official books, classification and close, using the accounting system and supporting evidence.

Complete the brief with the responsibility list, required reports and records, and a process for escalating unresolved exceptions. You can now judge both the proposed pool and your team's ability to run it.

When a simpler visibility and transfer setup is enough

Use the brief to identify the funding pattern or operating gap your group needs to address:

• Missing cash information: Build a consolidated view and refresh the forecast before assessing how much liquidity could be shared.
• Occasional known shortfalls: Investigate documented, approved intercompany transfers, checking access and terms for each flow.
• Recurring short-term mismatches: Take the feasibility brief to your bank when participation and operating capacity support a pooling discussion.
• Persistent structural deficits: Open a separate funding, tax and accounting review of the underlying requirement.

You can also adjust who runs payments. A centralised or hybrid payment operating model can combine group policy and visibility with local execution where it's useful. Here, “hybrid” describes the division of work between teams. It's separate from a hybrid physical and notional cash pool.

Group visibility can support either operating model.

If one subsidiary holds surplus cash and another needs funding, you can transfer funds between their iBanFirst accounts from one platform, using the permissions and approvals set for each entity. That gives you a way to carry out an agreed intercompany transfer when the group's access and funding terms allow it.

For a formal pool, confirm pooled-interest treatment, credit and guarantees with the bank operating the arrangement. Your finance and accounting team owns the entity records and close for the transfers you execute.

And whichever liquidity route you take, a future foreign-currency payment can create its own FX risk management need. Funding availability and currency exposure deserve separate attention as you organise the payment.

How iBanFirst helps you manage cash across entities

Locating entity cash, funding cross-border payments and gathering the records can leave your team moving between accounts before the payment work even begins.

That's where iBanFirst can help.

We're a cross-border payment provider for established businesses managing recurring international flows across entities. With iBanFirst, you can:

• View group balances and transfer between entity accounts while retaining separate permissions and approvals.
• Hold and receive supported currencies through a dedicated multi-currency account per entity.
• Use statements, payment records and fee details for reconciliation, giving your finance team the transaction evidence to work from.
• Manage FX risk with forward payment contracts and guidance from our FX specialists.

To bring group visibility, entity payment control and currency risk management into your recurring cross-border work, request an account.