SWIFT MT700 Field 44E and Its Relationship with UCP
Introduction
Field 44E (Port of Loading / Airport of Departure) is an optional MT700 routing field under SWIFT SR2018, Category 7, formatted as 65x narrative. SWIFT fixes the departure point the transport document must indicate; UCP 600 supplies the articles that require that point to appear and the examination standard that tests the document. The SWIFT/UCP relationship here is the familiar pattern: SWIFT provides the structured routing data, UCP provides the rule that gives it effect and enforces consistency with the rest of the credit.
Failure Modes
Failure Mode 1: Document port conflicts with 44E
Under Article 14(d), a differing port is a discrepancy.
Failure Mode 2: Document type cannot show the port
If 46A nominates a document that does not evidence a loading port, 44E is unenforceable.
Failure Mode 3: Routing inconsistency across 44-series fields
Conflict among 44A, 44E, and 44F produces an impossible route.
Failure Mode 4: MT701 divergence
A related MT701 must not conflict with the MT700; a different 44E port is a breach.
Failure Mode 5: Field omitted where required
Leaving 44E blank can leave the nominated document's port requirement undefined.
Resolution
- Draft 44E to name the exact departure port or airport.
- Match the document type in 46A to one that evidences that port.
- Reconcile 44E with 44A and 44F.
- Examine under Article 14(a) on the documents alone.
- Test the document port under Article 14(d).
- Verify no MT701 conflicts with 44E.
- Record the Article 20-28 basis for the routing.
Conclusion
The SWIFT/UCP relationship for 44E is that SWIFT states the departure point and UCP tests whether the document proves it within a coherent route. A credit holds when the field, the document type, and the adjacent routing fields agree; a presentation holds when the document shows the port without conflict.
FAQ
Why does UCP not reference 44E directly?
UCP 600 operates at the document level and does not track SWIFT field tags. The link is made through the transport-document articles and Article 14.
Is 44E needed for all shipments?
Only when the credit requires a stated loading port or departure airport. SWIFT marks it Optional.
Can an MT701 alter 44E?
No. A related MT701 must not conflict with the MT700.
What if 44E and 44F name the same place?
That can occur for short hauls, but the documents must show the loading and discharge points consistently.
Does the applicant's view control the examination?
No. Article 14 sets the bank's examination on the documents alone.
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 44E (Optional, Option E, 65x narrative). Context only.
- UCP 600 Articles 20-28 and Article 14. Context only.
- MT700 usage rules on related MT701 content. Context only.
Article 14(a) on the documents alone.
| Regulation | Article / Section | Requirement | Consequence |
|---|---|---|---|
| UCP 600 | Article 14 | Standard for Examination of Documents | Binary determination (compliant/discrepant) |
| UCP 600 | Article 20 | Bill of Lading | Binary determination (compliant/discrepant) |
← Scroll horizontally to see all columns
Quick Reference Summary
- No reference captured.
Compliance Checklist
| ✓ What Banks Expect | ✗ What Beneficiaries Often Do Wrong |
|---|---|
| Document port conflicts with 44E | Under Article 14(d), a differing port is a discrepancy. |
| Document type cannot show the port | If 46A nominates a document that does not evidence a loading port, 44E is unenforceable. |
| Routing inconsistency across 44-series fields | Conflict among 44A, 44E, and 44F produces an impossible route. |
| MT701 divergence | A related MT701 must not conflict with the MT700; a different 44E port is a breach. |
| Field omitted where required | Leaving 44E blank can leave the nominated document's port requirement undefined. |
← Scroll horizontally to see all columns
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 generates compliant SWIFT MT700 Field 44E and Its Relationship with UCP — 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