Birbal AI

ISO 20022 and SWIFT MX migration

ISO 20022 migration for UAE banks and payment firms, from message mapping to structured addresses.

Swift ended MT and ISO 20022 coexistence for cross-border payment instructions on 22 November 2025, Aani is built on ISO 20022, and structured postal addresses are next. Birbal AI maps your payment flows, structures customer address data in Arabic and English, updates the systems that create and read payment messages, and tests every flow end to end.

  • MT to MX message mapping
  • Structured addresses
  • Core and channel changes
  • End-to-end testing

Payment data, end to end

Structured at the source
1Customer dataNames and addresses structured where they are captured
2Initiationpain.001 from channels and corporate payment files
3Interbankpacs.008 and pacs.009 on Swift
4Reportingcamt.053 and camt.054 into reconciliation
CBPR+AaniArabic and English
Illustrative flow, simplified

Authorized vendor to

  • Ministry of Finance
  • Ministry of Interior
  • DGE Abu Dhabi
  • Etihad Aviation
  • EDGE Group

Delivered for

  • Hindustan Unilever
  • Nokia
  • Linde
  • USA Today
  • JSL

Procurement-ready

  • Emirati national company
  • National ICV certificate
  • Abu Dhabi Government Procurement Gate
  • UAE Ministry of Finance, federal procurement
  • Registered ADNOC vendor

Where things stand

The ISO 20022 dates that matter now

As published by Swift and Al Etihad Payments, checked on 19 November 2026.

22 November 2025: MT coexistence ended

Swift ended the coexistence of MT and ISO 20022 for cross-border payment instructions between financial institutions, so ISO 20022 is now required for them. Swift reports that more than 98% of payment instructions are sent in ISO 20022.

Structured addresses: deferred, not dropped

Swift had planned to stop accepting fully unstructured postal addresses in payment messages from 14 November 2026. On 27 August 2026 it deferred all payments changes in Standards Release 2026, this one included, and said it would set the new timing by December 2026 at the latest.

12 June 2027: the rest of the deferred release

The deferred Standards Release 2026 goes live on 12 June 2027 for MT messages other than Category 1 and for ISO 20022 securities, funds, tracker, and exceptions and investigations messages.

Aani runs on ISO 20022

Al Etihad Payments, which operates Aani, the UAE's instant payments platform, says the ISO 20022 standard is at the core of Aani's design.

What we do

What an ISO 20022 programme needs

Message mapping

Each flow mapped from MT to ISO 20022 under the CBPR+ usage guidelines: MT103 to pacs.008, MT202 and MT202 COV to pacs.009, MT101 to pain.001, MT940 and MT950 to camt.053, and MT900 and MT910 to camt.054.

Structured addresses

Customer and counterparty addresses split into town, country and the other structured fields with rules and AI that read Arabic and English, and staff checking what the rules can't settle.

Core and channel changes

Changes to the core banking system, payment hub, digital banking and corporate file formats wherever they create or read payment messages.

Screening and reconciliation

Sanctions screening and reconciliation that use the richer ISO 20022 fields instead of truncated MT text.

Testing

Test cases for each flow, including rejects, returns and investigations, run well before your release dates.

Data quality tracking

Dashboards showing how many customer records and outgoing payments still carry unstructured addresses, by channel and branch.

In the UAE

Where ISO 20022 shows up in a UAE institution

Cross-border payments

Payment instructions to and from correspondent banks on Swift, under the CBPR+ usage guidelines.

Aani instant payments

Instant payments through Aani from your mobile and online banking, on a platform built on ISO 20022.

Corporate clients

Payment files and statements for corporate clients' ERP systems: pain.001 in, camt.053 and camt.054 out.

How we work

From inventory to go-live

  1. 01

    Assess

    We list every system and channel that creates, changes or reads a payment message, and measure address quality in your customer data.

  2. 02

    Plan

    A plan by flow and system, aligned with Swift's dates and what your correspondent banks ask of you.

  3. 03

    Build and clean

    Mapping, system changes and address structuring, with your teams approving every data fix.

  4. 04

    Test and go live

    End-to-end tests, then release in waves, with rejects and repairs monitored after go-live.

Why Birbal AI

A UAE team for payment data and systems

An Emirati national company

ICV certified, with our office and development center in Al Zahiya, Abu Dhabi.

Data stays in the UAE

We deploy on your own servers or in UAE data centers, with open-weight models when the data can't leave.

People decide

Our systems prepare, score and recommend; your staff approve, with every action logged.

You own the work

Code, configurations and documentation are transferred to you on delivery, with NDAs as standard.

Free estimate

Get a free ISO 20022 migration estimate in 48 hours

Tell us which payment flows and systems are in scope and where you are today. You get a scope, timeline and cost range within 48 hours, then a fixed-price proposal after a short discovery.

  • Free and no obligation
  • Mapping, data and systems
  • NDA on request

4.9/5 average rating · 98% client satisfaction · 150+ clients served

Free ISO 20022 migration estimate

We only use your details to reply to you. Arabic or English, as you prefer.

FAQ

ISO 20022 migration: questions banks and payment firms ask

What is ISO 20022?

An international standard for financial messages, written in XML, that carries richer and more structured data than the older Swift MT format. The Swift community chose it for cross-border payments and reporting in 2018, and instant payment systems such as Aani use it too.

Is the MT to MX migration finished?

For cross-border payment instructions between financial institutions on Swift, yes: coexistence ended on 22 November 2025. The work that remains is structured addresses, the deferred Standards Release 2026 and internal systems that still work with MT-style data.

When will unstructured addresses stop being accepted?

Swift had planned 14 November 2026, then deferred all payments changes in Standards Release 2026 on 27 August 2026 and said it would set the new timing by December 2026 at the latest. The direction hasn't changed: fully structured or hybrid addresses, with at least town and country in their own fields.

Can you structure Arabic addresses?

Yes. We use rules and AI to split Arabic and English addresses into structured fields, flag what can't be resolved, and leave the final say to your staff.

Do you change our core banking system?

Where it creates or reads payment messages, yes, through your change process. Our Temenos and Finacle developers work on the core, and we update payment hubs, channels and file formats around it.

Does ISO 20022 affect our corporate clients?

Yes, if they send payment files or read statements. Corporate payment files map to pain.001, and statements and notifications to camt.053 and camt.054, and their addresses need the same structure.

Get your payment messages and data ready

Get a scope, timeline and cost range within 48 hours.

Get a free estimate