SWIFT MT700 Field 27: Troubleshooting Common Errors in Documentary Credit Messages

Introduction

When a SWIFT MT700 message is rejected or when the receiving bank flags an issue with Field 27 (Sequence of Total), the troubleshooting process must be systematic. Field 27 errors fall into two categories: format errors (rejected by SWIFT validation) and logical errors (accepted by SWIFT but flagged by the receiving bank). This guide provides a troubleshooting framework for both categories, with specific diagnostic steps and corrective actions.

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: Message Rejected by SWIFT — Format Error

The sending bank receives a NAK with a format error code for Field 27. The message was not transmitted. The bank must correct the field and resubmit.

Diagnostic steps:
1. Read the rejected MT700 message.
2. Locate Field 27.
3. Compare the content against the required format (X/Y where X and Y are integers).
4. Identify the specific deviation — alpha characters, wrong separator, spaces, or missing field.
5. Correct the field and resubmit.

FM2: Message Accepted but Receiving Bank Flags Sequence Error

The MT700 was transmitted successfully, but the receiving bank reports a sequence error. For example, Field 27 shows 1/3 but only one message was received.

Diagnostic steps:
1. Confirm that all messages in the sequence (e.g., 1/3, 2/3, 3/3) were transmitted.
2. Check SWIFT transmission logs for each message.
3. If a message was not transmitted, resend it.
4. If a message was transmitted but not received, contact the SWIFT network operator.

FM3: Field 27 Shows 1/1 but the Credit Data Is Truncated

The message shows a single-part sequence, but the credit data appears incomplete — fields are missing or cut off. This suggests the credit data exceeded the MT700 message capacity.

Diagnostic steps:
1. Check the message length against the MT700 maximum (approximately 35,000 characters).
2. If the data exceeds the capacity, split the credit across multiple messages.
3. Update Field 27 to reflect the correct sequence (e.g., 1/2, 2/2).
4. Resend all messages with the correct Field 27.

FM4: Receiving Bank Reports Field 27 Contains Incorrect Sequence

The message was transmitted, but the receiving bank reports that Field 27 does not match the actual number of messages. For example, the bank received three messages but Field 27 on message 1 shows 1/2.

Diagnostic steps:
1. Verify the total number of messages in the sequence.
2. Compare against Field 27 on each message.
3. If Field 27 is incorrect, issue an MT707 amendment to correct the sequence.
4. If the credit data has changed, recalculate the required number of messages.

FM5: Field 27 Is Correct but the Credit Cannot Be Advised

The Field 27 is correct, the messages are complete, but the advising bank cannot advise the credit. This may be due to other field errors (e.g., Field 31D expiry date issues, Field 59 beneficiary issues) that are unrelated to Field 27.

Diagnostic steps:
1. Confirm Field 27 is correct and all messages are received.
2. Examine the other fields in the MT700 for errors.
3. Address any non-Field-27 issues that may be preventing the credit from being advised.
4. If Field 27 is the only issue, confirm with the receiving bank what specific problem they are reporting.

Deterministic Resolution Architecture

Step 1: Identify the Error Type

Determine whether the error is a format error (rejected by SWIFT) or a logical error (accepted by SWIFT but flagged by the bank). Format errors prevent transmission; logical errors allow transmission but prevent processing.

Step 2: For Format Errors — Correct and Resubmit

Read the NAK error code, identify the specific Field 27 deviation, correct the format, and resubmit the MT700. Confirm acceptance (ACK) before proceeding.

Step 3: For Logical Errors — Verify the Sequence

Confirm that all messages in the sequence have been transmitted. Check SWIFT logs for each message. If a message is missing, resend it.

Step 4: For Truncated Messages — Split and Resend

If the credit data exceeds the MT700 capacity, split the data across multiple messages. Update Field 27 on each message to reflect the correct sequence. Resend all messages.

Step 5: For Incorrect Sequences — Issue MT707

If Field 27 shows an incorrect sequence after transmission, issue an MT707 amendment to correct the sequence information. The amendment must also carry the correct Field 27.

Step 6: Confirm End-to-End Processing

After correcting all errors, confirm that the MT700 is accepted by the SWIFT network, received by the advising bank, and that the credit can be advised to the beneficiary. Verify the complete sequence.

Step 7: Document and Prevent

Record the error type, root cause, and corrective action in the bank's quality control log. Implement pre-submission validation checks to prevent recurrence:
- Automated format validation before SWIFT submission.
- Sequence verification against the credit data length.
- Review of Field 27 content by a second operator.

Conclusion

Field 27 troubleshooting follows a systematic pattern: identify the error type, correct the specific deviation, verify the sequence, and confirm end-to-end processing. Format errors are corrected and resubmitted. Logical errors require sequence verification and, in some cases, MT707 amendments. The most effective prevention is pre-submission validation — checking Field 27 format, sequence, and logical consistency before the message enters the SWIFT network.

FAQ

Q1: How long does it take for a corrected MT700 to be processed?

A corrected MT700 follows the same processing timeline as the original — the SWIFT network transmits it within minutes, and the receiving bank processes it within the standard timeframe (up to five banking days under UCP 600 Art 14(b)).

Q2: Can the receiving bank advise the credit while a correction is pending?

No. The receiving bank cannot advise a credit until the sequence is complete and Field 27 is correct. An incomplete or non-compliant sequence prevents the credit from being advised.

Q3: Does the advising bank charge a fee for Field 27 corrections?

The advising bank's fee structure varies. Some banks charge for re-advice or amendment processing. The issuing bank should confirm the fee structure with the advising bank before issuing corrections.

Q4: Can Field 27 errors be corrected without an MT707?

If the error is in a message not yet transmitted, the bank corrects the MT700 and resubmits. If the error is in a message already transmitted, an MT707 is the standard mechanism for correction.

Q5: What is the most common Field 27 error?

The most common error is using a wrong separator character (hyphen instead of slash) or including alpha characters. These errors are preventable through pre-submission format validation.

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
• SWIFT — Standards MT November 2020 — Category 7 Message Reference Guide
• UCP 600 — Uniform Customs and Practice for Documentary Credits (ICC, 2007)