Provider offers to arrange an SBLC for a fee. Receiver wants the instrument for a financing transaction.
Case: Provider Requests a BPU
A third-party provider proposes MT799/BPU before issuing an MT760 SBLC.
Agreement says receiver bank sends a BPU after preliminary verification; provider bank then sends MT760.
Receiver gives the proposed wording/procedure to its bank before signing an obligation it cannot perform.
Bank says it can receive MT760 but will not issue the proposed unconditional BPU without credit approval/cash cover.
Parties either agree bank-acceptable security/payment mechanics or stop the deal.
Receiver verifies provider, claimed issuer and financier separately.
Only if banks approve does the provider bank issue the SBLC in the agreed route.
Financier makes its own decision; MT760 authenticity does not itself guarantee the proposed LTV.
What this case teaches
- A BPU can be a real bank obligation but is not universally required for SBLC issuance.
- Never sign a private SOP assuming your bank must follow it.
- Provider, issuer and financier must be verified separately.
Work the case like a practitioner
Before looking only at the outcome, separate the instrument from the surrounding transaction. Use these questions every time.
What undertaking, payment method or document is actually involved?
What rules, expiry, maturity or presentation deadline controls the next step?
Which facts are independently verified and which are only counterparty claims?
What must the bank authenticate, approve, examine or settle?
Remember: a case illustrates a method of thinking. A real bank may require different documents, approvals or procedures.
Check 1
What should the receiver do before agreeing to send a BPU?
