Category 1: Customer payments and cheques
MT103 REMIT Single Customer Credit Transfer (REMIT)
Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked
Retired in the 2025 standards release: no longer sent on the Swift network.
The MT103 REMIT was a variant of the MT103 that carried extended remittance information, such as a full invoice list, in an envelope field 77T instead of the four-line field 70. It was flagged with the code REMIT in field 119 of the user header and could only be used by banks registered in its Message User Group. Swift removed it from the FIN network on 22 November 2025.
- Message type
- MT103 REMIT
- Category
- 1
- Status
- Retired (SR 2025)
- ISO 20022
- No direct equivalent
What MT103 REMIT is used for
Field 77T was mandatory and field 70 was not used. The usual MT103 cover rules applied: field 20 of the MT103 REMIT went unchanged into field 21 of the related MT202COV, and the UETR in field 121 was copied unchanged.
Bank notices list the MT103 REMIT among the payment messages the network NAKs since 22 November 2025, with no conversion. In ISO 20022, remittance information travels in the remittance information element of the pacs.008.
Withdrawn from the Swift FIN network on 22 November 2025, when MT/MX coexistence for payment instructions ended: the network now rejects (NAKs) it instead of delivering it, and Swift does not convert it to ISO 20022.
- Sent by
- The ordering customer’s bank
- Sent to
- The next bank in the chain, registered for MT103 REMIT
Fields
This is a catalogue entry: the field-by-field structure is not shown here because we publish structures only where we have checked them against public sources.
ISO 20022
No direct replacement: the withdrawn MT103 REMIT is not converted. The pacs.008 has its own remittance information element for this data.
All MT messages · Category 1 messages · ISO 20022 messages · Codes · Troubleshooting