admi.024 — Notification of Correspondence

The targeted notification that a document, correspondence or reference change has been made available. Used by an operator or bank to flag a specific recipient (vs broadcast). admi sub-domain.

Purpose and place in the flow

admi.024 is used to targetedly notify a recipient that some content (correspondence, document, reference) is now available. Unlike admi.004 (broadcast to all), admi.024 targets a specific BIC. Typical for compliance reports, attestations, implementation notes, or to announce a client reference change (RAC, IBAN, BBAN).

Flow context: a system operator publishes a document on its secure portal, then sends admi.024 to the affected participant with the document reference. On receipt, the participant downloads the document via its standard channel.

XML structure

admi.024 is wrapped in <Document> then the root <NtfctnOfCrspdc>. Three main blocks:

• CrspdcId (Correspondence Identification) — unique notification identifier + datetime.
• CrspdcRcrd (Correspondence Record) — content metadata: reference, type, description, attached document.
• CrspdcRcvr (Correspondence Receiver) — targeted recipient (BIC or identifier).

Key fields

• CrspdcId/Id — Unique notification identifier (max 35 chars).
• CrspdcId/CreDtTm — Creation datetime (ISO 8601 with timezone).
• CrspdcRcrd/RcrdRef — Content reference (typically the made-available document identifier).
• CrspdcRcrd/RcrdTp — Correspondence type, 4-char code: MAIN (maintenance), IMPL (implementation guide), CONF (conformity), RGCH (reference change), NTCH (notification change).
• CrspdcRcrd/RcrdDesc — Textual description (max 350 chars).
• CrspdcRcrd/AttchdDocId — Attached document identifier or pointer to the portal.
• CrspdcRcvr/BICFI — Receiver BIC (8 or 11 chars).

XML example

Notification sent by Eurosystem T2 on 16 May 2026 to BNP Paribas for the availability of a Q2 2026 patch implementation note required before the 21 June 2026 production deployment window:

<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:admi.024.001.01">
  <NtfctnOfCrspdc>
    <CrspdcId>
      <Id>T2-CORR-20260516-001</Id>
      <CreDtTm>2026-05-16T11:30:00+02:00</CreDtTm>
    </CrspdcId>
    <CrspdcRcrd>
      <RcrdRef>T2-MAINT-2026-Q2-NOTICE</RcrdRef>
      <RcrdTp>MAIN</RcrdTp>
      <RcrdDesc>Q2 2026 mandatory patch deployment in TEST environment.
Production target window: 2026-06-21T00:00 to 2026-06-21T04:00 CEST.
Participant action: please review attached Implementation Notes and confirm readiness by 2026-06-15.</RcrdDesc>
      <AttchdDocId>T2-IMPL-NOTES-2026-Q2-V1</AttchdDocId>
    </CrspdcRcrd>
    <CrspdcRcvr>
      <BICFI>BNPAFRPP</BICFI>
    </CrspdcRcvr>
  </NtfctnOfCrspdc>
</Document>

Versions

Common pitfalls

• Non-standard RcrdTp — use the published external ISO codes. A proprietary code (T2-MTC) is not interpretable by other operators.
• Empty description — without RcrdDesc, the recipient does not know why it received the notification. Always state the expected action and deadline.
• Wrong recipient — a wrong BIC in CrspdcRcvr sends the notification to the wrong bank. Validate the BIC against the SWIFT BIC Directory.
• Document not yet published — sending an admi.024 referencing a document not yet on the portal. Always publish first, then notify.
• Confusion with admi.004 — admi.004 is broadcast (everyone), admi.024 is targeted (one BIC). Confusing the two leads to noise for other participants or a missed notification for the target.
• Missing timestamp — CreDtTm is mandatory and must include the timezone: essential for operator log correlation.

Related messages

• admi.002 — Message Rejection.
• admi.004 — System Event Notification (broadcast vs targeted).
• admi.005 — Report Query Request.
• admi.006 — Resend Request.
• admi.007 — Receipt Acknowledgement.