SWIFT MT700 Field 27: Format Requirements and Validation Rules

Introduction

SWIFT Field 27 (Sequence of Total) is a mandatory field in the MT700 documentary credit message. It establishes the sequence position and total count of messages in a multi-part credit issuance. The field's format requirements are precise — any deviation causes the message to be rejected by the SWIFT network. This guide defines the exact format requirements, validation rules, and compliance standards for Field 27 across the SWIFT Category 7 message family.

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 Exceeds Maximum Length

If Field 27 contains more than the required characters (e.g., 1/1 with a trailing space, or 01/01 with leading zeros), the field exceeds the expected length. SWIFT format validation rejects the message.

FM2: Field 27 Contains Non-Numeric Characters in the Sequence Number

If the sequence number contains an alpha character (e.g., 1/a), the field fails format validation. The sequence number must be purely numeric.

FM3: Field 27 Uses a Non-Standard Separator

The forward slash / is the only permitted separator. Using a hyphen, colon, period, or other character causes rejection. This is the most common format error in Field 27.

FM4: Field 27 Is Empty

An empty Field 27 causes the message to be rejected as non-compliant. The field must contain a value — it is mandatory in all MT700 messages.

FM5: Field 27 Contains Extra Fields or Data

If the field contains additional data beyond the sequence number and total (e.g., 1/1 additional text), the extra data violates the format. The field must contain only the sequence number, slash, and total.

Deterministic Resolution Architecture

Step 1: Confirm Field 27 Is Present

Before examining the content, confirm the field exists in the MT700 message. If absent, the message is non-compliant and must be resent with Field 27 included.

Step 2: Verify the Format Compliance

Check the field content against the 2n format:
- Exactly two digits, a forward slash, and two digits.
- No alpha characters, no special characters (except /), no spaces.
- No leading zeros.

Step 3: Verify the Length

Confirm the field content is exactly 5 characters (e.g., 1/1 is 3 characters — this is correct). The format allows 1-digit or 2-digit sequence numbers and totals. For single-digit numbers, the content is X/Y (3 characters). For double-digit numbers, it is XX/YY (5 characters).

Step 4: Verify the Logical Consistency

Confirm that the sequence number (X) is less than or equal to the total (Y). If X > Y, the sequence is invalid. If X = 0, the sequence is invalid (sequence numbers start at 1).

Step 5: Verify the Total Matches the Message Count

If Field 27 shows 1/3, the bank expects to receive three messages total. Verify that all three messages in the sequence have been received before advising the credit.

Step 6: Cross-Reference Against the Credit Amount and Length

If the credit is large and may require multiple messages, verify that Field 27 correctly reflects the number of messages needed. A credit that exceeds a single MT700's capacity (approximately 35,000 characters) requires multiple messages.

Step 7: If Non-Compliant, Issue a Corrective Message

If Field 27 is non-compliant, the sending bank must correct the error and resend the MT700 or issue an MT707 amendment. The receiving bank should not process the credit until Field 27 is correct.

Conclusion

Field 27 format requirements are simple but absolute. The field must contain exactly two numeric digits, a forward slash, and two more numeric digits. No deviations are permitted. SWIFT validates the format at transmission, and the receiving bank validates the logical consistency. Errors in Field 27 cause message rejection or incomplete credits. Compliance requires strict adherence to the 2n format and logical consistency between the sequence number and the total.

FAQ

Q1: What is the maximum sequence number allowed in Field 27?

The format allows up to two digits, so the maximum total is 99. In practice, documentary credits rarely exceed three messages.

Q2: Can Field 27 be 0/1?

No. Sequence numbers start at 1. 0/1 is invalid because the sequence number cannot be zero.

Q3: Can Field 27 be 1/10?

Yes, if the credit requires 10 messages. The format allows up to two digits for both the sequence number and the total. 1/10 means message 1 of 10.

Q4: Does Field 27 validation differ between MT700 and MT707?

The format is the same (2n) for both message types. The validation rules are consistent. However, MT707 messages amend existing credits, so the sequence in Field 27 may differ from the original MT700.

Q5: What happens if Field 27 is correct but the credit data exceeds the message capacity?

If the credit data is too long for a single MT700, the sending bank must split the data across multiple messages. Each message carries the correct Field 27 (e.g., 1/2, 2/2). If the bank sends only one message with Field 27 showing 1/1 but the data is truncated, the receiving bank may flag the truncation.

Source Notes

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

• SWIFT — Category 7: Documentary Credits and Guarantees/Standby Letters of Credit — Message Reference Guide, Standards MT November 2021
• SWIFT — Category 7: Documentary Credits and Guarantees — Message Reference Guide, Standards MT November 2019
• SWIFT — Category 7: Documentary Credits and Guarantees/Standby Letters of Credit — Message Reference Guide, Standards MT November 2018
• SWIFT — Standards MT November 2022 — Category 7 Message Reference Guide
• SWIFT — Standards MT November 2020 — Category 7 Message Reference Guide