Under a POBO model, a central treasury or service entity makes external payments that economically belong to other group companies. The bank account belongs to the central paying entity while internal accounting records an intercompany amount against the subsidiary whose supplier or obligation was paid.
The practical meaning of payments on behalf of, POBO
Under a POBO model, a central treasury or service entity makes external payments that economically belong to other group companies. The practical objective is not more paperwork; it is to know what must happen next and who has authority to change the planned outcome.
The bank account belongs to the central paying entity while internal accounting records an intercompany amount against the subsidiary whose supplier or obligation was paid. In practice, the finance team should translate that rule into a specific amount, owner and deadline instead of relying on the product name alone.
How payments on behalf of, POBO works from start to finish
POBO is not merely changing the name on a payment file because suppliers, banks and tax authorities can still need the underlying debtor, invoice or legal entity to remain identifiable. The important point for a business is that the operational treatment can change when the contract, currency, legal entity or transaction date changes.
The model can reduce external bank accounts and consolidate liquidity, but it also creates intercompany balances that require disciplined posting and settlement. Treasury should therefore test the exact wording or processor response before assuming the same treatment applies to every transaction.
The contractual and system details that matter
Service agreements, bank mandates, tax treatment, payment authority and remittance design should be agreed before local entities are moved to the central account. That makes traceability essential: the bank record, internal approval and accounting entry should all point back to the same commercial event.
Suppliers can misallocate legitimate payments when the bank statement shows the central treasury entity instead of the customer named on the invoice. A simple written control around this point can prevent a later cash, reconciliation or customer-service problem that is much harder to unwind.
Where the process can fail
Remittance data should preserve the underlying subsidiary, supplier account and invoice reference, with daily reconciliation between the bank movement and intercompany entry.
Payroll, tax, regulated or ring-fenced payments may need local arrangements and should be tested separately instead of being forced into a global standard.
Worked example: test the mechanics
Subsidiary A owes a supplier £80,000. Group Treasury Ltd pays the supplier from the POBO account and books an £80,000 receivable from Subsidiary A. The remittance identifies Subsidiary A and the invoice even though the sending account belongs to Group Treasury Ltd.
Use the example as a method, not a universal rule. The article-specific control point is this: POBO is not merely changing the name on a payment file because suppliers, banks and tax authorities can still need the underlying debtor, invoice or legal entity to remain identifiable. The business should reproduce the numbers and timing from its own contract, bank service or processor record before acting.
Governance for payments on behalf of, POBO
Implementation check: Service agreements, bank mandates, tax treatment, payment authority and remittance design should be agreed before local entities are moved to the central account. The operating owner should convert that requirement into a named approval, a dated record and a reconciliation step so the intended treatment can be reproduced later.
Monitoring check: Remittance data should preserve the underlying subsidiary, supplier account and invoice reference, with daily reconciliation between the bank movement and intercompany entry. Management reporting should show whether this control is working, including unresolved exceptions and material changes rather than only completed transaction volume.
Escalation check: Payroll, tax, regulated or ring-fenced payments may need local arrangements and should be tested separately instead of being forced into a global standard. If the assumption behind that point changes after approval, treasury should stop and reassess the transaction before cash, credit exposure or customer outcome becomes irreversible.
Decision check: The model can reduce external bank accounts and consolidate liquidity, but it also creates intercompany balances that require disciplined posting and settlement. The commercial choice should be made with that trade-off visible, then recorded together with the reason management accepted the remaining risk.
Editorial Verdict
BanksGB’s view starts with the underlying rule: Under a POBO model, a central treasury or service entity makes external payments that economically belong to other group companies. For payments on behalf of, POBO, the business should be able to show how that rule connects to the amount, timing, legal entity and financial outcome of the transaction rather than relying on the product label.
The second test is operational: Suppliers can misallocate legitimate payments when the bank statement shows the central treasury entity instead of the customer named on the invoice. A strong payments on behalf of, POBO process makes that failure mode visible early, preserves the evidence used for the decision and gives management a realistic escalation route before the position becomes expensive to unwind.
Sources
- J.P. Morgan, Centralising treasury and payments on behalf of: https://www.jpmorgan.com/insights/real-estate/commercial-real-estate/how-commercial-real-estate-can-centralize-treasury
- Deutsche Bank, Operational efficiency in treasury: https://flow.db.com/cash-management/operational-efficiency-in-treasury