Resource Center
SWIFT MT70010 min readUpdated June 2026

SWIFT MT700 Field-by-Field Audit Guide: Essential Compliance Checkpoints for Exporters

The SWIFT MT700 message format is the global standard used by issuing banks to transmit irrevocable Letters of Credit. For export document managers, performing a meticulous field-by-field audit upon receipt of an MT700 is the critical first line of defense against bank discrepancies under UCP 600. Below is an expert-level compliance audit checklist covering the key SWIFT MT700 fields, common formatting traps, and international banking rules.

1. Field 31D: Date and Place of Expiry

  • Compliance Standard: Dictates the final calendar date and geographical location where documents must be presented.
  • Audit Rule: Under UCP 600 Article 6(d)(ii), the credit must state an expiry date for presentation. The place for presentation must be located in the beneficiary's country or a designated bank's location.

Red Flag

  • An expiry location situated strictly at the issuing bank's counters in a foreign country, leaving the beneficiary insufficient courier transport time after shipping.

2. Field 44C: Latest Date of Shipment vs. Field 44D: Shipment Period

  • Compliance Standard: Specifies the final deadline for goods to be loaded on board or dispatched.
  • Audit Rule: Under UCP 600 Article 29(a), if the expiry date falls on a bank holiday, it is extended to the next banking day; however, the latest shipment date (Field 44C) is NEVER extended due to bank holidays.

Red Flag

  • Confusing shipment extension rules with expiry extension rules, leading to late shipment discrepancies.

3. Field 45A: Description of Goods, Services or Performance

  • Compliance Standard: The master contract baseline for invoices and trade documents.
  • Audit Rule: Under UCP 600 Article 18(c), the Commercial Invoice must strictly correspond with the exact text in Field 45A. Abbreviations, altered trade terms (e.g., FOB vs. CIF), or missing model numbers trigger automatic rejection by issuing banks.

Red Flag

  • Overly complex technical specifications pasted into Field 45A that cannot be mirrored word-for-word on the invoice.

4. Field 46A: Documents Required & Field 47A: Additional Conditions

  • Compliance Standard: Outlines every certificate, transport document, and policy needed for payment, alongside mandatory special instructions.
  • Audit Rule: Under ISBP 745 (Section A), documents must be issued by the entity named in the LC (or beneficiary if silent). Any condition in Field 47A that specifies a requirement without mandating a document (Non-Documentary Condition) is disregarded by banks under UCP 600 Article 14(h).

Red Flag

  • Clauses requiring “Approval by Applicant's QC Inspector” without specifying an Inspection Certificate document format.

5. Field 48: Period for Presentation

  • Compliance Standard: Number of days allowed after shipment for document submission.
  • Audit Rule: Under UCP 600 Article 14(c), if Field 48 is omitted, the default legal presentation period is 21 calendar days after the date of shipment (but not later than the expiry date in Field 31D).

Red Flag

  • Setting Field 48 to an unrealistically short timeframe (e.g., 5 days) when obtaining Bills of Lading or Certificate of Origin takes longer.

Streamlining MT700 Verification with Automated Pre-Audits

Manually reviewing SWIFT MT700 tags against dozens of ISBP 745 clauses is time-consuming and prone to human oversight under tight shipping deadlines.

LC Shield automatically maps SWIFT MT700 text fields, validates field logic against UCP 600 / ISBP 745 standards, and highlights discrepancy traps within 10 seconds. Exporters can pre-screen live MT700 data and draft immediate amendment requests before commencing shipment.

Frequently asked questions

Try it yourself

Run your first L/C audit free

Paste your SWIFT MT700 or trade documents and let LC Shield flag every UCP 600 / ISBP 745 discrepancy — with article references and suggested fixes — in seconds. No credit card, zero data retention.

Related guides