If you are sending money to Israel for a home purchase, an investment, or family support, the rules of the wire just changed. Since November 22, 2025, SWIFT’s new ISO 20022 message format is the default, forcing banks to send richer, structured data or face rejections, delays, and new fees.
What just changed, in plain terms
- ISO 20022 is now the required “language” for many SWIFT cross-border payment instructions.
- Banks still leaning on older MT formats face tighter validations, conversion limits, and potential message failures.
- Translation fallbacks that used to feel “free” become billable starting January 1, 2026.
- Israel’s central bank has been pushing ISO 20022 locally, positioning Israel to operate in the same modern format as advanced markets.
- A US escrow rule fight is bubbling again, and it can change costs and paperwork for Israel-linked property flows that touch US banks.
MX replaces MT on SWIFT, and Israel is in the flow
On November 22, 2025, the SWIFT network’s coexistence period ended, shifting cross-border payment instructions to ISO 20022 “MX” messages instead of legacy “MT” messages. ISO 20022 is a global standard that carries structured payment data. Israel is not a bystander: the Bank of Israel describes ISO 20022 adoption locally using the SWIFT IAP format.
For Israel-linked transfers, this is a practical change, not a slogan. ISO 20022 supports richer, more granular data, and SWIFT lists benefits including better automation and more accurate compliance processes. That matters in a market where cross-border flows are routine, from diaspora buyers to Israeli exporters.
Could your Israel-bound MT payment be rejected?
Banks that treat the change as “just a format conversion” are the ones likely to feel pain. BNY Mellon’s guidance warns that, from November 22, 2025, SWIFT permanently removes certain MT payment message types, meaning they will be rejected. Rejection often shows up as a “NAK,” short for negative acknowledgement.
BNY’s note also lays out a second category: some MT messages are pushed into contingency processing, where they may be converted into ISO 20022 equivalents if they pass stricter validations. If they fail the enhanced checks, they can be NAK’ed. For senders, that means fixing inputs, not arguing with the network.
Translation is now a paid crutch
The safety nets are changing shape, and price. SWIFT says its in-flow translation service becomes chargeable from January 1, 2026 for payment instruction messages, and it is enabled by default unless institutions opt out. That flips “temporary workaround” into a recurring cost for laggards.
There is also a data quality risk. SWIFT warns that translating MX back to MT can cause truncation or data loss when the older format has shorter fields or no equivalent fields. In cross-border Israel-linked transactions, that is where banks tend to ask follow-up questions, slowing settlement.
Does richer data mean tougher compliance questions?
ISO 20022’s promise is better data, but better data cuts both ways. SWIFT highlights more granular information and more accurate compliance processes, which can reduce manual intervention while strengthening automated screening. AML means anti-money laundering checks. KYC means knowing the customer. KYT means knowing the transaction.
The news update behind this report also notes that it did not identify new AML-specific cross-border wire circulars from the Bank of Israel or IMPA after mid-December 2025. Public Bank of Israel circular listings show the most recent AML risk-management circular dated December 31, 2024, suggesting the shift is operational, not a new rulebook.
FX providers race to smooth the new rails
Banks are not the only players under pressure. The update flags ongoing policy and product changes among cross-border payment and FX providers as the new data-rich rails become normal. The direction of travel is clear: providers are competing on speed, transparency, and fewer intermediaries, because customers expect cross-border payments to behave like modern digital services.
For Israel, this competition is strategically positive. It increases corridor resilience and offers more routes for legitimate inflows, especially when traditional correspondent banking can be slow or conservative. The practical takeaway is simple: the provider you choose can determine how much of ISO 20022’s “better data” actually shows up in the payment.
Will US escrow rule changes ripple into Israel transactions?
A separate, quieter fight in Washington can still touch Israel property flows. In late December 2025, the US Office of the Comptroller of the Currency proposed steps to preempt certain state “interest-on-escrow” laws, and to reinforce national banks’ flexibility over whether to pay interest or assess fees on real estate escrow accounts.
Escrow is a holding account used in transactions, often in real estate, to protect both sides. The Federal Register notice sets a comment deadline of January 29, 2026. These proposals are not final, but they can change the economics and disclosures for US-based escrow arrangements that later move funds to Israel.
| Development | What changed | Israel-linked impact |
|---|---|---|
| SWIFT ISO 20022 go-live | ISO 20022 became the default for cross-border payment instructions after Nov 22, 2025. | More structured data is expected on inbound wires to Israel, reducing ambiguity when done correctly. |
| Rejections and contingencies | Some MT message types are withdrawn and rejected; others face contingency conversion with stricter validations. | Israel-bound payments can fail faster when legacy fields are incomplete or noncompliant. |
| Translation becomes billable | In-flow translation becomes chargeable from Jan 1, 2026, and is on by default unless opted out. | Hidden costs and higher friction for banks and counterparties not ISO-native. |
| US escrow proposals | OCC proposes to protect bank flexibility on interest and fees in real estate escrow accounts. | US-based escrow used in Israel purchases may see fee and disclosure changes. |
| Summary | Payments are becoming more data-driven, more automated, and less forgiving. | Israel’s alignment with ISO 20022 is a competitive advantage, but senders must get details right. |
What to do before sending money to Israel
- Ask your bank or provider whether the payment will be sent in ISO 20022 MX format end to end, not just “converted.”
- Provide complete, consistent originator and beneficiary details, matching names and identifiers across documents.
- If a bank relies on in-flow translation, confirm whether translation charges will apply from January 1, 2026 and who pays them.
- For property transactions touching US escrow, request a clear fee and interest treatment summary in writing, since rules are under review.
Glossary
-
ISO 20022: A global standard for payment messages that carries structured, richer data than older formats, used for cross-border payment instructions on SWIFT.
-
SWIFT: The global financial messaging network banks use to exchange standardized instructions for payments and other financial messages.
-
MT and MX: MT refers to legacy SWIFT message types; MX refers to ISO 20022 messages, typically XML-based and more structured.
-
FINplus: A SWIFT service used to exchange ISO 20022 messages for payments and other domains, referenced in end-of-coexistence guidance.
-
In-flow translation: A SWIFT service that can deliver an ISO 20022 message with an embedded MT equivalent for receivers not ready to consume ISO 20022 natively, with charges starting in 2026.
-
Contingency processing: A temporary SWIFT fallback that converts certain MT payment messages into ISO 20022 equivalents under stricter validation rules, intended for short-term continuity.
-
Escrow account: A holding account, often used in real estate, that keeps funds under controlled terms until conditions of a transaction are met.
Methodology
This report is based on the provided news update and cross-checked against primary sources: SWIFT’s ISO 20022 migration and translation-service documentation, Bank of Israel publications on ISO 20022 adoption, and US OCC bulletins plus the Federal Register notice on escrow-related proposals.
FAQ
What exactly happened on November 22, 2025?
The coexistence period ended. For cross-border payment instructions in scope, ISO 20022 MX became the required format, replacing routine use of older MT payment message flows.
Can someone still send an MT103 to an Israeli bank?
Some MT payment messages are subject to contingency conversion, but others are withdrawn and rejected. Even where conversion exists, stricter validations apply, and failures can be NAK’ed. The safest assumption is that the payment needs ISO 20022 readiness on the sending side.
Why are banks asking for more details on wires to Israel?
ISO 20022 supports richer, structured fields. That improves automation and compliance screening, but it also means missing or inconsistent data stands out faster and triggers follow-ups. Translation back to MT can also truncate data, creating avoidable ambiguity.
What is the practical meaning of “translation charges” in 2026?
SWIFT says in-flow translation becomes chargeable from January 1, 2026 for payment instruction messages, and it is enabled by default unless opted out. That can turn legacy processing into a measurable per-message cost for some institutions.
Do the US escrow proposals affect Israel real estate purchases?
Potentially, when the funds move through US-based escrow or mortgage escrow arrangements. The proposals aim to preserve national banks’ flexibility on whether to pay interest and assess fees, and the Federal Register sets a January 29, 2026 comment deadline. It is still a proposal, not a final rule.
Is Israel prepared for ISO 20022?
The Bank of Israel has been promoting ISO 20022 adoption in Israel and describes benefits like faster, more precise transfers and improved efficiency. That alignment helps Israel interact smoothly with global payment modernization, provided senders supply high-quality data.
What happens next
For Israel-linked transactions, the winning move is operational discipline: treat payment data like part of the deal terms. Confirm your sending route is ISO 20022-capable, avoid reliance on paid translation fallbacks, and document escrow fee and interest terms when US banks are involved. Those steps reduce delays that no one can “negotiate away” once the wire is in motion.
The bottom line for Israel-linked cross-border payments
- ISO 20022 is now the standard format for key SWIFT cross-border payment instructions after November 22, 2025.
- Stricter validations and message withdrawals make sloppy legacy MT inputs more likely to fail.
- In-flow translation becomes chargeable from January 1, 2026, making “temporary” workarounds expensive.
- Israel’s ISO 20022 alignment is a strength, but only if senders provide clean, consistent data.
- US escrow proposals are a separate variable worth watching for Israel transactions routed through US banking infrastructure.
