What Is an MT103? How to Use It to Trace an International Wire

An overseas vendor emails AP to say last week's wire hasn't arrived and asks you to send "the MT103." The Swift MT103 is the bank-to-bank message for a single customer credit transfer, the instruction behind every MT103 wire transfer. Two things make the request harder than it sounds. The message was retired for cross-border instructions when Swift completed the switch to ISO 20022 on Nov. 22, 2025. The same payment now travels as a pacs.008, and the confirmation your bank hands you proves less than most vendors think.

You can still answer the vendor the same day. Start with what the MT103 carried and what replaced it. Then trace the wire with its UETR, read what the confirmation shows, and file the record once the money lands. Most of that comes down to asking your bank the right questions, in the right order, before anyone resends money.

Key takeaways

• An MT103 is the Swift message for a single customer credit transfer, replaced by pacs.008 for cross-border Swift instructions on Nov. 22, 2025.

• Ask your bank for the payment confirmation and the UETR, the reference that follows the wire end to end.

• A confirmation shows what your bank sent, and it can't show the vendor's bank credited the account.

• Receiving banks report credited, rejected, or on-hold status, measured within two business days.

• File the approval, confirmation, UETR, remittance advice, and reconciliation entry together.

Table of contents

• What is an MT103?

• Did ISO 20022 replace the MT103?

• How do you trace an international wire with an MT103?

• Is an MT103 proof of payment?

• What should AP keep on file for an international wire?

• Do ACH and virtual card payments need an MT103?

• How Corpay helps AP teams keep a clean payment record

• Frequently asked questions

What is an MT103?

An MT103 is a Swift message type that one bank sends to the next to instruct a single customer credit transfer. In AP terms, that's your company paying one beneficiary, such as an overseas vendor.

Huntington Bank's developer documentation describes the MT103 as "a single customer credit transfer message in SWIFT FIN format." People search for the "SWIFT code MT103," but a Swift or BIC code identifies a bank, while MT103 names a message type your bank sends. AP only sees a copy or a confirmation.

Treat the MT103 as an instruction. It says nothing about whether the vendor's account was credited. Its value to AP is the references it carries, which banks on both ends search when a payment goes missing.

What information does an MT103 contain?

An MT103 carries the payer, the payee, the amount and value date, a sender's reference, and a code for who pays the charges. Five core fields hold most of what AP needs.

Field 71A is the first place to look when a vendor says an invoice was paid short. Under SHA or BEN, some or all fees fall on the vendor's side and can come out before the money lands. Before you send a top-up, review what a wire actually costs once intermediary fees come out.

US rules set a floor on the data. Under 31 CFR 1010.410(f), US sending and intermediary banks must carry payer, payee, amount, and date details on any transmittal order of $3,000 or more. That's why your bank asks for full payee details.

Did ISO 20022 replace the MT103?

Yes, for cross-border payment instructions on Swift. Coexistence ended Nov. 22, 2025, according to Swift's ISO 20022 implementation FAQ, and Swift's announcement of the switch says ISO 20022 is now required for all payment instructions.

According to the same announcement, 97% of payment instructions used ISO 20022 on Nov. 24, 2025, and a conversion service handles remaining MT instructions "for a period." According to the implementation FAQ, Swift has charged banks for contingency processing and translation since Jan. 1, 2026. Those bank costs give the stragglers a reason to finish.

US domestic wires changed too. Federal Reserve Financial Services completed the Fedwire migration to ISO 20022 in July 2025. That puts domestic Fedwire messages on the same ISO 20022 standard as cross-border Swift instructions.

The confirmation's name is less settled. Banks vary in what they call the document. Ask for the payment confirmation and the UETR on it, whatever the label says.

One change is still pending. Swift deferred its structured-address deadline in August 2026 and said it would publish an update by December. Keep full vendor street addresses on file anyway.

What is pacs.008?

The pacs.008 is the ISO 20022 customer credit transfer message that the MT103 translates into. Swift's training material says it can carry additional information compared with the MT103. For AP, that can mean richer payer and payee data riding with the payment.

How do you trace an international wire with an MT103?

Ask your bank to trace it using the UETR, the 36-character reference that stays with the payment through every bank in the chain.

Swift calls the UETR an unalterable reference that lets "any of the parties in the chain" locate a payment at any time. The sending bank generates it, and intermediary banks must not issue a new one. On a legacy MT103 document, it sits in field 121.

1. Confirm the payment went as a Swift wire, not as ACH, a card payment, or a platform payout.

2. Pull the bank's payment confirmation and check for the reference, value date, amount, beneficiary, and UETR.

3. Ask your bank for the tracker status of that UETR.

4. Read the status against Swift's universal confirmations rule, which requires receiving banks to report credited, rejected, on hold, or transferred outside Swift.

5. Send the vendor the confirmation and UETR so their bank can search inbound.

6. Ask your bank to open a formal investigation if the status stays on hold or hasn't moved after two business days.

The order puts the cheapest checks first. A status check is a quick ask, and an investigation is slower. Ask whether your bank charges for copies or investigations before you request one. Under the same universal confirmations rule, Swift measures receiving-bank compliance at 80% of traffic within two business days, so a blank status on day one isn't a failure.

According to Swift's Spotlight on Speed 2025 figures, 75% of payments on its network reach beneficiary banks within 10 minutes. Crediting the vendor is a separate event. According to the Financial Stability Board's 2025 progress report, B2B and B2P services settled less than 45% of payments within one business day. That sample covers retail payment services under $100,000, so the figures don't compare directly.

Still, the gap between "reached the vendor's bank in minutes" and "credited within a business day" is where most "where's my money?" emails come from. If you've fielded a few, you know the vendor is often asking the wrong bank.

Should you or the vendor start the trace?

You should. Your bank originated the instruction, so it opens the trace. The vendor's bank searches inbound with the same UETR, amount, value date, and sender name.

When both inquiries quote the same UETR, both banks are looking at the same record. Don't resend the payment while a trace is open, or you risk paying twice. Ask your relationship manager whether your bank shows UETR status in its client portal.

Is an MT103 proof of payment?

Partly. It shows your bank sent the payment instruction, and it can't show the vendor's bank credited the account. The receiving bank's "credited" status is closer evidence of that.

A confirmation also can't tell you who controls the receiving account. If a fraudster changed the vendor's bank details, the confirmation still looks perfect. Knowing how business email compromise reaches AP helps your team spot the changed-account request first.

According to the FBI's 2025 Internet Crime Report, business email compromise drew 24,768 complaints and $3,046,598,558 in reported losses in 2025. The FBI's advice is blunt. If you discover a fraudulent transfer, "time is of the essence," so contact your bank immediately and request a recall.

A recall is a request. Under UCC § 4A-211, canceling or amending an accepted payment order isn't effective unless the receiving bank agrees or a funds-transfer system rule allows it. Article 4A is enacted state by state, so ask counsel about a specific case. The same FBI report says its Recovery Asset Team froze $679,013,183 of $1,163,919,846 in attempted theft across 3,900 referred incidents. Those cover all fraud types, and frozen money isn't the same as returned money.

The control that works sits upstream, in verifying vendor bank details before you pay. At Corpay, our managed service validates vendor banking details before payments go out, because a changed account has to be caught before any instruction exists.

The CFO's guide to AI payments fraud

Deepfakes, vendor impersonation, and synthetic identity are hitting AP now. Get the full breakdown of the threats — and the controls that stop them.

Download the whitepaper

What should AP keep on file for an international wire?

Keep everything needed to show what was approved, what your bank sent, and what the vendor applied the money to. For a cross-border wire, that comes down to five records.

• Approval record and the invoice it pays.

• Bank payment confirmation, with the UETR visible.

• Remittance advice sent to the vendor.

• Tracker status or the bank's credit confirmation.

• Reconciliation entry in your ERP.

Your bank's records don't replace this file. The data your bank carries under 31 CFR 1010.410(f) describes the transfer, with no view of which invoice it paid. Only your file ties the payment to the obligation.

An auditor will ask for the whole chain, so keep it in one place. Check remittance against what remittance advice should contain, and match the bank line to the invoice by reconciling payments to the ledger. Timing matters too, since when funds count as good funds affects when you mark the payment closed. Retention periods are a question for your policy and counsel.

Do ACH and virtual card payments need an MT103?

No. The MT103 belongs to Swift wires. Domestic ACH and card payments run on their own networks with their own references, so there's no MT103 to ask for.

Plenty of "send the MT103" emails come from domestic vendors paid by ACH who borrowed the term from an international customer. Answer with the ACH payment reference and remittance detail. A refresher on how an ACH payment works helps, since settlement timing is usually the vendor's real question.

At Corpay, when we pay suppliers by virtual card, ACH, or check, the remittance travels with the payment. The record reconciles back to the ERP, so the proof-of-payment question rarely starts.

How Corpay helps AP teams keep a clean payment record

A clean payment record keeps approval, payment, remittance, and reconciliation together. Nobody has to rebuild the story from email when a vendor asks. Corpay AP Automation is fully managed AP, with payments by virtual card, ACH, and check. Our team handles supplier enrollment and follow-up, so your staff isn't chasing vendors for bank details or explaining where a payment went.

Each payment carries its remittance, and the payment and remittance trail reconciles back to the ERP. We connect through 100+ ERP integrations, including NetSuite, Sage Intacct, Microsoft Dynamics 365 Business Central, and Acumatica. The reconciliation entry lands where your auditor will look for it, and the vendor gets the detail needed to apply the cash.

For vendors that accept card, single-use virtual cards replace a static account number with one issued for a single payment. That takes the changed-bank-details request out of the payment path, because there's no vendor account number to redirect. The results we report are about 40% time saved on AP processing and $800M+ in rebates paid to customers per year. Teams are live in weeks, and the ERP they already run stays in place. If you'd like to see what that record would look like for your vendor base, Talk to an Expert.

Frequently Asked Questions

What does MT103 mean?

MT103 names the Swift message type for a single customer credit transfer, one payer paying one beneficiary. A vendor asking for one usually means "show me your bank sent it." If you're sorting vendors by rail, our guide to electronic payment methods compares the options.

Is the MT103 still used?

Not for cross-border payment instructions on Swift, where the pacs.008 took over when coexistence ended. The name lives on in vendor requests. For the domestic payments we run, see how payments automation keeps the record in one place.

How do I track my MT103?

Ask your bank to trace the payment's UETR, with the value date, amount, and beneficiary name. Receiving banks are measured on reporting status within two business days, so give it that long. If chasing wire status eats your team's week, Talk to an Expert about moving eligible domestic vendors to virtual card or ACH.

Does an MT103 prove the vendor received the money?

No. It shows the instruction your bank sent, and the receiving bank's "credited" status is closer evidence of receipt. Even that can't show who controls the account, which is why we validate vendor banking details before paying. For the wider picture, read what automating supplier payments changes.

What is the difference between an MT103 and a pacs.008?

They do the same job in different standards. The MT103 is the legacy Swift MT format, and the pacs.008 is its ISO 20022 counterpart, which Swift says can carry more information. Neither applies to card or ACH payments, the lane Corpay Payments Automation covers.

David Luther

Product Marketing Program Manager

David Luther, MBA is a product marketing program manager with years of experience in commercial banking, finance, and technology sectors, with research and writing appearing in financial publications.

Payments Automation

AP Automation