UCP 600

MT700 Field 48 and Its Relationship with UCP 600

📅 2026-07-13 5 min read UCP 600 / ISBP 745

Introduction

SWIFT MT700 Field 48 specifies the presentation period allowed for the beneficiary to present documents under a documentary credit. This field plays a central role in ensuring that document presentation timelines align with the rules set out in UCP 600. When banks and beneficiaries fail to understand how Field 48 interacts with the ICC's Uniform Customs and Practice for Documentary Credits, discrepancies and payment delays result.

Failure Modes

1. Ambiguous Period Specification
When Field 48 states "within 30 days" without clarifying whether this means calendar days or banking days, the issuing bank and beneficiary may disagree on the deadline. UCP 600 does not mandate calendar or banking days for Field 48 itself, leaving interpretation to the parties.

2. Field 48 Conflicts with UCP 600 Article 14(c)
If Field 48 specifies a period shorter than the five-day examination window in Article 14(c), confusion arises about whether the presentation period or the examination period takes precedence. The two serve different functions: Field 48 governs when documents must arrive; Article 14(c) governs how long the bank has to examine them.

3. Missing or Blank Field 48
An MT700 issued without Field 48 creates uncertainty about the presentation deadline. While UCP 600 provides a default framework, the absence of an explicit period invites disputes between banks, particularly across jurisdictions with different commercial customs.

4. Presentation Period Calculated from Wrong Trigger Event
Field 48 may reference "shipment date" when the credit requires calculation from "on board date" or "date of dispatch." These dates may differ significantly, especially in containerized shipping where the vessel sailed date and the on-board notation date are not always identical.

Resolution Steps

  1. Always complete Field 48 explicitly when issuing an MT700. Specify the exact trigger event (e.g., "21 days after B/L date") and confirm whether the count uses calendar or banking days.

  2. Cross-reference Field 48 against UCP 600 Article 14(c) during the credit issuance review. Ensure the stated presentation period is realistic given the document preparation and transit time requirements.

  3. Use ISBP 745 paragraph A20 as a calibration tool when drafting Field 48 language. Follow the ICC's standard date-calculation conventions to prevent ambiguity.

  4. Include a Field 48 review checkpoint in your documentary credit amendment workflow. When amending a credit via MT707, confirm that any changes to shipment dates or document requirements are reflected in an updated Field 48.

  5. Train trade operations staff on the difference between presentation periods (Field 48) and examination periods (Article 14(c)). Confusing the two is a common source of internal process errors.

  6. When Field 48 is missing from an incoming MT700, request clarification from the issuing bank via MT799 or MT199 before proceeding. Do not assume a default period without written confirmation.

  7. Establish a standard template for Field 48 entries across your organization's trade finance operations. Standardized language reduces interpretation risk and improves processing efficiency.

Conclusion

Field 48 is a mandatory SWIFT element that directly interfaces with UCP 600's presentation and examination rules. Banks that treat it as a routine field risk creating discrepancies that delay payment and damage commercial relationships. A disciplined approach to drafting, reviewing, and cross-referencing Field 48 against the relevant UCP articles is essential for smooth documentary credit operations.

Frequently Asked Questions

Q1: Is Field 48 mandatory in all MT700 messages?
Yes. SWIFT requires Field 48 to be completed in every MT700 issuance message. Its absence constitutes a message formatting issue that the receiving bank should flag.

Q2: Can Field 48 specify a period shorter than what UCP 600 Article 14(c) allows for examination?
Field 48 governs the presentation deadline, while Article 14(c) governs the examination window. They serve different functions. A short presentation period does not reduce the bank's five-day examination window, but it does compress the beneficiary's time to prepare and submit documents.

Q3: What happens if Field 48 and the credit text specify different presentation periods?
UCP 600 Article 1(a) states that the credit is separate from the sale or other contract. When Field 48 in the SWIFT message conflicts with the credit text, the bank should seek clarification from the issuing bank. In practice, banks often treat the SWIFT message as controlling, but this is not universally established.

Q4: How does Field 48 interact with force majeure provisions under UCP 600 Article 36?
If an event of force majeure prevents timely presentation, Article 36 provides that the period is extended. Field 48's stated deadline is suspended during the force majeure period and resumes when the impediment is removed.

Q5: Should Field 48 use banking days or calendar days?
UCP 600 does not mandate one over the other for Field 48. The field should specify which type of day is intended. In the absence of specification, market practice varies by region, which is why explicit drafting is recommended.

Source Notes

The following sources were consulted as context only and do not constitute endorsements of this guide:

Did You Know?

UCP 600 Article 14(c) allows for examination?** Field 48 governs the presentation deadline, while Article 14(c) governs the examination window.

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 14Standard for Examination of DocumentsBinary determination (compliant/discrepant)
UCP 600Article 1Scope of the RulesBinary determination (compliant/discrepant)
UCP 600Article 36Force MajeureBinary determination (compliant/discrepant)

← Scroll horizontally to see all columns

Quick Reference Summary

  • No reference captured.

Compliance Checklist

0 of 5 completed

Get the Full LC Compliance Checklist

15-point pre-submission checklist covering UCP 600, ISBP 745, and SWIFT MT700 fields. Free PDF download.

No spam. Unsubscribe anytime.

DraftLC Compliance Engine

DraftLC generates compliant MT700 Field 48 and Its Relationship with UCP 600 — so you never face this failure mode.

DraftLC drafts your LC with UCP 600-compliant terms and flags conflicts during drafting — before documents reach the bank.

No credit card required · See how DraftLC drafts compliant credits