Account Management

IdentificationVerificationReportV04

acmtarea

024message

001variant

04version

Account Management

The VoP answer: match, close match with the correct name returned, or no match.

Start with the payment story

SEPA Instant

Then the technical flows

Schema versions

SWIFT and ISO publish successive XSD revisions of the same business message (e.g. pacs.008.001.08 → .10 → .13; same pattern for camt and pain). Markets pin one via a usage guideline (EPC SEPA, CBPR+, Swiss SPS…) and may add a country suffix (pacs.008.001.08.ch.02) — the Document xmlns must match that XSD.

ISO catalogue (XSD) ↗SWIFT / CBPR+ ↗SWIFT & versioning glossary →

Catalogue entry acmt.024.001.04 (variant 001, version 04).

Facts

Root element: IdVrfctnRpt
Direction: Bank → bank
Namespace: urn:iso:std:iso:20022:tech:xsd:acmt.024.001.04
Variant (flavour): 001
Version: 04

vopmatchreportacmtipr

Elements a validator will insist on

Not the full XSD — the paths whose absence causes the rejections you actually see in production.

IdVrfctnRpt/Assgnmt/MsgId
IdVrfctnRpt/Rpt/OrgnlId
IdVrfctnRpt/Rpt/Vrfctn

Usage in flows

ISO 20022 payload· XML

acmt.024 verification report (close match)

A close match. Vrfctn=false with UpdtdPtyAndAcctId carrying the correct legal name — show it to the PSU and let them decide, but do not auto-correct. Switch XML | JSON in the inspector without leaving this sample.

<Agt>

<BICFI>COBADEFFXXX</BICFI>

</FinInstnId>

</Agt>

</Assgnr>

<Agt>

<BICFI>DEMOFRPPXXX</BICFI>

</FinInstnId>

</Agt>

</Assgne>

</Assgnmt>

</OrgnlAssgnmt>

<Rpt>

<Vrfctn>false</Vrfctn>

<Rsn>

</Rsn>

<Pty>

<Nm>Atelier Rousseau SARL</Nm>

</Pty>

<Acct>

<Id>

</Id>

</Acct>

</OrgnlPtyAndAcctId>

<Pty>

<Nm>Atelier Rousseau S.A.R.L.</Nm>

</Pty>

</UpdtdPtyAndAcctId>

</Rpt>

</IdVrfctnRpt>

</Document>

Open in Try editor →

Edit in the XML / JSON tab, then run the check.