SWIFT MT103 Field 32A — Value Date / Currency / Amount

Last reviewed: · Curated by Ohmyfin Organisation editorial.

Field 32A is one of the most important fields on an MT103. It carries the value date, currency and amount of the interbank settlement. Draft an MT103 with a valid field 32A → · Track any SWIFT payment free →

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 specification: 6 digits (YYMMDD) + 3 letters (ISO 4217 currency code) + amount. The amount uses a comma as the decimal separator (European convention) and no thousands separators. Example: 260315USD25000,00 means value date 15 March 2026, currency US Dollar, amount 25,000.00. The maximum number of digits in the amount (before the comma) is 12; the maximum number of decimal places is 2 for most currencies, but some currencies (e.g. Japanese Yen, JPY) have zero decimal places by convention, in which case the comma and fractional digits are omitted.

The value date (first 6 digits, YYMMDD) is the interbank settlement date — the date on which the sending bank's nostro account is debited and the beneficiary bank's account is credited at the settlement level. This is distinct from the booking date (when the transaction is posted in the bank's accounting system) and the available date (when the beneficiary can spend the funds). For same-day urgent payments, the value date equals the send date. For standard cross-border payments, the value date is typically 1–2 business days after the send date, depending on currency cut-off times.

Currency cut-off times directly affect the value date that can be specified in field 32A. If a payment is sent after the Fedwire cut-off (18:00 ET for USD), the value date cannot be the same day — it must be the next USD business day. Setting a past or unreachable value date in field 32A will cause the receiving bank to re-date the message. When Ohmyfin shows the value date in a tracking result, it shows the most recent value date as updated by the SWIFT GPI status record, which may differ from the original field 32A if a correspondent re-dated the payment.

The currency code in field 32A must be a valid ISO 4217 three-letter currency code (USD, EUR, GBP, CHF, JPY, AUD, CNY, etc.). Using an invalid or deprecated code (e.g. a code for a currency that has been replaced) will cause the message to be rejected. For Eurozone countries, the currency code must be EUR — individual legacy codes like FRF (French franc) or DEM (Deutsche mark) are no longer valid.

The amount in field 32A is the interbank settlement amount — the amount in the specified currency that the sending bank is committed to delivering to the beneficiary bank. If the original customer instruction was in a different currency (e.g. a UK customer sent GBP that was converted to USD by the bank), the original customer amount appears in field 33B (Currency/Original Ordered Amount) and field 32A shows the USD settlement amount. This is important for regulatory transparency in jurisdictions that require full disclosure of FX conversion.

Quick facts

SWIFT field specification
Example value:32A:251015USD1000,00
Valid characters / formatYYMMDD + 3!a + 15d (decimal comma)
Required on MT103Mandatory
Required on MT202Mandatory
Required on pacs.008Mandatory
NotesValue date + currency + amount. Mapped to <IntrBkSttlmDt>/<IntrBkSttlmAmt> on pacs.008.

Key facts

Frequently asked questions

Why is the decimal a comma in field 32A?

SWIFT MT messages use the European decimal convention (comma as decimal separator) for all amount fields. ISO 20022 pacs.008 uses a period (dot) as the decimal separator instead. If you are building or validating an MT103, always use a comma for decimals in amounts.

Can the value date in field 32A be today?

Yes, if the payment is sent before the relevant currency cut-off time. For USD, the Fedwire cut-off is 18:00 ET. For EUR, the TARGET2 cut-off is 18:00 CET. For GBP, CHAPS closes at 16:00 GMT. A same-day value date is only achievable if the payment message is sent and accepted before those cut-offs.

What happens if field 32A has an invalid value date?

A past value date or a non-business day will typically cause the payment to be rejected or re-dated by the receiving correspondent. Banks may re-date the value date to the next available business day and update the SWIFT GPI tracking record accordingly. Ohmyfin shows the most current value date from the GPI status.

What is the maximum amount in field 32A?

The field allows up to 15 characters for the combined amount (up to 12 digits before the comma plus the comma plus up to 2 decimal digits). In practice the maximum is 999,999,999,999.99 in any currency. Most banking systems have their own transaction limits well below this technical maximum.

How does field 32A relate to field 33B?

Field 32A shows the interbank settlement currency and amount — what the banks are actually moving between themselves. Field 33B shows the original currency and amount that the customer instructed before any FX conversion. If the customer asked to send EUR 10,000 and the bank converted it to USD 10,950 for settlement, field 32A shows USD 10,950 and field 33B shows EUR 10,000.

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 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