acmt: Account Management
acmt.023 Identification Verification Request
Written and maintained by ZagTrader. Last reviewed . How this page is sourced and checked
acmt.023 is the ISO 20022 IdentificationVerificationRequest message in the Account Management business area (acmt). The latest version is acmt.023.001.04, and 4 versions are in the repository.
- Message
- IdentificationVerificationRequest
- Latest version
- acmt.023.001.04
- Submitting organisation
- GUF
- MT equivalent
- None listed
In use: published in the current ISO 20022 catalogue.
What acmt.023 is for
The IdentificationVerificationRequest message is sent by an assigner to an assignee. It is used to request the verification of party and/or account identification information.
The IdentificationVerificationRequest message is sent before the sending of one or several transactions messages.
The IdentificationVerificationRequest message can contain one or more verification requests.
acmt.023 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 |
|---|---|---|
| acmt.023.001.04latest | Registered | Latest version set |
| acmt.023.001.03 | Registered | Previous version set |
| acmt.023.001.02 | Registered | Archive |
| acmt.023.001.01 | Registered | Archive |
acmt.023 message structure
The building blocks of acmt.023.001.04 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]IdVrfctnReqIdentificationVerificationRequest [1..1]AssgnmtAssignment [1..1]IdentificationAssignment4Identifies the identification assignment.
MsgIdMessage Identification [1..1]Max35TextPoint to point reference, as assigned by the assigner, 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 identification assignment was created.
CretrCreator [0..1]Party50Choice (choice)Party that created the identification assignment.
PtyParty [1..1]PartyIdentification272AgtAgent [1..1]BranchAndFinancialInstitutionIdentification8
FrstAgtFirst Agent [0..1]BranchAndFinancialInstitutionIdentification8Identifies the first agent in the identification chain, following the payment initiating party.
FinInstnIdFinancial Institution Identification [1..1]FinancialInstitutionIdentification23BrnchIdBranch Identification [0..1]BranchData5
AssgnrAssigner [1..1]Party50Choice (choice)Party that assigns the identification assignment to another party.
PtyParty [1..1]PartyIdentification272AgtAgent [1..1]BranchAndFinancialInstitutionIdentification8
AssgneAssignee [1..1]Party50Choice (choice)Party that the identification assignment is assigned to.
PtyParty [1..1]PartyIdentification272AgtAgent [1..1]BranchAndFinancialInstitutionIdentification8
VrfctnVerification [1..*]IdentificationVerification5Information concerning the identification data that is requested to be verified.
IdIdentification [1..1]Max35TextUnique identification, as assigned by a sending party, to unambiguously identify the party and account identification information group within the...
PtyAndAcctIdParty And Account Identification [1..1]IdentificationInformation5Party and/or account identification information for which verification is requested.
PtyParty [0..1]PartyIdentification272AcctAccount [0..1]CashAccount40AgtAgent [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 acmt.023 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 acmt.023
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
- ExternalClearingSystemIdentification1Code172 codes
- ExternalFinancialInstitutionIdentification1Code0 codes
- ExternalOrganisationIdentification1Code15 codes
- ExternalPersonIdentification1Code11 codes
- ExternalProxyAccountType1Code22 codes
acmt.023 questions
- What is the latest version of acmt.023?
- The latest version in the ISO 20022 e-Repository release of 24 April 2025 is acmt.023.001.04.
- What is the root element of acmt.023?
- The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:acmt.023.001.04, and its message element is IdVrfctnReq (IdentificationVerificationRequest).
- Is there an MT equivalent of acmt.023?
- 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.