Your money is not lost. A Field 56 error means the transfer instruction was sent without specifying the intermediary bank needed to route the payment correctly. Because that routing detail was absent, the payment could not complete its journey and was either rejected before leaving the network or returned from a bank that could not pass it forward.
In SWIFT's message format, Field 56 carries the details of the "Intermediary Institution." This is a bank that sits between your sending bank and the recipient's bank, passing the funds along when those two banks do not have a direct banking relationship with each other. Most international transfers, particularly those between different currency zones or between banks in countries without direct correspondent ties, require at least one intermediary. Field 56 is where that bank's identity is specified. Leave it blank and the payment has no routing path to follow.
Think of it like a flight with a required stopover. If your ticket does not specify the connecting airport, the airline cannot book the leg and the journey stalls. The error does not mean the money evaporated. It means the instruction was incomplete and the network sent the funds back rather than guess at the correct route.
Why This Happens
Field 56 errors are almost always caused by a gap in the transfer instruction. Here are the specific reasons the intermediary bank detail ends up missing:
- Recipient did not provide intermediary bank details. Many people sharing their banking details only provide an account number and BIC. For certain corridors, that is not enough. If the route requires an intermediary bank and the recipient did not include one, Field 56 stays empty.
- Sending bank system did not prompt for intermediary details. Some retail banking platforms and mobile apps do not surface the intermediary bank field to the customer at all. The instruction goes out incomplete because the interface never asked for the information.
- Your bank does not have a direct correspondent relationship with the destination bank. When two banks lack a direct relationship, an intermediary is required to bridge them. If your bank's system cannot automatically identify the correct intermediary for that route, it may send the instruction without Field 56 populated, hoping the network resolves it. It does not.
- Intermediary bank BIC entered incorrectly. The field was populated but with an incorrect or outdated BIC. The network cannot match it to a valid institution and treats it as effectively missing.
- Currency corridor requires a specific clearing bank. USD payments often require routing through a US-based clearing bank like JP Morgan or Citibank. GBP payments may need to route through a UK clearing institution. If the instruction does not specify the required clearing bank in Field 56, the payment fails at the currency clearing stage.
- Bank merger or rebranding made the intermediary BIC obsolete. The intermediary BIC was correct when the sender last used it, but the institution has since merged or rebranded and the old BIC is no longer active. The network rejects the reference and treats the field as invalid.
- Template used from a previous transfer. The sender reused an old transfer template where the intermediary bank had changed since the template was saved. Outdated templates are a common source of this error.
- Third-party payment platform did not pass the full instruction. Some fintech platforms and online transfer services send simplified SWIFT instructions to the underlying bank. If the platform's system does not capture or pass along the intermediary bank detail, it is absent from the transmitted message.
What Happens to Your Money
The outcome depends on where in the chain the error was caught.
Caught at your sending bank before transmission. The payment was flagged internally and never entered the SWIFT network. Your funds are still in your account or in a pending queue at your bank. This is the cleanest scenario. No correspondent fees, no return delay. Your bank contacts you, you provide the missing intermediary details, and the transfer is resubmitted.
Caught by a correspondent bank mid-route. The instruction entered the network, reached a correspondent bank, and was rejected there because Field 56 was missing or unresolvable. The correspondent bank holds the funds briefly and initiates a return message back to your originating bank. The funds travel back through the chain. Expect the return credit in your account within five to ten business days, sometimes longer on complex multi-hop routes.
Caught at the destination bank. The payment reached the recipient's bank but could not be matched to a valid routing path within their system. The destination bank holds the funds and returns them. Same return timeline. Five to ten business days in most cases.
In all scenarios, fees may be deducted. Correspondent banks charge for processing even failed instructions. Your bank may add its own return fee. The amount returned to your account will often be slightly less than what you sent.
If currency conversion was involved, the return is processed at the exchange rate on the return date, not the original send date. Check the current rate using the live exchange rate pages on AbokiCalculator so you can reconcile the numbers when the return arrives.
What to Do Now
- Call your bank's international transfers desk. Not general customer service. Ask specifically for the team handling international or correspondent payments. Tell them you received a Field 56 error and need to know where in the chain the payment was rejected and whether a return has been initiated.
- Get the SWIFT UETR for the original transfer. The UETR (Unique End-to-End Transaction Reference) is the unique tracking code assigned to every SWIFT payment. Your bank can provide this. It tracks the payment's full journey through the network and is what you use to follow up on the return.
- Ask for the exact error code or rejection message. A Field 56 error appears in the SWIFT rejection notice with specific wording, such as "Field 56 missing," "intermediary institution not specified," or "routing BIC unresolvable." The exact phrasing confirms the problem and tells you precisely what was absent from the instruction.
- Get the correct intermediary bank details from the recipient's bank. This is the critical step. Contact the recipient and ask them to call their bank directly and request the following: the name of the intermediary bank required for incoming international transfers in the relevant currency, and that intermediary bank's full BIC/SWIFT code. Do not guess. Do not use an intermediary BIC from a previous transfer without confirming it is still current.
- Verify the intermediary BIC before resending. Once you have the intermediary bank's BIC, check it using the SWIFT lookup tool on AbokiCalculator. Confirm it is active, assigned to the correct institution, and appropriate for the currency and country in question. An intermediary BIC that was valid two years ago may have changed due to a merger or restructure.
- Wait for the return credit before resending. Do not submit a new transfer instruction until the original payment has cleared the return process and the funds are confirmed back in your account. Sending a second instruction while the first is still in the return chain creates a duplicate that is complicated to unwind.
- Rebuild the transfer instruction from scratch. When you are ready to resend, do not copy the old instruction and patch it. Start a new transfer and enter all fields cleanly, including Field 56 with the confirmed intermediary bank BIC. Ask your bank to confirm Field 56 is populated in the outgoing message before they transmit it.
- Follow up if the return has not arrived within fifteen business days. Provide your bank with the UETR and ask them to trace the return through the SWIFT gpi system. Returns stall occasionally and a formal trace request is the fastest way to locate and release them.
How to Avoid This Next Time
Ask the recipient for complete banking details before every transfer. This means more than an account number or IBAN. For international transfers, you need the recipient's BIC/SWIFT code, the name and BIC of any required intermediary bank for the specific currency, and any local routing codes required by the destination country such as an ABA routing number for USD, a sort code for GBP, or a BSB for AUD. Ask the recipient to confirm these details directly with their bank, not from memory or an old document.
Verify every BIC in the instruction, including the intermediary. Before submitting any international transfer, check all BICs using the SWIFT lookup tool on AbokiCalculator. This applies to the beneficiary bank BIC in Field 57 and the intermediary bank BIC in Field 56. Both need to be active and correctly assigned. A two-minute check on both codes before sending eliminates the most common source of Field 56 and Field 57 errors.
Ask your bank directly about intermediary requirements for the destination corridor. Different currency routes require different intermediary setups. Before initiating a transfer to a new country or in a new currency for the first time, call your bank and ask: "Does this route require an intermediary bank, and if so, which one do you use and what is their BIC?" Your bank knows their correspondent network. Getting this information upfront costs five minutes and prevents the entire problem.
