MT700 Field 47A When Its Conditions Contradict Other Fields

Introduction

SWIFT MT700 field 47A is the "Additional Conditions" field. It is an optional narrative field (Option A, 100×65z) that carries conditions not accommodated elsewhere in the message — special instructions, document-specific requirements, and qualifications that modify the credit's effect. Because field 47A supplements the rest of the MT700, it is a frequent source of internal contradiction: a condition added here can undermine a term set in field 45A, 46A, 44B, or 49.

This guide focuses on the failure pattern where field 47A conditions contradict other MT700 fields. It draws on the SWIFT MT700 field 47A specification, including the network-validated rule on electronic-record presentation, and on UCP 600 Article 14 (standard of examination, no-conflict rule, and non-documentary conditions). It shows how a contradictory additional condition becomes a discrepancy.

Failure Mode Analysis

Failure Mode 1: Field 47A Condition Contradicts Field 45A Goods Description

Field 45A describes "REFINED SUNFLOWER OIL." Field 47A adds a condition referencing "crude oil inspection." The goods implied by the additional condition conflict with the field 45A description, and the document set cannot satisfy both coherently.

Failure Mode 2: Field 47A Imposes an Insurance Obligation Conflicting with Field 45A Incoterm

Field 45A states "EXW BUYER'S WAREHOUSE" (buyer bears risk). Field 47A requires a seller-issued insurance certificate. The additional condition contradicts the risk allocation in the Incoterm, and the beneficiary cannot comply with both without amendment.

Failure Mode 3: Field 47A Electronic-Presentation Address Conflicts with Field 46A

The credit allows electronic presentation. Field 47A must specify the electronic address for presentation. If field 46A instead attempts to carry that address, or if field 47A names an address that conflicts with the credit's presentation rules, the presentation mechanics are contradictory.

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

Field 46A requires a "clean on board bill of lading." Field 47A adds a condition that the bill show a clause incompatible with the clean transport rule. The document cannot satisfy both the field 46A requirement and the field 47A condition.

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

Field 47A requires a document issued within a timeframe that conflicts with the latest shipment date in field 44C or the expiry in field 31D. The beneficiary cannot issue the document within both windows, producing a discrepancy under Article 14(g).

Deterministic Resolution Architecture

Step1: Extract Field 47A and Read It Against the Whole Message

Record every additional condition in field 47A and compare it against fields 44B, 45A, 46A, 44C, 31D, and 49. Treat field 47A as a modifier of the whole credit, not an isolated note.

Step2: Identify Each Condition's Document Target

For every field 47A condition, determine which document it modifies or which it implies. A condition that targets no document may be non-documentary and disregarded under Article 14.

Step3: Test Each Condition for Conflict with Field 45A

Confirm the field 47A condition does not contradict the goods description or Incoterm in field 45A. Where it does, the credit is internally inconsistent and must be amended.

Step4: Test Each Condition Against Field 46A Documents

Confirm the condition can be satisfied by the document named in field 46A. If the condition requires something the field 46A document cannot show, request amendment.

Step5: Apply the Electronic-Presentation Rule Correctly

If only electronic records are allowed, ensure the electronic presentation address is in field 47A (per the SWIFT network-validated rule) and not placed in field 46A. Confirm the address is complete and unambiguous.

Step6: Reconcile Timing Conditions with Field 44C and Expiry

Where field 47A imposes a document-issue timeframe, confirm it fits within the latest shipment date and the expiry. Resolve any overlap conflict before document preparation.

Step7: Request Amendment for Any Contradiction

If field 47A cannot be reconciled with another field, request a specific amendment — deleting or rewording the conflicting condition — rather than presenting a document set that satisfies one field at the expense of another.

Step8: Final Cross-Field Verification

Before presentation, re-read field 47A alongside the fields it modifies and confirm no condition conflicts. Document the verification as an internal audit record.

Conclusion

Field 47A is the SWIFT home for conditions that do not fit elsewhere, which makes it the most common site of internal credit contradiction. A field 47A condition that conflicts with field 45A's goods or Incoterm, with a field 46A document requirement, or with the timing in field 44C or the expiry, produces a discrepancy the examining bank catches under Article 14. The electronic-presentation address rule further shows how field 47A placement matters. The resolution is to treat field 47A as a modifier of the whole message and to amend any condition that cannot coexist with the credit's other fields.

FAQ

Q1: Is field 47A mandatory?
No, field 47A is optional under SWIFT. Credits use it for conditions that do not fit other fields, but a credit may have none.

Q2: Can a field 47A condition contradict field 45A?
It can, and when it does the credit is internally inconsistent. The beneficiary should request amendment; the document set cannot satisfy both a field 45A goods description and a conflicting field 47A condition.

Q3: Where must the electronic-presentation address go?
Per the SWIFT network-validated rule, if only electronic records are allowed, the electronic address for presentation must be in field 47A, not in field 46A.

Q4: Are all field 47A conditions examined by the bank?
Only conditions linked to a stipulated document are examined. A condition that no document can fulfill is disregarded as non-documentary under Article 14, but a condition that conflicts with a stipulated document or another field is a discrepancy.

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

Q6: Can an applicant waiver cure a field 47A contradiction?
A waiver can accept non-complying documents after presentation, but the bank is not required to take them up. Amending the conflicting condition before presentation is the more reliable path.

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 that the electronic-record presentation address must be specified in field 47A, 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 inter-field contradiction patterns.