MT700 Field 47A — Common Errors and Discrepancies

Introduction

SWIFT MT700 Field 47A is the "Additional Conditions" field — an optional narrative block (Option A, 100×65z) that carries conditions not accommodated elsewhere in the credit message. Practitioners treat it as a harmless appendix, a place to dump leftover instructions. That illusion collapses at document examination. Field 47A is the single most prolific source of non-documentary conditions, ambiguous mandates, and internal contradictions in the documentary credit lifecycle. When an issuing bank drafts Field 47A carelessly, the condition either gets disregarded entirely under UCP 600 Article 14(h) or, worse, creates a conflict that no document set can satisfy. This guide isolates the three most destructive error patterns in Field 47A, traces each to its regulatory root in UCP 600 and ISBP 745, and provides a deterministic resolution architecture that eliminates the discrepancies before they reach the examining bank.

Failure Mode Analysis

Failure Mode 1: Non-Documentary Conditions That Silently Disappear

The most common Field 47A error is drafting a condition that names no document. The issuing bank includes language such as "Goods must be packed in wooden crates" or "Shipment must be effected by vessel not exceeding 20 years of age" without stipulating which document must evidence compliance.

The failure mechanism: Under Article 14(h), the examining bank disregards the condition. The beneficiary's document set passes examination. But the applicant — who believed the condition was operative — discovers post-payment that the goods arrived in plastic wrapping or on a 35-year-old vessel. The applicant claims the issuing bank failed to examine properly. The issuing bank responds that the condition was non-documentary and properly disregarded. The applicant sues. The court applies Article 14(h) and dismisses the claim.

The systemic mutation: The error originates at credit issuance but manifests at document examination or post-payment. The applicant and issuing bank share the illusion that Field 47A conditions are self-executing. They are not. Under UCP 600, a condition without a documentary anchor is a nullity.

Failure Mode 2: Ambiguous Conditions That Produce Interpretation Disputes

Field 47A conditions frequently use vague language that admits multiple interpretations. Examples include "Documents must be issued by a first-class bank," "Insurance must cover all risks," or "Certificate of origin must be issued by competent authority."

The failure mechanism: The beneficiary interprets the condition in the most favorable light. The examining bank interprets it in the most restrictive light. Under Article 14(d), data in a document must not conflict with data in the credit — but when the credit's data is ambiguous, the no-conflict test becomes indeterminate. The examining bank raises a discrepancy. The beneficiary disputes it. The dispute enters ICC DOCDEX or litigation, consuming months and generating legal costs that dwarf the transaction value.

The compounding factor: ISBP 745 paragraph A1 addresses abbreviations but does not address ambiguous substantive conditions. The phrase "first-class bank" has no ICC-defined meaning. The phrase "all risks" conflicts with the Institute Cargo Clauses taxonomy (A, B, C). The phrase "competent authority" depends on the jurisdiction of the issuing entity. Each ambiguity is a seed for discrepancy disputes that could have been eliminated by precise drafting in Field 47A.

Failure Mode 3: Conditions Requiring Applicant-Generated Documents

Field 47A is the field through which applicants insert document requirements that only they can fulfill. Common examples: "Signed letter from applicant confirming shipment," "Applicant's authorization for partial shipment," or "Buyer's inspection certificate countersigned by applicant."

The failure mechanism: The beneficiary cannot produce a document signed by the applicant. The applicant has no contractual obligation under the credit to provide documents — the credit is the issuing bank's undertaking, not the applicant's. ISBP 745 Preliminary Consideration (vii) warns against this practice, but Field 47A is the mechanism through which it enters the credit. The beneficiary faces a binary choice: request an amendment (which may not arrive before expiry) or present without the document (which triggers a discrepancy under Article 14(d) if the condition is deemed to require a document, or is disregarded under Article 14(h) if it is non-documentary).

The paradox: If the Field 47A condition names a document (e.g., "applicant's certificate"), Article 14(h) does not apply — the condition stipulates a document. But the beneficiary cannot produce it. If the condition does not name a document (e.g., "applicant must approve shipment"), Article 14(h) applies and the condition is disregarded — but the applicant expected the condition to be enforced. Either outcome produces a failure: discrepancy + refused documents, or disregarded condition + disappointed applicant.

Deterministic Resolution Architecture

Step 1: Audit Every Field 47A Condition for Documentary Anchoring

Before the credit is issued, the issuing bank must verify that every condition in Field 47A either (a) names a specific document to evidence compliance, or (b) is intentionally non-documentary and the applicant understands it will be disregarded under Article 14(h). Any condition that falls into neither category must be redrafted.

Step 2: Replace Ambiguous Language with Precise Documentary Requirements

Audit Field 47A for vague terms: "first-class," "all risks," "competent authority," "satisfactory," "acceptable." Replace each with a concrete documentary specification. "Insurance must cover Institute Cargo Clauses (A)" replaces "Insurance must cover all risks." "Certificate of origin issued by the chamber of commerce of the exporting country" replaces "Certificate of origin issued by competent authority."

Step 3: Eliminate Applicant-Generated Document Requirements

Remove any Field 47A condition that requires a document to be issued, signed, or countersigned by the applicant. If the condition is commercially necessary, move it to the underlying sale contract — not the credit. The credit deals with documents, not with performance obligations between buyer and seller (Article 5).

Step 4: Cross-Check Field 47A Against All Other MT700 Fields

Compare every Field 47A condition against fields 44A through 46A (description of goods, documents required), field 45A (goods description), field 49 (confirmation instructions), and field 58A (nominated bank). A condition in Field 47A that contradicts any of these fields produces a discrepancy under Article 14(d). Resolve the contradiction by amendment before issuance.

Step 5: Verify Field 47A Character Encoding and Length

Field 47A Option A allows 100 lines of 65 characters. Complex conditions may be truncated at the SWIFT boundary. Truncation produces a data-mutation failure — the condition as transmitted differs from the condition as intended. Verify that every condition fits within the field constraints. If it does not, split the condition across Field 47A and Field 79 (Narrative), or restructure the condition to use fewer characters.

Step 6: Test Each Condition Against ISBP 745 Paragraph A26

For every non-documentary condition in Field 47A, verify that no stipulated document in the credit contains data that conflicts with the condition. A packing instruction in Field 47A ("wooden crates") that conflicts with a packing declaration on the bill of lading ("flexible intermediate bulk containers") produces a discrepancy under Article 14(d) via the ISBP 745 A26 no-conflict constraint.

Step 7: Issue the Credit Only After Full Field 47A Reconciliation

The credit should not be transmitted until every Field 47A condition has been validated against Steps 1 through 6. Treat Field 47A as a source of documentary obligations, not as a free-text annotation. The examining bank will treat it with the same rigor as Field 46A.

Conclusion

Field 47A is not a narrative supplement — it is a source of documentary obligations that the examining bank evaluates under the same rules as every other field. The three failure modes — non-documentary conditions that silently disappear, ambiguous conditions that produce interpretation disputes, and conditions requiring applicant-generated documents — are all deterministic consequences of treating Field 47A as informal commentary rather than as a operative component of the credit. The resolution architecture is equally deterministic: audit every condition for documentary anchoring, replace ambiguity with precision, eliminate applicant-generated requirements, cross-check against all other fields, verify character encoding, and test against ISBP 745 A26 before transmission. The issuing bank that follows these steps eliminates the discrepancies at their source rather than discovering them at examination.

FAQ

Q1: What happens if Field 47A contains a condition but no document is named to evidence compliance?

Under UCP 600 Article 14(h), banks disregard the condition entirely. The condition is treated as not stated. ISBP 745 paragraph A26 elaborates: the condition need not be evidenced on any stipulated document, but no stipulated document may contain data conflicting with it. The practical effect is that the condition is unenforceable through the credit mechanism — it exists only as a potential source of conflict with other documents.

Q2: Can a beneficiary ignore a Field 47A condition that appears ambiguous?

A beneficiary should not unilaterally ignore any Field 47A condition. The correct response to ambiguity is to request clarification or amendment before the expiry date. If the beneficiary presents without addressing an ambiguous condition, the examining bank may raise a discrepancy under Article 14(d) — the beneficiary's interpretation may conflict with the credit's data. ISBP 745 does not provide a safe harbor for "reasonable interpretation" of ambiguous conditions.

Q3: Is the issuing bank liable if Field 47A contains a condition that contradicts another field?

Yes. Under UCP 600 Article 14(a), the issuing bank must examine documents to determine whether they constitute a complying presentation. If Field 47A contains a condition that contradicts field 46A or field 45A, no document set can satisfy both, and the issuing bank has created an internally inconsistent credit. The issuing bank bears the risk of ambiguity in the credit terms (ISBP 745 Preliminary Consideration v: "The applicant bears the risk of any ambiguity in its instructions to issue or amend a credit").

Q4: Can Field 47A require a document from the applicant?

ISBP 745 Preliminary Consideration (vii) states that a credit "should not require presentation of a document that is to be issued, signed or countersigned by the applicant." If a credit nonetheless includes such a requirement, the beneficiary should "consider the appropriateness of such a requirement and determine its ability to comply with it, or seek a suitable amendment." Field 47A is the primary vehicle for such requirements, and they are strongly discouraged under international standard banking practice.

Q5: Does Field 47A override Field 46A if the two conflict?

No. Under UCP 600 Article 14(d), data in a document must not conflict with data in any other stipulated document or the credit. If Field 47A and Field 46A impose contradictory requirements, the document set cannot comply with both, and the examining bank will raise a discrepancy. Neither field overrides the other — both must be reconciled before issuance. The examining bank evaluates the credit as a single, internally consistent instrument.