reda.066 — Calendar Detail Report

The detailed operational calendar of a payment or settlement system: business days, holidays, special operational windows. Published by operators (T2S, T2, Fedwire, CHIPS, EBA Clearing) so participants can calibrate their own internal calendars.

Purpose and place in the flow

reda.066 publishes the detailed calendar of a payment / settlement system over a given period (typically the whole year). Each day is classified as open or holiday, with an optional description (extended window, partial opening, national holiday affecting only a subset of the system).

Flow context: participants download reda.066 at year-end (typical Q4 for the next year) and integrate it into back-office systems to calibrate business-day computations, cut-off windows, interest calculations. Mid-year, ad hoc reda.066 may be published on changes (national holiday declared, exceptional closure).

XML structure

reda.066 is wrapped in <Document> then the root <CalDtlRpt>. Structure:

• MsgHdr (Message Header) — Identifier + creation datetime.
• Cal (Calendar) — Main block.
• Sys/SysId — System identifier (T2-RTGS, T2S, FedWire, CHIPS).
• CalYr (Calendar Year) — Year covered.
• BizDay (Business Day) — Repeated block: each notable day with date, type, description.

Key fields

• MsgHdr/MsgId — Report identifier (max 35 chars).
• MsgHdr/CreDtTm — Creation datetime (ISO 8601 with timezone).
• Cal/Sys/SysId — System identifier (T2-RTGS, T2S, FED-WIRE, CHIPS, EURO1, CHAPS-RTGS, SWIFTNET).
• Cal/CalYr — Calendar year (YYYY).
• Cal/BizDay/Dt — Date of the notable day (ISO YYYY-MM-DD).
• Cal/BizDay/Tp — Type: OPEN (open with specifics), HOLI (holiday, closed), HALF (half-day).
• Cal/BizDay/Desc — Description (max 350 chars) — holiday name, reason, impact.

XML example

Q3 2026 calendar report for the Eurosystem T2 RTGS system sent on 16 May 2026, listing three notable days: 14 July (closed for French national holiday), 15 August (Assumption, T2 closed), 30 September (open with extended cut-off for quarter-end):

<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:reda.066.001.01">
  <CalDtlRpt>
    <MsgHdr>
      <MsgId>T2-CAL-2026-Q3</MsgId>
      <CreDtTm>2026-05-16T16:00:00+02:00</CreDtTm>
    </MsgHdr>
    <Cal>
      <Sys>
        <SysId>T2-RTGS</SysId>
      </Sys>
      <CalYr>2026</CalYr>
      <BizDay>
        <Dt>2026-07-14</Dt>
        <Tp>HOLI</Tp>
        <Desc>Bastille Day — TARGET system closed (France).</Desc>
      </BizDay>
      <BizDay>
        <Dt>2026-08-15</Dt>
        <Tp>HOLI</Tp>
        <Desc>Assumption — TARGET system closed.</Desc>
      </BizDay>
      <BizDay>
        <Dt>2026-09-30</Dt>
        <Tp>OPEN</Tp>
        <Desc>Quarter-end. Extended cut-off 18:00 CEST.</Desc>
      </BizDay>
    </Cal>
  </CalDtlRpt>
</Document>

Versions

Common pitfalls

• Partial calendar — a reda.066 covers only a period. For the full year, wait for the initial Q4 N-1 publication. For ad hoc updates, follow admi.004 notifications.
• Proprietary SysId — each operator has its own SysId (T2-RTGS, T2S, FED-WIRE). No universal norm; consult operator documentation.
• Tp OPEN misread — OPEN + Desc = open day with specifics (extended cut-off, partial opening). Without Desc, it is just a normal-opening reminder.
• Timezones — the calendar is in operator local time. T2 is CET/CEST. An APAC participant must convert to calibrate its own cut-offs.
• Half-day not handled — HALF indicates a shortened day (e.g. Christmas Eve in the US where Fedwire closes at 14:00). Business-day calculations must factor it in (not a full business day).
• Retroactive update impossible — a reda.066 published in July cannot modify the January-June calendar. For historical corrections, contact operator N2/N3.

Related messages

• reda.029 — Calendar Query (calendar request that triggers reda.066).
• reda.008 — Security Reference Data Update Request.
• admi.004 — System Event Notification (ad hoc, vs predictable calendar).
• admi.024 — Notification of Correspondence.