MT700 Field 48 and Its Relationship with UCP 600 Articles

Introduction

SWIFT MT700 field 48 records the period for presentation in days — the number of days after the date of shipment within which documents must be presented. It is an optional field (3n[/35x]) that works together with the expiry date to set the outer deadline for a complying presentation. Although field 48 appears in the MT700 message, its conceptual home in UCP 600 is Article 36 (transferable credits) read alongside Article 38 and the presentation-period rules in Article 14 and Article 29 (the "half-month" and tolerance rules).

This guide maps field 48 to the UCP 600 articles that govern presentation timing and, per the source dossier's cross-reference, the transferable-credit framework of Articles 36 and 38. It explains how a SWIFT presentation-period field interacts with the UCP rules that determine whether documents are presented in time.

Failure Mode Analysis

Failure Mode 1: Presentation Outside the Field 48 Day Count

Field 48 allows presentation within 21 days of shipment. The beneficiary presents on day 25. Under the presentation rules, the presentation is late and not complying, triggering the Article 16 refusal pathway.

Failure Mode 2: Field 48 Conflicts with the Expiry Date

Field 48 permits presentation 30 days after shipment, but the expiry in field 31D falls only 10 days after shipment. The earlier of the two deadlines governs; a presentation that satisfies field 48 but misses the expiry is discrepant.

Failure Mode 3: Field 48 Omitted, Creating Uncertainty in a Transferable Credit

In a transferable credit, field 48 is blank. Article 36 and 38 require the transferring bank to manage the terms of the transfer, and the absence of an explicit presentation period leaves the transferred credit's deadline ambiguous.

Failure Mode 4: Transferred Credit Alters the Field 48 Period Improperly

Under Article 38, the transferred credit may reduce certain terms, but the presentation period must be handled consistently with the transfer rules. An improper extension or reduction of the field 48 day count in the transferred credit creates a discrepancy between the original and transferred credits.

Failure Mode 5: Field 48 Day Count Read Without Article 29 Tolerances

The beneficiary applies a strict day count and rejects a presentation that Article 29's interpretive rules would permit. Misreading the interaction between field 48 and Article 29 produces an unnecessary refusal or a missed presentation window.

Deterministic Resolution Architecture

Step1: Extract Field 48 and the Expiry

Record the field 48 day count and the expiry date in field 31D. The presentation must occur within both: the earlier deadline controls.

Step2: Compute the Presentation Deadline from Shipment

Measure the field 48 day count from the date of shipment shown on the transport document. Confirm the computed deadline and compare it with the expiry.

Step3: Apply Article 29 Interpretive Rules

Use Article 29's rules for interpreting timing terms and tolerances when reading field 48 and the shipment date. Avoid miscomputing the window through a strict-reading error.

Step4: Confirm the Presentation Occurs Within Both Limits

Verify the actual presentation date falls within the field 48 window and before the expiry. A presentation meeting one but not the other is not complying.

Step5: Handle Field 48 in a Transferable Credit

Where the credit is transferable under Article 36/38, confirm the transferring bank has applied field 48 consistently in the transferred credit. The presentation period is a term the transfer must respect.

Step6: Verify the Transferred Credit's Field 48 Consistency

For a transferred credit, confirm the field 48 day count was altered only as permitted by Article 38 and that the second beneficiary's presentation satisfies the transferred credit's period.

Step7: Cross-Check Partial Shipments

If the credit permits partial shipments (Article 31), confirm each presentation's field 48 window is computed from its own shipment date, not the first or last shipment.

Step8: Pre-Presentation Timing Verification

Before submission, confirm: field 48 extracted, expiry noted, deadline computed, Article 29 applied, presentation within both limits, and (if transferable) transferred-credit consistency verified. Present only when all hold.

Conclusion

Field 48 is the SWIFT carrier of the presentation-period term, and its relationship with UCP 600 runs through Article 14 (examination of a complying presentation), Article 29 (timing interpretation), and — per the source dossier — Articles 36 and 38 (transferable credits). The field 48 day count and the expiry together set the presentation deadline; the earlier controls. In transferable credits, the transferring bank must carry the field 48 term through the transfer under Articles 36 and 38. Computing the window correctly, applying Article 29, and respecting the transfer rules avoids the late-presentation and transfer discrepancies this guide describes.

FAQ

Q1: Which UCP 600 articles relate to field 48?
Primarily Article 14 (complying presentation), Article 29 (timing interpretation and tolerances), and — per the source cross-reference — Articles 36 and 38 (transferable credits). The expiry and honour timing (Articles 31–33) also interact.

Q2: Is field 48 mandatory?
No, field 48 is optional under SWIFT. When blank, the presentation period is governed by the expiry and the applicable UCP rules.

Q3: Which controls — field 48 or the expiry?
The presentation must satisfy both. The earlier of the field 48 deadline (days after shipment) and the expiry date controls. A presentation outside either is not complying.

Q4: How does field 48 matter in a transferable credit?
Under Articles 36 and 38, the transferring bank manages the credit's terms in the transfer. The field 48 presentation period is a term that must be carried through consistently to the transferred credit.

Q5: Can the transferred credit change the field 48 period?
Article 38 permits certain terms to be reduced in the transferred credit, but the presentation period must be handled within the transfer rules. An improper alteration creates a discrepancy between the original and transferred credits.

Q6: Does Article 29 affect how field 48 is read?
Yes. Article 29's interpretive rules for timing terms and tolerances inform how the field 48 day count and the shipment date are read, preventing miscomputation of the presentation window.

Source Notes

Context only: The source dossier for this guide contained the SWIFT MT700 field 48 specification (SWIFT SR2018, Category 7) and the UCP 600 article cross-reference for field 48 (Articles 36 and 38, transferable credits). No text from those sources has been reproduced. This guide was composed from first principles using the SWIFT MT700 field specification, the UCP 600 framework, and independent analysis of field 48's article relationships, including the presentation-period and transferable-credit rules.