admi.004 — System Event Notification

The system event notification: scheduled maintenance, incident, payment-system closing. Broadcast by operators (Eurosystem T2, The Clearing House CHIPS, Federal Reserve Fedwire, BoE CHAPS, SWIFTNet) to every connected participant to flag a status change.

Purpose and place in the flow

admi.004 is a broadcast message sent by a payment-system operator (Eurosystem for T2/T2S/TIPS, EBA Clearing for EURO1, BoE for CHAPS, Fed for Fedwire, SWIFT for SWIFTNet) to notify every connected participant of an event affecting the service: day start, settlement window close, technical incident, scheduled maintenance, settlement cut-off.

In practice, at 06:00 CET T2 emits an admi.004 «SYSTEM OPENING»; at 17:45 CET an admi.004 «CLOSING»; on an incident, an admi.004 «FREZ» (temporary freeze). Participating banks read these notifications to adjust their in-flow processing (pause sends during a freeze, trigger EOD on closing).

XML structure

admi.004 is wrapped in <Document> then the root <SysEvtNtfctn>. Minimal structure, a single block:

• EvtInf (Event Information) — single block with event code, optional parameter, description and timestamp.

Key fields

• EvtInf/EvtCd — Event code (4 chars). Published ISO 20022 external codes: OPEN (system opening), CLSD (closed), FREZ (frozen / suspended), SUSP (suspended for incident), WAIT (queueing only).
• EvtInf/EvtParam — Optional parameter scoping the event: affected window identifier, system identifier, incident identifier. Max 35 chars.
• EvtInf/EvtDesc — Textual description (max 350 chars). Read by operators on support tickets.
• EvtInf/EvtTm — Event datetime (ISO 8601 with timezone).

XML example

Notification issued by Eurosystem T2 on 16 May 2026 at 10:00 CET to flag an RTGS deferred net settlement window freeze for a technical incident, with a 30-minute postponement:

<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:admi.004.001.02">
  <SysEvtNtfctn>
    <EvtInf>
      <EvtCd>FREZ</EvtCd>
      <EvtParam>T2-RTGS</EvtParam>
      <EvtDesc>RTGS deferred net settlement window freeze for technical incident.
Settlement of accepted instructions postponed by 30 minutes.</EvtDesc>
      <EvtTm>2026-05-16T10:00:00+02:00</EvtTm>
    </EvtInf>
  </SysEvtNtfctn>
</Document>

Versions

Common pitfalls

• Proprietary vs external code confusion — each operator can publish its own codes (T2: FREZ, DRWN…) alongside generic ISO codes. Use the code the participant expects.
• Missing timezone — an EvtTm with no timezone is ambiguous for a global system. Always include the UTC offset (+02:00 CET summer).
• Unfiltered broadcast — admi.004 is sent to every participant; participating systems must filter at receive time to act only on relevant events (by BIC, by service).
• Broadcast latency — for an urgent incident, SWIFTNet broadcast latency can reach 30-60 seconds. Complement with an out-of-band channel (operator phone, email) for critical events.
• Empty or non-explicit description — EvtDesc is read on support: an empty description makes diagnosis hard. Always state the cause and expected impact.

Related messages

• admi.002 — Message Rejection (technical message reject).
• admi.005 — Report Query Request.
• admi.006 — Resend Request.
• admi.007 — Receipt Acknowledgement (positive ack).
• admi.024 — Notification of Correspondence (targeted vs broadcast).