MT700 Field 31D and UCP 600 Articles

Introduction

Field 31D of the SWIFT MT700 carries the expiry date and the place for presentation of documents under a documentary credit. Although the field is a SWIFT network construct, its substance is dictated by the Uniform Customs and Practice for Documentary Credits (UCP 600). This guide maps the field to the specific UCP 600 articles that govern its content, so that a message drafter can place each 31D entry on a firm rule basis.

Failure Modes

1. Omitting the place for presentation. Article 6 requires a place; a 31D with only a date breaches the article and the mandatory field rule.
2. Stating an expiry place that conflicts with the availability bank in 41a. Article 6 ties the expiry location to the bank with which the credit is available.
3. Confusing shipment date with expiry date. Field 44C governs shipment; 31D governs presentation. Mixing the two misapplies Article 6.
4. Assuming automatic extension. Article 29 does not extend the expiry for general disruptions unless the credit explicitly says so; drafters sometimes assume a grace period that the articles do not grant.
5. Using a non-numeric or mis-ordered date. This breaches the 6!n format even though the UCP article is otherwise satisfied.

Resolution

1. Anchor 31D on Article 6 by always recording both a date and a place.
2. Set the expiry place equal to the location of the 41a availability bank, or state the beneficiary's location when the credit is freely negotiable.
3. Keep 44C (shipment) and 31D (expiry) distinct; the presentation period in field 48 bridges them under Articles 14 and 6.
4. Where extension risk exists, add explicit clause language rather than relying on Article 29, which does not provide a blanket extension.
5. Apply the YYMMDD numeric format strictly to satisfy the SWIFT field rule.
6. Cross-check the expiry against the underlying contract's delivery schedule before issuance.
7. Where amendment is needed, use MT707 and re-confirm the Article 6 basis with the applicant.
8. Maintain a checklist that pairs each 31D element with its governing UCP article.

Conclusion

Field 31D is the SWIFT expression of UCP 600 Article 6. Treating the field as a mechanical date stamp misses the article's place requirement and its link to the availability bank. Mapping 31D to Article 6, supported by Articles 14 and 29, produces credits that are internally sound and defensible on examination.

FAQ

1. Which UCP 600 article governs 31D? Article 6 (Expiry date and place for presentation).
2. Does Article 6 require both a date and a place? Yes; both elements are required, matching the mandatory SWIFT field.
3. Can the expiry be at the applicant's bank? It can be, but Article 6 couples the expiry place to the bank with which the credit is available, so consistency with 41a is required.
4. Does a strike automatically extend the expiry? No. Article 29 addresses such events only where the credit provides for extension; there is no automatic grace period.
5. Is the presentation period part of 31D? No. The presentation period is field 48; 31D holds the final expiry date those days count toward.

Source Notes

Context only. SWIFT MT700 field 31D specification (format 6!n29x, Mandatory, definition) from SWIFT SR2018 Category 7. UCP 600 relationship cited as Article 6 (Expiry date and place for presentation); Articles 14 and 29 referenced as related examination and extension provisions. UCP 600 official text available in the provided dossier; article numbers cited, long passages not reproduced.