SWIFT MT700 Field 44C vs. Field 31C: The Two Dates That Determine Documentary Credit Survival

Introduction: One Credit, Two Clocks, Binary Outcomes

Every documentary credit operates on two independent temporal constraints: the latest shipment date (SWIFT MT700 Field 44C) and the expiry date (Field 31C). These dates serve distinct regulatory functions, trigger different compliance pathways, and mutate under different conditions. The structural illusion is that both dates simply mark deadlines. The real failure mode is that they are governed by separate UCP 600 articles, respond differently to banking-day disruptions, and produce asymmetric consequences when violated. A beneficiary who conflates them risks losing the entire credit — not because of a single error, but because the two clocks tick on independent tracks.

Failure Mode Analysis

Failure Mode 1: Expiry Date Extension Misapplication

A beneficiary presents documents on the first banking day after the stated expiry date, believing the extension under Article 29(a) applies. However, the latest shipment date (Field 44C) has already passed, and the transport document evidences shipment after that date. The expiry extension does not retroactively validate a late shipment. The bank rejects under Article 14(c). The root cause is the false equivalence between the two dates — one extends, the other is immutable.

Failure Mode 2: Shipment Date Satisfied, Presentation Deadline Violated

The goods ship on time (within Field 44C), but the beneficiary fails to present documents within 21 calendar days of shipment or before the expiry date, whichever is earlier (Article 14(c)). The transport document is clean, but the presentation arrives after Field 31C. The bank rejects. The beneficiary conflates "shipped on time" with "presented on time." These are separate compliance obligations under separate articles.

Failure Mode 3: Non-Banking Day Collision Without Extension Awareness

Field 31C falls on a Saturday. The beneficiary believes the presentation deadline is the next Monday. However, the credit was issued by a bank in a jurisdiction where Saturday is a banking day but Sunday is not. The expiry date does not extend because the bank was open on the stated date. The beneficiary presents on Monday and is rejected. Article 29(a) only triggers when the bank is closed on the expiry date — the definition of "closed" is jurisdiction-dependent and must be verified against the issuing bank's calendar.

Deterministic Resolution Architecture

1. Isolate the two dates at issuance. Verify Field 31C (Expiry Date) and Field 44C (Latest Shipment Date) are populated. If Field 44C is blank, the latest shipment date defaults to the expiry date per standard SWIFT practice. Confirm this assumption with the issuing bank.

2. Establish the temporal buffer. Calculate 44C + 21 calendar days (Article 14(c)). If this sum exceeds Field 31C, the effective presentation deadline is Field 31C. If it does not, the 21-day window governs. The beneficiary must comply with whichever is earlier.

3. Verify the issuing bank's calendar. Determine which days the issuing bank treats as non-banking days. Article 29(a) only extends the expiry date when the bank is closed. A bank open on Saturday does not trigger the extension. Request the bank's holiday calendar if the expiry date falls on or near a weekend.

4. Decouple shipment compliance from presentation compliance. Treat Field 44C and Field 31C as independent constraints. Satisfying one does not satisfy the other. Document both compliance pathways separately in the presentation checklist.

5. Apply the Article 29(c) truncation rule. When the expiry date extends under Article 29(a), verify that the latest shipment date has not already passed. The extension applies only to presentation, not to shipment. If the extension pushes the presentation date past the shipment date, the transport document must already evidence a shipment date within Field 44C.

6. Map the 21-day calculation precisely. Count 21 calendar days from the shipment date (on-board notation date per ISBP 745). Do not count from the date of document issuance or the date of loading. The on-board notation date is the shipment date.

7. Trigger the Article 16 notice pathway. If a presentation is rejected due to a Field 44C or Field 31C violation, the bank must issue a single notice under Article 16(c) stating each discrepancy. Verify the notice is issued by telecommunication or other expeditious means no later than the close of the fifth banking day following the day of presentation (Article 16(d)). Failure to issue the notice precludes the bank from claiming non-compliance (Article 16(f)).

Conclusion: Two Clocks, One Deterministic Path

Field 44C and Field 31C are governed by separate UCP 600 articles, respond differently to banking-day disruptions, and produce asymmetric consequences when violated. The latest shipment date is immutable under Article 29(c). The expiry date extends under Article 29(a) when the bank is closed. The 21-day presentation window under Article 14(c) creates a third temporal constraint that binds both dates. The only deterministic path forward is to isolate each date, verify the issuing bank's calendar, and apply each regulatory provision independently. Conflating the two dates is not a minor procedural error — it is a systemic failure mode that voids the credit.

FAQ

Q1: Can the expiry date (Field 31C) be earlier than the latest shipment date (Field 44C)?
A: No. UCP 600 establishes that the latest shipment date must not be later than the expiry date. If a credit appears to contain this inconsistency, request an amendment from the issuing bank before presentation. The credit as issued may be non-compliant from inception.

Q2: If the expiry date falls on a Saturday and the bank is closed, does the latest shipment date also extend?
A: No. UCP 600 Article 29(c) explicitly states that the latest date for shipment will not be extended as a result of sub-article 29(a). Only the expiry date for presentation extends to the first following banking day. The shipment date remains fixed.

Q3: What is the shipment date for purposes of Article 14(c) — the date of the transport document or the on-board notation date?
A: Per ISBP 745, the shipment date is the date of the on-board notation when the transport document bears a separate dated on-board notation. When the on-board notation is pre-printed on the transport document, the document date serves as the shipment date. The on-board notation date governs the 21-day calculation.

Q4: If I ship goods on the last day of Field 44C and present documents 22 days later, but before Field 31C, is the presentation compliant?
A: No. Article 14(c) requires presentation not later than 21 calendar days after the date of shipment, but in any event not later than the expiry date. Twenty-two days after shipment violates the 21-day rule, regardless of whether the expiry date has passed. Both constraints must be satisfied simultaneously.

Q5: Does Article 29(a) extend the expiry date if the bank is open but its systems are down?
A: No. Article 29(a) triggers only when the bank is closed for reasons other than those referred to in Article 36 (force majeure). A systems outage does not constitute the bank being "closed" for purposes of the expiry date extension. The beneficiary must present within the stated deadline.