MT700 Field 31D: Relationship with UCP

Introduction

Field 31D of the MT700 implements, at the message level, the UCP 600 framework for expiry and presentation. Understanding the relationship between the SWIFT field and the UCP rules helps applicants, issuing banks, and confirming banks avoid discrepancies that arise when the two are treated as separate systems. This guide describes how the UCP framework shapes what 31D must contain.

Failure Modes

1. Treating 31D as SWIFT-only. A drafter who ignores the UCP basis may omit the place, breaching Article 6.
2. Disconnecting expiry place from availability. The UCP links expiry location to the 41a bank; ignoring that link creates a contradiction.
3. Confusing UCP expiry with Incoterms delivery dates. The sale contract's delivery window is not the credit expiry; the two operate under different rules.
4. Expecting UCP to supply a missing place. UCP 600 requires a place; it does not back-fill one from elsewhere in the message.
5. Relying on implied extension. The UCP framework does not imply an extension of expiry for delays outside the stated rules.

Resolution

1. Begin 31D drafting from Article 6: secure both an expiry date and a presentation place.
2. Align the 31D place with the 41a availability bank's location per the UCP link.
3. Separate the sales-contract delivery date from the credit expiry; use 44C for shipment and 31D for presentation cutoff.
4. Apply the 6!n date format so the SWIFT rule and the UCP date requirement are both met.
5. Where uncertainty about extension exists, draft explicit credit language rather than assuming UCP coverage.
6. Review 31D against 44C and 48 to confirm a workable presentation window under the UCP examination timeline.
7. Use MT707 for corrections and record the UCP basis for the change.
8. Train message preparers to read 31D as the Article 6 field, not a free-text date.

Conclusion

The relationship between 31D and UCP is direct: the SWIFT field is the carrier, and Article 6 is the rule. Reading the field through the UCP framework keeps the expiry date and place consistent with the availability structure and prevents the discrepancies that appear when the two are decoupled.

FAQ

1. What is the UCP basis for 31D? Article 6 (Expiry date and place for presentation).
2. Why must 31D include a place? Article 6 requires a place for presentation, and the SWIFT field is mandatory.
3. How does UCP tie expiry to availability? Article 6 states the expiry is at the location of the bank with which the credit is available.
4. Does UCP extend expiry for delays? Only where the credit provides for it; Article 29 does not give a general extension.
5. Is 31D format set by UCP or SWIFT? The format (6!n29x) is set by SWIFT; the content requirement is set by UCP Article 6.

Source Notes

Context only. SWIFT MT700 field 31D specification (SWIFT SR2018 Category 7): format Option D 6!n29x, Mandatory, definition of latest date and place for presentation. UCP 600 relationship: Article 6 (Expiry date and place for presentation), with Articles 14 and 29 as related framework provisions. UCP 600 text available in provided dossier; citations only, no long reproduction.