SWIFT MT700 Field 27: Common Field Format Errors and How to Avoid Them

Introduction

Field 27 (Sequence of Total) in the SWIFT MT700 message is one of the simplest fields in format but one of the most consequential when it is wrong. The field must contain exactly two numeric digits, a forward slash, and two more numeric digits. Any deviation — extra characters, wrong separators, non-numeric input — causes the message to be rejected by the SWIFT network or misinterpreted by the receiving bank. This guide identifies the most common Field 27 format errors and provides deterministic fixes.

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.

Failure Mode Analysis

FM1: Alpha Characters in Field 27

The most basic error is entering alpha characters in a numeric field. For example, 1/a instead of 1/1. SWIFT rejects this with a format error. The fix is to replace the alpha character with the correct numeric digit.

FM2: Wrong Separator Character

The forward slash / is the only permitted separator. Using a hyphen (1-1), colon (1:1), or period (1.1) causes rejection. The fix is to use the forward slash.

FM3: Spaces in Field 27

Spaces within the field (1 /1 or 1/ 1) cause rejection. SWIFT treats the field as a single token — spaces are not permitted. The fix is to remove all spaces.

FM4: Leading Zeros

Entering 01/01 instead of 1/1 is a format error. SWIFT does not accept leading zeros in numeric fields. The fix is to remove leading zeros.

FM5: Sequence Number Greater Than Total

Entering 2/1 (message 2 of 1) is a logical error. The sequence number (X) must be less than or equal to the total (Y). This may not be caught by SWIFT format validation but will be flagged by the receiving bank. The fix is to correct the sequence number or the total.

FM6: Missing Field 27 Entirely

If the sending bank omits Field 27 from the MT700, the message is rejected by SWIFT as non-compliant. The fix is to include Field 27 with the correct content.

FM7: Extra Characters After the Numbers

Entering 1/1 (with a trailing space) or 1/1a (with a trailing character) causes rejection. The field must contain exactly the format — no extra characters.

Deterministic Resolution Architecture

Step 1: Receive the SWIFT NAK (Negative Acknowledgement)

If the message is rejected, the sending bank receives a NAK with an error code. The error code identifies which field is non-compliant. Field 27 errors are flagged with a format validation error.

Step 2: Identify the Specific Error

Read the rejected message and compare Field 27 against the required format (X/Y where X and Y are integers). Identify the specific deviation — alpha characters, wrong separator, spaces, leading zeros, or logical error.

Step 3: Correct the Field Content

Apply the specific fix for the identified error:
- Replace alpha characters with numeric digits.
- Replace wrong separators with the forward slash.
- Remove spaces.
- Remove leading zeros.
- Correct the sequence number/total relationship.

Step 4: Resubmit the Corrected Message

After correcting Field 27, resubmit the MT700 through the SWIFT network. Confirm that the message is accepted (ACK — positive acknowledgement).

Step 5: If the Error Was in an Already-Transmitted Message

If the error was in a message already received by the advising bank, the sending bank must issue an MT707 amendment to correct the sequence information. The advising bank cannot advise the credit until the sequence is correct.

Step 6: Verify the Complete Message

After correcting Field 27, verify that the entire MT700 message is consistent. If the correction changed the sequence (e.g., from 1/2 to 1/1), confirm that the credit data fits within the single message.

Step 7: Document the Error for Process Improvement

Record the error and the correction in the bank's quality control log. Field 27 errors are preventable through pre-submission validation. Implement a validation check in the message preparation process.

Conclusion

Field 27 errors are format errors that are entirely preventable. The field must contain exactly two numeric digits, a forward slash, and two more numeric digits — no more, no less. The SWIFT network rejects non-compliant messages before they reach the receiving bank. The fix is to correct the format and resubmit. For messages already transmitted, an MT707 amendment corrects the sequence information.

FAQ

Q1: Does SWIFT auto-correct Field 27 errors?

No. SWIFT validates the format and rejects non-compliant messages. It does not auto-correct. The sending bank must correct the error and resubmit.

Q2: Can the receiving bank advise the credit if Field 27 is wrong?

The receiving bank cannot advise an incomplete or non-compliant credit. If Field 27 indicates a multi-part message and only part 1 is received, the bank waits for the remaining parts.

Q3: What if the credit data is correct but Field 27 is wrong?

The credit data is irrelevant if Field 27 is non-compliant — the message is rejected before the bank examines the credit data. The fix is to correct Field 27 and resend the entire message.

Q4: Can Field 27 be corrected via MT707?

Yes. An MT707 amendment can correct the sequence information if the original MT700 had an incorrect Field 27. The amendment must also carry the correct Field 27.

Q5: Is Field 27 validation the same across all MT message types?

Field 27 is mandatory in MT700, MT701, MT705, MT707, and MT710. The format is the same (2n) across all these message types. The validation rules are consistent.

Source Notes

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

• 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 2023
• 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