MT700 Field 47A and Its Relationship with UCP 600 Articles

Introduction

SWIFT MT700 field 47A is the "Additional Conditions" field. Optional in the message (Option A, 100×65z narrative), it carries conditions that do not fit the dedicated fields — special instructions, document qualifications, and credit modifications. Field 47A's relationship with UCP 600 is governed primarily by Article 14, which sets the standard of examination, the no-conflict rule, and the treatment of non-documentary conditions. The field also engages the document-type articles where its conditions modify documents listed in field 46A.

This guide maps field 47A to the UCP 600 articles that apply to its contents, with attention to Article 14's several subrules and to Articles 18–28 where field 47A conditions touch specific documents. It explains how a SWIFT "additional conditions" narrative becomes a UCP 600 examination issue.

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 clause the clean transport rule (Articles 26–27) does not permit. The document cannot satisfy both, and the presentation is discrepant.

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

Field 45A describes specific goods; field 47A references different goods or a different Incoterm allocation. The conflict makes the credit internally inconsistent under Article 14(d).

Failure Mode 3: Non-Documentary Condition in Field 47A Creates Uncertainty

Field 47A states a condition no document evidences (for example, a requirement about the goods' quality without a required certificate). The bank disregards it under the non-documentary principle, leaving unclear whether the credit intended a document.

Failure Mode 4: Electronic-Presentation Address Misplaced

The credit allows only electronic records, but the electronic address is placed in field 46A rather than field 47A. The SWIFT network-validated rule is breached, and the presentation mechanics are undefined.

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

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

Deterministic Resolution Architecture

Step1: Catalog Field 47A Conditions

List every additional condition in field 47A. Classify each as document-linked or potentially non-documentary.

Step2: Link Each Condition to Its Document or Field

For document-linked conditions, identify the target document in field 46A and the governing article (18–28). For potentially non-documentary conditions, note they may be disregarded under Article 14.

Step3: Test Document-Linked Conditions Against the Governing Article

Confirm the field 47A condition can be satisfied consistently with the document's article. Where it conflicts (for example, a clean-transport violation), request amendment.

Step4: Test Conditions Against Field 45A

Confirm no field 47A condition contradicts the field 45A goods description 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. Confirm it is complete and not duplicated in field 46A.

Step6: Reconcile Timing Conditions

Where field 47A imposes a document-issue timeframe, confirm it fits within field 44C and the expiry. Amend if it conflicts.

Step7: Decide Non-Documentary Treatment

For conditions no document evidences, confirm with the issuing bank whether a document was intended. If so, have it added to field 46A; if not, accept that it will be disregarded.

Step8: Final Field 47A Verification

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

Conclusion

Field 47A's relationship with UCP 600 is mediated by Article 14. The article's examination standard, no-conflict rule, and non-documentary treatment determine whether a field 47A condition is examined, disregarded, or a discrepancy. Where a condition modifies a specific document, the document's governing article (18–28) applies alongside. The SWIFT electronic-presentation rule further fixes field 47A's placement role. Drafting field 47A so its conditions are document-linked, internally consistent, and correctly placed yields a clean credit; contradictory or misplaced conditions yield the discrepancies this guide enumerates.

FAQ

Q1: Which UCP 600 article primarily governs field 47A?
Article 14 — its examination standard (14(a)), no-conflict rule (14(d)), and non-documentary condition treatment (reflected in 14 and ISBP 745 A2). Document-specific conditions also engage Articles 18–28.

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

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

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

Q5: Can a field 47A condition conflict with field 45A?
Yes, and when it does the credit is internally inconsistent under Article 14(d). The beneficiary should request amendment.

Q6: What if a field 47A timing condition conflicts with the expiry?
The beneficiary cannot meet both windows. Request amendment to align the condition 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 article relationships.