SWIFT

SWIFT MT700 Field 44D: Shipment Period — Complete Field Guide for Documentary Credit Messages

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

Introduction

SWIFT Field 44D (Shipment Period / Last Date of Shipment) specifies the time window within which the goods must be shipped under a documentary credit. The field is one of the most commercially significant fields in the MT700 — it defines the deadline by which the beneficiary must ship the goods to comply with the credit. An error in Field 44D — an ambiguous date, a conflict with the expiry, or a period that cannot be met — has direct commercial consequences: the beneficiary misses the shipment window, the credit expires unused, or the transport document shows a shipment date outside the permitted period.

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 and UCP 600.

Failure Mode Analysis

FM1: Field 44D Specifies "AT LATEST" Without a Date

If Field 44D contains only the words "AT LATEST" without an actual date, the shipment period is undefined. The bank cannot determine the latest shipment date from the credit. The receiving bank must request clarification from the issuing bank.

FM2: Shipment Period Is in the Past at Issuance

If Field 44D specifies a shipment period that has already expired before the credit is issued (e.g., "SHIPMENT BY 2023-12-31" when the credit is issued in January 2024), the credit is unusable. The beneficiary cannot ship within a period that has already passed.

FM3: Shipment Period Exceeds the Expiry Date

If Field 44D specifies a latest shipment date of April 15 but the credit expiry (Field 31D) is March 30, the shipment period exceeds the expiry. The beneficiary cannot ship after the credit expires. The receiving bank should flag this conflict.

FM4: Relative Period References a Non-Existent Event

If Field 44D states "WITHIN 30 DAYS AFTER B/L DATE" but the credit does not specify a B/L date or the B/L is not required, the relative period is unanchored. The beneficiary cannot calculate the shipment deadline without a reference date.

FM5: Field 44D Contains Multiple Inconsistent Periods

If Field 44D states "SHIPMENT FROM JANUARY TO MARCH" in line 1 and "AT LATEST APRIL 30" in line 2, the two periods are inconsistent. The bank must determine which period controls — or request clarification from the issuing bank.

Deterministic Resolution Architecture

Step 1: Extract Field 44D Content

Read the full text of Field 44D from the MT700. If the field is absent, note that the default shipment period is the credit's expiry date under Article 6.

Step 2: Parse the Date(s)

Identify all dates in Field 44D. Convert them to a standard format (YYYYMMDD) for comparison. If the field contains relative periods (e.g., "30 DAYS AFTER B/L DATE"), note the reference event and calculate the deadline.

Step 3: Compare Against the Expiry Date

Confirm that the latest shipment date in Field 44D does not exceed the credit's expiry date (Field 31D). If it does, the credit has a conflict that must be resolved before advising.

Step 4: Verify the Shipment Period Is in the Future

At the time of credit issuance, confirm that the shipment period has not already expired. If it has, the credit is unusable and must be corrected.

Step 5: Check for Internal Consistency

If Field 44D contains multiple lines, verify that all lines are consistent. If the lines specify different periods, the bank must determine which period controls — or request clarification.

Step 6: Match Against Transport Documents

When the beneficiary presents a bill of lading or other transport document, compare the shipment date against Field 44D. The shipment date must fall within the specified period.

Step 7: If Ambiguous, Request Clarification

If Field 44D contains ambiguous or conflicting data, the advising bank should contact the issuing bank for clarification before advising the credit. The beneficiary should not assume a shipment period that is not clearly stated.

Conclusion

Field 44D is the commercial heart of the MT700 — it defines when the beneficiary must ship the goods. The field accepts free-format text, but the content must be clear, unambiguous, and internally consistent. The shipment period must not exceed the credit's expiry date, must be in the future at issuance, and must be anchored to a calculable reference if relative. Errors in Field 44D have direct commercial consequences: missed shipment windows, unusable credits, and documentary discrepancies.

FAQ

Q1: Can Field 44D be amended after issuance?

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

Q2: What if Field 44D specifies "AS PER UCP 600"?

"AS PER UCP 600" is not a shipment period — it is a reference to the rules. Field 44D must specify an actual date or period. The receiving bank should request clarification from the issuing bank.

Q3: Does Field 44D apply to standby letters of credit?

Field 44D is defined for documentary credits. For standby letters of credit (subject to ISP98 or URDG 758), the shipment period concept may not apply. The field's applicability depends on the credit type.

Q4: Can Field 44D specify multiple shipment windows?

Yes, if the credit allows partial shipments. For example, "SHIPMENT IN MARCH AND APRIL 2024" specifies two months. Each shipment must fall within the stated window.

Q5: What if Field 44D is absent and the credit allows partial shipments?

If Field 44D is absent, the shipment period defaults to the credit's expiry date. For partial shipments, each shipment must occur before the expiry date.

Source Notes

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

Did You Know?

Article 20 requires the bill of lading to show the date of shipment.

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 6Availability, Expiry Date and Place for PresentationBinary 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