MT700 Field 44A: Best Practices for Accurate Completion

Introduction

Field 44A (Place of Taking in Charge / Place of Receipt) in the SWIFT MT700 message is optional under SR2018, Category 7. Many practitioners assume its optionality means it is inconsequential — a field to be filled only when convenient, with whatever data the back office happens to have. This illusion produces a deterministic failure mode: the place named in 44A cannot coexist with the routing data, transport document requirements, or trade terms stated elsewhere in the credit. The result is a discrepancy flagged under Article 14(d) of UCP 600, a refusal notice under Article 16, and a presentation that fails on first submission. The fix is not complexity; it is a binary compliance check applied before the credit is issued or the documents are presented.

Failure Mode Analysis

Failure Mode 1: 44A Names a Port That Does Not Exist in the Credit's Routing Structure

The credit specifies 44E (Port of Loading) as "Rotterdam" and 44A as "Amsterdam Inland Terminal." The transport document shows the place of receipt as "Amsterdam" and the port of loading as "Rotterdam." The routing is internally coherent, but the credit's 44A entry has created an expectation that the transport document will evidence Amsterdam as the taking-in-charge point. If the transport document omits Amsterdam, the presentation is discrepant under Article 14(d). If the transport document states a different inland point, the discrepancy compounds.

Failure Mode 2: 44A Omitted Where the Nominated Document Type Requires a Stated Receipt Place

The credit calls for a multimodal transport document under Article 19 but leaves 44A blank. The applicant's underlying contract specifies FCA (Free Carrier) terms at a named inland point. The beneficiary presents a multimodal transport document showing a place of taking in charge that differs from the FCA point. The examining bank must determine whether the blank 44A constitutes an omission that permits any receipt place, or whether the credit's other terms impliedly restrict the receipt location. The ambiguity is systemic — it arises from the credit's own drafting, not from the beneficiary's presentation.

Failure Mode 3: 44A Restated with Conflicting Data in a Related MT701

The MT700 states 44A as "Hamburg CY." A related MT701, sent to cover additional goods descriptions, restates 44A as "Hamburg CFS" (Container Freight Station). The MT700 usage rules prohibit a related MT701 from conflicting with information present in the MT700. The two entries describe materially different locations with different implications for the transport document's on-board notation. The discrepancy is binary: either the MT700 or the MT701 is incorrect, and the presentation cannot compile against both.

Deterministic Resolution Architecture

1. Before issuing or amending the credit, read field 44A together with 44E (Port of Loading), 44F (Port of Discharge), 44B (Place of Final Destination), and 44C (Latest Shipment Date). Confirm that the place named in 44A is geographically and logically consistent with the routing structure.

2. Cross-reference 44A against the transport document type nominated in 46A. If the credit requires a bill of lading under Article 20, confirm that 44A names a place that supports the port of loading stated in 44E. If the credit requires a multimodal transport document under Article 19, confirm that 44A names a place that is distinct from 44E where the transport chain requires it.

3. Compare 44A against the delivery term and named place in 45A (Goods Description). If 45A states an FCA or CPT term with a named place, confirm that 44A is consistent with that place or that the credit explicitly permits variation.

4. Verify the completeness of the 44-series fields. Each field that is populated must be internally consistent. If 44A is populated, confirm that 44E, 44F, and 44B do not create a routing that the transport document cannot evidence.

5. Where a related MT701 is used, confirm that 44A is not restated with a conflicting narrative. If the MT701 contains 44A data, the data must be identical to the MT700 entry or the credit must explicitly permit variation.

6. Apply Article 14(d) to the final credit text. Read the 44A narrative in context with 44E, 44F, 44B, 45A, and 46A. If any pair produces a conflict that the transport document cannot resolve, the credit must be amended before issuance.

7. Before presenting documents, confirm that the transport document's place of receipt or taking in charge matches the 44A narrative exactly, or that any variation is supported by ISBP 745 tolerance provisions (e.g., A23 for misspellings, A17 for optional fields).

8. Document the cross-check in the presentation file. Record the specific field pairs tested and the outcome. This audit trail isolates discrepancies before the examining bank applies the five-banking-day examination period under Article 14(b).

Conclusion

Field 44A is optional, but its optionality does not exempt it from the conflict test imposed by Article 14(d). The field must compile against the routing structure, the transport document type, the goods description, and any related MT701. The resolution is deterministic: read the 44-series fields together, cross-reference against the nominated transport document and the goods description, and apply Article 14(d) before the credit is issued or the documents are presented. A presentation should be cleared only after the routing fields produce no binary conflict.

FAQ

Is field 44A mandatory in an MT700?
No. SWIFT SR2018 defines 44A as Optional. A credit may omit it entirely. However, under ISBP 745 paragraph A17, the absence of data in a field does not create a discrepancy unless the credit or UCP 600 explicitly requires that data.

What happens if 44A names a place that does not appear on the transport document?
Under Article 14(d), data in the transport document must not conflict with the credit. If the credit states 44A and the transport document omits the named place or shows a different place, the presentation is discrepant. The examining bank applies the "must not conflict" standard, not a "must be identical" standard.

Can 44A and 44E name the same place?
It depends on the transport type. For multimodal or overland movement, 44A (receipt/taking in charge) and 44E (port of loading) legitimately name different points. For a pure seaport shipment, they may coincide, but the transport document must evidence the relationship clearly.

Does a misspelling in 44A create a discrepancy?
Under ISBP 745 paragraph A23, a misspelling that does not affect the meaning of the word is not a discrepancy. However, if the 44A narrative names a port or place that does not exist — for example, "Rotterdam" misspelled as "Roterdam" in a way that could be interpreted as a different location — the discrepancy stands.

Who decides whether a routing conflict in 44A is material?
The examining bank decides under Article 14 on the basis of the documents alone. The applicant's interpretation does not control the examination standard. The bank must determine whether the 44A data conflicts with other credit terms or with the transport document's routing data.