An MT103 is a SWIFT payment message that banks use to instruct and confirm an international wire transfer, and it has long served as the standard proof of payment for cross-border transactions. When you need to trace a payment or resolve a dispute in 2026, prioritize the UETR and a SWIFT Tracker status over a PDF screenshot of the message itself, since banks may now issue an ISO 20022 confirmation instead of a classic MT103.
TL;DR:
- Tracking payments with the UETR and SWIFT Tracker provides real-time status updates and speeds up dispute resolution compared to static screenshots.
- Requesting “the SWIFT or ISO 20022 payment confirmation and the UETR” ensures you cover all formats after the migration deadline, avoiding reliance on outdated MT103 documents.
- Accurate field entry, especially for sender, receiver, and amounts, is critical to prevent delays or rejections in cross-border payments.
- Banks now often issue ISO 20022 confirmations instead of MT103s, so asking for the confirmation along with the UETR is essential for effective tracing.
- Building internal workflows that prioritize UETR and field-20 references will streamline disputes and reconciliation processes throughout 2026.
Demivoltdemivolt.comSimplify Cross-Border Payment OperationsDemivolt gives modern businesses compliant infrastructure for IBAN accounts, SEPA and SWIFT payments, and controlled business expenses.Explore Demivolt
Table of Contents
- What an MT103 Message Contains and How to Read It
- When You Actually Need an MT103 for Proof or Disputes
- How to Request an MT103 or Payment Investigation
- ISO 20022 Migration: What to Ask for Instead of “MT103”
- Field Accuracy and Process Habits That Prevent Delays
- How Demivolt Supports Compliant SWIFT and ISO 20022 Workflows
- Standardizing Around UETR-First Workflows in 2026
- How Demivolt Can Help With SWIFT and SEPA Payments
- Where to Verify These Details Yourself
- Sources
- FAQ
What an MT103 Message Contains and How to Read It
An MT103 is built from structured fields, each identified by a numeric tag, that together tell a bank exactly who sent money, who should receive it, and under what terms. Field 20 carries the sender’s reference, a unique code your bank assigns to the transaction that you will need whenever you follow up on a payment.
The fields that matter most for tracing and disputes are:
- Field 32A: the value date, currency, and amount actually being transferred.
- Field 50a: the ordering customer, meaning the person or business that sent the payment.
- Field 59a: the beneficiary, the account and name receiving the funds.
- Field 71A: how charges are allocated between sender and receiver.
- Field 121: the UETR, a unique identifier attached to the transaction.
Every MT103 variant, such as MT103 STP and MT103 REMIT, carries a UETR in field 121, which SWIFT’s Tracker uses to follow the payment end to end. MT103 STP is a stricter version meant for automated, straight-through processing, with tighter field formatting and fewer optional entries. MT103 REMIT separates out remittance information into a linked message so the payment instruction itself stays lean. Knowing which variant your bank generated helps you understand why a confirmation might look slightly different from one transfer to the next, even when the underlying payment logic is the same.
When You Actually Need an MT103 for Proof or Disputes
Finance teams typically ask for an MT103 or its equivalent in three situations: a beneficiary claims a payment never arrived, a reconciliation report shows a gap between what left your account and what was recorded as received, or a regulator or auditor requests documented evidence of a specific transaction.
An MT103 or its ISO 20022 counterpart, pacs.008, shows the routing path, the charges applied, and the amount actually credited to the beneficiary, which makes it useful for confirming what happened to a specific payment. What it cannot do, especially as a static screenshot, is proved the current status of that payment inside the banking network.
- A screenshot only shows the instruction as sent, not what happened afterward.
- A Tracker or UETR-based confirmation shows live or recorded status, including whether funds were credited or rejected.
- Disputes resolved with Tracker evidence tend to move faster because the data is verifiable at the source rather than visually copied.
For anyone building a habit around this, our guide on tracking an international wire transfer walks through the UETR and Tracker mechanics in more depth.
How to Request an MT103 or Payment Investigation
When a payment needs tracing, start with the bank or regulated payment provider that sent it, since only the sending institution can initiate a Tracker check on your behalf.
- Contact your sending bank or provider directly rather than the beneficiary’s bank, which typically cannot open an investigation from its side alone.
- Provide the UETR (field 121) and the sender’s reference (field 20) together, since SWIFT’s Tracker searches by UETR first but can still match a payment using field 20 if the UETR is missing.
- Include the exact amount, currency, and value date from field 32A, along with the beneficiary’s name and account details from field 59a.
- Attach the invoice number or stated payment purpose, which helps the investigating bank match the transaction internally.
- Ask specifically for the Tracker status rather than a document, since statuses like ACCC (credited), RJCT (rejected), and ACSP (accepted for processing) tell you more than a static confirmation ever will.
Universal Confirmations require banks receiving MT103 messages to report status back to the Tracker, so a proper request typically returns a clear outcome rather than silence. Timelines vary by bank and corridor, and some institutions charge a fee for manual investigations, so ask about cost before requesting one.
Pro Tip: Save your UETR the moment a payment is sent, not after a problem appears. It is far easier to locate in your outgoing transfer confirmation than to retrieve later from a support ticket.
ISO 20022 Migration: What to Ask for Instead of “MT103”
The coexistence period between legacy SWIFT MT messages and the newer ISO 20022 standard ended on November 22, 2025 for in-scope cross-border, bank-to-bank messages. From that date, pacs.008 became the required format for those payment instructions rather than an optional alternative.
This means a request for “an MT103” may now return something different. Banks handling in-scope FI-to-FI messages may issue a native ISO 20022 confirmation or a converted output derived from the legacy MT format rather than a traditional MT103 document, and some legacy MT variants have been subject to contingency processing or removal entirely since the migration date.
The practical fix is to change your wording. Ask your bank for “the SWIFT or ISO 20022 payment confirmation and the UETR” rather than insisting on an MT103 specifically. That phrasing covers whichever format the bank actually produces and keeps the UETR, the one identifier that survives the format change, at the center of the request.
Field Accuracy and Process Habits That Prevent Delays
Small errors in field placement cause a disproportionate share of payment delays and rejections. Regulatory guidance tied to FATF Recommendation 16 stresses that ordering customer and beneficiary information must sit in the correct fields to pass screening cleanly.
- Include a full IBAN or BIC in fields 50a and 59a rather than partial account references.
- Put remittance information in field 70, or field 77T when the message type requires it, so beneficiary banks can match the payment to an invoice.
- Ask for an MT202 COV when a cover payment is involved, since the underlying serial message can otherwise be hard to trace.
Pro Tip: Log both the UETR and the field-20 reference in every support ticket you open. Investigating teams move faster when they have both identifiers up front instead of chasing one down mid-conversation.
How Demivolt Supports Compliant SWIFT and ISO 20022 Workflows
Demivolt is a regulated European fintech platform built around business banking and payment infrastructure, including SWIFT and SEPA processing (https://demivolt.com). Businesses managing cross-border payments through Demivolt work with dedicated IBAN accounts and documentation designed to support reconciliation and investigation requests, including references and confirmations tied to individual transactions. That structure matters most when a finance team needs to match a UETR or field-20 reference against its own records quickly, rather than piecing together evidence after the fact.
Standardizing Around UETR-First Workflows in 2026
The MT103 label is losing relevance faster than most finance teams realize. Chasing a specific document format wastes time when the UETR, not the message type, is what actually survives the shift to ISO 20022. The smarter move is standardizing internal payment templates and vendor onboarding forms to capture the UETR and field-20 reference from day one, then building dispute procedures that start with a Tracker lookup instead of a request for paperwork. Teams that make this switch now will spend 2026 resolving disputes in days rather than waiting on banks to translate old habits into new formats.
— dd
How Demivolt Can Help With SWIFT and SEPA Payments
Businesses that send or receive international payments need banking infrastructure that keeps pace with how SWIFT and ISO 20022 actually work today, not how they worked five years ago. Some fintech platforms support SWIFT payments and dedicated IBAN accounts alongside SEPA processing, providing finance teams a single place to manage cross-border transfers and reconcile them against key references.
| Need | Demivolt product |
|---|---|
| Dedicated IBAN for receiving payments | Business accounts |
| SWIFT and SEPA payment processing | Payments |
| Business expense cards | Card programmes |
If your business regularly sends or receives SWIFT transfers and needs infrastructure built for compliance and traceability, consider opening a business account with a suitable provider or contact their sales team to discuss your payment volumes.
Where to Verify These Details Yourself
For field-level verification, consult SWIFT’s UETR guidance, the Universal Confirmations rulebook, and the MT to ISO 20022 conversion FAQ. Developer message samples are also available for deeper field-by-field study.
FAQ
What does MT103 stand for in banking?
MT103 refers to a SWIFT message type used to instruct and confirm a single international wire transfer between banks. It contains structured fields covering the amount, currency, sender, beneficiary, and a unique transaction identifier called the UETR.
How do I get an MT103 confirmation from my bank?
Contact the bank or provider that sent the payment and provide the UETR and sender’s reference (field 20) along with the amount, currency, value date, and beneficiary details. Since the ISO 20022 migration, your bank may return an ISO 20022 confirmation rather than a classic MT103 document.
What is the difference between MT103 and MT202?
MT103 carries a customer payment instruction from an ordering customer to a beneficiary, while MT202 moves funds between banks, often to cover an MT103 payment behind the scenes. When a payment seems to have disappeared between banks, requesting the related MT202 COV can reveal where the cover funds are sitting.
Why did my bank send an ISO 20022 confirmation instead of an MT103?
Cross-border, bank-to-bank message formats moved to ISO 20022 once the coexistence period ended in November 2025. Banks handling in-scope payments may now issue a native ISO 20022 confirmation or a converted MT output instead of a legacy MT103.
Is a UETR more reliable than an MT103 screenshot for disputes?
Yes, because the UETR is tied to live status reporting through SWIFT’s Tracker, while a screenshot only shows the instruction as it was sent. Banks receiving payments are required to report mandatory status updates, such as credited or rejected, back to the Tracker system, which gives disputes a verifiable data trail rather than a static document.