SWIFT MT700 Field 44C and Its Relationship with UCP

Introduction

Field 44C (Latest Date of Shipment) is an optional MT700 date field under SWIFT SR2018, Category 7, carrying a fixed six-digit date. SWIFT defines the field's format and presence; UCP 600 defines what the date means in practice and how a bank reacts when a presentation respects or breaches it. This division is the essence of the SWIFT/UCP relationship: SWIFT supplies the structured data, UCP supplies the rule that interprets it. Ignoring the linkage produces credits whose deadlines cannot be met or presentations examined on the wrong basis.

Failure Modes

Failure Mode 1: Date present but unenforceable

A 44C that sits after expiry or with no presentation window cannot be complied with, an internal flaw the UCP time rules expose.

Failure Mode 2: Document date conflicts with 44C

Under Article 14(d), a shipment date later than 44C is a discrepancy.

Failure Mode 3: Shipment date not evidenced

Without the right Article 20-28 document, the deadline has nothing to test against.

Failure Mode 4: MT701 divergence

A related MT701 that states a different latest shipment date conflicts with the MT700 usage rules.

Failure Mode 5: Presentation period inconsistent

A period for presentation that collapses against 44C breaches Article 33.

Resolution

1. Define 44C as a clear 6!n date when needed.
2. Tie the shipment-date evidence to the correct Article 20-28 document.
3. Keep the expiry and presentation period consistent with 44C.
4. Examine under Article 14(a) on the documents alone.
5. Test the document date under Article 14(d).
6. Verify no MT701 conflicts with 44C.
7. Document the article basis for the deadline.

Conclusion

The SWIFT/UCP relationship for 44C is that SWIFT names the deadline and UCP decides its consequences. A credit works when the deadline nests inside the credit's other time controls, and a presentation works when the document's shipment date honors it. The two layers are inseparable.

FAQ

Why does UCP not define field 44C's format?
UCP 600 works at the document and obligation level and does not specify SWIFT message formats. SWIFT defines the field; UCP defines its legal effect.

Can the applicant extend 44C unilaterally?
A change to the latest shipment date is a credit amendment governed by the amendment rules, not a unilateral act.

What if no shipment date appears on the document?
The applicable Article 20-28 rule determines evidencing; absence may itself be a discrepancy under Article 14.

Does Article 33 override 44C?
Article 33 governs presentation timing; it interacts with 44C but does not replace it. Both must be satisfied.

Is 44C needed when 44D gives a shipment period?
Not necessarily; if 44D defines the window, a separate latest date may be redundant, though consistency between them remains required.

Practical Checklist

Practical Checklist

• Confirm the field appears only where the credit structure requires it.
• Cross-check the field value against the related MT700 fields before issuance.
• Verify the cited UCP 600 article is the one that governs the field's function.
• Where the SWIFT format is fixed, do not substitute free text.
• File the source note (SWIFT SR2018 + UCP 600) with the credit record.

Source Notes

• SWIFT SR2018, Category 7, MT700 field 44C (Optional, 6!n, latest date of shipment). Context only.
• UCP 600 Article 33, Article 14, and Articles 20-28. Context only.
• MT700 usage rules on related MT701 content. Context only.