MT700 Field 46A and Its Relationship with UCP

Introduction

Field 46A of the SWIFT MT700 message is the "Documents Required" field. Optional in the message (Option A, 100×65z narrative), it nonetheless defines the entire documentary obligation of the credit. Everything the beneficiary must present — and therefore everything the examining bank must check — flows from what field 46A lists. Its relationship with UCP 600 is therefore the relationship between a SWIFT instruction list and the UCP's document-by-document examination regime.

This guide examines how field 46A connects to the UCP framework as a whole, emphasizing Article 14 (examination standard, no-conflict rule, and treatment of unstipulated documents) and Articles 18–28 (the document-type rules). It is written to show how a SWIFT narrative list becomes a UCP compliance matrix.

Failure Mode Analysis

Failure Mode 1: Listed Document Type Not Matched by the Presentation

Field 46A requires "multimodal transport documents." The beneficiary presents a single-mode bill of lading. Under Article 19 the presented document does not meet the multimodal requirement, and the presentation is discrepant.

Failure Mode 2: Condition in Field 46A Conflicts with the Governing Article

Field 46A requires a clean transport document with a specific clause that the relevant article does not require or permits differently. The examining bank reconciles the condition against the article and may find the document non-complying.

Failure Mode 3: Field 46A Requires an Impossible Document

Field 46A requires a certificate that cannot be issued for the goods or by the named entity. The credit is internally flawed, and the beneficiary cannot produce a complying document without amendment.

Failure Mode 4: Implied Document Omitted from Field 46A

Field 45A states a CIF term and field 47A references insurance, but field 46A omits the insurance document. The beneficiary must determine whether an insurance document is required and, if so, seek its inclusion; its absence is a discrepancy.

Failure Mode 5: Unstipulated Document Presented and Disregarded

The beneficiary attaches a document not listed in field 46A. Under Article 14(h) the bank disregards and returns it, which can leave the presentation short of what the credit requires if the beneficiary assumed the extra document would substitute for a listed one.

Deterministic Resolution Architecture

Step1: Build the Field 46A Document Register

List every document in field 46A with its attached conditions. This register is the credit's documentary obligation set and the basis for all preparation.

Step2: Assign Each Document to Its Governing Article

Map each listed document to its UCP article (18–28). Confirm the document type named matches the article's definition so the correct rule set applies.

Step3: Confirm the Presented Document Type Matches

Verify the document the beneficiary will present is the type field 46A requires. A sea waybill cannot satisfy a bill of lading requirement; a single-mode document cannot satisfy a multimodal requirement.

Step4: Apply the No-Conflict Rule Across Documents

Under Article 14(d), confirm the documents listed in field 46A do not carry data conflicting with each other or with fields 44B/45A. The rule spans the whole set.

Step5: Reconcile Field 46A Conditions with Field 45A

Where field 46A imposes freight, insurance, or delivery conditions, align them with the Incoterm in field 45A. Request amendment where they conflict.

Step6: Account for the Invoice Even If Unlisted

The commercial invoice is required in every credit under Article 18. Prepare it regardless of whether field 46A names it, and ensure its description corresponds with field 45A.

Step7: Resolve Impossible or Missing Documents by Amendment

If field 46A requires an unissuable document or omits one the credit implies, request an amendment specifying the correct document before presentation.

Step8: Produce a Field 46A Compliance Matrix

Before submission, list each document, its article, its conditions, and confirmation of compliance. Present only when every entry is satisfied and no unstipulated document is relied upon.

Conclusion

Field 46A is the SWIFT instruction list that activates the UCP 600 examination machinery. Article 14 frames what is examined and what is disregarded; Articles 18–28 supply the per-document rules. A field 46A that names correct document types, attaches consistent conditions, and aligns with the credit's other fields yields a clean presentation. One that lists impossible documents, omits implied ones, or contradicts field 44C or 45A is the origin of the discrepancies this guide describes.

FAQ

Q1: What is field 46A's core relationship with UCP 600?
Field 46A lists the documents required; Article 14 governs their examination and Articles 18–28 govern each document type. The field is the SWIFT trigger for the UCP document regime.

Q2: Is field 46A mandatory?
No, field 46A is optional under SWIFT. A credit may require only the invoice, but most credits populate field 46A to define the beneficiary's documentary obligations.

Q3: Does UCP require the invoice to appear in field 46A?
No. The invoice is required in every credit under Article 18 even if field 46A does not list it.

Q4: Can the bank examine a document not in field 46A?
Under Article 14(h), a document not stipulated in the credit is disregarded and returned. It does not form part of the examination.

Q5: What if field 46A requires a document that cannot be issued?
The credit is flawed. Request an amendment to replace or remove the impossible requirement rather than present a non-complying substitute.

Q6: How does field 46A relate to field 44C?
Field 46A may state a transport document date rule; field 44C states the latest shipment date. The two must agree, or the credit contains an internal contradiction requiring amendment.

Source Notes

Context only: The source dossier for this guide contained the SWIFT MT700 field 46A specification (SWIFT SR2018, Category 7), including the usage rule on specifying the ultimate date of issue of a transport document with the relative document entry, and the UCP 600 article cross-reference (Articles 14 and 19–28). 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 46A's relationship with UCP.