MT103: What Is It, Format, Fields and How to Obtain
If you have ever waited on an international payment that seemed to disappear into thin air, you have probably been told to ask for the MT103. And if you had no idea what that meant, you are not alone.
An MT103 is the official record of your SWIFT wire transfer, the document that tells you exactly what was sent, when, how much, and through which banks. For Indian exporters and freelancers receiving payments from overseas, understanding the MT103 is the difference between chasing a payment blindly and having a concrete document to trace it, dispute it, or use it for compliance.
This blog explains what an MT103 is, what each field means, how to request one, and what has changed since SWIFT moved to a new messaging standard in November 2025.
TL;DR - Summary
- What it is: - An MT103 is the SWIFT message that confirms a wire transfer was sent — the digital receipt for a cross-border payment.
- What it tells you: - Who sent the money, how much, through which banks, and who paid the fees.
- 2025 update: - MT103 has been replaced by PACS.008 under SWIFT's ISO 20022 standard as of November 2025, but it works the same way for your purposes.
- Why it matters for India: - Essential for generating e-FIRA, resolving delayed payments, and staying compliant with FEMA.
What Is an MT103 SWIFT Message?
An MT103 is the standardised SWIFT message for international wire transfers. Every time money moves across borders through the SWIFT network, an MT103 is generated at the sending bank to record and instruct the transfer. It is not the money itself, it is the structured document that travels alongside the money, carrying all the key details of the transaction.
A good way to think about it: the money is the parcel, and the MT103 is the shipping label and tracking document combined. It tells every bank handling the transfer exactly where the payment came from, where it is going, how much is being sent, and who bears the charges.
The parcel
The actual funds moving from the sender's bank to yours through the SWIFT network.
The shipping label
The document that travels with the money -- recording where it came from, where it is going, and who pays the charges.
What Information Does an MT103 Contain?
An MT103 is made up of numbered fields, each carrying a specific category of information. Together they give a complete picture of the transaction:
- Sender details: the name, account number, and bank of whoever initiated the transfer
- Recipient details: the name, account number, and bank of whoever is receiving the money
- Transaction details: the amount, currency, value date (the date the funds settle between banks), and the unique transaction reference number
- Routing information: any intermediary or correspondent banks the payment passed through on its way to the beneficiary
- Charge details: who is paying the transfer fees, the sender, the recipient, or split between both
Each of these sits in a specific field tagged with a code like :20: or :32A:. Once you know what each tag means, the document becomes easy to read. We cover this field by field in the format section below.
MT103 vs MT202: What Is the Difference?
Both are SWIFT message types and both relate to international payments. The confusion comes from the fact that they often exist side by side for the same transaction.
The MT103 is the customer transfer message. It carries the full transaction details, sender, recipient, amount, purpose, and is the document you would request as proof of payment.
The MT202 is a bank-to-bank transfer message. Banks use it to move funds between themselves, typically to settle or cover an MT103 that has already been sent. It contains no customer details and is never something you would need to request.
| MT103 — Customer transfer | MT202 — Bank-to-bank transfer | |
|---|---|---|
| Initiated by | Sending bank, on behalf of a customer | Sending bank, on behalf of itself |
| Contains customer details | Yes sender name, account, recipient details, purpose | No bank identifiers only, no customer data |
| Used for | Moving money from one customer to another across borders | Settling funds between banks, often to cover an MT103 |
| Who requests a copy | The sender or receiver as proof of payment | Banks only -- customers never need to request this |
When someone sends you a wire, the MT103 is generated for the transaction. Behind the scenes, the sending bank may also generate an MT202 for interbank settlement. You never see that one and you do not need it.
Why Do We Need MT103 in International Payments?
For most international payments that go through without a hitch, the MT103 works quietly in the background and no one thinks about it. But the moment something goes wrong, or when compliance asks for documentation, it becomes the most important document in the transaction.
Proof of Payment
The MT103 is globally recognised as the official proof that a SWIFT wire transfer was initiated. If payment is claimed to have been made but funds have not arrived, the MT103 settles the question. It shows the date the payment was initiated, the exact amount, the reference number, and the banks it travelled through.
Tracking Delayed or Missing Payments
Every MT103 carries a transaction reference in Field 20. Most MT103s sent through SWIFT's gpi network also carry a UETR -- a Unique End-to-End Transaction Reference -- which works like a real-time tracking number for the wire. If a payment is stuck at an intermediary bank, the UETR allows any bank in the chain to locate it instantly rather than waiting days for a manual investigation.
UETR stands for Unique End-to-End Transaction Reference. It is a 36-character reference code assigned to every SWIFT gpi payment. When a payment is delayed, sharing the UETR with your bank lets them run a live trace rather than filing a manual inquiry.
Resolving Payment Disputes
Field 71A of the MT103 shows who is responsible for paying the transfer fees, the sender (OUR), the recipient (BEN), or both sharing (SHA). If SHA or BEN was selected, intermediary banks can deduct their charges from the amount in transit before it reaches the beneficiary's account.
Here is a real scenario: a $5,000 invoice is paid in full but only $4,960 arrives. Without the MT103, it is impossible to know whether the shortfall was a legitimate intermediary fee or an error. With the MT103, Field 71A identifies the charge arrangement, and Field 56A shows the deducting bank. That information is enough to either accept the deduction or escalate for a formal trace.
Ask the sender to select OUR when initiating a SWIFT transfer. This means the sender bears all intermediary fees and the recipient receives the full amount. Getting this right upfront avoids reconciliation issues later.
Compliance, Auditing, and FIRA Documentation
For Indian exporters and freelancers, this is the most relevant use of the MT103. When an inward SWIFT remittance arrives at an Indian bank, the bank uses the MT103 data to generate the e-FIRA, the Electronic Foreign Inward Remittance Advice, which is the RBI-compliant proof of foreign income receipt. The MT103 reference number appears in the e-FIRA, linking the two documents into a clean compliance record.
Without a clean MT103, the bank may have difficulty generating the e-FIRA correctly, especially if there are mismatches between the sender's name in the MT103 and the name on the invoice. The MT103 also matters when:
- Filing ITR and needing proof of foreign income
- Claiming GST refunds on exported services
- Responding to FEMA compliance queries
- Applying for export incentives that require proof of payment realisation
Tired of chasing your bank for e-FIRA every time a payment arrives? Skydo generates it automatically with every inward remittance, no follow-ups, no delays. See how it works.
What Is the Format of an MT103?
An MT103 is a structured document made up of numbered fields, each identified by a tag that begins with a colon. When you receive a copy from your bank, it typically comes as a formatted PDF or letter. The fields appear in a standard sequence and each one carries a specific, consistent meaning regardless of which bank issued it.
The document is not something most people encounter every day, but once you have seen one, the structure becomes familiar quickly. Below is what a typical MT103 looks like when received as a document, this is an MT103 SWIFT message example with realistic field values.
ⓘ Hover over any section to learn what it means
SWIFT MT103 — SINGLE CUSTOMER CREDIT TRANSFER
Issued by Sending Bank | Internationally recognised proof of payment
Field :20:
Transaction Reference
RequiredUnique ID the sending bank assigns to this transfer. Use this when tracing a payment.
✔ Keep this for all follow-ups
Field :23B:
Bank Operation Code
RequiredCRED indicates a standard customer credit transfer.
✔ Should say CRED for standard transfers
Field :32A:
Value Date / Currency / Amount
RequiredDate banks settle, currency, and interbank amount. May differ from your invoice if fees were deducted.
✔ Compare with your invoice amount
Field :50A:
Ordering Customer
RequiredName, account, and address of whoever initiated the transfer.
✔ Confirm sender identity matches your records
Field :59:
Beneficiary Customer
RequiredYour name, account, and address. Mismatches can trigger compliance holds at your Indian bank.
✔ Ensure details match your bank records exactly
Field :56A:
Intermediary Bank
OptionalCorrespondent bank the payment routes through. Key to tracing delays and deductions.
✔ Use this to identify where fees were deducted
Field :71A:
Details of Charges
RequiredOUR = sender pays all. SHA = shared. BEN = recipient pays all. SHA or BEN can reduce what you receive.
✔ Ask sender to select OUR
Field :70:
Remittance Information
OptionalInvoice numbers or payment purpose. Ask sender to always include your invoice number here.
✔ Match this to your invoice number
Field :72:
Sender to Receiver Info
OptionalAdditional notes or instructions from sender to receiving bank.
✔ Check for instructions affecting processing
| Tag | Field Name | What It Contains | Required? | What to Check |
|---|---|---|---|---|
| :20: | Transaction Reference | Unique ID assigned by sending bank | Yes | Use this to trace the payment with your bank |
| :23B: | Bank Operation Code | Usually CRED (credit transfer) | Yes | Should say CRED for standard transfers |
| :32A: | Date / Currency / Amount | Value date, currency code, settled amount | Yes | Verify amount matches your invoice |
| :50A: | Ordering Customer | Sender's name, account, address | Yes | Confirm sender identity matches your records |
| :59: | Beneficiary Customer | Recipient's name, account or IBAN | Yes | Ensure your details are correct and match your bank |
| :71A: | Details of Charges | OUR / BEN / SHA -- who pays fees | Yes | Check if fees were deducted from your amount |
| :56A: | Intermediary Bank | BIC of intermediary bank if used | No | Helps trace delays and unexpected deductions |
| :70: | Remittance Information | Invoice number, payment purpose | No | Match to your invoice number |
| :72: | Sender to Receiver Info | Additional instructions or notes | No | Check for special instructions affecting processing |
Field :32A: shows the amount settled between banks, which may differ from the amount originally sent if intermediary fees were deducted along the route. Always compare the :32A: amount with your invoice to identify any shortfall before contacting your bank.
How To Get an MT103 from Your Bank?
MT103s are not automatically issued or shared. Your bank has the record in its system, but you have to specifically ask for it.
Step-by-Step Process to Request an MT103
How to request an MT103 — hover each step to expand
Confirm the transfer was sent
The MT103 only exists once a SWIFT transfer has been initiated. Ask the sender to confirm they have sent the wire and to share the transaction reference number or UETR if available.
Contact your bank or ask the sender
Ask the sender to request a copy from their bank and forward it to you, or request it from your own Indian bank as an inward remittance trace. Platforms like Skydo provide payment confirmation documents instantly, with no separate request needed.
Provide the transaction reference
Give your bank the transaction reference from Field 20 if you have it, or the approximate date, amount, and sender details. This helps your bank locate the correct entry in the SWIFT system quickly.
Allow processing time
Indian banks typically take one to three business days to retrieve and issue an MT103 copy. Some private banks allow requests through net banking or a relationship manager. Public sector banks often require a written request at the branch.
How Much Do Banks Charge for an MT103 Copy?
Bank charges for MT103 copies vary and are not always transparently published. As a general guide, Indian private banks typically charge between ₹500 and ₹1,500 per MT103 copy request, plus GST. Public sector banks like SBI may charge similarly for branch-based requests. Virtual account platforms like Skydo provide payment confirmation documents as part of their service at no additional charge.
Before paying your bank for an MT103, ask the sender to share theirs first. The sending bank's copy is as valid as anything your receiving bank would issue.
With Skydo, you never have to pay your bank for payment confirmation documents. You get them instantly, free, with every transfer. Open your free account.
Who Can Request an MT103?
Both the sender and the receiver can request an MT103, but from different banks.
The sender requests it from their own bank -- the one that initiated the transfer.
The receiver requests it either from the sender directly (who forwards the sending bank's copy) or from their own Indian bank as an inward remittance investigation. The Indian bank charges a fee for this because it requires a SWIFT trace query.
In most day-to-day situations, asking the sender to share their copy is a practical first step before initiating a formal request through your bank.
How To Track a SWIFT Payment Using MT103?
When a payment is delayed, the MT103 gives you two things you need to trace it: the transaction reference (Field 20) and, for SWIFT gpi transfers, the UETR.
Here is how to use them:
First, get the MT103 or at minimum the UETR from the sender. The UETR is a 36-character code. Share this with your Indian bank's forex or SWIFT desk and ask them to run a gpi trace. If your bank supports SWIFT gpi, they can see exactly where the payment is in the network, whether it is still with the sending bank, in transit via a correspondent bank, or held at your bank pending compliance checks.
If the payment has been stuck for more than three business days after the value date in Field :32A:, escalate formally. Give your bank the MT103 reference, the UETR, and the sender's bank BIC from Field :50A:. Most delays are resolved at the intermediary bank level and clear within a day or two of the trace being raised.
SWIFT gpi stands for Global Payments Innovation. It is SWIFT's tracking layer that gives every participating bank real-time visibility into where a payment is. As of 2024, over 90% of SWIFT cross-border payments travel on the gpi network. If both banks support gpi, you can see live payment status without even requesting the MT103 document.
Skip the SWIFT trace queue. Skydo surfaces your UETR and live payment status directly in your dashboard, no bank calls needed. Try Skydo
Is MT103 Being Replaced?
Yes. As of November 22, 2025, SWIFT officially decommissioned the MT103 message format as part of its migration to ISO 20022, a new global messaging standard. The MT103 has been replaced by PACS.008.
This does not mean MT103 documents are now invalid -- transfers made before November 2025 still generated MT103s, and you may still encounter the format in older records or from banks that are slower to migrate. But for payments made on SWIFT after November 2025, the underlying message format is now PACS.008.
What Is PACS.008?
PACS.008 is the ISO 20022 equivalent of the MT103. It is an XML-based message format that carries the same core information -- sender, recipient, amount, currency, routing -- but in a more structured and data-rich format.
Where MT103 used compressed coded fields with limited text, PACS.008 uses full XML structure with dedicated fields for every piece of information. It supports full Unicode (meaning it can handle Indian names and addresses correctly), carries richer remittance information, and is designed to enable straight-through processing with fewer manual interventions.
MT103 vs PACS.008: Key Differences
| Dimension | MT103 — Legacy | PACS.008 — ISO 20022 |
|---|---|---|
| Format | Proprietary SWIFT FIN text | XML-based (ISO 20022) |
| Data richness | Limited structured fields | Significantly more detailed and structured |
| Character set | Restricted SWIFT character set | Full Unicode -- supports all scripts including Indian languages |
| Remittance info | Field 70 -- limited free text | Structured fields for invoice references and payment purpose |
| End-to-end tracking | UETR added via gpi (retrofitted) | Native UETR support built in |
| Status as of Nov 2025 | Decommissioned Legacy format | Active SWIFT's new standard |
| What you receive | MT103 PDF for older payments | PACS.008 confirmation for payments after Nov 2025 |
What Does This Mean for Indian Exporters and Freelancers?
Practically speaking, the transition from MT103 to PACS.008 does not change what you need to do. The document you receive will look different -- it will be XML-structured rather than the old coded text format -- but it serves the same purpose.
What matters is that you update your mental model: when someone says "ask for the MT103," what they really mean going forward is "ask for the SWIFT payment confirmation document," which is now a PACS.008. Your Indian bank will use this document the same way it used MT103s -- to generate your e-FIRA and close out the remittance record.
If you receive an MT103-formatted document for a payment made after November 2025, it may mean the sending bank has not yet completed the ISO 20022 migration. This is not a red flag — some banks are migrating in phases — but worth noting if you are trying to reconcile records or raise a trace.
Do You Always Need an MT103?
No. For most routine international payments that arrive on time and in full, you do not need to request an MT103. Your bank statement showing the inward credit, combined with your invoice, is sufficient for day-to-day reconciliation.
An MT103 becomes necessary in specific situations:
- The payment is delayed beyond three to five business days with no credit appearing
- The amount received is less than the amount invoiced and you need to identify the deduction
- A dispute arises over whether payment was made and you need the sender's bank record
- Your bank requires the MT103 reference to generate your e-FIRA correctly
- You are responding to a FEMA compliance query and need to demonstrate the payment trail
- You are claiming a GST refund or export incentive that requires proof of foreign payment realisation
How Virtual Account Platforms Eliminate the Need for MT103
When Indian exporters and freelancers use virtual USD account platforms like Skydo, the need for MT103 in routine situations largely disappears. This is because virtual accounts receive payments through local rails, ACH in the US, SEPA in Europe, Faster Payments in the UK, rather than SWIFT. When a sender pays via local rails into a virtual account, no SWIFT message is generated, which means no MT103, but also no intermediary bank fees, no multi-day delays, and no need to chase documentation.
The platform itself provides the payment confirmation, generates your e-FIRA automatically, and gives you a clean record for compliance purposes. The SWIFT-and-MT103 process only becomes relevant when a sender insists on a traditional wire transfer.
Even when SWIFT is used, platforms like Skydo surface the UETR and payment details in the dashboard, removing the need to manually request documents from your bank.
Most of your international payments do not need to go through SWIFT at all. Skydo gives you local USD, GBP, EUR and SGD accounts so your clients pay locally and you receive faster, with zero intermediary deductions. Get your virtual account
How Should Indian Freelancers and Exporters Use MT103?
Knowing what an MT103 is and knowing how to actually use it are two different things. For Indian exporters and freelancers specifically, the MT103 shows up in two very practical situations: getting your e-FIRA sorted, and proving to an overseas sender that you have not received a payment they claim to have made.
Using MT103 to Obtain e-FIRA from Your Bank
When a SWIFT inward remittance hits your Indian bank account, your bank generates an e-FIRA using the data from the MT103. The e-FIRA contains your RBI-required purpose code, the remitter's details, the INR amount credited, and the exchange rate applied. The MT103 reference number (Field 20) links the two documents together.
If your e-FIRA is delayed or incorrectly generated, the MT103 is the document you take to your bank to resolve it. Your bank needs the Field 20 reference to locate the corresponding SWIFT transaction in their records and generate or correct the e-FIRA.
Keep the following documents together for every international payment received via SWIFT:
- Your invoice
- The MT103 or PACS.008 from the sender
- Your bank credit advice
- The e-FIRA once generated
This set of four documents is your complete compliance record for that payment. You will need it for ITR filing, GST refund claims, and any FEMA audit.
Skydo automatically links your e-FIRA to every inward payment. No document chasing, no manual reconciliation. Your compliance record stays clean without the paperwork. See Skydo in action
How to Ask Your US Client for MT103 Proof of Payment
Most overseas clients have never heard of an MT103. They know they sent a wire transfer but they do not know that a document with that name exists.
The most effective way to ask is to be specific and practical:
"Hi [Name], could you please request a copy of the SWIFT payment confirmation for the transfer you made on [date]? The document may be called an MT103, SWIFT receipt, or payment confirmation. You can usually get it from your bank's online portal or by calling their business banking support. I need the transaction reference number and the payment details for my compliance records in India."
Most banks in the US and Europe provide the MT103 or SWIFT confirmation through online banking. Once the sender has it, they can forward the PDF or screenshot directly.