Intercompany and Multi-Entity Cash Pooling

Executive summary

Intercompany cash pooling is the practice of managing the cash of several related legal entities as one liquidity position, so that a surplus in one entity covers a shortfall in another instead of each entity holding a buffer and borrowing on its own. In a mid-market group with five or ten entities and a dozen bank accounts, the typical symptom is simple: one subsidiary is on an overdraft or drawing the revolver while another holds a balance that earns little or nothing.

The operational benefit is easy to size: you need the daily balance of every account, the cost of borrowing, and the yield on idle cash. The legal and tax side is different. Moving cash between legal entities creates intercompany loans or deposits, with documentation, withholding and transfer pricing consequences that depend on the countries involved and your credit agreements. This guide covers the treasury mechanics and the control framework. It does not give tax, legal or transfer pricing advice, and nothing here replaces your tax advisers, counsel and lenders. Where a design choice has legal or tax consequences, we say so and stop.

Start by building a one-page picture of every account, every entity, and the balance of each at the end of the day for the last 60 days. That picture will tell you whether pooling is worth designing at all.

When to use this

Use this guide when:

• The group has two or more legal entities with separate bank accounts, and at least one entity regularly funds another by ad hoc wire.
• You see simultaneous borrowing and idle cash in different entities on the same day.
• The 13-week cash forecast is built entity by entity and nobody can say what the consolidated position is today.
• A lender or sponsor has asked for a consolidated liquidity report.
• You are integrating an acquisition and need to bring its accounts into the group structure.

Do not start here if you cannot produce daily bank balances for every account, or if it is unclear whether a credit agreement restricts intercompany loans, guarantees, or the location of cash. Resolve those first, with counsel. Pooling can also be restricted in jurisdictions with exchange controls, which is a question for local advisers and your bank.

Diagnostic questions

Answer these before you design anything. Most can be answered from bank portals and the entity chart.

1. How many legal entities and how many bank accounts does the group have, and which entities hold the accounts?
2. In which currencies does each account hold cash?
3. For each of the last 60 days, what was the closing balance of each account? Where is the data, and how long does it take to assemble?
4. On how many of those days was one entity overdrawn or drawing on a facility while another held a surplus above its operating need?
5. What does the group pay on borrowings, and what does it earn on idle balances? What is the spread between the two?
6. Which entities lend to or borrow from each other today, on what documentation, and at what interest rate if any?
7. What do the credit agreements say about intercompany loans, guarantees, liens on accounts, and where cash may be held?
8. Do minority owners, regulatory capital rules or exchange controls limit moving cash out of any entity?
9. Who approves an intercompany transfer today, and is the approval documented?
10. Are intercompany balances reconciled monthly, and do both sides agree to the dollar?
11. Which banks hold the accounts, and what pooling products do they offer in each jurisdiction?

How to read the answers. If question 4 shows little overlap, pooling saves little and you need only a better forecast. If question 6 shows undocumented balances, fix the documentation before adding more flows. If question 7 or 9 is unanswered, stop and get advice. Pooling is a legal structure with a treasury process on top, not a spreadsheet exercise.

The framework: structures, mechanics and constraints

There are three broad structures, and most real designs mix them. Names vary between banks, so describe your design by what physically happens to the cash.

Two further components sit around the structure.

Header or concentration account. The account to which participants sweep. It should be owned by a clearly designated entity, usually the parent or a treasury entity.

Intercompany ledger. Whichever structure you choose, every cash movement between entities is a receivable in one set of books and a payable in another. The intercompany ledger is the record that makes the pool auditable. If it is not kept, the pool will fail its first audit or lender review.

Constraints that decide the design

The constraints come before the savings case, because they can rule a structure out.

• Credit agreements. Check restrictions on intercompany loans, on guarantees (notional pooling often needs cross-guarantees), and on liens over accounts. Your lender may require that certain accounts be subject to control agreements. Counsel reads the document; the finance team should not infer it.
• Tax and transfer pricing. Intercompany loans and deposits generally need to be documented and priced under rules that differ by country, and may have withholding, thin capitalization, or deemed dividend implications. Whether a rate is acceptable, how it is set, and what records support it are questions for your tax advisers.
• Legal entity matters. Directors may owe duties to each entity and to its creditors and minority holders. A sweep out of a subsidiary that is nearly insolvent is not the same as a sweep out of a healthy one. Corporate law, capital maintenance rules and, in some jurisdictions, solvency tests apply. Counsel decides.
• Currency and exchange controls. Cross-currency pools add FX exposure and, in some countries, regulatory limits on cash leaving the entity.
• Bank terms. Each bank has its own product, fees and set-off rights. Read the master agreement and the pooling addendum.

Step-by-step process

The steps below are the treasury workstream. Run the legal and tax workstream in parallel and treat its sign-off as a gate on steps 7 and 8.

1. Map entities and accounts. List every legal entity, bank, account number, currency, signatories, and the purpose of the account. Owner: Treasury or Controller. Output: account register.
2. Collect 60 days of daily balances. Use the bank portals or the bank's reporting file. Owner: Treasury. Output: a table of closing balance by account by day.
3. Quantify the opportunity. For each day, compute total debit balances and total credit balances, the net position, and the cost of gross borrowing versus net. Owner: FP&A. Output: a savings estimate with all assumptions stated.
4. Inventory the intercompany balances. List every existing intercompany loan, advance and trade balance, with the document that supports it. Owner: Controller. Output: intercompany schedule.
5. Read the constraints. Ask counsel and tax advisers to review the credit agreements, the entity structure and the jurisdictions in scope. Owner: CFO. Output: written advice on what is permitted, what documentation is needed, and which entities are in or out.
6. Choose the structure. Pick the simplest design that works for the entities in scope. Owner: CFO with the bank. Output: design memo that states the structure, the header account owner, target balances, and the cut-off times.
7. Document the arrangement. Intercompany agreements, bank pooling agreements, board approvals, and any transfer pricing documentation your advisers require. Owner: General Counsel or outside counsel, with tax advisers. Output: signed documents.
8. Configure and test. Set sweep rules or notional offsets, test with small balances for a week, and reconcile every sweep to the bank statement and to both entities' ledgers. Owner: Treasury. Output: test log signed off by the Controller.
9. Go live entity by entity. Start with the entities that have the clearest legal position. Owner: Treasury. Output: go-live checklist per entity.
10. Run the monthly close. Reconcile intercompany balances, accrue and settle interest as documented, and review exceptions. Owner: Controller. Output: reconciled intercompany schedule and a variance note.
11. Review quarterly. Check the pool against its design purpose and that documentation still matches practice. Owner: CFO. Output: review memo.

Worked example

Illustrative. The numbers below are made up to show the method and are not a benchmark. The group has four operating entities A to D plus a header account in the parent. At the end of one day the balances, in $ millions, are:

Without pooling. Gross overdrafts are $1.2M (0.9 + 0.3). Gross surplus is $2.9M (2.4 + 0.5). The group is paying the overdraft rate on $1.2M and earning the deposit rate, which may be near zero, on $2.9M. The net position is $1.7M positive (2.9 − 1.2).

With a target balance sweep. Suppose each entity keeps a target balance of $0.1M for operations. At day end:

Check: the four entities hold 0.4 (4 × 0.1) and the header holds 1.3, total 1.7, which equals the net position before the sweep. No cash was created or lost.

The cost saving, symbolically. The overdraft interest avoided per day is $1.2M × [overdraft rate] ÷ [day-count basis]. The deposit income lost on the surplus entities is whatever those balances were earning. The net benefit is the difference, plus whatever the group can earn or save on the $1.3M header balance, for example by repaying a revolver draw. Use your bank's actual rates and day-count convention. We do not state a rate here because the right numbers are in your own agreements.

The intercompany records, which are the point. After the sweep the ledgers show new balances:

The header entity owes A and C $2.7M in total and is owed $1.4M by B and D, so its net position as an intermediary is a $1.3M liability to the entities that sent surplus, matched by the $1.3M cash it holds. Whether these balances bear interest, at what rate, and how the rate is documented are decisions for your tax advisers. If each entity's books do not show these balances every day, the pool has no audit trail.

What the example does not tell you. It shows one day. Run the same calculation over all 60 days to find how often surpluses and shortfalls coincide and how large the net is. Whether the saving justifies the legal work is your call once you have that number.

Templates

Account register (copy into a spreadsheet)

Daily position sheet

Intercompany ledger

Pool design decision memo (headings)

Entities in scope and excluded, with reasons; structure chosen and why simpler options were rejected; header account owner, target balances and cut-off times; constraints checked and who signed off; controls and approvers; exit conditions.

Metrics and KPIs

Setting targets without invented benchmarks. Anchor on your own history. Take the 60-day overlap analysis as the baseline, set a goal for reduction in gross borrowing based on the days where surplus and shortfall coincided, and track against that. For interest, compare your actual net cost to the rates in your own bank and credit agreements. Do not borrow a savings percentage from a vendor brochure.

Common mistakes

1. Designing before reading the credit agreement. Restrictions on intercompany loans, guarantees or account liens can invalidate a design. Read first, with counsel.
2. Treating a sweep as an accounting entry only. A sweep moves cash and creates an intercompany balance in two sets of books. If either side is missing, the books diverge.
3. Leaving intercompany balances undocumented and unpriced. An undocumented loan with no stated terms creates tax and audit questions. Your advisers decide how to document and price.
4. Pooling an entity that should not be pooled. Entities with minority owners, regulatory requirements, or solvency concerns need a specific legal decision before inclusion.
5. Ignoring currency. A cross-currency pool shifts FX exposure to someone. Decide who bears it and record that.
6. Setting target balances without a forecast. If a target is too low, an entity is overdrawn by midday and the pool does not help.
7. Letting the header account become a hidden slush fund. The header balance is cash owed to entities. Track it by lender and keep it visible.
8. Skipping the monthly intercompany reconciliation. Breaks that are small today become unexplained differences at year end and during diligence.

AI prompt assistance

Use AI to prepare analysis and drafts. Supply the data yourself, and check every figure against bank statements and ledgers. Do not ask AI for a legal or tax conclusion.

1. Quantify overlap from balance data.

I will paste a table of daily closing balances by account for 60 days, with the entity for each account. For each day, compute the total of negative balances, the total of positive balances, and the net. Count the days on which both a negative and a positive balance existed in different entities. Show the formulas you used.

Check: recompute three days by hand and confirm that account balances tie to the bank statements.

2. Draft the intercompany ledger from a sweep file.

Here is a bank sweep report with the source account, destination account and amount for each sweep on each day. Map the accounts to entities using the register I provide and produce a ledger with lender, borrower, date and amount. Flag any sweep whose accounts are not in the register.

Check: sum each entity's net sweep for the month and confirm it equals the change in that entity's intercompany balance in the GL.

3. Prepare questions for advisers.

I am considering a target balance sweep across these entities and jurisdictions (list below). Draft a list of questions for our tax advisers and corporate counsel covering intercompany loan documentation, interest, withholding, restrictions in our credit agreement, and director duties. Do not answer the questions.

Check: have the CFO and counsel add questions specific to the group before sending.

Implementation guide

Governance: the CFO owns the policy, Treasury owns the process, the Controller owns the books and reconciliation, and counsel and tax advisers own the legal and tax positions. The Treasury policy should state who may approve intercompany transfers, the target balances, and the limits. See the treasury policy guide for where that sits.

Do not promise savings to the board before the constraints are cleared.

Downloadable assets

The account register, daily position sheet, intercompany ledger and decision memo headings above are designed to be copied into a spreadsheet or document. For the group-level forecast that sits on top of the pool, use the 13-week cash flow builder.

Related resources

• Cash management hub: the other guides in this series, from forecasting to liquidity triage.
• Treasury policy for mid-market companies: the policy that sets who approves transfers and what limits apply.
• Forecasting cash receipts from AR: the receipts side of the entity-level forecast.
• Cash flow operating system playbook: the weekly rhythm that a pooled position plugs into.
• Working capital hub: where entity cash connects to the cash cycle.
• 13-week cash flow builder: a consolidated forecast by entity.

Frequently asked questions

What is intercompany cash pooling?

Intercompany cash pooling is a treasury arrangement that manages the cash of several related legal entities as one liquidity position, so surpluses in some entities cover shortfalls in others. It can work by physically sweeping balances to a header account or by notionally offsetting balances at the bank. Each design has different legal, tax and accounting effects that advisers must review.

What is the difference between physical and notional cash pooling?

Physical pooling moves cash between accounts at day end, which creates intercompany loans or deposits. Notional pooling leaves balances in place and has the bank offset them for interest purposes, which can avoid intercompany loans but often requires cross-guarantees. Availability, legal treatment and tax outcomes depend on the jurisdictions and the bank, so confirm with advisers.

Do intercompany balances in a cash pool need interest?

That is a tax and transfer pricing question, and the answer depends on the countries and entities involved. In general, intercompany loans and deposits are documented and priced, and the supporting records matter. Ask your tax advisers how to set, document and review the rate for your group before the pool goes live.

Can credit agreements restrict cash pooling?

Yes. Credit agreements often limit intercompany loans, guarantees, liens and where cash can be held, and notional pooling may need cross-guarantees that the agreement does not permit. Have counsel read the agreement and, if needed, get the lender's consent before designing the pool or changing account structures.

How do you know whether a cash pool is worth setting up?

Measure overlap: count the days when one entity was borrowing or overdrawn while another held surplus above its operating need, and size the gross-versus-net borrowing difference. If overlap is rare or small, a better forecast may be enough. If it is frequent and material, weigh the saving against the legal, tax and operating cost.

How this works in a System of Performance

A pool only works if the daily position, the intercompany balances and the decisions about transfers stay connected. Today those usually live in bank portals, entity ledgers and email. A Performis routine can take on a recurring job like this, with the scope and fit agreed with you: it works from the records your team supplies, prepares the work for your named reviewer, and keeps each approval on record. To see how your own entities' cash lines up, bring it to us as a launch partner.