MT700 Field 44F and Its Relationship with UCP 600

Introduction

SWIFT MT700 field 44F records the port of discharge or airport of destination that the transport document must show. The field is optional in the MT700 message, but when it is populated it sets a destination constraint that the transport document must satisfy on its face. Field 44F sits inside a cluster of place-and-time fields — 44B (place of final destination / for transportation to / place of delivery), 44C (latest date of shipment), and 44D (shipment period) — that together define where and when the goods must move.

This guide examines how field 44F interacts with UCP 600 Articles 20 through 28, which govern transport documents and the port of discharge or destination that such documents must evidence. It covers where a mismatch between field 44F and the presented transport document produces a discrepancy, and how the examining bank applies the Article 14 standard of examination to destination data.

Failure Mode Analysis

Failure Mode 1: Transport Document Shows a Different Port of Discharge Than Field 44F

The credit's field 44F names "Port of Rotterdam" as the port of discharge. The presented bill of lading shows "Port of Antwerp" as the port of discharge. Under Article 20 and Article 14(d), the destination data conflicts with the credit, producing a discrepancy even if every other element of the bill complies.

Failure Mode 2: Airport of Destination Mismatch on Air Transport Documents

For air transport governed by Article 23, field 44F may name an airport of destination such as "Frankfurt Airport (FRA)." The air waybill shows "Munich Airport (MUC)." Because the destination is a key routing element, the conflict is a discrepancy under Article 23 read with Article 14(a).

Failure Mode 3: Field 44F Conflicts with Field 44B (Final Destination / Place of Delivery)

Field 44F specifies the port of discharge, while field 44B may specify the final destination or place of delivery inland. If field 44F names a seaport and field 44B names the same seaport as a "place of delivery," the examining bank must reconcile whether the credit intends discharge and delivery at the same point. Inconsistent pairings create ambiguity that surfaces during Article 14 examination.

Failure Mode 4: Multimodal Document Destination Not Evidenced

Where the credit contemplates multimodal transport under Article 19 and field 44F names a port of discharge, the multimodal transport document must show the place of receipt, the port or place of loading, the port or place of discharge, and the place of final destination. If the document omits the field 44F destination, it fails to evidence the required routing.

Failure Mode 5: Field 44F Populated but No Destination on the Transport Document

A credit populates field 44F but the beneficiary presents a transport document that omits any port of discharge or destination clause. The examining bank cannot confirm the document satisfies the routing requirement, and the presentation is discrepant under the relevant transport article and Article 14(a).

Deterministic Resolution Architecture

Step 1: Extract Field 44F and the Full Routing Cluster

Before preparing the transport document, extract field 44F (port of discharge / airport of destination) together with fields 44B, 44C, and 44D. Treat the cluster as a single routing-and-timing specification rather than isolated fields.

Step 2: Identify the Governing Transport Article

Determine which transport document the credit requires and which UCP 600 article governs it — Article 20 (bill of lading), 21 (sea waybill), 22 (charter party), 23 (air), 24 (road/rail/inland), 25 (courier/post), or 19 (multimodal). Each article defines which destination elements the document must show.

Step 3: Match the Transport Document Destination to Field 44F

Confirm the transport document evidences the exact port of discharge or airport of destination named in field 44F. The spelling and code must correspond; a differently named port is a conflict under Article 14(d).

Step 4: Reconcile Field 44F with Field 44B

Verify that field 44F (discharge/destination) and field 44B (final destination / place of delivery) are internally consistent. If 44B extends beyond 44F, the transport document should evidence the full intended movement; if they conflict, request amendment before presentation.

Step 5: Confirm the Document Type Supports the Routing

Some transport documents do not evidence a port of discharge in the same way as a bill of lading. Confirm the document type required by the credit can evidence the field 44F destination; if not, the credit terms themselves are inconsistent and should be amended.

Step 6: Cross-Check the Destination Against Other Documents

The destination on the transport document must not conflict with the invoice, insurance document, or certificate of origin under Article 14(d). A certificate of origin showing a different destination country than the field 44F port signals a conflict.

Step 7: Validate Before Presentation

Build a routing checklist: field 44F extracted, governing article identified, transport document destination matched, field 44B reconciled, no cross-document conflict. Present only after each item is confirmed.

Step 8: Amend Field 44F or the Credit if Correction Is Impossible at the Document Level

If the transport document genuinely cannot evidence the field 44F destination (for example, the shipment leg terminates elsewhere), request an amendment to field 44F rather than attempting to cure the conflict through a waiver.

Conclusion

Field 44F is the SWIFT carrier of the credit's destination requirement. Although optional, once populated it binds the transport document to show a matching port of discharge or airport of destination under UCP 600 Articles 20 through 28. The examining bank applies the Article 14 standard, and any conflict between the field 44F destination and the transport document's destination is a discrepancy. Treating the routing cluster — 44F, 44B, 44C, 44D — as one coordinated specification, and matching the transport document's destination to field 44F before presentation, removes the most common destination-based discrepancies.

FAQ

Q1: Is field 44F mandatory in an MT700 credit?
No. Field 44F is optional under the SWIFT MT700 specification. When left blank, the credit imposes no specific port of discharge or destination requirement through this field, though other fields or documents may still set routing constraints.

Q2: Can the transport document show a destination different from field 44F if the goods still reach the buyer?
No. UCP 600 examination is on the document's face, not the commercial outcome. A destination that conflicts with field 44F is a discrepancy under Article 14(d) regardless of the actual delivery.

Q3: How does field 44F differ from field 44B?
Field 44F specifies the port of discharge or airport of destination to be indicated on the transport document. Field 44B specifies the place of final destination or place of delivery, which may be an inland point beyond the discharge port. The two serve different points in the routing.

Q4: Which UCP 600 article applies to field 44F?
Field 44F itself is a SWIFT field, not a UCP article. Its destination requirement is enforced through the transport-document articles — Articles 19 through 28 — read together with Article 14, which governs the standard of examination and the no-conflict rule.

Q5: What if the bill of lading shows the correct port of discharge but the certificate of origin names a different country?
The certificate of origin's destination country must not conflict with the credit's routing under Article 14(d). A mismatch triggers a discrepancy even when the transport document matches field 44F. Reconcile all destination references across documents before presentation.

Q6: Can an applicant waiver cure a field 44F destination mismatch?
A discrepancy can be waived by the applicant after presentation, but the examining bank is not obliged to take up non-complying documents. The cleaner path is to amend field 44F or present a transport document that matches the credit.

Source Notes

Context only: The source dossier for this guide contained the SWIFT MT700 field 44F specification (SWIFT SR2018, Category 7) and the UCP 600 article cross-reference for field 44F (Articles 20–28, port of discharge / destination). No text from those sources has been reproduced. This guide was composed from first principles using the SWIFT MT700 field specification, the UCP 600 article framework, and independent analysis of field 44F's documentary implications.