Part of our POBO & COBO Solutions guide.
The Problem
POBO becomes useful when the entity that owes a commercial obligation is not the same entity that owns the bank account from which the payment is made. In a multinational group, Group Treasury may pay supplier invoices for subsidiaries. In a PSP/MSB model, a regulated provider may execute payments for external customers.
Those two structures should not be confused.
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.
Corporate POBO
A group treasury center can centralize supplier and operating payments for subsidiaries. The subsidiary remains the underlying obligor while the central entity becomes the external payer.
External-Customer POBO
If a platform or payment company pays beneficiaries for unrelated customers, the structure may involve regulated payment activity, FBO accounts, customer ledgering, and licensing.
What the Bank Needs to See
The provider needs a coherent explanation of the account owner, ultimate debtor, payment purpose, beneficiary, source of funds, and relationship between the parties.
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
Is POBO the same as a payment factory?
No. A payment factory may centralize instructions while each subsidiary still pays from its own account. In true POBO, a central entity typically pays from its account on behalf of another entity.
Does POBO require an FBO account?
Not necessarily. Corporate-group POBO may use normal treasury accounts. External-customer POBO may require FBO, safeguarded, pooled, or other program accounts.
Does POBO eliminate licensing?
No. POBO describes a transaction structure; it is not a licensing exemption.
Related POBO / COBO Pages
- POBO & COBO Solutions
- POBO vs. COBO: What Is the Difference?
- POBO for Corporate Treasury and Multinational Groups
- POBO for PSPs, MSBs, and Payment Companies
- POBO & COBO Compliance: Ultimate Debtor, Ultimate Creditor, and Payment Transparency
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.