Holiday calendars is where your organisation keeps its own calendars: named lists of closed days, the dates on which business does not happen. The platform reads them in three places.
A filing deadline rule that counts business days skips every closed day, a trading venue does not trade on a day its calendar closes, and a bank rail connection counts its payment days, cut-off and deadlines on its calendar, as Set when the bank takes payments describes.
Saturday and Sunday need no entry, because the deadline calculation never counts them as business days. A bank rail connection set to No holiday calendar counts every day as a business day, weekends included.
Each calendar can extend a base calendar: a calendar the platform ships for a whole market, such as the TARGET2 settlement calendar. An extending calendar inherits every day its base closes and adds the days that only your organisation observes, such as an office closure or a local holiday. Other organisations cannot see the days your organisation closes. Platform administrators publish and maintain the base calendars on Base calendars.
The “Holiday calendars” table, with one row for each calendar your organisation owns.
The table has the columns “Calendar”, “Jurisdiction”, “Closed this year” and “Next closure”, and each row holds a Close a day button. A trading venue's calendar also appears, with “Trading venue” as its jurisdiction and “Managed on the venue” in place of the button. “New calendar” sits at the top of the page.
Steps
Create a calendar
Select New calendar at the top of the page. The sheet reads “Closed days on this calendar are seen by your organisation alone.”
- Enter a Name.
- Choose a Jurisdiction: a country, or a regional code such as EU. The jurisdiction labels the calendar in the table and in every list where it is offered. It does not change which days are closed.
- In Extends, choose the calendar to inherit from: the list offers “Extends nothing”, the platform's base calendars and your organisation's own calendars, each shown as the name with its jurisdiction. Another organisation's calendar is never offered, and a venue's own calendar is not offered as a parent.
- Optionally add a Reason (optional) of up to 1,000 characters, which the platform records in the audit trail with the change.
- Select Create calendar. Until the form is complete the button stays unavailable and says “Enter a name to publish.” or “Choose a jurisdiction to publish.”
The message “A calendar with this name already exists. Choose another name.” means the name produces an identifier your organisation already uses. Choose a different name. A name that forms no identifier reads “Calendar name can't form an identifier. Use Latin letters or digits, and replace any letters from other alphabets.” A new calendar closes no day of its own until you close one.
Close a day
- On the calendar's row, select Close a day. The dialog “Close a day on
<calendar>” opens. - Choose the Date in the calendar, or the dialog says “Choose the date to close.” The calendar offers days from 1 January 2024 through 31 December of the tenth year after the current year.
- Choose a Reason: “Public holiday”, “Bank holiday”, “Settlement holiday”, “Exchange holiday”, or “One-off closure”. The reason is a label for whoever reads the calendar later. It does not change how a deadline or a venue treats the day: every closed day is closed in the same way.
- Optionally enter a Name (optional) of up to 120 characters for the day, such as “Christmas Eve”, and a “Reason (optional)” of up to 1,000 characters for the audit trail.
- Select Close a day. A second dialog names the day, for example “Close 24 Dec 2026?”, and says “A closed day is added and never removed, so 24 Dec 2026 stays closed for good.” Check the year: every calendar and venue below this calendar in a chain stops counting it as a business day. Type the day as the dialog shows it, then select “Close 24 Dec 2026” to add it, or “Keep 24 Dec 2026 open” to go back and change the date.
Closing a day that the base calendar or this calendar already closes is harmless: the day stays closed once. Closing the same day again with another reason, or as another owner or platform administrator, adds a second line under that year, and the day still counts once. Close a weekend day only for a venue that trades at the weekend: a filing deadline never counts Saturday or Sunday.
Read the calendars
The page lists the calendars your organisation owns in a table, and Search calendars filters it. The table has four columns:
- Calendar shows the name and what it extends, such as “extends TARGET2 settlement calendar”.
- Jurisdiction shows the calendar's jurisdiction.
- Closed this year counts the closed days, such as “3 days”.
- Next closure shows the next closed day, or “None scheduled” when there is none.
The last cell of each row holds Close a day, or for a venue's own calendar the link “Managed on the venue” to the venue's “Trading calendar” tab. With no calendar, the page reads “No organisation calendars yet” with “Create one to close a day of your own.”
Expand a row to read its closed days. A note such as “Extends TARGET2 settlement calendar” names the chain, and the days are grouped under a heading for each year with its count, such as “3 closed days”. The columns are “Date”, “Name” (shown when some day has a name), “Reason” and Added by.
In “Added by” an inherited day shows “from” and the name of the calendar that closes it, for example “from Northwind closures”. Days closed on your organisation's calendars show “Organisation administrator”, also when a platform administrator closed them, and a platform base day shows “Platform administrator”. The Audit trail names the person who closed each day.
A day from a published source shows that source, with any web address in it shown as a link named by its site. A calendar with no closed day reads “This calendar has no closed days yet”.
The list can also show two kinds of calendar that you did not create on this page. A calendar that carries a base calendar's name is the extension the platform creates when a venue administrator picks that base for a venue. It mirrors the base, and the platform refuses a closed day on it. A venue's own calendar shows “Trading venue” as its jurisdiction and “Managed on the venue” where the “Close a day” button would be, because only the venue's Trading calendar tab can close a day on it.
How a calendar chain decides a closed day
A calendar's closed days are its own days plus every day closed by the calendars above it in its chain. “Extends” names the calendar directly above. A chain holds at most eight calendars, and the platform refuses a parent that would make the chain longer or make a calendar extend itself through another one.
Each calendar sees every day closed above it, and it can add days but never remove one it inherits.
The chain has three levels. A venue administrator chooses a venue's trading week and parent calendar, and can add, edit and delete venue-only closed days dated from the current date onward. The table shows who manages each level.
The platform ships four base calendars. “TARGET2 settlement calendar”, “UK bank holidays (England and Wales)”, and “US federal holidays” carry closed days computed from their published rules for 2024 through 2040. “ADGM business days (UAE public holidays)” carries only the UAE public holidays that have been announced, because the UAE can move a holiday. Each later date is added once it is announced.
Closed days and computed deadlines
Every closed day records when the platform learned about it. When the platform computes a filing deadline, it counts only the closed days it knew about at that moment. A day closed afterwards does not move a deadline that was already computed, so a deadline that a filer has relied on stays fixed. Changing the calendar a calendar extends, which only the Platform API can do, replaces what it inherits: the old parent's days stop applying, and the new parent's days count only from the moment of the change.
The venue's Trading calendar tab states the rule for venues: “A day closed here shuts this venue alone. A day inherited from the shared calendar shuts every venue that extends it.” Trading calendar explains what an instrument does on a day with no session.
Troubleshooting
Calendars could not be read
The error card “Calendars could not be read” says “The calendars this organisation owns could not be read. Reload to try again.” when the organisation's own calendars fail to load. When only the base calendars fail, the page still shows the table, with a Base calendars line and a retry control. Reload the page. If the message stays, check Platform status for a platform fault before you retry.
The calendar or the day could not be saved
A failed create reads “The calendar could not be stored.” and a failed closed day reads “The day could not be closed.” Check the form for a name that is taken or a date outside the allowed range, then try again.
The Create calendar button stays disabled
Create calendar needs a name that is free and a jurisdiction. A name that collides with an existing calendar shows the message “A calendar with this name already exists. Choose another name.” under the field. A name made only of punctuation, or containing a letter or digit from another script such as Chinese, Cyrillic or Arabic, produces no identifier, so the button stays disabled until the name uses only Latin letters and digits. Accented Latin letters are fine: “Café” gives “cafe”. If another administrator creates that name while your form is open, your create is refused. The existing calendar stays unchanged, and your form keeps its inputs. Choose another name and create again.
A day was closed by mistake
A closed day cannot be removed, by your organisation or by a platform administrator. Deadlines computed before the mistake keep their dates. Deadlines computed after it skip the day, and a venue that extends the calendar does not trade on it. If the mistake must not affect a venue, point the venue at a different calendar in Holiday calendar on its “Trading calendar” tab.
Creating a calendar with a parent is refused
A chain holds at most eight calendars. The platform refuses a parent whose chain is already eight calendars long, with “The holiday calendar would reference itself”, the same message as a cycle. Choose a parent higher up the same chain, or a base calendar directly.
A deadline did not move after a day was closed
This is expected when the deadline was computed before the day was closed. A deadline counts only the closed days the platform knew about when it computed the deadline, so a later closure applies to deadlines computed after it.
Holiday calendars is not in the sidebar
The entry appears only for an organisation owner or a platform administrator with an active organisation. Ask an owner of your organisation to make the change, or to give you the Owner role if your organisation intends that. Roles and permissions lists the roles.
Frequently asked questions
Can I reopen a day that a base calendar closes?
No. The Console has no control that removes an inherited day. Through the Platform API, changing a calendar's parent stops the old parent's days counting for deadlines computed after the change and for every venue that extends the calendar. Deadlines computed before it keep their dates. If your organisation trades or files on a day a base closes, create a calendar that extends nothing and close every day yourself, or ask a platform administrator whether a different base calendar fits your market.
Does a day my organisation closes affect another organisation?
No. Days closed on your organisation's calendars are visible to your organisation only. Only a day closed on a base calendar reaches every organisation whose calendar extends that base.
Can I delete a calendar?
No. Neither the Console nor the Platform API deletes a holiday calendar. A calendar you no longer need stays in the list. Stop using it by pointing each venue at another calendar on its Trading calendar tab and each reporting obligation at another calendar through the API.
Do I have to close Saturdays and Sundays?
Not for filing deadlines: the deadline calculation never counts Saturday or Sunday as a business day. A venue's trading week is set separately on its Trading calendar tab, so a weekend closure matters only for a venue that trades on a weekend day.
Why does my list show a calendar named after a base calendar?
A venue administrator picked that base calendar for a venue. The platform then creates a calendar for your organisation that extends the base, and the venue's own calendar extends that one. It mirrors the base. The Console shows Close a day on it, but the platform refuses the write with “The holiday calendar was not found”. To add days for venues on top of a base, create your own calendar that extends the base, close the days there, and point each venue at it on its “Trading calendar” tab.
API routes
The Platform API exposes the same operations under the organisation settings calendar endpoints: GET /api/ lists your calendars, GET /api/ lists the base calendars, PUT /api/ creates or updates a calendar (send If- to refuse an id that exists), and POST /api/ adds a closed day.
The Console gives a calendar it creates the id org:<organisation. A parent that would make a cycle or a chain longer than eight answers 409 PLATFORM_ (DALP-14351), and an id that is taken answers 409 PLATFORM_ (DALP-14352).
A create or update through the API can also change an existing calendar's name, jurisdiction, or parent, which the Console does not offer. The request and response shapes are in the Platform API reference.
A filing deadline rule names the calendars it counts against when you configure a reporting obligation through the API. Reporting obligations explains how a deadline rule uses them.