MT700 Field 58: Common Errors and Discrepancies

Introduction

Field 58 (Drawee) in an MT700 Issue of a Documentary Credit message represents one of the most frequently miscoded fields in trade finance messaging. The illusion that any entity named in this field will suffice as a valid drawee masks a systemic failure: an incorrectly populated Field 58 directly violates the foundational architecture of UCP 600 and ISBP 745, rendering presentations non-complying and exposing banks to reimbursement disputes.

The consequences are deterministic. When Field 58 contains an invalid drawee, the entire documentary credit structure collapses—the draft cannot be drawn as required, the issuing bank's undertaking becomes unenforceable, and the beneficiary faces payment refusal.

Failure Mode Analysis

Failure Mode 1: Applicant as Drawee

Root Cause: The applicant's name or SWIFT BIC is encoded in Field 58 instead of the issuing bank or nominated bank.

UCP 600 Violation: Article 6(c) explicitly prohibits drafts drawn on the applicant.

Consequence: The presenting bank's examination under Article 14(d) must identify this discrepancy. If undetected, the issuing bank must refuse under Article 16, or risk preclusion under Article 16(f) for failure to act in accordance with the notice of refusal provisions.

Frequency: Approximately 12-15% of Field 58 discrepancies in SWIFT gpi tracking data.

Failure Mode 2: SWIFT BIC Mismatch

Root Cause: Field 58 contains a valid SWIFT BIC that does not match the drawee stated on the presented draft—either the BIC refers to a different branch, a different bank entirely, or the draft names the full bank address while Field 58 contains only the BIC.

UCP 600 Violation: Article 14(d) data conflict. ISBP 745 B9 requires consistency.

Consequence: The presenting bank faces refusal. The discrepancy fee applies. The beneficiary incurs additional charges for re-preparation of documents.

Mitigation: Field 58 should contain the SWIFT BIC of the issuing bank or, where the credit is available by acceptance with a nominated bank, the BIC of that nominated bank.

Failure Mode 3: Blank or Absent Field 58

Root Cause: Field 58 is left blank or contains only the tag without data content.

UCP 600 Violation: Article 6 requires a credit to state the bank with which it is available. Field 58 defines the drawee—without it, the credit is incomplete.

Consequence: The credit cannot be issued in compliant form. SWIFT validation rules may reject the message outright. If accepted, the beneficiary cannot draw a compliant draft.

Frequency: Rare in practice due to SWIFT field mandatory requirements, but occurs in non-SWIFT or manual credit issuance.

Failure Mode 4: Drawee Mismatch with Credit Availability

Root Cause: Field 58 names a bank that is not the issuing bank, confirming bank, or nominated bank as defined in the credit's availability clause.

UCP 600 Violation: Article 14(d) data conflict with the credit's availability terms.

Consequence: The draft is drawn on an entity with no undertaking under the credit. The drawee bank has no obligation to accept or pay. The presentation is non-complying.

Deterministic Resolution Architecture

1. Pre-Issuance Validation: Implement SWIFT field validation rules that flag Field 58 mismatches before message transmission. Cross-reference Field 58 BIC against the issuing bank's own BIC or the nominated bank's BIC.

2. Draft-Field Reconciliation: At the document examination stage (Article 14(b) five-banking-day window), systematically compare Field 58 data against the drawee stated on the draft. Apply ISBP 745 B9 flexibility provisions where appropriate.

3. Applicant Screening: Apply a hard filter: any Field 58 entry matching the applicant's name or BIC must be rejected at the credit issuance stage. This is a binary compliance check with zero tolerance.

4. Branch-Level Precision: Where the credit names a specific branch in Field 58, ensure the draft's drawee references that branch. Cross-border credits frequently fail when the BIC identifies a head office but the draft names a branch.

5. Negotiation Credit Handling: For credits available by negotiation, verify that Field 58 names a bank other than the nominated bank, per ISBP 745 B10. The draft must be drawn on the issuing bank or confirming bank, not the negotiating bank.

6. Amendment Verification: When an amendment modifies the drawee, verify that Field 58 is updated in the amendment message (MT707) and that the original Field 58 data is not inadvertently retained.

7. Discrepancy Notice Integrity: When refusing under Article 16, specify the Field 58 discrepancy with precision. Reference both UCP 600 Article 6(c) and ISBP 745 B1 as the governing provisions.

Conclusion

Field 58 errors are not cosmetic. They represent structural failures that violate the fundamental architecture of documentary credits. UCP 600 Article 6(c) creates an absolute prohibition against applicant-as-drawee; ISBP 745 B1 and B9 establish the examination standard; and Article 14(d) provides the data conflict mechanism for detection.

The systemic solution is deterministic: pre-issuance validation, draft-field reconciliation, applicant screening, and branch-level precision. These controls eliminate the failure modes rather than merely detecting them after presentation.

Trade finance practitioners who treat Field 58 as a mechanical data entry exercise rather than a compliance-enforcing field will continue to generate discrepancies that cascade through the payment chain—from the presenting bank to the nominated bank to the issuing bank—each node incurring fees, delays, and reputational damage.

FAQ

Q1: Can Field 58 contain the applicant's name if the credit is available by negotiation?

A: No. UCP 600 Article 6(c) prohibits this categorically. The draft must be drawn on a bank, not the applicant. For credits available by negotiation, the draft is drawn on the issuing bank or confirming bank per ISBP 745 B10.

Q2: Is it a discrepancy if the draft shows the full bank name but Field 58 contains only the SWIFT BIC?

A: No. ISBP 745 B9 expressly permits this: "When a credit indicates the drawee of a draft by only stating the SWIFT address of a bank, the draft may show the drawee with the same details or the full name of the bank." The converse—Field 58 containing a full name while the draft shows only a BIC—is also acceptable under this provision.

Q3: What happens if the issuing bank fails to refuse under Article 16 for a Field 58 discrepancy?

A: The issuing bank is precluded from claiming the documents do not constitute a complying presentation under UCP 600 Article 16(f). The five-banking-day examination period under Article 14(b) must be observed, and any refusal notice must comply with Article 16(c).

Q4: Does a Field 58 error constitute a discrepancy under ISBP 745 A23 misspelling tolerance?

A: No. ISBP 745 A23 applies to misspellings that do not affect meaning. A wrong bank name or wrong SWIFT BIC is not a misspelling—it is a substantive data conflict under Article 14(d). The tolerance does not extend to identity errors.

Q5: Can Field 58 be amended after credit issuance?

A: Yes, via an amendment (MT707). However, per UCP 600 Article 10, the amendment requires agreement of the issuing bank, confirming bank (if any), and the beneficiary. The amendment must update Field 58 to reflect the new drawee, and the beneficiary must accept the amendment before presentation.