Why Bank Guarantee UAT Needs URDG 758 Coverage
URDG 758 — the Uniform Rules for Demand Guarantees — is the ICC standard that governs demand guarantees and counter-guarantees internationally. Bank guarantee modules on core banking platforms must reflect URDG 758 rules for how demands are presented, examined, and paid — and how the "extend or pay" mechanism works when a beneficiary requests guarantee extension rather than immediate payment.
The most common UAT failure in bank guarantee implementations is testing the issuance and expiry paths but not the demand path. A guarantee exists to be called. The demand presentation, examination, and payment — or refusal — logic is what matters to the beneficiary in a real dispute, and it is almost never tested in depth.
Core URDG 758 Test Scenario Areas
BG-URDG-001
Guarantee issuance
Guarantee issued under URDG 758. SWIFT MT760 generated with correct field content — guarantee type, amount, expiry, applicant, beneficiary. System must distinguish URDG from ISP98 and UCP 600 guarantees.
BG-URDG-002
Counter-guarantee issuance
Issuing bank instructs correspondent via MT760 to issue local guarantee. System must link the counter-guarantee to the master guarantee and track liability across both.
BG-URDG-003
Demand presentation
Beneficiary presents complying demand within validity period. URDG 758 Art. 15: bank has 5 business days to examine. System must open examination clock from demand receipt.
BG-URDG-004
Extend or pay demand
Beneficiary requests extension of guarantee rather than immediate payment. System must notify applicant, track response deadline, and process either extension or payment based on applicant instruction.
BG-URDG-005
Partial demand
Demand for less than the full guarantee amount. System must update outstanding liability, retain guarantee for remaining balance, and allow further demands up to the original amount.
BG-URDG-006
Expiry and auto-closure
Guarantee expires with no demand. System must automatically close the guarantee, release the applicant's contingent liability, and generate closure advice to all parties.
The Extend or Pay Mechanism — Most Commonly Undertested
The extend or pay demand is the scenario that most frequently reveals implementation gaps in production. When a beneficiary does not want to call the guarantee outright but does not want it to expire, they present an "extend or pay" demand — the bank must extend the guarantee or pay the demand within a defined period.
Under URDG 758 Article 23, the guarantor has until the business day before the current expiry date to notify the beneficiary of extension or payment. The system must:
- Accept and record the extend or pay demand
- Notify the applicant immediately with a defined response deadline
- Process an extension if the applicant agrees — including updating the guarantee record and generating an MT767 amendment
- Process payment if the applicant does not agree or does not respond within the deadline
- Generate the correct SWIFT message in each outcome
Common UAT Gap
Extend or pay is almost universally absent from first-round UAT registers. Teams test issuance, amendment, and expiry. The demand path — particularly extend or pay — is deferred to "Phase 2" and then enters production untested. This is the scenario that triggers the highest-value guarantee disputes.
SWIFT MT760 Series Coverage
- MT760 — Guarantee / Standby LC Issuance: Field 22A (purpose), 23X (file reference), 30 (date), 22D (form of guarantee), 40C (applicable rules — URDG 758), 31E (expiry), 50 (applicant), 59 (beneficiary), 32B (amount) — all must be tested for content accuracy
- MT767 — Guarantee / Standby Amendment: Amendment type and changed fields. Beneficiary acceptance required for amount increases under URDG 758.
- MT768 — Acknowledgement of Guarantee Message: Correspondent bank acknowledgement. System must record receipt and link to the original guarantee.
- MT769 — Advice of Reduction or Release: Generated when guarantee amount is reduced on partial demand or guarantee is released. Must reconcile to the original amount and any prior demands.
Guarantee Types That Need Separate Test Coverage
- Performance Guarantee: Called when contractor fails to perform. Demand evidence requirements are defined in the guarantee wording — system must not apply UCP 600 documentary standards
- Advance Payment Guarantee: Reduces pro-rata as advance is repaid — system must track reduction schedule and update outstanding amount on each repayment
- Bid Bond / Tender Guarantee: Short validity, called only if tenderer withdraws bid or fails to execute contract — auto-expiry on contract execution must be tested
- Retention Guarantee: Replaces retention money withheld under a construction contract — release on defects liability period expiry must be tested
URDG 758-aligned bank guarantee test cases — ready to use
Issuance · Counter-guarantee · Demand · Extend or pay · SWIFT MT760 series · All guarantee types
Get in Touch →