Base calendars
Publish the platform-wide holiday calendars that every organisation can extend, and close days on them for every organisation at once.
A base calendar is a holiday calendar the platform offers to every organisation: a named list of closed days for one market, such as the TARGET2 settlement calendar. An organisation does not edit a base calendar. It extends one: its own calendar, created on Holiday calendars, inherits every day the base closes and adds days of its own. Filing deadlines that count business days skip those closed days, and a trading venue does not trade on them.
"Base calendars" is where a platform administrator publishes these calendars and keeps their closed days current. A day closed here reaches every organisation calendar and every venue that extends the base, directly or through another calendar. No organisation can reopen it.
Use this page when a market publishes a holiday that a base calendar does not carry yet, or when organisations on the platform need a base for a market the platform does not ship. Do not use it for a closure that applies to one organisation only: that organisation closes the day on its own calendar, and no other organisation sees it.
A closed day is permanent, on a base calendar as everywhere else. The dialog states the rule: "A closed day is added, never removed. A correction published later never moves a deadline that was already computed." A wrong date on a base calendar reaches every organisation that extends it, so confirm the date against the market's published source before you close it.
One closed day on a base calendar reaches every calendar that extends it, across every organisation.
What the platform ships
Four base calendars are present on every platform before an administrator adds anything:
| Calendar | Jurisdiction | What it closes |
|---|---|---|
| "TARGET2 settlement calendar" | EU | The published TARGET2 closing days, computed for 2024 through 2040 |
| "UK bank holidays (England and Wales)" | GB | The UK bank holidays for England and Wales, computed from their rules for 2024 through 2040 |
| "US federal holidays" | US | The US federal holidays, computed from their rules for 2024 through 2040 |
| "ADGM business days (UAE public holidays)" | AE | Only the UAE public holidays already announced |
The ADGM calendar holds announced dates only, because the UAE can move a public holiday after the rules would place it. Close each new UAE holiday on it once the date is announced. The other three calendars need a new closed day only when the published rules change or a one-off closure is declared. Their computed dates end with 2040.
How a closed day takes effect
Every closed day records when the platform learned about it. A filing deadline counts only the closed days the platform knew about when it computed that deadline. A day you close today therefore applies to deadlines computed from now on and leaves earlier deadlines where they are, so a filer who planned around a published deadline is not surprised by a later correction.
A venue's "Trading week" tab states the rule for venues: "a day inherited from the shared calendar shuts every venue that extends it." A day you close on a base therefore shuts every venue whose calendar chain reaches the base. Venue operations explains what a market does on a day with no session.
Before you start
Steps
Open Base calendars
Open Platform settings, then "Base calendars". The page lists every base calendar with its name, its jurisdiction badge, and its closed days grouped by year. Each day shows its reason and its source: "Platform administrator" for a day closed on this page, or the published dataset it came from for a shipped day. The source names the kind of administrator, not the person who closed the day.
Publish a base calendar
Skip this step when the calendar already exists. Under "Publish a base calendar", enter a "Name" and choose a "Jurisdiction": a country, or a regional code such as EU. The jurisdiction is a label and does not change which days are closed. Select "Publish". A base calendar published through this Console form extends nothing. The Platform API can also create a base that extends another base.
Publishing cannot be undone. Neither the Console nor the Platform API deletes a base calendar, and organisations can extend it from the moment it is published.
The calendar is offered to every organisation as soon as "The base calendar is published." appears, even before it closes any day. An organisation that extends an empty base inherits nothing until you close days on it. A deadline calculation that uses calendars requires at least one effective closure in each calendar it names. Publish the relevant closed days before organisations use the new base for reporting.
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 readers of the calendar. Every closed day counts the same way for deadlines and venues, whatever its reason.
Read the dialog, check the date against the published source, and select "Close a day" to add it. The day cannot be removed afterwards by you or by any organisation.
API equivalents
The platform administration calendar endpoints list base calendars, publish or update one, and add a closed day. An update through the API can change an existing base calendar's name, jurisdiction, or parent base, which the Console does not offer. A base that extends another base inherits its closed days. The request and response shapes are in the Platform API reference.
Troubleshooting
Base calendars is not in the sidebar
The entry appears only for a platform administrator. An organisation owner manages the organisation's own calendars on Holiday calendars instead.
Publish stays disabled
"Publish" needs a free name and a jurisdiction. "A calendar with this name already exists. Choose another name." means the name produces the identifier of an existing base calendar. Names that differ only in case or punctuation, such as "UK Bank Holidays" and "uk-bank-holidays", produce the same identifier. A name with no Latin letter or digit produces no identifier at all.
A day was closed on the wrong date
The day stays closed on the base and on every calendar that extends it. Deadlines computed before the mistake keep their dates. Close the correct date as well, and tell the organisations that extend the calendar, because their deadlines computed from now on skip both days and their venues do not trade on either. The Console has no list of the calendars that extend a base, so reach every organisation on the platform, listed under Organisations.
An organisation reports a deadline that ignores a new holiday
The deadline was computed before the holiday was closed on the base. A deadline counts only the closed days the platform knew about when it computed it, so the new holiday applies to deadlines computed after it.
Frequently asked questions
Can an organisation stop inheriting a base calendar's day?
No. An organisation calendar that extends a base inherits every day the base closes. An organisation that must not inherit a day creates a calendar that extends nothing and closes its own days.
Does a base calendar need weekend closures?
No. A filing deadline never counts Saturday or Sunday as a business day, and each venue sets its own trading week. Close a weekend day on a base only if a venue that trades at weekends must not trade on it.
Who sees a day an organisation closes?
Only that organisation. A day reaches other organisations only when it is closed on a base calendar.
Related pages
- Holiday calendars: an organisation's own calendars, which extend a base.
- Venue operations: where a venue picks its holiday calendar and sets its trading week.
- Reporting obligations: how a deadline rule counts business days.