The end of the SWIFT MT/ISO 20022 coexistence period marked a major migration milestone for financial institutions, but migration alone does not guarantee business value. Deutsche Bank reports that 97% of payment instructions are now exchanged in ISO 20022, yet only 39% of respondents have seen tangible benefits, while 45% have not. The next question for banks is therefore less about compliance and more about how they use structured payments data to improve operations, manage risk, and make better financial decisions.
What should banks do with ISO 20022 data after migration?
As banks move beyond the core ISO 20022 migration phase, they need to make the resulting data usable, trustworthy, and accessible across the organisation. Simply carrying richer information through a new message format does not create value; banks need to make that information usable across the processes that depend on it.
Preserve the richness of structured payments data
Banks need to protect data quality throughout the payment lifecycle. Legacy systems, inconsistent field mapping, incomplete information, and translation processes can still strip away some of the detail that makes ISO 20022 valuable.
That makes post-migration data governance a business priority. Banks should:
- Validate important payment information at source.
- Monitor where data becomes incomplete or loses structure.
- Maintain consistent mappings across downstream systems.
- Establish clear ownership for payment-data quality.
Connect data to enterprise processes
The value of structured payments data depends on what banks do with it after a transaction enters the organisation. Rather than keeping richer payment information within the payments function, banks can connect it to the systems and teams responsible for risk, operations, finance, and customer outcomes.
KPMG’s 2026 Partnering for Payment Modernization report shows that this shift is already underway: 44% of banks are focusing on monetising enriched payment data through new products and services, while 43% are enhancing upstream and downstream systems to make greater use of structured data. The message is clear: ISO 20022 migration creates the data foundation, but banks need to embed that data across enterprise processes to turn compliance into measurable value.
How does structured payments data improve fraud detection and reconciliation?
Richer payment information can strengthen controls and reduce operational friction, but the benefit does not happen automatically. Banks need to connect the additional data fields to the systems and processes responsible for detecting risk, resolving exceptions, and matching transactions.
Give risk controls better context
Structured payment data can give fraud, AML, and sanctions-screening systems richer and more consistent information to assess transactions. When banks capture and preserve that information end to end, risk teams can apply more context to transaction monitoring, reduce unnecessary investigations, and focus analysts on higher-risk activity.
KPMG reports that banks using ISO 20022 have reported reviewing around 84% of payment messages through automation and reducing false positives by 25–30%. These figures do not mean ISO 20022 migration alone produces these outcomes. Rather, they illustrate the potential gains when banks combine richer payment information with automated risk controls that can interpret and act on it.
Reduce reconciliation and exception-management effort
Reconciliation benefits from the same improvement in data quality. More complete remittance and transaction information can make it easier to match payments with invoices, accounts, or other records. Better matching can reduce manual investigation, payment repairs, and exception handling, while supporting higher straight-through processing.
The opportunity is therefore broader than faster payment processing. Structured payments data can help banks reduce the operational effort required to understand and resolve payment exceptions.
How can treasury teams use ISO 20022 data?
Treasury teams can take the value of structured payments data a step further. Instead of treating payment information as a record of completed transactions, they can use richer data to improve visibility into cash movements and support forward-looking financial decisions.
Improve cash-flow and liquidity visibility
More granular payment information can help treasury teams understand:
- Incoming and outgoing payment flows
- Cash positions and movements
- Payment timing and patterns
- Short-term liquidity requirements
- Cash-flow forecasts
This richer information can make it easier to identify emerging funding needs and understand how money moves across accounts, entities, and payment corridors.
Turn payment information into financial intelligence
The strategic opportunity emerges when banks aggregate and analyse payment information over time. Treasury teams can identify recurring payment patterns, anticipate cash requirements, and support working-capital decisions with more timely information.
That shifts the role of payment data from transaction record to decision input. This supports more proactive liquidity planning, better forecasting, and a clearer view of the organisation’s financial position.
Turning ISO 20022 data into operational value requires more than a compliant message format. Infosys BPM brings financial-services expertise across payments processing, reconciliation, exception management, fraud, AML/KYC, transaction monitoring, and process transformation. Its BPM solutions for financial services can help organisations embed payment data into processes such as reconciliation, exception management, compliance, and transaction monitoring, turning richer information into measurable operational value.
Make ISO 20022 migration the starting point, not the finish line
The most important measure of ISO 20022 migration should not be whether messages meet the standard, but whether banks can extract sustained value from the information those messages carry. Structured data still depends on disciplined capture, validation, and governance. Banks that build those capabilities can turn a compliance milestone into a foundation for stronger controls, leaner operations, and more informed financial decisions.
Frequently asked questions
MT messages carry payment details in short, fixed-length fields; ISO 20022 carries them as structured XML with far more room and defined data elements. The practical consequence is that information that had to be compressed into free text under MT—including full party names and addresses, remittance details, and purpose codes—now arrives as separate, machine-readable fields that downstream systems can act on without parsing.
Three families cover most day-to-day activity: pain messages for customer payment initiation, pacs messages for interbank clearing and settlement, and camt messages for cash management, statements, and reporting. Knowing which family carries which data matters when tracing where detail is lost between systems.
Truncation is the loss of data when a rich ISO 20022 message passes through a system that cannot hold all of it, typically a legacy platform mapped to shorter MT-era fields. The message still settles, so nothing appears to fail, but the remittance detail or party information that would have improved screening and reconciliation is gone by the time downstream teams see it.
Ownership works best when it sits with the business process that consumes the data rather than with the payments platform alone. Payments operations owns capture and validation at source, while risk, reconciliation and treasury each own the fields they depend on. Assigning quality solely to IT tends to produce monitoring without anyone accountable for fixing the upstream cause.
Corporates receive richer remittance information alongside the payment, so more incoming cash can be matched to open invoices automatically instead of being investigated manually. That reduces unapplied cash, shortens the collections cycle, and gives treasury a more accurate near-term view of what has actually been received.


