Skip to content

SWIFT Message Error Codes: A Practical Reference Guide

SWIFT message error codes are short identifiers that the network or a receiving bank uses to explain why a payment instruction was rejected, delayed or returned. When a transfer does not go through, these codes are often the first clue about what went wrong.

SWIFT is the global messaging network banks use to send standardized payment instructions to one another. Errors are reported through status messages, return messages and validation reports rather than through a single universal list. The codes below describe typical categories, and the exact wording your bank receives may vary by message type and institution.

Why Payment Messages Sometimes Come Back With Errors

A SWIFT payment message travels through several institutions before the money reaches its destination. Each receiving bank checks the message against formatting rules, sanctions screening requirements, account data and its own internal policies. If any check fails, the message is rejected or returned, and an explanatory code is attached.

Errors are not always a sign of wrongdoing. Many come from simple data problems such as a mistyped account number, a missing field or a bank identifier that no longer matches the directory. Recognizing that most rejections are mechanical can keep a customer calm while the issue is traced.

The sending bank usually receives the error first and then informs the customer. Depending on the institution, the notice may be a message in online banking, an email or a call from a branch. The customer should keep a copy of the payment reference so the bank can locate the transaction quickly.

How Error Codes Are Structured

Most SWIFT-related errors combine a category, a reason and sometimes a field reference. Category tells the reader whether the problem was syntactic, semantic or procedural. Reason gives the specific cause, and the field reference points to the part of the message that triggered the failure.

Think of the structure like a postal address check. The post office first confirms the envelope is properly formatted, then checks that the street exists, and eventually confirms the recipient is at that address. A SWIFT validation error works in a similar layered way.

See also  SWIFT Messaging Workflow: How a Payment Moves Step by Step

Because the wording differs between message types and networks, banks often map internal reason text to the underlying code. Staff can explain the meaning in plain language, which is usually more useful to a customer than the raw identifier.

Common Error Categories Banks Encounter

Errors generally fall into a small number of groups. The following categories cover most situations that customers and staff discuss when a transfer is delayed or returned.

  • Format errors, where a field does not match the required length, character set or structure
  • Invalid account or identifier errors, where the beneficiary account or bank code cannot be matched
  • Missing mandatory information, such as an absent purpose field or incomplete address data
  • Compliance holds, where screening systems pause a payment for review before release
  • Currency or amount issues, such as unsupported currencies or amounts outside a receiving bank’s limits

Knowing which group an error belongs to narrows the search considerably. A format error can usually be fixed by correcting the message and resending it. A compliance hold, by contrast, requires patience, because the bank may need documentation before it can proceed. Staff can tell customers which path applies.

Reading a Return or Reject Message

A return message reverses a payment after it has been accepted, while a reject message stops the payment before it moves further. Both carry reason information, and reading that information carefully saves time. The reference number in the message links it back to the original instruction.

Customers rarely see the raw message, so their bank typically translates it. When reviewing a notice, look for the date, the amount, the reference and the stated reason. If any detail does not match the payment you sent, contact your bank promptly and provide the reference number.

Keep in mind that some returns include a fee or an exchange-rate adjustment. The account agreement and fee schedule explain how these are handled, and it is reasonable to ask the bank to explain any charge applied to a returned payment.

Preventing Errors Before You Send a Payment

Most errors can be prevented with a careful review of payment details before submission. Confirm the beneficiary name exactly as it appears on the account, check the account number character by character, and verify the bank identifier against the recipient’s official information.

Many customers find it helpful to store verified payment details in a secure location, so they do not need to retype them each time. Be cautious about instructions that arrive by email or phone claiming to change account details, since altered details are a common route for misdirected funds.

See also  SWIFT Message Types Explained: A Plain-English Guide

Provide any purpose information the bank requests. Including a clear reason for the payment reduces the chance of a compliance hold and often speeds the process for legitimate transfers.

Working Through Errors Step by Step

When a payment fails, a structured response helps resolve the issue without unnecessary delay. The steps below apply to most situations, although the exact process depends on your bank’s procedures and the type of error involved.

Step One: Gather the Details

Collect the payment reference, the date, the amount and the beneficiary information. Having these details ready allows the bank to locate the transaction in its systems without asking you to repeat everything. Save any notice you received, since it may include the error reason.

Write down exactly when you initiated the payment and which channel you used, such as online banking or a branch. This timeline can help staff determine where the message stopped and whether a resubmission is needed.

Step Two: Ask for the Reason in Plain Language

Request that your bank explain the error in plain language and identify the category it falls under. Ask whether the issue can be corrected by changing the data or whether it requires documentation or a review. A clear answer tells you what action, if any, you need to take.

If the explanation is unclear, politely ask for the specific field or rule involved. Many staff members can show you where the problem appears in the payment details, which makes correction much easier.

Step Three: Correct, Resubmit or Escalate

If the error is a simple data problem, correct the details and ask the bank to resubmit the payment under the proper process. Do not send a duplicate payment on your own, because this can create a second transfer that is harder to reverse. Confirm with the bank before taking any new action.

If the payment is on hold for review, respond promptly to any document requests. If you believe the decision was made in error, you may ask for escalation to a supervisor or review the complaint process described in your account agreement.

Protecting Yourself From Fraud Linked to Failed Payments

Failed or returned payments can sometimes be used as a pretext for scams. Fraudsters may contact customers by phone or email, claim that a transfer was rejected, and ask for login details, one-time codes or payment to a new account. Legitimate banks rarely ask for passwords or verification codes over the phone.

See also  SWIFT Messaging Regulations: A Plain-English Guide

If you receive an unexpected message about a failed payment, verify it independently. Call the bank using the number printed on your card or on its official website, not a number supplied in the message, and ask staff to confirm the transaction details.

Report suspicious contacts to your bank as soon as possible. Quick reporting helps the institution protect other customers and may help limit any financial loss to you.

Questions Banks and Customers Often Raise

A frequent question is whether a rejected payment is charged to the sender. The answer depends on the bank, the reason for the rejection and the account terms. Some institutions refund the amount in full, while others may apply a fee. The account agreement or fee schedule usually explains the policy.

Another common question is how long a corrected payment takes. Processing time varies with the destination, the currency and any review steps. Your bank can give a realistic estimate once it knows the correct details and whether any compliance check remains open.

Customers also ask whether the error will appear on their record. Routine payment rejections generally do not affect a credit report, though the bank’s internal records will reflect the event. Where you are unsure, contacting the bank directly is the most reliable route.

Checklist for Reviewing an Error Notice

When a notice about a failed or returned payment arrives, a short checklist can help you respond accurately. Work through the items below before contacting the bank, so your questions are focused and specific.

  • Confirm the payment reference, amount and date match the transfer you initiated
  • Note the error reason as written, and record the category if the bank provides one
  • Check whether the notice asks you to take action or only provides information
  • Verify the source of the notice by contacting the bank through its official channels
  • Keep copies of all correspondence and any corrected payment instructions you submit

Following this checklist keeps the process orderly and reduces the chance of errors compounding. If anything in the notice conflicts with your records, stop and contact your bank before submitting new instructions or sharing personal information.

Building Better Payment Habits Going Forward

Over time, a simple routine can reduce the number of failed transfers you experience. Keep a verified list of recipient details, confirm changes directly with the recipient through a trusted channel, and review each payment before approving it. These habits protect both accuracy and security.

For businesses and frequent senders, periodic reviews of stored beneficiary information are worthwhile. Accounts change, banks merge or update identifiers, and out-of-date data is a common source of rejected payments. A scheduled check keeps records aligned with current information.

Stay engaged with your bank’s guidance and any updates it publishes about its payment processes. Ask questions when something is unclear, and consult your account agreement for the specific terms that apply to your situation.