A payment factory centralizes payment execution and bank connectivity for many entities. The goal is standard controls, fewer local process variants, and clearer bank channels.

Keep three ideas separate:

  1. The factory — operations and bank connectivity
  2. The in-house bank — internal books and funding
  3. POBO / ROBO — who appears as the party on the rail

Not every factory is POBO. Many successful factories still release entity-level payments with central operations. See POBO vs entity-level payments. A factory is also not automatically an in-house bank — books and funding are a separate design (payment factory vs in-house bank).

What sits inside

  • Payment initiation from ERP / TMS, validation, and approval matrices
  • Format and channel management (ISO 20022, host-to-host, APIs, SWIFT, local rails)
  • Bank wallet strategy and contingency channels
  • Investigations, recalls, and reporting
  • Fraud controls, including dual control and business-email-compromise defenses

POBO versus entity-level release

POBO changes who appears as the payer and who needs legal capacity and disclosure. A factory can support POBO where allowed and fall back to entity-level payments elsewhere. “Global POBO factory” without a corridor matrix is how go-lives slip.

Funding ties back to cash pooling and liquidity management: usable cash must sit behind release. Payment-run design is also a working capital lever — uncontrolled early pays inflate DPO noise without helping suppliers.

Design checks

  • Who owns the payment file and the last approval?
  • How does factory activity reconcile to each entity’s GL?
  • Which countries block POBO or require local clearing presence?
  • What is the contingency path if the primary channel fails?

In markets such as China, domestic rails and cross-border documentation shape the footprint as much as technology does.

Sequence that works

  1. Define scopes (domestic vs cross-border; entity-level vs POBO).
  2. Fix funding (local balances vs concentration vs IHB).
  3. Select channels and formats per corridor.
  4. Implement controls and reconciliation before adding exotic corridors.