Payment on Behalf of (POBO) means one group entity (often the treasury center or in-house bank) executes a payment in its own name to settle another entity’s obligation.
A payment factory can run without POBO. Many factories use entity-level payments with central ops. POBO is the model where the wire party must be the center. Decision page: POBO vs entity-level payments.
What changes on the wire
In entity-level release, the subsidiary remains the paying party where the scheme requires it. In POBO, the center is the payer on the rail, while accounting still shows which subsidiary owed the commercial obligation. Banks, regulators, and beneficiaries may require disclosure of the on-behalf relationship.
When it helps
- Fewer funded local accounts for low-volume entities
- Stronger dual-control and fraud standards at the center
- Better liquidity usage when paired with cash pooling or cross-border cash pooling
When it breaks
- Local schemes or beneficiary banks that reject third-party payer patterns
- Missing corporate authority or agency documentation
- Tax / VAT invoice and statutory payment-party mismatches
- Corridors where cross-border POBO needs local presence — validate per market; China is a frequent special case
Minimum design package
- Legal capacity and intercompany agency / reimbursement rules
- Corridor matrix (domestic / cross-border / currency / scheme)
- ERP–TMS–bank posting and reimbursement flows
- Beneficiary remittance information standards
- Funding at the paying entity (IHB books, pool header, or prefund)
ROBO is the collection-side counterpart.