---
title: "ISO 20022 | Skills We Assign For | Azendo"
description: "ISO 20022 for payment messaging — richer data, migration, plus the Azendo roles assigned for it."
url: "https://azendo.co/skills/iso-20022/"
---

[Skills](https://azendo.co/skills/) APIs and integration 

# ISO 20022.

ISO 20022 is the international standard for financial messaging, using structured XML with a common data dictionary. It is replacing older formats across payment systems including SWIFT, SEPA and domestic schemes.

## Where ISO 20022 fits on a long engagement.

The migration is mandated rather than optional, with scheme deadlines that have already passed for some systems and are approaching for others. It is a compliance programme for banks and payment providers rather than a modernisation they chose.

The richer data is the genuine benefit. Structured remittance information, proper party identification and extended references mean a payment carries context that legacy formats truncated — which improves reconciliation and reduces the manual investigation that truncated references cause.

## What an assigned team does with ISO 20022.

Coexistence is the hard part in practice. During migration, systems must handle both the new format and legacy messages, and translating between them loses data in one direction because the older format cannot carry the richer fields.

Designing for that asymmetry rather than assuming a clean cutover is the realistic approach, and it is part of how migration scope is agreed in [how the monthly fee is built](https://azendo.co/pricing/).

## What we use ISO 20022 for.

* Scheme deadlines met Migration delivered against the mandated dates rather than deferred.
* Richer remittance data used Structured references improving reconciliation rather than merely being carried.
* Coexistence handled honestly Translation designed with its data loss acknowledged rather than assumed away.

## How ISO 20022 capacity is assigned.

Financial messaging work is assigned inside development capacity, with coexistence between formats planned rather than treated as a cutover.

## Industries that ask for it

* [Financial services and fintech](https://azendo.co/industries/financial-services-and-fintech/)

## Related in apis and integration

* [REST — skill we assign for](https://azendo.co/skills/rest/)
* [GraphQL — skill we assign for](https://azendo.co/skills/graphql/)
* [gRPC — skill we assign for](https://azendo.co/skills/grpc/)
* [webhooks — skill we assign for](https://azendo.co/skills/webhooks/)
* [Kafka — skill we assign for](https://azendo.co/skills/kafka/)
* [API design — skill we assign for](https://azendo.co/skills/api-design/)
* [message queues — skill we assign for](https://azendo.co/skills/message-queues/)
* [FastAPI — skill we assign for](https://azendo.co/skills/fastapi/)

## Tell us what your roadmap needs ISO 20022 for.

A service delivery manager replies with the disciplines we would assign, the monthly capacity and what the first month looks like.

[All skills we assign for](https://azendo.co/skills/)