Part of our POBO & COBO Solutions guide.
The Problem
POBO and COBO deliberately separate the external account owner from the underlying commercial party. Without proper documentation and data, a legitimate structure can look like an unexplained third-party payment.
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.
Ultimate Debtor
The underlying party whose obligation is being settled.
Ultimate Creditor
The underlying party economically entitled to the incoming payment.
KYC/KYB and Screening
Providers may need to identify and screen both account holders and underlying parties depending on the model.
Reconciliation and Audit Trail
The internal ledger should connect the bank transaction to the underlying invoice, entity, customer, merchant, and commercial purpose.
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
Why not just put the subsidiary name in the payment reference?
Free-text references may be insufficient for compliance, screening, and straight-through processing. Structured ultimate-party data is preferable where supported.
Is third-party payment risk always prohibited?
No. Properly structured agency, treasury, and regulated-payment models exist, but they must be understood and approved.
Related POBO / COBO Pages
- POBO & COBO Solutions
- POBO & COBO With SWIFT and ISO 20022
- POBO & COBO Account Structures: Named, Virtual, FBO, and Pooled Accounts
- POBO & COBO U.S. Money Transmission and Licensing Considerations
- POBO & COBO Implementation Checklist
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.