UCP 600 Article 2: Applicant's Role vs. Account Party
Introduction
The distinction between the Applicant and the Account Party is a foundational concept in documentary credit practice. Under Article 2(a), the Applicant is the party on whose request the credit is issued. However, in practice, the Applicant may or may not be the same party as the Account Party (the party who ultimately pays for the goods or services). This guide examines the roles of the Applicant and the Account Party, their differences, and the practical implications under UCP 600.
Failure Mode Analysis
Failure Mode 1: Assuming Applicant Always Pays
Risk: The presenter assumes the Applicant will pay for the goods.
Impact: In some transactions, the Account Party is a third party (e.g., a parent company, a government agency, or a development bank). The Applicant's obligation to pay is governed by the credit application, not by UCP 600.
Failure Mode 2: Back-to-Back Credit Confusion
Risk: In a back-to-back credit, the beneficiary of the first credit becomes the applicant of the second credit. The Account Party of the first credit is the original applicant.
Impact: The distinction between Applicant and Account Party is important in back-to-back credits. The presenter must understand who is ultimately responsible for payment.
Failure Mode 3: Amendment Request by Non-Applicant
Risk: A party other than the Applicant requests an amendment to the credit.
Impact: Under Article 10(a), amendments require agreement of the issuing bank, confirming bank (if any), and the applicant. A non-Applicant cannot unilaterally request amendments.
Deterministic Resolution Architecture
Resolution 1: Party Role Identification
- Identify the Applicant under Article 2(a)
- Determine whether the Applicant is also the Account Party
- If different, identify the Account Party
- Verify the credit application reflects the correct parties
Resolution 2: Payment Obligation Analysis
- Review the credit application for payment terms
- Determine who provides the funds
- Verify the issuing bank's obligation under Article 2(f)
- Confirm the beneficiary's payment expectation
Resolution 3: Back-to-Back Credit Protocol
- Identify the first credit's Applicant and Account Party
- Identify the second credit's Applicant (the first credit's beneficiary)
- Verify the second credit's terms match the first credit
- Confirm the payment chain
Resolution 4: Bank-Side Examination Protocol
- Verify the Applicant under Article 2(a)
- Confirm the credit application is properly authorized
- Verify the Account Party relationship
- Document the party roles
Conclusion
The Applicant and the Account Party are distinct concepts under UCP 600, even though they are often the same party. The Applicant initiates the credit, while the Account Party provides the funds. Understanding this distinction is important for back-to-back credits, transferred credits, and third-party funded transactions.
Frequently Asked Questions
1. Can the Applicant be different from the Account Party?
Yes. In some transactions, the Applicant requests the credit, but a third party (the Account Party) provides the funds. This is common in government procurement or parent company funding.
2. Who is responsible for paying the issuing bank?
Under UCP 600, the issuing bank's obligation to pay is independent of the Applicant's obligation to reimburse. The Applicant's obligation is governed by the credit application agreement, not by UCP 600.
3. Can the Account Party request amendments?
Only the Applicant can request amendments under Article 10(a). If the Account Party is different from the Applicant, the Account Party must work through the Applicant to request amendments.
Source Notes
Context only. This guide is based on UCP 600 Articles 2 and 10 (ICC Publication No. 600). Source references in the search results pointed to general ICC Academy pages, which provided contextual framing but not article-specific text.
| Regulation | Article / Section | Requirement | Consequence |
|---|---|---|---|
| UCP 600 | Article 2 | Definitions | Binary determination (compliant/discrepant) |
| UCP 600 | Article 10 | Amendments | Binary determination (compliant/discrepant) |
← Scroll horizontally to see all columns
Quick Reference Summary
- No reference captured.
Compliance Checklist
| ✓ What Banks Expect | ✗ What Beneficiaries Often Do Wrong |
|---|---|
| Assuming Applicant Always Pays | **Risk:** The presenter assumes the Applicant will pay for the goods. |
| Back-to-Back Credit Confusion | **Risk:** In a back-to-back credit, the beneficiary of the first credit becomes the applicant of ... |
| Amendment Request by Non-Applicant | **Risk:** A party other than the Applicant requests an amendment to the credit. |
← Scroll horizontally to see all columns
Get the Full LC Compliance Checklist
15-point pre-submission checklist covering UCP 600, ISBP 745, and SWIFT MT700 fields. Free PDF download.
No spam. Unsubscribe anytime.
DraftLC generates compliant UCP 600 Article 2 — so you never face this failure mode.
DraftLC drafts your LC with UCP 600-compliant terms and flags conflicts during drafting — before documents reach the bank.
No credit card required · See how DraftLC drafts compliant credits