A company with one legal entity, one primary bank, and one operating currency has a treasury function that most spreadsheet tools can handle adequately. Once you add a second entity — a subsidiary, an acquisition, a foreign operating company — the complexity doesn't double. It multiplies in ways that aren't obvious until you're running the weekly cash position meeting and someone asks which entity is funding the Canadian subsidiary's payroll next Thursday.
Mid-market companies — the industrials, distributors, services companies, and specialty manufacturers headquartered in the Midwest and across the country with revenues between $75M and $600M — almost universally end up here. They grew through organic expansion or acquisition, built banking relationships piecemeal, and structured legal entities for tax and regulatory reasons that had nothing to do with treasury convenience. By the time treasury complexity demands a systematic approach, the organization has 8 entities, 14 bank accounts, three currencies, and a CFO asking for a consolidated cash position every Monday morning.
Understanding Your Entity Structure Before Optimizing It
Before changing anything about how cash moves between entities, treasury needs a clear map of the legal and financial structure. This sounds obvious, but many mid-market treasury teams operate with incomplete pictures of their own entity landscape — particularly for recently acquired subsidiaries or dormant holding companies that still carry balances.
The map you need for treasury purposes differs from the legal org chart. You need to know: which entities are wholly owned (enabling intercompany lending without third-party approvals), which are joint ventures or partially owned (where cash movement triggers fiduciary obligations), which operate in jurisdictions with currency controls or repatriation restrictions, and which are guarantors or co-borrowers on debt facilities (triggering covenant implications when their cash positions change).
A practical approach is to build a one-page entity register with five columns: entity name, jurisdiction, ownership percentage, primary banking relationship, and currency. That register is the foundation for every interco funding decision and for the rules that govern automated cash sweeps.
The Three Structural Mechanics of Multi-Entity Cash
1. Intercompany Loans
The most common mechanism for moving cash between entities is an intercompany loan from the parent to a subsidiary, or from one subsidiary to another. These require proper documentation — a promissory note at arm's-length interest rates (transfer pricing compliance), board resolutions where required by jurisdiction, and booking entries in both entities' general ledgers.
The documentation requirement is where mid-market companies most often cut corners under time pressure. When the Wisconsin subsidiary needs $800K to cover payroll by Friday and the Texas operating company has $1.4M sitting in a money market account, the instinct is to transfer and document later. "Later" often means never, creating undocumented intercompany positions that generate audit findings and complicate any future sale or restructuring of those entities.
2. Cash Pooling Structures
For companies with multiple wholly-owned domestic entities, zero-balance account (ZBA) pooling with a single bank is the most operationally clean structure. Under ZBA pooling, each entity maintains its own bank account for transactional activity, and a daily automated sweep concentrates all entity balances into a master account — typically held by the parent. Overdrafts in subsidiary accounts are automatically funded from the master account, eliminating the need for manual interco wires.
Notional pooling, more common in international structures, allows entities to maintain their own balances while the bank calculates interest on the net position. No actual cash movement occurs — the benefit is interest rate optimization across the pool rather than physical concentration. Notional pooling is standard practice in European operations but requires banks with the right structure and creates accounting complexity around whose interest benefit is whose.
Multi-currency pooling adds another layer: the FX conversion timing and rates within the pool have to be governed carefully to avoid inadvertent currency risk transfer between entities.
3. Manual Interco Sweeps
For companies without formal pooling structures — and for situations where pool mechanics don't apply (different banks, different jurisdictions, partial ownership) — manual interco sweeps remain the day-to-day tool. A manual sweep is a wire transfer between two entity accounts, booked as an interco loan or equity contribution, executed by treasury on a scheduled or as-needed basis.
The operational challenge with manual sweeps is timing. Wire cutoff times for same-day ACH are typically 3:00-4:00 PM Eastern. International wires need to be initiated earlier. If treasury is making the sweep decision at 2:30 PM because that's when the afternoon position report is complete, the window is narrow and errors are costly.
Why Entity-Level Visibility Is Non-Negotiable
The core operational problem in multi-entity treasury is not that cash moves between entities — it's that treasury doesn't know precisely where cash is within the entity network at any given moment. When a consolidated cash report shows $12M "available," that number might reflect $9M in the parent operating account, $1.5M in a subsidiary that's restricted for a specific purpose, $900K committed to a letter of credit, and $600K in a Canadian account that can't be repatriated without triggering withholding tax. The $12M headline is not $12M of freely available liquidity.
Entity-level visibility — meaning balance, currency, restriction status, and covenant implications displayed per entity, not just consolidated — changes how treasury makes funding decisions. Consider a growing specialty manufacturer with 11 entities across the US and Canada. Their treasury team spent roughly 90 minutes every Monday morning pulling balance information from eight separate bank portals, normalizing the data into a master spreadsheet, and computing which entities needed funding. By the time the consolidated view was ready, the intraday balances had already moved. Entity-level visibility with automated bank data feeds compresses that 90-minute ritual to a dashboard refresh.
Common Mistakes in Multi-Entity Treasury Operations
We're not saying single-entity treasury tools are inadequate for every company. For a business with one operating entity and clean bank relationships, a simpler approach works fine. The inflection point where multi-entity purpose-built tools pay for themselves is typically around four to six entities with at least two banking relationships — the complexity threshold where manual aggregation creates material decision-making error.
Beyond the data collection problem, mid-market treasury teams consistently make three structural mistakes: failing to standardize interco loan documentation until an audit forces it; running ZBA sweeps without a clear policy on whether subsidiaries can run negative (and under what conditions the parent will fund); and optimizing entity-level cash balances independently rather than as a managed pool, resulting in one entity holding expensive idle cash while another entity draws on a revolving credit facility.
Building Toward a Scalable Structure
The path from ad-hoc multi-entity cash management to a scalable treasury structure doesn't require a full TMS implementation. The practical steps, roughly in order of impact: establish entity-level bank connectivity so positions are visible without manual portal logins; standardize interco loan documentation templates so the first action in any sweep is already half-complete; define a sweep policy (what triggers a sweep, what amounts are swept, what approval is required) so decisions are rule-based rather than judgment calls; and model the 13-week cash forecast per entity so funding needs are visible three months ahead, not three days ahead.
That last step is where most mid-market treasury teams leave significant value on the table. A CFO looking at a 13-week entity-level forecast sees a completely different picture from one looking at a consolidated 30-day forecast. They can see that the Chicago entity will be flush while the Canadian subsidiary runs lean in weeks 8 through 10 — and they can pre-arrange the interco loan terms and FX hedge before the shortfall arrives. The interco sweep stops being a scramble and starts being a planned treasury action.