Jonathan Prince (Finologee): orchestrating cash across banks
Jonathan Prince, co-founder and Chief Sales Officer of Finologee, explains how its Banking Orchestrator gives multi-banked groups a single, real-time view of their liquidity. Interview.
How does the Banking Orchestrator give multi-banked groups visibility over their cash?
In most multi-banked structures, the morning position still gets assembled by hand: logging into three or more bank portals, downloading statements, pasting figures into a spreadsheet. By the time the picture is consolidated, any same-day value transfer decision has lost its window. Our Banking Orchestrator provides straight-through bank connectivity via SWIFT, EBICS and SFTP through a single integration layer. Routing through our own BIC on the SWIFT network extends reach beyond the EU open-banking perimeter to virtually any bank worldwide. We retrieve balances and transactions automatically and consolidate them into one dashboard across all entities, banks and currencies, with conversion in the reporting currency. The result improves visibility and control over group liquidity, giving the data quality needed for same-day decisions on sweeping, overdraft avoidance and short-term placement. Every retrieval gets logged for audit.
How do you move from visibility to action on cash concentration and sweeping?
The Banking Orchestrator carries the intelligence layer for cross-bank liquidity management: automated pooling and sweeping across banking relationships, with overnight and fixed-term deposit instructions where relevant. We configure zero-balance, target-balance, threshold and range-based rules in the platform, with scheduling, four-eyes approval on exceptions, full audit evidence and bank-specific cut-offs handled, so nothing fails on a Friday afternoon. Notional pooling works as a different mechanism. It sits inside a single bank's infrastructure, with the bank netting balances across the accounts it holds. The Orchestrator does not replicate that. We do not hold funds. We orchestrate instructions across the banks that do. Since it stays bank-agnostic and independent of any single bank's cash management infrastructure, we deploy surplus cash optimally regardless of which bank holds the account. It sits at the banking and execution layer and coexists with a TMS where treasury analytics depth is needed.
"We do not hold funds. We orchestrate instructions across the banks that do."
Why do multi-banked structures struggle to optimise cash?
A corporate group with subsidiaries across several jurisdictions, or a fund structure with 10 SPVs across four banks, easily ends up with 15 or more accounts. Each bank brings its own portal, statement format and cut-off logic, so no consolidated picture exists without manual assembly. We see two elements typically go missing. First, the data: sweeping rules, target balances and yield decisions all need a reliable, current position underneath them, and most groups still rebuild that position by hand every morning. Second, execution reach: bank-native cash management tools work within one bank's account perimeter and stop the moment an account sits elsewhere. Multi-bank connectivity via EBICS and SWIFT through a single integration layer remains the prerequisite for both. The starting point of an optimisation programme is rarely a sweeping engine. It is a connectivity decision, a data model and a governance framework. Optimisation comes once those three sit in place.