SWIFT Error Codes Overview (NACK, Routing, Business Rejects)

SWIFT is a messaging network. Errors may occur before business processing (format), during routing (correspondent or intermediary logic), or during beneficiary-side processing (business reason such as funds or account status). In SEPA, returns are typically scheme-level reason codes (e.g. R01, R02) issued by the debtor or beneficiary bank. In SWIFT, you commonly see a NACK at the network or gateway when the message fails format or structural validation — that is distinct from a business reject returned later by the beneficiary. A SWIFT NACK is not the same as a business reject. NACK indicates the message was not accepted for processing; a business reject indicates the payment was processed but could not be completed (e.g. insufficient funds, account closed). Treating them separately in triage and monitoring avoids misdiagnosis and speeds resolution.

Commonly observed stages where errors surface:

1. Submission → Network validation (format). Invalid BIC, missing or malformed fields (e.g. field 59), or message-type issues typically produce a NACK at this stage. The message does not progress to routing or processing.
2. Gateway → Intermediary validation. Routing and correspondent logic (e.g. field 56/57, nostro alignment) can cause rejections or returns at the intermediary hop. The message may have passed format checks but fails routing or relationship rules.
3. Beneficiary bank processing. Business-level outcomes — insufficient funds, account closed, compliance blocks — are typically signalled here. The message reached the beneficiary; the reject is a business decision, not a format or routing failure.
4. Settlement / posting. Final settlement or posting failures may generate further status or return messages. Timing and status flows (e.g. pacs.002 in ISO 20022) help distinguish accepted vs settled vs rejected.

Mapping the error category to the correct stage (network, intermediary, beneficiary, settlement) is essential for correct triage and escalation.

• Confirm whether you received a NACK or a business return. NACK = message not accepted; business return = processed but not completed.
• Identify the stage: network vs intermediary vs beneficiary. Use the typical signals and “where it occurs” from the table to narrow it down.
• Extract the exact reason text or code from the NACK or return message. This drives the next step (format fix, routing fix, or client/beneficiary follow-up).
• Check BIC, field formatting, and routing fields (56/57) when the failure is at network or intermediary stage. Commonly observed scenarios include invalid BIC, missing beneficiary, or nostro mismatch.
• Confirm whether the issue is structural (format, routing) or business (funds, account, compliance). Structural issues are corrected and resubmitted; business issues may require funding, account update, or compliance resolution.

Cross-cluster links to detailed references:

• SWIFT NACK – Format Error → /swift/nack-format-error
• Intermediary Routing Failure → /swift/intermediary-routing-failure
• IBAN Validation Failure → /validation/iban-validation-failure
• SEPA R01 – Insufficient Funds → /sepa/r01-insufficient-funds