Part of our POBO & COBO Solutions guide.
The Problem
A multinational group may maintain dozens or hundreds of operating bank accounts because each subsidiary pays its own suppliers. POBO can centralize outgoing payments into a smaller set of treasury accounts while preserving the underlying subsidiary as the ultimate debtor.
The correct design starts with the flow of funds: who owns the funds, who owes or is owed money, who owns the external bank account, what the relationship is between the parties, and whether the underlying parties are related group companies or external customers.
Typical Flow
The diagram is intentionally generic. Actual implementation depends on the legal entities, jurisdictions, bank/provider rules, payment rails, currencies, licensing status, and reconciliation model.
Why Treasury Uses POBO
The goals are usually bank-account rationalization, liquidity centralization, standardized controls, FX consolidation, and stronger cash visibility.
Intercompany Ledgering
When treasury pays a subsidiary's obligation, the internal books must capture the resulting intercompany position or settlement logic.
Bank Messaging
The bank and beneficiary should receive sufficient underlying-party and remittance data to understand whose obligation is being paid.
Core Design Questions
- Who is the legal account owner?
- Who is the economic owner of the funds?
- Who is the debtor and who is the ultimate debtor?
- Who is the creditor and who is the ultimate creditor?
- Are the underlying parties related companies or external customers?
- Which countries and currencies are involved?
- Which rails are required?
- What monthly volume and transaction count are expected?
- Is a named, virtual, pooled, FBO, or safeguarded account required?
- Who performs KYC/KYB, sanctions screening, and transaction monitoring?
- How will the internal ledger and reconciliation work?
What We Can Help With
We can help map the transaction, identify the appropriate banking/payment architecture, determine what type of provider is required, prepare the provider-facing flow of funds, and source or introduce suitable banks, PSPs, MSBs, or program partners where there appears to be a fit.
Frequently Asked Questions
Can POBO eliminate every local bank account?
Usually not. Payroll, taxes, local regulations, exchange controls, or local clearing requirements may still require local accounts.
Can POBO work across currencies?
Yes, if the central treasury has the required currency accounts, FX capability, and bank support.
Related POBO / COBO Pages
- POBO & COBO Solutions
- What Is POBO? Payments On Behalf Of Explained
- COBO for Corporate Treasury and Multinational Groups
- POBO, COBO, In-House Banks, and Payment Factories
- POBO & COBO With SWIFT and ISO 20022
Related Services
Get Help Designing This Structure
Send us your entity chart and flow of funds. If you do not have a diagram, describe who pays, who receives, who owns each account, what the underlying obligation is, and where the money ultimately goes.
