MT700 Field 47A and Its Relationship with UCP

Introduction

Field 47A of the SWIFT MT700 message holds the credit's "Additional Conditions." It is optional (Option A, 100×65z narrative) yet frequently decisive: practitioners use it for instructions and qualifications that the dedicated fields cannot express. Its relationship with UCP runs through Article 14, which governs how the examining bank treats additional conditions — whether they are examined, disregarded as non-documentary, or become discrepancies when they conflict with the rest of the credit.

This guide examines field 47A's relationship with the UCP rules as a whole. It centers on Article 14's examination standard and the no-conflict and non-documentary principles, and it shows how the SWIFT network-validated rule on electronic presentation fixes field 47A's placement role. The aim is a clear picture of how an "additional conditions" narrative is handled under UCP.

Failure Mode Analysis

Failure Mode 1: Field 47A Condition Conflicts with a Field 46A Document

Field 46A requires a clean transport document; field 47A adds a notation the clean transport rule (Articles 26–27) forbids. The document cannot comply with both, and the presentation is discrepant.

Failure Mode 2: Field 47A Condition Contradicts Field 45A

Field 45A describes one goods set; field 47A references another or a different Incoterm allocation. The internal conflict is caught under Article 14(d).

Failure Mode 3: Non-Documentary Condition Creates Ambiguity

Field 47A imposes a requirement no document evidences. The bank disregards it, but the beneficiary is unsure whether a document was intended, risking a dispute with the applicant.

Failure Mode 4: Electronic-Address Misplacement

Only electronic records are allowed, yet the address is in field 46A rather than field 47A. The SWIFT rule is breached and the presentation route is undefined.

Failure Mode 5: Timing Condition Conflicts with Expiry or Field 44C

Field 47A requires a document issued within a window that conflicts with the latest shipment date or the expiry. The beneficiary cannot satisfy both, producing a discrepancy under Article 14(g).

Deterministic Resolution Architecture

Step1: Enumerate Field 47A Conditions

List every additional condition and classify each as document-linked or potentially non-documentary.

Step2: Link Conditions to Documents or Fields

For document-linked conditions, identify the target document in field 46A and its governing article. For non-documentary conditions, note they may be disregarded.

Step3: Test Document-Linked Conditions Against the Article

Confirm the condition can be satisfied consistently with the document's article. Where it conflicts, request amendment.

Step4: Test Conditions Against Field 45A

Confirm no field 47A condition contradicts field 45A's goods or Incoterm. Resolve contradictions by amendment.

Step5: Apply the Electronic-Presentation Rule

If only electronic records are allowed, place the electronic address in field 47A per the SWIFT network-validated rule. Verify it is complete and not in field 46A.

Step6: Reconcile Timing Conditions

Confirm any field 47A timeframe fits within field 44C and the expiry. Amend if it conflicts.

Step7: Clarify Non-Documentary Intent

For conditions no document evidences, confirm with the issuing bank whether a document was intended. If so, add it to field 46A; if not, accept disregard.

Step8: Final Field 47A Check

Before presentation, re-read field 47A against the fields it modifies. Confirm no conflict, correct address placement, and consistent timing. Present only when all hold.

Conclusion

Field 47A's relationship with UCP is governed by Article 14. The article decides whether an additional condition is examined, disregarded as non-documentary, or a discrepancy when it conflicts with the credit. Document-specific conditions engage Articles 18–28, and the SWIFT electronic-presentation rule fixes field 47A's placement. A field 47A drafted with document-linked, internally consistent, correctly placed conditions supports a clean presentation; a contradictory or misplaced one produces the discrepancies described here.

FAQ

Q1: What is the core UCP rule for field 47A?
Article 14 — its examination standard (14(a)), no-conflict rule (14(d)), and non-documentary treatment. Document-specific conditions also engage Articles 18–28.

Q2: Is field 47A mandatory?
No, field 47A is optional under SWIFT. It is used for conditions that do not fit dedicated fields.

Q3: Are field 47A conditions always examined?
No. A condition no document can fulfill is disregarded as non-documentary. A condition linked to a stipulated document is examined.

Q4: Where does the electronic-presentation address go?
If only electronic records are allowed, the SWIFT network-validated rule requires the electronic address in field 47A, not field 46A.

Q5: Can field 47A contradict field 45A?
It can, and the conflict makes the credit internally inconsistent under Article 14(d). Request amendment.

Q6: What if a field 47A timing condition conflicts with the expiry?
The beneficiary cannot meet both windows. Request amendment to align it with field 44C and the expiry before presentation.

Source Notes

Context only: The source dossier for this guide contained the SWIFT MT700 field 47A specification (SWIFT SR2018, Category 7), including the network-validated rule on electronic-record presentation addresses, and the UCP 600 article cross-reference for field 47A (Article 14). No text from those sources has been reproduced. This guide was composed from first principles using the SWIFT MT700 field specification, the UCP 600 framework, and independent analysis of field 47A's relationship with UCP.