Holiday calendars
Create the calendars your organisation owns and close the days on which its filing deadlines and trading venues do not count.
A holiday calendar is a named list of closed days: dates on which business does not happen. The platform reads them in two places. A filing deadline rule that counts business days skips every closed day, and a trading venue does not trade on a day its calendar closes. Saturday and Sunday need no entry, because the deadline calculation never counts them as business days.
"Holiday calendars" is where your organisation keeps its own calendars. Each one 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. Days your organisation closes are visible to your organisation alone. Platform administrators publish and maintain the base calendars on Base calendars.
Use this page when a deadline or a venue must skip a day that the base calendar does not close, or when a venue or a reporting duty needs a calendar of its own to point at. Do not use it to change a base calendar's days: an organisation can add days on top of a base, but it cannot reopen a day the base closes.
A closed day is permanent. The confirmation dialog says so: "A closed day is added, never removed. A correction published later never moves a deadline that was already computed." Check the date before you confirm, because the Console has no control that reopens a day.
Each calendar sees every day closed above it. A calendar can add days, never remove one it inherits.
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.
The chain has three levels in practice. A venue administrator chooses its trading week and parent calendar. A venue operator or administrator can add venue-only closed days:
| Level | Who manages it | Where | Who sees its closed days |
|---|---|---|---|
| Base calendar | A platform administrator | Base calendars | Every organisation whose calendar extends it |
| Holiday calendar | An Owner or Admin of your organisation | This page | Your organisation only |
| Venue calendar | Venue administrator; operator for closed days | The venue's "Trading week" tab, under Venues | That venue only |
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 week" 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." Venue operations explains what a market does on a day with no session.
Before you start
Steps
Open Holiday calendars
Open Organisation settings, then "Holiday calendars" under Business operations. The page lists the calendars your organisation owns. Each card shows the calendar's name, its chain, such as "Northwind closures → TARGET2 settlement calendar", and a jurisdiction badge. Closed days are grouped by year, and an inherited day is marked "inherited from" with the name of the calendar that closes it. The card also shows the reasons and sources of its closed days. A shared reason or source appears once above the year groups. "Platform administrator" and "Organisation administrator" identify manually added closures, not the person who added them. Inherited seeded dates retain their published provenance, and venue-only dates show their venue source.
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 appears without a "Close a day" button, because only the venue's "Trading week" tab can close a day on it.
Create a calendar
Under "Create a calendar", enter a "Name" and choose a "Jurisdiction": a country, or a regional code such as EU. The jurisdiction labels the calendar on its card 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 the platform's base calendars and your organisation's own calendars, each shown with its jurisdiction. Another organisation's calendar is never offered. Select "Create".
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 new calendar closes no day of its own until you close one.
Close a day
On the calendar's card, select "Close a day". Enter the "Date" and 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.
Read the dialog before you confirm. The day cannot be reopened, and every calendar and venue below this calendar in a chain stops counting it as a business day. Select "Close a day" in the dialog to add it.
Closing a day that the base calendar or this calendar already closes is harmless: the day stays closed once. Close a weekend day only for a venue that trades at the weekend: a filing deadline never counts Saturday or Sunday.
API equivalents
The Platform API exposes the same operations under the organisation settings calendar endpoints: list your calendars, list the base calendars, create or update a calendar, and add a closed day. 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.
Troubleshooting
Calendars could not be read
The page shows "Calendars could not be read" when it cannot load your organisation's calendars or the base calendars behind them. Reload the page. If the message stays, check Platform status for a platform fault before you retry.
The Create button stays disabled
"Create" 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 produces no identifier, so the button stays disabled until the name contains a Latin letter or a digit.
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 holiday calendar on its "Trading week" 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 a message that extending it "would put the chain past 8 calendars". 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 Admin with an active organisation. Ask an owner of your organisation for the Admin role on Admins and roles.
Frequently asked questions
Can I reopen a day that a base calendar closes?
No. A calendar inherits every day closed above it, and no organisation can remove an inherited day. If your organisation genuinely 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 week" 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 week" 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 a message that starts "No visible holiday calendar is configured under the identifier". 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 week" tab.
Related pages
- Base calendars: the platform-wide calendars an organisation calendar extends.
- Venue operations: where a venue picks its holiday calendar and sets its trading week.
- Reporting obligations: how a deadline rule counts business days.