SWIFT

SWIFT MT700 Field 44D: Format Requirements and Validation for Shipment Period

📅 2026-07-13 6 min read UCP 600 / ISBP 745

Introduction

SWIFT Field 44D (Shipment Period / Last Date of Shipment) in the MT700 documentary credit message specifies the time window within which the goods must be shipped. The field's format requirements determine how the shipment period is expressed, and validation errors in this field cause delays in credit issuance or discrepancies in documentary presentations. This guide defines the format requirements, validation rules, and practical compliance standards for Field 44D.

The sources available for this guide include a contextual reference from Trade Finance Global's analysis of MT707 amendment messages. No direct article text was extracted. The authority is the SWIFT MT Standards for Category 7 — Documentary Credits and Guarantees and UCP 600.

Failure Mode Analysis

FM1: Field 44D Contains an Ambiguous Date Range

If Field 44D states "SHIPMENT IN FEBRUARY" without specifying a year, the shipment period is ambiguous. The examining bank may interpret the period as the February immediately following the credit issuance. An ambiguous period creates uncertainty about compliance.

FM2: Field 44D Specifies a Date That Conflicts with the Expiry Date

If Field 44D specifies a latest shipment date of March 15 but the credit expiry date (Field 31D) is March 10, the shipment period conflicts with the expiry — shipment after expiry is impossible. The receiving bank should flag this conflict before advising the credit.

FM3: Field 44D Contains Non-Standard Date Formats

SWIFT accepts free-format text in Field 44D, but the receiving bank must be able to interpret the date format. Non-standard formats (e.g., "SHIPMENT BY MID-MARCH" or "WITHIN 2 WEEKS OF B/L DATE") create ambiguity. Standard formats (e.g., 20240101-20240228) reduce ambiguity.

FM4: Field 44D Is Empty When a Shipment Period Is Required

If the credit requires a shipment period but Field 44D is empty, the credit may still be valid — the shipment period defaults to the credit's expiry date under UCP 600 Art 6. However, this default may not match the issuing bank's intent.

FM5: Field 44D Contains a Shipment Period That Cannot Be Met

If Field 44D specifies a shipment period that has already expired at the time of credit issuance, the beneficiary cannot comply. The credit is effectively unusable from the moment it is issued.

Deterministic Resolution Architecture

Step 1: Read Field 44D Content

Extract the full text of Field 44D from the MT700 message. If the field is absent, the credit has no specific shipment period — the default is the expiry date under Article 6.

Step 2: Parse the Date Format

Identify the date format used in Field 44D. Common formats include:
- Explicit date range: BETWEEN 20240101 AND 20240228
- Latest date: AT LATEST 20240315
- Relative period: WITHIN 30 DAYS AFTER B/L DATE

If the format is non-standard, interpret the intent and confirm with the issuing bank if necessary.

Step 3: Verify the Shipment Period Against the Expiry Date

Confirm that the latest shipment date in Field 44D does not exceed the credit's expiry date (Field 31D). If the shipment period extends beyond the expiry, the credit has a logical inconsistency that must be corrected.

Step 4: Confirm the Shipment Period Is in the Future

Verify that the shipment period has not already expired at the time of credit issuance. If the period has expired, the credit is unusable and must be corrected before advising.

Step 5: Match the Shipment Period Against the Transport Document

When the beneficiary presents a bill of lading, compare the shipment date on the bill of lading against the period in Field 44D. The shipment date must fall within the specified period.

Step 6: Check for Consistency Across All Messages

If the credit is issued in multiple MT700 messages (Field 27 indicates multi-part), verify that Field 44D is consistent across all messages. A shipment period that appears in one message but not in the other creates ambiguity.

Step 7: If Non-Compliant, Request Amendment

If Field 44D contains an error, conflict, or ambiguity, request an MT707 amendment from the issuing bank to correct the shipment period. The amendment must specify the corrected period.

Conclusion

Field 44D defines the shipment period for a documentary credit. The field accepts free-format text, but the content must be clear, unambiguous, and consistent with the credit's expiry date. Validation requires parsing the date format, verifying it against the expiry date, and confirming it against the transport document's shipment date. Errors in Field 44D — ambiguity, conflicts, or expired periods — delay credit issuance and create discrepancies in documentary presentations.

FAQ

Q1: Is Field 44D mandatory in MT700?

No, Field 44D is optional. If the field is absent, the shipment period defaults to the credit's expiry date under UCP 600 Article 6.

Q2: Can Field 44D specify a relative period (e.g., "within 30 days of B/L date")?

Yes. Field 44D accepts free-format text. A relative period is acceptable as long as it is clear and unambiguous. The beneficiary must calculate the actual date range from the B/L date.

Q3: What happens if Field 44D conflicts with the expiry date?

The credit has a logical inconsistency. The receiving bank should contact the issuing bank for clarification or an MT707 amendment before advising the credit.

Q4: Can the shipment period be extended after issuance?

Yes, through an MT707 amendment. The amendment updates Field 44D with the new shipment period. The beneficiary must accept the amendment before it takes effect.

Q5: Does Field 44D apply to both air and sea shipments?

Field 44D applies to all shipment types — sea, air, road, rail, or multimodal. The field defines the shipment period regardless of the transport mode.

Q6: What date format does SWIFT recommend for Field 44D?

SWIFT accepts free-format text, but the recommended format is YYYYMMDD for dates (e.g., 20240101) and BETWEEN YYYYMMDD AND YYYYMMDD for date ranges. Standard formats reduce ambiguity.

Source Notes

Context only — no direct article text was extracted from these sources during research:

Did You Know?

Article 14(c) states that if a credit contains a condition without stipulating the document to indicate compliance, the bank disregards the condition.

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 6Availability, Expiry Date and Place for PresentationBinary determination (compliant/discrepant)
UCP 600Article 14Standard for Examination of DocumentsBinary determination (compliant/discrepant)
UCP 600Article 20Bill of LadingBinary determination (compliant/discrepant)

← Scroll horizontally to see all columns

Quick Reference Summary

  • No reference captured.

Compliance Checklist

0 of 5 completed

Get the Full LC Compliance Checklist

15-point pre-submission checklist covering UCP 600, ISBP 745, and SWIFT MT700 fields. Free PDF download.

No spam. Unsubscribe anytime.

DraftLC Compliance Engine

DraftLC generates compliant SWIFT MT700 Field 44D — so you never face this failure mode.

DraftLC drafts your LC with UCP 600-compliant terms and flags conflicts during drafting — before documents reach the bank.

No credit card required · See how DraftLC drafts compliant credits