Skip to content

Systems and records

International business holiday calendar data: how to compute local deadlines

By SourceX Editorial · Reviewed by Noah Loul ·

10 sections

Short answer

Name the governing calendar before counting: the jurisdiction and subdivision, any institution schedule, the weekend days, the holiday list with observed and estimated flags, the counting rule, and the time zone and cutoff. Store that calendar as dated, versioned evidence with each record and its computed deadline, so the date can be recomputed and explained. The same start date can produce different deadlines under different calendars.

Countries and languages

International business

This page covers international business holiday calendar data: how to compute local deadlines.Illustrative

Key takeaways

  • Decide whose calendar governs each deadline type before counting days.
  • Weekends, regional holidays, substitute days, institution schedules and estimated dates each move deadlines.
  • Store the calendar as dated, versioned evidence with the record, the counting rule, the time zone and the cutoff.
  • The same start date can give different deadlines on the U.S. federal and Federal Reserve calendars.
  • Statutory and contractual deadlines need a qualified reviewer in the governing jurisdiction before use as labels.

How should a task calculate deadlines using local business calendars?

Name the calendar that governs the deadline before counting anything: the jurisdiction and subdivision, the institution if it has its own schedule, the weekend days, the holiday list with its observed-day rule, the counting convention and the time zone and cutoff. Then store that calendar as dated evidence alongside the record and the computed answer, so anyone can recompute it and see why it came out that way.

Most deadline errors in international records are not arithmetic errors. They come from an assumed weekend, a national holiday list used where a regional one applies, a substitute day nobody recorded, or the wrong party's calendar. A support SLA of three business days, a supplier's ten-working-day response window and a statutory period expressed in days can each land on different dates for the same start date, depending on whose calendar is used.

For international business holiday calendar data, that means the calendar is part of the record. A ticket export that keeps the due date but not the calendar used to compute it cannot be checked, and a model trained on it learns dates without the reasons behind them.

Which calendar facts change a deadline?

Six facts do most of the damage. Each has a published source you can cite and date instead of assuming it.

Which calendar facts change a deadline?
Calendar factReal exampleWhere it is publishedWhat goes wrong if assumed
Weekend daysUnicode CLDR lists Friday and Saturday as the weekend for Saudi Arabia and several other territories, Sunday alone for India, and Saturday and Sunday as the defaultCLDR supplemental week dataA Sunday counted as a non-working day in Riyadh, or a Friday counted as a working day
Holiday list by subdivisionEngland and Wales, Scotland and Northern Ireland publish separate bank holiday listsNational government calendarsA Scottish office's deadline computed on the England list
Observed or substitute dayWhen a UK bank holiday falls on a weekend, a substitute weekday is usually a holiday insteadThe same national calendarsCounting the Monday after Boxing Day as a working day
Institution-specific scheduleU.S. federal employees observe a Saturday holiday on the Friday before, while Federal Reserve Banks stay open that FridayOPM and Federal Reserve holiday schedulesA payment deadline computed on the federal employee calendar
Estimated holiday datesSome Islamic holidays depend on lunar calendars and are estimated until announcedOfficial announcements; libraries mark estimatesA deadline shifted by an Eid date that later moved
Counting conventionUnder EU Regulation 1182/71 a period ending on a public holiday, Saturday or Sunday ends at the end of the next working dayThe governing law or contractA deadline set on a Sunday instead of the following working day

Whose calendar governs: sender, recipient, contract or institution?

The calendar of the party or system that must act usually governs, unless a contract, statute or service agreement names another one. Record which applies for each deadline type, because a single case can involve several.

Consider a supplier in Riyadh answering a buyer in London under a contract governed by English law, with payment through a U.S. bank. The response window may follow the supplier's working week, the contractual notice period may follow the governing law's counting rule, and the payment cutoff follows the bank's operating calendar. Collapsing all three into one country calendar gives at least one wrong date.

When the source system already chose a calendar, for example a helpdesk whose SLA policy is attached to a business-hours schedule with a holiday list, export that configuration with the tickets. The schedule name, its time zone and its holiday entries for the period are the evidence that explains each due date.

Where is the calendar a system actually used, and what if it disagrees?

Usually in configuration, not in the records. Before building a calendar from public lists, export the one the business actually ran on, because that is what produced the dates in its records, including any local closures and errors.

When the system calendar and the official calendar disagree, keep both and label the difference rather than correcting the record. The system calendar explains what the business did; the official calendar explains what it should have done. A deadline missed because a site worked on a public holiday, or met because the system skipped a day the law did not, is often the most informative case in the set, so store which calendar produced each due date and the officially computed date beside it.

Look in these places, and export each with its change history where the system keeps one:

  • Helpdesk and service desk tools: business-hours schedules, the holiday entries attached to them and which SLA policy uses which schedule.
  • ERP and manufacturing systems: working or factory calendars per plant or company code, which drive promised dates and lead times.
  • Payroll and HR systems: pay calendars and site holiday lists, which often include local days off that no national list shows.
  • Logistics and carrier portals: service calendars and cutoff times that explain why a shipment promised for one day left on another.
  • Contract repositories: clauses that define business days, notice periods and the governing law, often in the original language.

The dated calendar evidence and task specification

Attach these fields to every record whose deadline depends on a calendar, or to each calendar that a group of records shares. The examples are illustrative. A task built from the record should be answerable from these fields alone.

The dated calendar evidence and task specification
FieldWhat to recordIllustrative valueCheck
Calendar authorityWhose calendar governs and why (party, contract clause, statute, institution)Supplier working calendar per contract clause 7Reason is written, not inferred
Jurisdiction and subdivisionCountry and region codes for the governing calendarGB, England and WalesSubdivision present wherever holidays differ by region
Weekend definitionNon-working weekdays and the source and version usedFriday and Saturday, from CLDR week dataMatches the authority, not the data processor's location
Holiday entriesEach holiday in range with date, name, observed flag and estimated flag2026-12-28, Boxing Day substitute, observedEvery observed or estimated entry is labeled as such
Calendar source and retrievalPublisher, URL or library version, and retrieval dateNational calendar retrieved on a stated dateA later retrieval that differs creates a new calendar version
Counting ruleCalendar or working days, whether day one is the start day, end-day roll rule, any retroactive periodWorking days, start day excluded, roll forwardRule is cited to contract, policy or law
Time zone and cutoffIANA time zone name and the time of day the deadline expiresEurope/London, 17:00Timestamps carry offsets; cutoff stated
Inputs and answerStart timestamp, period length, computed deadline, each skipped day with its reasonStart 2026-12-24, 2 working days, due 2026-12-30Recomputing from the fields gives the same answer
Language and original textOriginal-language wording of the clause or policy and its translation IDClause text in Arabic with English translation referenceThe original is kept; the translation is linked, not substituted

Worked example (illustrative): one start date, three calendars

These tasks are illustrative; the holiday facts come from the cited official schedules. They show how the same counting rule produces different deadlines when only the calendar changes.

Task one, England, two working days from Thursday 24 December 2026. The GOV.UK list for England and Wales gives Christmas Day on Friday 25 December and, because Boxing Day falls on Saturday, a substitute bank holiday on Monday 28 December. Skipping Friday, the weekend and the substitute Monday, the working days are Tuesday 29 and Wednesday 30 December, so the deadline is Wednesday 30 December. A calendar without the substitute day returns Tuesday 29 December.

Task two, United States, three business days from Wednesday 1 July 2026, where Independence Day falls on Saturday 4 July. OPM's rule for most federal employees treats Friday 3 July as the holiday, so the count runs Thursday 2, Monday 6 and Tuesday 7 July: due Tuesday 7 July. The Federal Reserve's schedule says Reserve Banks are open the Friday before a Saturday holiday, so on a Federal Reserve operating calendar the count runs Thursday 2, Friday 3 and Monday 6 July: due Monday 6 July. Same country, same start, one day apart.

Task three, the exception: a supplier in Saudi Arabia with a ten-working-day reply window that crosses an Eid holiday. The weekend is Friday and Saturday, and the Eid dates in any precomputed calendar are estimates until announced. The open-source holidays library, for example, defines Saudi Arabia's weekend as Friday and Saturday and can label Islamic holiday dates as estimated. The correct record keeps the estimate flag, and the task is either recomputed after the official announcement or marked as depending on an estimated date.

Which assumption could reverse the answer?

Check these before trusting a computed deadline or turning it into a training label. Any one of them can move the date, and some move it in either direction.

At a glance

Which assumption could reverse the answer

  • The wrong authority: the processor's or buyer's calendar used instead of the party that must act.
  • A missing subdivision: national holidays used where regional or state holidays apply.
  • An unrecorded observed rule: substitute days skipped, or applied to an institution that does not follow them.
  • Estimated dates treated as final, especially for lunar-calendar holidays.
  • The counting start: whether the triggering day counts as day one.
  • The end-day rule: EU Regulation 1182/71 rolls a period ending on a holiday or weekend to the next working day, but not periods calculated retroactively, and a specific law or contract can override it.
  • The time zone and cutoff: a deadline at 17:00 in one zone may already have passed in another.
  • Ad hoc closures: governments and institutions sometimes add closure days by order after calendars are published.

How do you keep calendar evidence dated and versioned?

Treat every calendar as a versioned dataset with a retrieval date, and never overwrite it in place. Holiday lists change by proclamation, weekends change by law, and shared reference data is revised between releases.

Weekend definitions are a good example of reference data that moves. The current CLDR week data lists Friday and Saturday as the weekend for Saudi Arabia and several other territories, while the United Arab Emirates is not in that list and falls under the Saturday and Sunday default. A record dated before a country changed its working week must be computed with the calendar in force at the time, so store the version used, not only the current one.

Libraries help but are not authorities. The holidays library documents an observed parameter that adds observed days by default, and working-day functions such as checking whether a date is a working day and finding the nth working day after a date. Record the library version with every computed deadline, and prefer the official publisher's list when they disagree.

Which deadlines need counsel or a local operator before they become labels?

Statutory, court, regulatory and contractual notice deadlines need a qualified reviewer in the governing jurisdiction before they are used as answers. The specification makes the computation transparent; it does not decide which rule applies.

Bring in a local operator or a localization specialist when the source text is in another language, when a holiday depends on a religious or regional calendar, or when the business followed a working week different from the national default. Narrow the scope to deadline types with an unambiguous authority if those reviews are not available, and mark the rest as excluded rather than guessing.

Preparing calendar-dependent records from outside the U.S.

Records that carry their calendar evidence are easier to review and to license, because the buyer can see how each date was computed. Keep the original-language policy text, the calendar version and the counting rule with the records you might offer.

SourceX prepares and licenses selected business records as AI datasets, including rights review and delivery, and its coverage rule matters for calendar-heavy records from abroad: it works with companies in the U.S., Canada and the EU that reached 50 or more full-time employees at their peak (contractors not counted), and companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia can be considered when at least 70 percent of the offered data is English, a share confirmed on the actual dataset. For those companies the English share is measured on the records actually offered, not the company's country, and every dataset still goes through rights, privacy, quality and buyer-fit review. Checking whether a company qualifies starts with a short assessment that asks for no uploaded files.

Frequently asked questions

Can I use one country holiday list for all of a company's records?

Only if every deadline in the records was governed by that country's calendar with no regional holidays. Most multi-site or cross-border records need a calendar per authority and subdivision, recorded with each deadline.

Which day counts as day one when counting business days?

It depends on the governing rule. Many contracts and laws exclude the day of the triggering event and start counting the next day, but the rule should be cited from the contract, policy or law and stored with the record rather than assumed.

How should holiday dates that are only estimated be handled?

Keep the estimate flag on the holiday entry. Either recompute the deadline after the official announcement, or mark the task as depending on an estimated date so it is not scored as a fixed answer.

Is a time zone enough, or do I also need the cutoff time?

You need both. A deadline is a date in a calendar plus a time of day in a named time zone, and a deadline at the end of business in one zone may have passed already in another.

Are holiday libraries reliable enough to compute deadlines?

They are useful and transparent, but they are maintained reference data, not authorities. Record the library version, check important dates against the official publisher, and prefer the official list when the two disagree.

Sources

  • Unicode CLDR supplemental week data lists Friday-Saturday weekends for Saudi Arabia and several other territories, a weekend starting and ending Sunday for India, and Saturday-Sunday as the default for other territories, including the United Arab Emirates. Source
  • GOV.UK publishes separate bank holiday lists for England and Wales, Scotland and Northern Ireland, with substitute days when a holiday falls on a weekend; its 2026 England and Wales list gives Christmas Day on Friday 25 December and the Boxing Day substitute on Monday 28 December. Source
  • OPM says that for most federal employees a holiday falling on a Saturday is observed on the preceding Friday, and one falling on a Sunday on the following Monday. Source
  • The Federal Reserve's holiday schedule says that for holidays falling on Saturday, Reserve Banks and branches are open the preceding Friday, and for holidays falling on Sunday they are closed the following Monday. Source
  • EU Regulation 1182/71 provides that a period ending on a public holiday, Saturday or Sunday ends with the last hour of the following working day, except for periods calculated retroactively. Source
  • The holidays library documentation describes an observed parameter, on by default, that adds observed holiday dates, and working-day functions including is_working_day and get_nth_working_day. Source
  • The holidays library's Saudi Arabia calendar sets the weekend to Friday and Saturday, notes the Umm al-Qura calendar for administrative purposes and can label Islamic holiday dates as estimated. Source

See if your company qualifies

A short company assessment. No data uploads are needed.

See if your company qualifies