# MESSAGE acmt.024 Identification Verification Report

The `acmt.024` is the response to the `acmt.023` proxy resolution or account resolution request.

For further detail on each element in the `acmt.023` and `acmt.024`, please refer to the [Message Guidelines (Excel)](/messaging-and-translation/message-guidelines-excel.md).

### Structure of the acmt.024 Identification Verification Response V03 <a href="#toc159257084" id="toc159257084"></a>

<figure><img src="/files/4tKmFJXx5T9BmzWdUZpW" alt=""><figcaption><p>Main blocks of the acmt.024 Identification Verification Request</p></figcaption></figure>

The `acmt.024` is also split into two blocks:

* Similarly to the `acmt.023` message, the `acmt.024` the **Assignment** block contains information about who is making the request and providing the response
  * **Creator** remains the same as the `acmt.023`, describing the Sender who made the original proxy or account resolution request
  * **First Agent** remains the same as the `acmt.023`, describing the Source PSP
  * **Assigner** changes to the Destination Proxy Directory Operator
  * **Assignee** changes to the Source PSP (ie is the same as First Agent)
* The **Report** block contains the information about the Recipient:
  * **Verification** is either *true* (if the payment can proceed) or *false* (if any error means that the payment cannot proceed)
  * **Reason** will only be filled if Verification is false, and will contain an error code explaining why the verification failed (eg proxy not registered). (See [#toc143525641](#toc143525641 "mention") *below*).
  * **OriginalPartyAndAccountIdentification** is an exact copy of the “PartyAndAccountIdentification” from the `acmt.023`
  * **UpdatedPartyAndAccountIdentification** is where the updated information (from either the Proxy Directory or the Destination PSP) is provided

## acmt.024 for Proxy Resolution <a href="#toc143525638" id="toc143525638"></a>

For a proxy resolution request, the Destination PSP should add the following information to the *UpdatedPartyAndAccountIdentification* block:

* *… > Party > Name –* this is the verified name of the account holder, in full. It can be used by the Source PSP for sanctions screening.
* *… > Account > Identification > IBAN or Account > Identification > Other > Identification -* this identifies the specific account of the Recipient/Creditor
* *… > Account > Name* (in Nexus this is the display name of the Recipient, which can be shown to the Sender)
* *… > .Agent > FinancialInstitutionIdentification > BICFI* (or *Agent > FinancialInstitutionIdentification > ClearingSystemMemberIdentification > MemberIdentification*, for non-BIC IDs)

## acmt.024 for Account Resolution <a href="#toc143525639" id="toc143525639"></a>

For an account resolution, the Destination PSP should add the following information added to the *UpdatedPartyAndAccountIdentification* block:

* *… > Party > Name*
* *… > Party > PostalAddress*
  * At least Country and Town Name should be provided here, to support with sanctions screening and other compliance checks and to ensure alignment with the [CPMI’s ISO 20022 harmonization requirements](https://www.bis.org/cpmi/publ/d218.htm).
* (Optional) *Party > Identification > PrivateIdentification > DateAndPlaceOfBirth*
  * This is optional but can help to reduce false alerts against sanctions screening lists
* *Account > Name*
  * To be used as the display name shown to the Sender, to enable confirmation of payee. This display name can be partially masked.

## Message transformation by Nexus <a href="#toc143525640" id="toc143525640"></a>

When an `acmt.024` travels through Nexus, Nexus will update the Assignee to the Id of the Source PSP. This is the only change.

## Error codes <a href="#toc143525641" id="toc143525641"></a>

If there is an error either with proxy resolution or account resolution, an `acmt.024` should be sent:

* The element *… > Report > Verification* should be set to false
* The element *… > Report > Reason > Code* should be set to the appropriate error code from the table below

Error codes are taken from the ISO 20022 External Code Set.

The standard `acmt.024` [Message Guidelines (Excel)](/messaging-and-translation/message-guidelines-excel.md) specify that error codes must be from the **ExternalVerificationReason1Code** set, but there are only 3 codes in this set and they are insufficient. For that reason, we propose to also permit codes from **the ExternalStatusReason1Code** set, with the following limited code set:

#### Table: ISO 20022 Error Codes for use in Nexus acmt.024 <a href="#toc143525642" id="toc143525642"></a>

<table data-header-hidden data-full-width="true"><thead><tr><th></th><th width="85"></th><th></th><th width="190"></th><th></th></tr></thead><tbody><tr><td><strong>Code Type</strong></td><td><strong>Code Value</strong></td><td><strong>Code Name</strong></td><td><strong>Nexus-specific meaning</strong></td><td><strong>Proxy / Account Resolution</strong></td></tr><tr><td>ExternalVerificationReason1Code</td><td>AC01</td><td>Incorrect Account Number</td><td>Account number provided does not match any account held by the Creditor Agent</td><td>Account</td></tr><tr><td>ExternalStatusReason1Code</td><td>AC04</td><td>Closed Account Number</td><td>Account number specified has been closed on the Receiver’s books</td><td>Account</td></tr><tr><td>ExternalStatusReason1Code</td><td>AC06</td><td>Blocked Account</td><td>Account specified is blocked, prohibiting posting of transactions against it.</td><td>Account</td></tr><tr><td>ExternalVerificationReason1Code</td><td>AGNT</td><td>Incorrect Agent</td><td>The PSP exists but is not onboarded with Nexus, so cannot receive Nexus payments. Alternative payment rails may work. (Contrast to <code>RC07</code> Invalid Creditor BIC)</td><td>Both</td></tr><tr><td>ExternalStatusReason1Code</td><td>AB08</td><td>Offline Creditor Agent</td><td>Creditor Agent is not able to respond to account resolution requests, either permanently (they don’t have the capability) or temporarily (they are offline or have a technical issue).</td><td>Account</td></tr><tr><td>ExternalStatusReason1Code</td><td>BE23</td><td>Account Proxy Invalid</td><td>Proxy is not registered (No account is associated with the proxy provided)</td><td>Proxy</td></tr><tr><td>ExternalStatusReason1Code</td><td>DUPL</td><td>Duplicate Request</td><td></td><td>Both</td></tr><tr><td>ExternalStatusReason1Code</td><td>FRAD</td><td>Fraudulent Origin</td><td>Proxy directory, IPSO or Destination PSP suspects abuse of the proxy resolution service by the Sender and is refusing additional requests from this Sender.</td><td>Both</td></tr><tr><td>ExternalStatusReason1Code</td><td>MD07</td><td>End Customer Deceased</td><td></td><td>Both</td></tr><tr><td>ExternalStatusReason1Code</td><td>RC06</td><td>Invalid Debtor BIC Identifier</td><td>BIC provided is not a valid BIC.</td><td>Both</td></tr><tr><td>ExternalStatusReason1Code</td><td>RC07</td><td>Invalid Creditor BIC Identifier</td><td>The FI ID is not valid or blank. Could be used for account resolution or proxy resolution where the Creditor Agent BIC is required, such as the Philippines. (In contrast to <code>AGNT</code>, <code>RC07</code> means that the FI ID is incorrect and the PSP is not found.)</td><td>Both</td></tr><tr><td>ExternalStatusReason1Code</td><td>RR01</td><td>Missing Debtor Account Or Identification</td><td>The Destination Country requires further information about the Sender in order to pre-screen the Sender.</td><td>Both</td></tr><tr><td>ExternalStatusReason1Code</td><td>RR02</td><td>Missing Debtor Name Or Address</td><td>The Destination Country requires further information about the Sender in order to pre-screen the Sender.</td><td>Both</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nexusglobalpayments.org/messaging-and-translation/message-acmt.024-identification-verification-report.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.