MT700 Field 43T: Relationship with UCP 600 Articles

Introduction

Field 43T records the transhipment permission in an MT700. Under UCP 600, transhipment is defined and defaulted by rule, and the transport documents that evidence it are examined against specific articles. The field is the SWIFT expression of that permission; its correct use determines whether a transhipped movement can still be compliant.

Failure Mode Analysis

Failure Mode 1: Field omitted, default misread

43T is blank and the parties assume a prohibition, whereas UCP 600 default rules may permit transhipment in defined circumstances. The assumption is wrong.

Failure Mode 2: Code outside the permitted set

A non-standard phrase is entered instead of the defined code. The field fails Option T and the instruction is ambiguous.

Failure Mode 3: Permission not reflected in documents

43T allows transhipment but the presented transport document carries a clause that the examining bank reads under Articles 20–28 as inconsistent, raising a discrepancy question.

Failure Mode 4: Routing clause conflicts with 43T

A required document's "intended" or routing wording contradicts the 43T value, so the document cannot satisfy both readings.

Failure Mode 5: Repetition in MT701

The 43T instruction is duplicated in an MT701, breaching the non-repetition rule and creating a divergent source.

Deterministic Resolution Architecture

1. State the transhipment policy explicitly in 43T using the correct code.
2. Validate the code under Option T (11x) before submission.
3. Where the field is omitted, document the applicable UCP 600 default for the file.
4. Align the 44-series routing with the policy; a transhipment-requiring route needs ALLOWED.
5. Check required transport document clauses against 43T under Articles 20–28.
6. Brief the examining bank that transhipment is assessed under Article 41(a) and Articles 20–28.
7. Keep the instruction only in 43T; never repeat it in an MT701.
8. Record the resolved policy for presentation review and dispute handling.
9. On amendment, change 43T through a proper amendment and revalidate the code.

Conclusion

Field 43T encodes the UCP 600 transhipment instruction under Article 41(a), operationalised through Articles 20–28. A valid 43T uses a defined code, matches the routing and document clauses, and is held solely in the MT700. Where omitted, the UCP 600 default governs and must be recorded. The field is changed only by amendment.

FAQ

Which UCP articles relate to 43T?
Article 41(a) and Articles 20–28.

What if 43T is omitted?
UCP 600 default rules apply; record which default governs before issuance.

Must the code be exact?
Yes. Field 43T uses an 11x code from the permitted set; free text is non-conforming.

How is transhipment proved or disproved?
Through the transport documents examined under Articles 20–28.

Does 43T override a document clause?
No. The document clause and 43T must be consistent; a conflict must be cured.

Can 43T appear in an MT701?
No. Its content must not be repeated in a related MT701.

Source Notes

• Context only: SWIFT SR2018 Category 7, MT700 field 43T specification (Option T 11x, optional, codes; non-repetition in MT701).
• Context only: UCP 600 Article 41(a) (Transhipment) and Articles 20–28.