MT700 Field 43P: When the Partial-Shipment Instruction Contradicts Other Fields

Introduction

Field 43P states whether partial shipments are allowed under a documentary credit. It is an optional code field, but its instruction must cohere with the transport, shipment-date, and goods descriptions elsewhere in the message. When 43P says one thing and a related field implies another, the credit is contradictory and the beneficiary cannot plan compliant shipments.

Failure Mode Analysis

Failure Mode 1: 43P forbids partials but routing implies multiple loads

Field 43P shows NOT ALLOWED, while the place of receipt, port of loading, and port of discharge imply several separate consignments. The transport plan cannot satisfy the prohibition.

Failure Mode 2: 43P allows partials but the goods quantity is indivisible

The credit permits partial shipments, yet the goods description defines a single sealed contract quantity with no split basis, leaving the permission unactionable.

Failure Mode 3: 43P contradicts an instalment schedule elsewhere

An instalment shipment schedule appears in narrative while 43P says partial shipments are not allowed, producing a direct conflict.

Failure Mode 4: 43P inconsistent with the latest shipment date

A single latest shipment date (44C) is given, but 43P allows multiple shipments, and no schedule reconciles them.

Failure Mode 5: 43P repeated in an MT701

The instruction is placed in 43P of the MT700 and again in a related MT701, breaching the rule that designated MT700 field information must not be repeated in an MT701.

Deterministic Resolution Architecture

1. Decide the partial-shipment policy before issuing the credit.
2. Encode it in 43P as the correct code (ALLOWED / NOT ALLOWED).
3. Validate the code format under Option P (11x).
4. Check the 44-series routing against the policy: multiple receipt/load points may require ALLOWED.
5. Reconcile the goods description quantity with the ability to split shipments.
6. Ensure any instalment schedule in narrative matches the 43P code.
7. Confirm the latest shipment date and presentation period support the chosen policy.
8. Keep the instruction only in 43P; do not repeat it in any MT701.
9. Record the resolved policy for document examination under Articles 31–33.

Conclusion

Field 43P is the SWIFT encoding of the partial-shipment permission under Article 41(b) and Article 31. Its code must align with the routing, goods quantity, instalment schedule, and shipment dates in the credit. A contradiction makes compliant shipment impossible and must be resolved before advice, with the instruction held solely in 43P.

FAQ

Is 43P mandatory?
No. It is optional, but when omitted the credit should be read with UCP 600 default rules.

What codes are permitted in 43P?
The field uses an 11x code; the instruction must be one of the defined partial-shipment codes.

Can 43P conflict with the transport routing?
It should not. Routing that implies multiple loads must match an ALLOWED instruction.

Does an instalment schedule override 43P?
No. The two must be consistent; a conflict must be cured before issuance.

Can 43P be repeated in an MT701?
No. Designated MT700 field content must not be repeated in a related MT701.

Which UCP articles apply to a 43P dispute?
Article 41(b) and Articles 31–33.

Source Notes

• Context only: SWIFT SR2018 Category 7, MT700 field 43P specification (Option P 11x, optional, codes; non-repetition in MT701).
• Context only: UCP 600 Article 41(b) (Partial Shipments) and Articles 31–33.