URBPO 750: The Bank Payment Obligation
An LC's bank promise for open-account trade, with data matching in place of document checking.
A large share of world trade now runs on open account: the seller ships and the buyer pays later, with no letter of credit. A bank payment obligation (BPO) adds a bank's promise to that model without bringing back the paper. Instead of checking documents, banks compare data from the purchase order, invoice and shipment in a matching system, and the buyer's bank pays when the data match.
The rules are the ICC Uniform Rules for Bank Payment Obligations, ICC Publication No. 750 (URBPO), developed with SWIFT, approved by the ICC Banking Commission in April 2013 and effective from 1 July 2013. They apply when the payment obligation segment of the data expressly states it is subject to them.
You save ₹200 today
- 5 full-length mocks
- 553 questions, chapter by chapter
- Rate & risk calculations
One payment, no subscription · Valid for 2 months
The Terms URBPO Defines
- BPO
- An irrevocable and independent undertaking of an obligor bank to pay a specified amount to a recipient bank, on a specified date, after all the data sets required by an established baseline have been submitted and matched.
- Obligor bank
- The bank that issues the BPO. Usually the buyer's bank.
- Recipient bank
- The bank that is the beneficiary of the BPO. Under URBPO it is always the seller's bank.
- Transaction matching application (TMA)
- The central data-matching and workflow application that compares the data sets automatically. All involved banks must use the same one.
- Baseline and established baseline
- The baseline is the agreed transaction data, such as goods, amount and shipment terms. It becomes established once the TMA reports zero mismatches between the buyer's and seller's banks' data.
- Data match
- A comparison of all required data sets that results in zero mismatches. A match triggers the obligor bank's payment.
BPO vs Letter of Credit
Undertaking given to
Letter of credit (UCP 600)
The beneficiary (exporter)
BPO (URBPO 750)
The recipient bank (seller's bank), bank to bank
Banks examine
Letter of credit (UCP 600)
Paper or electronic documents
BPO (URBPO 750)
Data sets in a matching application
Who decides compliance
Letter of credit (UCP 600)
Bank examiners, within five banking days
BPO (URBPO 750)
The TMA, automatically
If data or documents mismatch
Letter of credit (UCP 600)
Discrepancy; applicant may waive
BPO (URBPO 750)
Mismatch; the buyer's bank may accept it and the obligor bank may still pay
Core principle
Letter of credit (UCP 600)
Banks deal with documents
BPO (URBPO 750)
Banks deal with data, not documents, goods or services
| Letter of credit (UCP 600) | BPO (URBPO 750) | |
|---|---|---|
| Undertaking given to | The beneficiary (exporter) | The recipient bank (seller's bank), bank to bank |
| Banks examine | Paper or electronic documents | Data sets in a matching application |
| Who decides compliance | Bank examiners, within five banking days | The TMA, automatically |
| If data or documents mismatch | Discrepancy; applicant may waive | Mismatch; the buyer's bank may accept it and the obligor bank may still pay |
| Core principle | Banks deal with documents | Banks deal with data, not documents, goods or services |
Rules That Mirror the LC Family
- check_circleIndependence: a BPO is separate from the sale contract, and involved banks are not bound by it (Article 6).
- check_circleData, not documents: banks deal with data, not with documents, goods, services or performance (Article 7). This is the BPO version of UCP 600's "documents, not goods".
- check_circleExpiry: all required data sets must reach the TMA no later than 23:59:59 UTC on the expiry date (Article 8).
- check_circleAmendment: changing an established baseline needs the agreement of each involved bank (Article 11).
- check_circleSeveral BPOs in one baseline create no joint and several liability between obligor banks (Article 10).
URBPO definitions and LC comparisons. No signup.
Seller's Bank Is Always the Recipient
In an LC the beneficiary is the exporter itself. In a BPO the beneficiary is a bank: the recipient bank, which URBPO defines as always the seller's bank. The exporter benefits through its bank, which can then offer post-shipment finance against a bank undertaking rather than the buyer's open-account promise.
How CCFE Tests This
- check_circle"What does a BPO undertaking depend on?" Matching of data in a TMA, not presentation of documents.
- check_circle"Who is the recipient bank?" Always the seller's bank. The trap option is the buyer's bank, which is usually the obligor.
- check_circlePublication and date questions: ICC Publication 750, effective 1 July 2013.
- check_circleParallel-principle questions: which rule set says banks deal with data rather than documents.
FAQs
What is a bank payment obligation?expand_more
An irrevocable, independent undertaking by an obligor bank, usually the buyer's bank, to pay the seller's bank on a specified date once the trade data submitted to a matching application match.
What is URBPO 750?expand_more
ICC's Uniform Rules for Bank Payment Obligations, Publication No. 750, effective 1 July 2013 and developed with SWIFT. They govern BPOs that expressly state they are subject to them.
How is a BPO different from a letter of credit?expand_more
An LC is a bank's promise to the exporter against compliant documents checked by bank staff. A BPO is a bank-to-bank promise triggered by an automatic data match, with no document examination.
Who is the obligor bank in a BPO?expand_more
The bank that issues the BPO and must pay on a data match. It is usually the buyer's bank.
Next steps
Take a full CCFE mock test100 questions across all six modules, timed and scored.