Payment Investigations Migrating to ISO 20022: How Data-Rich Messages Reshape Workflows

Why Payment Investigations Are Entering a New Era

Payment investigations have long been one of the most resource-intensive functions in banking operations. Whenever a payment exception triggers, analysts chase correspondent banks across fragmented channels. They sift through truncated MT messages while manually reconstructing transaction trails across legacy payment systems.  

The financial cost of these operational friction points is substantial. SWIFT estimates that inefficiencies in Exceptions and Investigations (E&I) resolution cost the global banking industry around $1.6 billion each year. In contrast, shifting to modernized, automated E&I processes could unlock as much as $600 million in combined operational and liquidity savings annually.

For institutions still reliant on legacy systems, these figures translate into real operational strain. The effects manifest as rising staffing costs, slower resolution timelines, and operations teams overwhelmed by manual payment investigations.

ISO 20022 addresses the root cause by introducing structured, data-rich messaging as the new operating standard across major payment market infrastructures worldwide. For banks that move beyond basic format compliance and redesign their workflows, the gains are both measurable and immediate.

‍

What ISO 20022 Actually Changes for Payment Investigations Teams

ISO 20022 is not simply an upgrade to the MT format. It represents a fundamental shift in how structured payment data is exchanged and understood.

Under the MT model, critical payment information is compressed into limited free-text fields, creating room for inconsistency, ambiguity, and manual interpretation. ISO 20022 replaces this approach with structured, machine-readable data. Information that once came in a single unstructured field, such as a beneficiary address, is now captured across clearly defined data elements including, street name, building number, postal code, city, and country.

The same advancement applies to remittance data. While an MT103 provides only limited reference information, a pacs.008 message delivers a comprehensive, structured remittance block—including invoice references, line-item details, and tax identifiers.

For payment investigations, this degree of precision is transformative, enabling faster, more accurate resolution.

ISO 20022 also brings standardized investigation messages that support the entire investigation lifecycle including, unable-to-apply queries, value claims, payment recalls, cancellation requests, and resolution confirmations. Each interaction contains structured, auditable data that systems can automatically parse, route, and action while reducing manual effort and accelerating investigation timelines.

The Power of Structured Data in Modern Payment Investigations

How Structured Payment Data Reshapes the Investigation Workflow

Faster case initiation

In MT-based environments, investigations typically begin with unstructured Swift messages that rely heavily on the receiving bank’s interpretation. ISO 20022 payments messages introduce standardized case identifiers, structured party data, and machine-readable reason codes from the outset. This eliminates the need for operations teams to manually reformat or interpret incoming requests before routing them for action.

Automated message classification

With structured data available at source, up to 84% of investigation messages can now be automatically classified into the appropriate case type without human intervention. This marks a significant departure from the manual triage processes that defined legacy payment operations.

Centralized case orchestration through Swift Case Manager

Swift Case Manager adds a centralized orchestration layer for managing exceptions and investigations across institutions. When a creditor initiates an inquiry using a camt.110 message, the platform routes the case to the institution best positioned to resolve it.  

Responses are returned through camt.111 messages, creating a fully auditable case lifecycle with shared visibility across all participants. As of April 2025, more than 170 Case Management subscriptions had been submitted, reflecting accelerating industry adoption of this operating model.

Reduced manual intervention

Payment investigation platforms built for ISO 20022 can automatically ingest and parse structured camt messages. Cases are created or updated as investigation messages arrive, while status changes, timestamps, and resolution actions are tracked in real time. Manual triage, once a major drain on investigator capacity, is increasingly removed from the workflow.

Richer evidence for faster resolution

Structured fields covering debtor and creditor agents, UETR (Unique End-to-End Transaction Reference) tracking, and detailed remittance data give investigators a far more complete view of a payment journey.  

Instead of contacting correspondent banks sequentially to reconstruct transaction history, investigators can access critical evidence directly within the message. As a result, resolution timelines that previously stretched across hours can often be reduced to minutes when complete data is available from the start.

Preparing for the Swift Case Manager Migration Timeline

The SWIFT Case Manager Deadlines Operations Teams Cannot Ignore

The mandatory migration of E&I messages through Swift Case Manager is subject to firm, non-negotiable deadlines. From November 2026, all financial institutions must be capable of receiving camt.110 messages through Case Management. By November 2027, all E&I messages must be exchanged in ISO 20022 formats and, MT messages for these purposes will be retired entirely.

This transition changes the operating model for investigation teams. Serial bilateral message chains give way to a centralized case management layer with real-time visibility into case status, response times, and SLA performance.  

For institutions still running legacy banking systems, these dates represent a concrete operational risk. Legacy payment systems that cannot generate or process camt.110 and camt.111 messages will face increasing disruption as counterparties route investigations exclusively through the Case Management infrastructure.

What Payment Operations Teams Must Do Right Now

Banking technology modernization programs targeting ISO 20022 migration must address several dimensions beyond format conversion.

Workflow redesign is essential

ISO 20022 assumes investigation processes have been redesigned to consume and act on structured payment data. Operations teams need updated procedures, trained investigators, and payment investigation software that can natively support camt workflows.

Data quality governance becomes mission-critical

ISO 20022 payments messages are only as valuable as the data they contain. Institutions that populate structured fields with incomplete, truncated, or unstructured information undermine the operational efficiencies ISO 20022 makes possible. Swift’s Data Quality Analytics gives operations and technology teams the visibility needed to monitor, manage, and continuously improve data quality.

Legacy system remediation remains a critical challenge

For many institutions, legacy banking systems continue to generate MT messages through translation layers, often introducing data truncation and structural inconsistencies. Investigation teams are then forced to compensate for these gaps through manual intervention. Meaningful payment operations transformation requires addressing these issues at the source.

‍