Northwind Components: Cash Positioning with Stale Bank Data
Northwind Components operates 14 operating accounts at six local banks in five countries. Daily bank statements arrive by 09:00 local for four accounts, but two subsidiaries' statements arrive T+2 and include only prior-day closing balances. The group has $38 million of gross cash, a $10 million minimum operating balance per country, and a $15 million revolver with a 5.1% rate. The treasurer forecasts 13-week cash but updates it weekly using spreadsheet extracts. Last quarter, a $4.2 million unnecessary revolver draw occurred because a European subsidiary's $5.8 million balance was not visible until two days after a supplier payment run. The CFO wants to reduce gross debt and idle cash without violating local liquidity rules.
1. Diagnose the cash positioning failure and specify the minimum data and process changes needed to prevent a repeat.
Read the worked answer
The failure is not a forecasting failure alone; it is a visibility and availability gap. Treasury sees $38 million gross, but $5.8 million was unavailable for positioning because it sat in a T+2 reporting account and the payment run was released before the balance was confirmed. The 09:00 local statements cover only four accounts, so the daily position is built on stale data for two subsidiaries.
Minimum fixes: (1) obtain same-day intraday or prior-day end-of-day balances via bank API or MT940 for all 14 accounts; (2) map each account to availability rules-minimum balance, blocked cash, local regulatory reserve-not just ledger balance; (3) run a daily cash position at a consistent cutoff with a two-day look-ahead for known payment runs; (4) reconcile the 13-week forecast to actual bank balances weekly. The $4.2 million draw was avoidable if the $5.8 million European balance had been treated as available or if the payment run had been sequenced after confirmation. A target-balance or sweep structure should follow only after visibility is fixed.
2. Should Northwind move to a payment-on-behalf-of (POBO) or in-house bank structure, or retain local accounts? Recommend and state conditions.
Read the worked answer
Retain local accounts in the near term; POBO is not the first fix. With five countries, local liquidity rules, and a $10 million minimum operating balance per country, an in-house bank can centralize visibility and funding decisions without eliminating local accounts. POBO would reduce account count and payment fragmentation, but it requires local tax and VAT review, supplier acceptance, FX conversion rules, and regulatory clearances.
A hybrid is more defensible: retain local collection and operating accounts where required, overlay a notional or physical pooling structure where permitted, and centralize payment initiation through a hub while local entities remain payer of record. Conditions for POBO later: more than 80% of payments standardized, legal and tax sign-off, robust entity-level accounting, and reliable bank connectivity. The goal is availability visibility and reduced idle cash, not account elimination for its own sake.
3. What KPIs should the CFO use to judge whether cash positioning has improved?
Read the worked answer
Use a small set that links to the stated goals: (1) cash visibility coverage-percentage of gross cash with same-day available balance, target above 95%; (2) forecast accuracy-13-week actual versus forecast variance by entity, with a 5% threshold; (3) idle cash ratio-cash above local minimum balances divided by gross cash; (4) revolver utilization and days drawn, with a target of zero unnecessary draws; (5) cost of avoidable draws, calculated as drawn amount times rate times days; (6) payment timing exceptions-payment runs released without confirmed available balance.
Track these weekly, not monthly, because positioning is a daily process. The $4.2 million draw is a useful baseline: at 5.1%, each 10 days of unnecessary draw costs about $5,900, so even small timing errors compound. The CFO should require root-cause codes for each exception.