SWIFT MT103 Field 33B — Currency / Original Ordered Amount

Last reviewed: · Curated by Ohmyfin Organisation editorial.

Field 33B is the Currency / Original Ordered Amount. It is used when an FX conversion happened before the payment was sent — field 32A shows the settlement currency, field 33B shows the original customer currency. Draft a valid MT103 with field 33B →

Payment Tracker

LIVE

Paste your UETR — we query the SWIFT GPI network in real time.

36-character UUID from your MT103 field 121 or pacs.008 <UETR> tag. Where to find it →

Receive your tracking result instantly after search
If not found, we’ll monitor for 7 days and alert you
No account needed — one-click unsubscribe
2
Trusted by 2M+ users monthly  ·  No account or card required
Encrypted | SWIFT Network Coverage | Real-time GPI
SWIFT MT103 message diagram showing fields 20, 32A, 50K, 59, 70 and 121 (UETR)
How an MT103 maps to the UETR (field 121), sender reference (field 20), value-date/currency/amount (field 32A) and beneficiary details. Source: SWIFT MT103 specification.

Details

Format: 3 letters (ISO 4217 currency code) + amount (comma as decimal separator, no thousands separators). Example: EUR23000,00 in field 33B alongside USD25150,00 in field 32A means the customer originally instructed EUR 23,000 and the sending bank converted it to USD 25,150 before sending the SWIFT message. The presence of field 33B is the signal to every bank in the chain — including the beneficiary bank and any regulatory authority reviewing the message — that an FX conversion was made by the originating bank.

Field 33B is required in the European Union under PSD2 (Payment Services Directive 2) and related EBA technical standards whenever a payment involves a currency conversion. EU payment service providers must disclose the exchange rate, the charges, and the amount in the original currency to the payer before execution. Field 33B provides the machine-readable "original currency and amount" data that supports this disclosure. Omitting field 33B when an FX conversion occurred is a regulatory non-compliance issue in the EU.

The exchange rate implied by field 33B and field 32A can be used to calculate the exact FX rate applied by the sending bank. Dividing the field 32A amount by the field 33B amount gives the rate (or its inverse, depending on the currency pair direction). For example, if 32A is USD 25,150 and 33B is EUR 23,000, the EUR/USD rate applied is 25,150 / 23,000 = 1.0935. This makes field 33B a transparency tool for FX cost benchmarking.

Field 33B is distinct from field 36 (Exchange Rate), which may also appear on some MT103 messages and carries the explicit exchange rate used for conversion. Not all sending banks include field 36, but field 33B is more commonly included because it is required by EU regulations and is also used in SEPA credit transfer processing to satisfy transparency obligations.

In ISO 20022 pacs.008, the equivalent of field 33B is the InstrAmt (Instructed Amount) element within CdtTrfTxInf. When InstrAmt is in a different currency from IntrBkSttlmAmt (Interbank Settlement Amount), the difference signals an FX conversion. pacs.008 also has a separate XchgRate element for the explicit exchange rate, and the Dbtr's bank can include the original debiting amount in a separate sub-element, providing even richer transparency than the MT103 field combination.

Quick facts

SWIFT field specification
Example value:33B:USD1000,00
Valid characters / format3!a currency + 15d amount
Required on MT103Optional
Required on MT202Not used
Required on pacs.008Optional
NotesOriginal instructed currency/amount before FX.

Key facts

Frequently asked questions

When is field 33B mandatory?

Whenever an FX conversion occurred between the customer's original instruction and the SWIFT message, and whenever the EU PSD2 / SEPA regulatory framework requires disclosure of the original currency and amount. In practice, EU banks must include it on all FX-converted payments. Outside the EU, it is best practice but not always enforced.

If field 32A is EUR and field 33B is also EUR, is that valid?

Field 33B is only meaningful when it shows a different currency from field 32A. If both are the same currency, field 33B should be omitted — it would be redundant and potentially confusing. Field 33B exists specifically to disclose an FX conversion.

How can I calculate the FX rate from fields 32A and 33B?

Divide the field 32A amount by the field 33B amount (or the inverse, depending on the currency direction). For example, if 32A = USD 11,000 and 33B = GBP 8,500, the GBP/USD rate is 11,000 / 8,500 = 1.2941. This rate may differ from mid-market by a few percent — the difference is the bank's FX margin.

What is PSD2 and why does it require field 33B?

PSD2 (Payment Services Directive 2) is the EU regulation governing payment services. It requires payment service providers to disclose to the payer the exchange rate applied, the total charges, and the amount in the customer's original currency before and after executing a currency conversion. Field 33B provides the original currency amount that supports this disclosure in SWIFT messaging.

Does field 33B appear on my bank statement?

The field 33B data may be shown to you as "original amount" on your payment receipt or statement alongside the "settlement amount" from field 32A. Whether and how it is displayed depends on your bank's statement format. EU banks are required to show you both amounts and the exchange rate under PSD2.

Get 100 free credits — track unlimited SWIFT payments

No card needed. Free for ordinary users — completely free for individuals — no daily limit, no card required. Track any international wire across 11,000+ banks.

Track a payment now — completely free Or try the tracker now →
ExploreSWIFT trackerUETR trackerCurrency exchange ratesUSD → EUR rateGBP → USD rateEUR → GBP rateUSD → JPY rateWestern Union MTCN trackerMoneyGram reference trackerRia PIN trackerRemitly trackerXoom / PayPal trackerWorldRemit trackerWise trackerRevolut trackerOFX trackerZelle trackerVenmo trackerCash App trackerPayoneer trackerSkrill trackerNeteller trackerInstarem trackerTRN trackerDraft & validate hubMT ↔ MX translatorMX → MT translator@ohmyfin/swift-draft (npm)MT103 drafterMT202 drafterMT202COV drafterMT199 drafterpacs.008 drafterpacs.009 drafterpacs.002 draftercamt.053 draftercamt.054 drafterMT103 trackerWire-transfer trackerSWIFT GPI trackerBIC lookupIBAN explainedUETR explainedTRN explainedBIC explainedMT103 guideMT202 guidepacs.008 guideField 20Field 32AField 50KField 57AField 121 (UETR)Track USDTrack EURTrack GBPTrack CNYTrack INRSWIFT vs SEPASWIFT vs ACHSWIFT vs WiseUETR vs TRNBIC vs IBANMT103 vs pacs.008How long: UKHow long: USHow long: IndiaHow long: EurozoneStatus: ACSPStatus: ACCCStatus: RJCTStatus: PDNGSWIFT GPISWIFTNetOhmyfin AI AssistantSWIFT status todayBank trackersTrack HSBCTrack ChaseTrack BarclaysTrack NatWestTrack WiseTrack RevolutAsk: How to track SWIFTAsk: UETR not foundAsk: Stuck 2 weeksAsk: Get UETR from bankAsk: Is Ohmyfin freeAlliance AccessAlliance GatewaySWIFT GoKYC RegistryAbout swift.comSWIFT productsCurrency guidesPayment comparisonsPayment speedStatus codesSWIFT field referencePayments glossarySWIFT message typesSWIFT/BIC directoryCorrespondent banksKnowledge centerReject codesAC01 rejectAC04 rejectBE01 rejectCH09 rejectRR04 rejectHelp & troubleshootingPayment not receivedFind UETR on MT103Cancel SWIFT paymentFake MT103 warningMajor banksJPMorgan Chase BICHSBC BICDeutsche Bank BICCiti BICBNY Mellon BICCountry corridorsSend US → IndiaSend US → MexicoSend US → PhilippinesSend UK → IndiaSend UK → PakistanSend UAE → IndiaSend UAE → PhilippinesSend Saudi → IndiaSend Canada → IndiaSend Australia → IndiaMT message referenceMT202COVMT199MT940MT942MT900MT910MT195MT103 STPBanks by countryBanks in USBanks in UKBanks in GermanyBanks in IndiaBanks in ChinaBanks in UAEBanks in Saudi ArabiaBanks in SingaporeBanks in Hong KongBanks in JapanBanks in BrazilUse casesFreelancer paid abroadPay overseas supplierE-commerce payoutsTuition paymentReal estate abroadFamily remittanceScam alertsFake MT103 fraudMoney-transfer providersTrack WiseTrack RevolutTrack Western UnionTrack MoneyGramTrack RemitlyTrack RiaTrack XoomTrack WorldRemitTrack PayoneerTrack PayPalTrack OFXTrack SkrillTrack SendwaveTrack InstaremTrack TransferGoTrack Stripe payoutTrack AirwallexTrack HSBC Global MoneyTrack Monzo / Revolut / N26Wise vs RevolutWise vs PayPalWise vs Western UnionWise vs bank wireWestern Union vs MoneyGramRemitly vs Western UnionSend money to IndiaSend money to PhilippinesSend money to MexicoSend money to NigeriaSend money to PakistanSend money to UKAdvance-fee fraudBEC / CEO fraudPig butchering scamRomance scam wire