remt: Payments Remittance Advice
remt.001 Remittance Advice
Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked
remt.001 is the ISO 20022 RemittanceAdvice message in the Payments Remittance Advice business area (remt). The latest version is remt.001.001.06, and 6 versions are in the repository.
- Message
- RemittanceAdvice
- Latest version
- remt.001.001.06
- Submitting organisation
- IFX/OAGi
- MT equivalent
- None listed
In use: published in the current ISO 20022 catalogue.
What remt.001 is for
The RemittanceAdvice message allows the originator to provide remittance details that can be associated with a payment.
remt.001 versions
Every version published in the e-Repository, newest first. A message keeps its business purpose across versions; each new version is a separate schema with its own namespace.
| Version | Registration status | Published in |
|---|---|---|
| remt.001.001.06latest | Registered | Latest version set |
| remt.001.001.05 | Registered | Previous version set |
| remt.001.001.04 | Registered | Archive |
| remt.001.001.03 | Registered | Archive |
| remt.001.001.02 | Registered | Archive |
| remt.001.001.01 | Registered | Archive |
remt.001 message structure
The building blocks of remt.001.001.06 to three levels, with multiplicity ([0..1] optional, [1..1] mandatory, * any number) and the data type or component. Element names and definitions are from the ISO 20022 repository; usage guidelines such as CBPR+ or a market infrastructure's rules can restrict them further.
Document[1..1]RmtAdvcRemittanceAdvice [1..1]GrpHdrGroup Header [1..1]GroupHeader122Set of characteristics shared by all remittance information included in the message.
MsgIdMessage Identification [1..1]Max35TextPoint to point reference, as assigned by the instructing party, and sent to the next party in the chain to unambiguously identify the message.
CreDtTmCreation Date Time [1..1]ISODateTimeDate and time at which the message was created.
AuthstnAuthorisation [0..2]Authorisation1Choice (choice)User identification or any user key to be used to check whether the initiating party is allowed to initiate transactions from the account specified...
CdCode [1..1]Authorisation1CodePrtryProprietary [1..1]Max128Text
CpyIndCopy Indicator [0..1]CopyDuplicate1CodeSpecifies if this document is a copy, a duplicate, or a duplicate of a copy.
InitgPtyInitiating Party [1..1]PartyIdentification272Party that initiates the payment.
NmName [0..1]Max140TextPstlAdrPostal Address [0..1]PostalAddress27IdIdentification [0..1]Party52Choice (choice)CtryOfResCountry Of Residence [0..1]CountryCodeCtctDtlsContact Details [0..1]Contact13
MsgRcptMessage Recipient [0..1]PartyIdentification272Party authorised by the account owner to receive information about movements on the account.
NmName [0..1]Max140TextPstlAdrPostal Address [0..1]PostalAddress27IdIdentification [0..1]Party52Choice (choice)CtryOfResCountry Of Residence [0..1]CountryCodeCtctDtlsContact Details [0..1]Contact13
FwdgAgtForwarding Agent [0..1]BranchAndFinancialInstitutionIdentification8Financial institution that receives the instruction from the initiating party and forwards it to the next agent in the payment chain for execution.
FinInstnIdFinancial Institution Identification [1..1]FinancialInstitutionIdentification23BrnchIdBranch Identification [0..1]BranchData5
RmtInfRemittance Information [1..*]RemittanceInformation23Provides information to enable the matching of an entry with the items that the associated payment is intended to settle, such as commercial invoices in an accounts' receivable system, tax obligations, or garnishment orders.
RmtIdRemittance Identification [0..1]Max35TextUnique identification, assigned by the originator, to unambiguously identify the remittance information within the message.
UstrdUnstructured [0..*]Max140TextInformation supplied to enable the matching/reconciliation of an entry with the items that the payment is intended to settle, such as commercial...
StrdStructured [0..*]StructuredRemittanceInformation18Information supplied to enable the matching/reconciliation of an entry with the items that the payment is intended to settle, such as commercial...
RfrdDocInfReferred Document Information [0..*]ReferredDocumentInformation8RfrdDocAmtReferred Document Amount [0..1]RemittanceAmount4CdtrRefInfCreditor Reference Information [0..1]CreditorReferenceInformation3InvcrInvoicer [0..1]PartyIdentification272InvceeInvoicee [0..1]PartyIdentification272TaxRmtTax Remittance [0..1]TaxData1GrnshmtRmtGarnishment Remittance [0..1]Garnishment4AddtlRmtInfAdditional Remittance Information [0..3]Max140Text
OrgnlPmtInfOriginal Payment Information [1..1]OriginalPaymentInformation10Set of elements used to provide information on the original transactions, to which the remittance message refers.
RefsReferences [1..1]TransactionReferences8PmtTpInfPayment Type Information [0..1]PaymentTypeInformation26AmtAmount [0..1]AmountType3Choice (choice)XchgRateInfExchange Rate Information [0..1]ExchangeRate1ReqdExctnDtRequested Execution Date [0..1]DateAndDateTime2Choice (choice)ReqdColltnDtRequested Collection Date [0..1]ISODateDbtrDebtor [0..1]PartyIdentification272DbtrAcctDebtor Account [0..1]CashAccount40DbtrAgtDebtor Agent [0..1]BranchAndFinancialInstitutionIdentification8CdtrCreditor [0..1]PartyIdentification272CdtrAcctCreditor Account [0..1]CashAccount40CdtrAgtCreditor Agent [0..1]BranchAndFinancialInstitutionIdentification8
SplmtryDataSupplementary Data [0..*]SupplementaryData1Additional information that cannot be captured in the structured elements and/or any other specific block.
PlcAndNmPlace And Name [0..1]Max350TextUnambiguous reference to the location where the supplementary data must be inserted in the message instance.
EnvlpEnvelope [1..1]SupplementaryDataEnvelope1Technical element wrapping the supplementary data.
Have a remt.001 message? Paste it into the parser to see every element with its name and definition, and format checks on BICs, IBANs, dates and amounts.
External code sets used in remt.001
These elements take their values from ISO 20022 external code sets, which are published separately and updated every quarter without a new message version.
- ExternalAccountIdentification1Code4 codes
- ExternalCashAccountType1Code28 codes
- ExternalCategoryPurpose1Code49 codes
- ExternalClearingSystemIdentification1Code172 codes
- ExternalCreditorReferenceType1Code7 codes
- ExternalDateType1Code5 codes
- ExternalDocumentAmountType1Code27 codes
- ExternalDocumentLineType1Code19 codes
- ExternalDocumentType1Code23 codes
- ExternalFinancialInstitutionIdentification1Code0 codes
- ExternalGarnishmentType1Code3 codes
- ExternalLocalInstrument1Code114 codes
- ExternalOrganisationIdentification1Code15 codes
- ExternalPersonIdentification1Code11 codes
- ExternalProxyAccountType1Code22 codes
- ExternalServiceLevel1Code29 codes
remt.001 questions
- What is the latest version of remt.001?
- The latest version in the ISO 20022 e-Repository release of 24 April 2025 is remt.001.001.06.
- What is the root element of remt.001?
- The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:remt.001.001.06, and its message element is RmtAdvc (RemittanceAdvice).
- Is there an MT equivalent of remt.001?
- No Swift MT message is listed as its direct equivalent on this site. Many ISO 20022 messages have no MT counterpart.
All ISO 20022 messages · ISO 20022 code sets · MT messages
The ISO 20022 message definitions, element names and definitions on this page are reproduced from material published at iso20022.org under the ISO 20022 Intellectual Property Rights policy. This is not the official source: the up-to-date ISO 20022 standards and repository material are published only at iso20022.org. Explanations in our own words are by ZagTrader. ZagTrader is not affiliated with or endorsed by ISO or Swift.