SWIFT

SWIFT MT700 Field 27: Complete Field Guide for Documentary Credit Messages

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

Introduction

SWIFT MT700 is the message format used by banks to issue or amend documentary credits. Field 27 (Sequence of Total) is one of the mandatory fields in every MT700 message. It indicates whether the message is a single-part message or part of a multi-part sequence. Errors in Field 27 — wrong format, wrong sequence number, or missing field — cause the entire message to be rejected by the SWIFT network or misinterpreted by the receiving bank. This guide provides a complete reference for Field 27 format, content, and validation.

The sources available for this guide are contextual references from SWIFT Category 7 Message Reference Guides (2018–2023). No direct article text was extracted. The authority is the SWIFT MT Standards for Category 7 — Documentary Credits and Guarantees.

Failure Mode Analysis

FM1: Field 27 Contains Non-Numeric Characters

SWIFT validates all fields against their defined format. Field 27 must be exactly 2n — two numeric digits separated by a forward slash. If the field contains alpha characters (e.g., 1/a), special characters (e.g., 1-1), or spaces (e.g., 1 /1), the SWIFT network rejects the message.

FM2: Sequence Number Exceeds Total

If Field 27 shows 3/2 (message 3 of 2), the sequence number exceeds the total. This is a logical error that the SWIFT validation may not catch, but the receiving bank will flag as non-compliant. The sequence number must never exceed the total.

FM3: Single-Part Message Shows 1/2

If the credit fits in a single MT700 message but Field 27 shows 1/2, the receiving bank expects a second message (MT701). When the second message does not arrive, the credit cannot be advised — it is incomplete. The bank must either receive the second message or the sending bank must correct the field.

FM4: Field 27 Missing Entirely

SWIFT rejects MT700 messages that omit mandatory fields. If Field 27 is missing, the message is rejected by the SWIFT network before it reaches the receiving bank. The sending bank must include Field 27 in every MT700 message.

FM5: Multiple Messages Without Correct Sequencing

When a credit requires multiple MT700 messages (e.g., 2/3, 3/3), each message must carry the correct Field 27. If one message shows 1/3 and the next shows 2/3 but the third is missing, the receiving bank cannot process the credit — the sequence is incomplete.

Deterministic Resolution Architecture

Step 1: Verify Field 27 Exists

Confirm that the MT700 message contains Field 27. If the field is missing, the message is non-compliant and must be resent.

Step 2: Check the Format

Verify that Field 27 contains exactly two numeric digits, a forward slash, and two more numeric digits. The format is X/Y where X and Y are integers. No alpha characters, no special characters, no spaces.

Step 3: Confirm the Sequence Number Does Not Exceed the Total

Verify that X ≤ Y. If X > Y, the sequence is invalid. The sending bank must correct the field.

Step 4: Verify Single-Part Messages Are Correctly Sequenced

For single-part messages, confirm Field 27 shows 1/1. If the credit fits in one message but shows 1/2 or higher, the message is incorrect.

Step 5: Verify Multi-Part Sequences Are Complete

For multi-part messages, confirm that all messages in the sequence have been received. If Field 27 shows 1/3, the receiving bank must receive messages 2/3 and 3/3 before the credit can be advised.

Step 6: Cross-Reference Against the Message Content

If Field 27 indicates a multi-part message, verify that the credit data across all messages is consistent. The credit amount, beneficiary, expiry date, and other fields must be consistent across the sequence.

Step 7: If the Field Is Non-Compliant, Request Correction

If Field 27 is in an incorrect format, the sending bank must issue a corrective message (MT707 amendment) to correct the sequence information. The receiving bank should not advise the credit until the sequence is correct.

Conclusion

Field 27 (Sequence of Total) is a mandatory field in every MT700 message. It must contain exactly two numeric digits, a forward slash, and two more numeric digits (format 2n). The sequence number must not exceed the total. Single-part messages must show 1/1. Multi-part messages must be complete before the credit can be advised. Errors in Field 27 cause message rejection or incomplete credits that cannot be processed. The sending bank must validate Field 27 before transmitting the message.

FAQ

Q1: Can an MT700 message have more than 99 parts?

In theory, the format allows up to 99/99. In practice, credits rarely exceed two or three parts. The SWIFT standard accommodates up to 99 parts.

Q2: What happens if only part 1 of a 3-part message is received?

The receiving bank cannot advise the credit until all parts are received. The bank waits for parts 2 and 3, or contacts the sending bank for retransmission.

Q3: Can Field 27 be amended separately?

Yes, through an MT707 amendment message. The amendment can correct the sequence information if it was incorrect in the original MT700.

Q4: Does Field 27 apply to MT707 amendment messages?

Yes. MT707 messages also carry Field 27 for sequencing. The same format and validation rules apply.

Q5: What is the difference between Field 27 and Field 28 (Documentary Credit Number)?

Field 27 is the message sequence number. Field 28 is the unique reference number assigned to the documentary credit. They serve entirely different purposes.

Q6: Can the SWIFT network auto-correct a wrong Field 27?

No. SWIFT validates the format but does not correct logical errors (e.g., sequence number exceeding total). The sending bank must correct the error and resend the message.

Source Notes

Context only — no direct article text was extracted from these sources during research:

Did You Know?

Article 9(a) states that an irrevocable credit constitutes a definite undertaking of the issuing bank.

Regulatory Reference Table
RegulationArticle / SectionRequirementConsequence
UCP 600Article 9Advising of Credits and AmendmentsBinary determination (compliant/discrepant)

← Scroll horizontally to see all columns

Quick Reference Summary

  • No reference captured.

Compliance Checklist

0 of 6 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 SWIFT MT700 Field 27 — 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