SWIFT MT700 Field 44A and Its Relationship with UCP

Introduction

Field 44A (Place of Taking in Charge / Place of Receipt) is an optional routing field in the MT700 under SWIFT SR2018, Category 7. Its SWIFT definition fixes the place where the carrier receives the goods or takes them in charge. The relationship with UCP is structural: UCP 600 does not repeat the SWIFT field layout, but it supplies the articles that determine what the transport document must show about that place and how the bank must examine it. A user who treats 44A as a free-text note misses the layered control that SWIFT and UCP share over routing data.

Failure Modes

Failure Mode 1: Field treated as narrative only, not a routing control

Drafting 44A loosely ignores the Article 20-28 requirement that the document evidence the named place, producing a credit the documents cannot satisfy.

Failure Mode 2: Document presented shows the wrong place

Under Article 14(d), a place on the document that conflicts with 44A is a discrepancy regardless of intent.

Failure Mode 3: Place repeated in MT701 with divergence

The usage rules prohibit an MT701 from conflicting with MT700 information; a second, different statement of 44A breaks the UCP linkage.

Failure Mode 4: No transport-document article identified

Without tying 44A to a specific Article 20-28 document type, the examination standard becomes ambiguous.

Failure Mode 5: Delivery term conflated with receipt place

The 45A trade term names a commercial obligation; 44A names a routing point. Treating one as the other distorts both.

Resolution

1. Draft 44A to name the exact taking-in-charge or receipt place required by the shipment.
2. Select the transport document type in 46A that can evidence that place under its article.
3. Map 44A to the specific Article 20-28 rule that applies.
4. Examine under Article 14(a) on the documents alone.
5. Test the document's place against 44A under Article 14(d).
6. Keep any MT701 consistent with the MT700 44A content.
7. Record the article basis for the routing decision.

Conclusion

The SWIFT/UCP relationship for 44A is a division of labor: SWIFT states the place, UCP tests whether the document proves it. Neither layer works alone. A credit holds up when the field and the applicable article are aligned, and a presentation holds up when the document evidences the field without conflict.

FAQ

Why does UCP not mention field 44A by name?
UCP 600 operates at the document level and does not mirror SWIFT field tags. The connection is made through the transport-document articles and Article 14.

Must 44A always be used when goods are received inland?
Only when the credit needs to state that place. SWIFT marks it Optional, but the applicable transport article may still require the place to be shown on the document.

How does an MT701 interact with this relationship?
An MT701 may carry additional credit information but must not conflict with the MT700. A divergent 44A in an MT701 is a direct breach of that usage rule.

Is the conflict rule the same for all transport documents?
The conflict principle in Article 14(d) applies across documents; the specific place-evidencing rule varies by document type in Articles 20-28.

Can the beneficiary cure a 44A mismatch after presentation?
A discrepancy is handled under the credit's refusal and waiver process; correction before presentation is the cleaner control.

Source Notes

• SWIFT SR2018, Category 7, MT700 field 44A (Optional, Option A, 65x narrative). Context only.
• UCP 600 Articles 20-28 and Article 14. Context only.
• MT700 usage rules on related MT701 content. Context only.