3. Enquiry and Investigation (E&I) messages in MX format
Changes to Enquiries and Investigation (E&I) messages have been deferred to Q1 2027; the mandate to receive camt.110 will be implemented with the SR2026 deferred partial release in Q1 2027.
Enquiry & Investigation (E&I) and Swift Case Management
J.P. Morgan supports the industry's transition towards structured Enquiry & Investigation (E&I) messaging and recognises the significant benefits of Swift’s Case Management solution in enabling greater automation, transparency, and faster resolution of payment enquiries.
Since 2025, J.P. Morgan has participated in the Swift CASE Pilot alongside more than 40 financial institutions. Through this collaborative effort, participants have tested enquiry workflows and message structures to validate data sufficiency and support increased straight-through processing wherever possible.
The results to date reinforce our view that Case Management represents an important step forward for the industry, helping to reduce operational complexity, improve efficiency, and accelerate the resolution of payment enquiries.
As the industry progresses towards broader adoption, J.P. Morgan continues to expand its participation in the pilot while evaluating the most effective approach for scaling the solution across our global businesses and branches. During this transition period, we will continue to support existing enquiry processes, including MT199-based interactions where required, to ensure continuity for counterparties as industry adoption evolves.
Industry readiness
J.P. Morgan encourages all Swift participants to prepare for upcoming industry milestones:
Mandate to send camt.110 and camt.111 messages, reducing reliance on MT199 messages for enquiry workflows.
Mandate to route Stop and Recall requests through the Swift central tracking service.
Our commitment
J.P. Morgan remains an active participant in the Swift CASE Pilot and is continuing to expand testing activities beyond the initial business scenarios and BICs. We remain committed to supporting industry adoption and helping drive the transition towards a more efficient, standardised, and automated approach to payment enquiries and investigations.
Swift resources supporting E&I migration:
ISO 20022 is a universal financial messaging framework for payments that leverages structured data fields to standardize cross-border payments, enhancing efficiency, reducing errors and facilitating global insights.
- Banks and non-bank financial institutions connected to the Swift FINPlus platform must align with Swift’s end of coexistence roadmap and J.P. Morgan’s adoption schedule. Continue to plan and budget for ISO changes, including end of unstructured address, prioritizing interoperability across cross-border payments and PMIs, and stay informed on evolving market practices while following industry guidance.
- Banks, non-bank financial institutions and corporate Swift members who connect to J.P. Morgan via proprietary channels should continue to prepare for the removal of unstructured address data and migration to the new standards/requirements. Prepare to adopt the ISO 20022 standard soon, and evaluate the benefits of enhanced data and how your business will use it.
- Corporate Swift members who connect via Swift SCORE (Swift Standardized Corporate Environment) or a CUG (Closed User Group), may use MT101; however, they may continue to update payment messages to meet hybrid address requirements by using the F-tag. J.P. Morgan is currently reviewing the possibility of supporting pain.001 via Swift SCOREPlus in 2026, despite recent changes to the Swift release schedule.
Example using the MT101 Field 59 (F-option) format for a hybrid postal address:
:59F:/BE30001216371411
1/JOHN SMITH
2/HOOGSTRAAT 6, 18TH FLOOR
3/BE/BRUSSELS
Where: 1/= Name (JOHN SMITH), 2/=Address Line (HOOGSTRAAT 6, 18TH FLOOR), 3/=Country Code (BE), Town Name (BRUSSELS),
If agents are identified by name and postal address in MT messages, use the D option. This approach ensures frictionless processing by the Debtor Agent upon receipt, aligning with best practices for address data submission.
Some local payment methods, such as domestic transfers or SEPA, may still allow the initiation of payments using MT101 fields 50/59 with unstructured data. However, when address details are provided in an unstructured format, the bank processing the transaction will not be able to pass on these details. This limitation could lead to payment delays, rejections, or costly follow-up inquiries, especially for cross-border payments where structured address information is required.
- FI/NBFI Swift Users, if you use native MX messages, you should no longer have truncation issues. Swift users leveraging contingency translation may still see the impact of truncation. In particular, name and address data may be truncated. Where possible, we’ll provide a ‘+’ symbol as an indication of where truncation has occurred. Incoming funds may be paid to your account via MX messages, which may include enhanced information that could be truncated or omitted within existing reporting formats. Adopting the ISO-enabled reporting options will help mitigate these impacts. It’s important to start developing your implementation plan for camt. messages.
What clients should continue to do
