A date-only value is different from an instant on a clock. The tools separate calendar planning and time-zone conversion so daylight-saving transitions do not silently change date counts.
Define boundaries and holiday inputs
The holiday-aware counter includes the start and excludes the end. It counts Monday–Friday and subtracts unique holiday dates you enter. No official calendar is fetched. Enter observed closures explicitly; a holiday on a weekend does not subtract a second day. Invoice terms instead add calendar days with the invoice date as day zero.
Preserve a monthly anchor
A January 31 recurrence needs a shorter-month convention. The monthly schedule computes each date directly from the original anchor. February clamps to month end and March returns to the 31st. Repeatedly shifting a previously clamped date is a different rule.
Convert one explicit instant
The meeting tool requires Z or a numeric UTC offset. A local clock time can repeat or not exist during a daylight-saving transition. It displays that single instant in IANA zones using the browser database. Verify future rule changes and attendees’ actual calendar entries separately.
Worked example
Scroll the table horizontally on small screens to see every column.
| Occurrence | Date |
|---|---|
| 1 | 2024-01-31 |
| 2 | 2024-02-29 |
| 3 | 2024-03-31 |
No banking or holiday adjustment is implied. A contract may use another convention.
Sources and checks
Examples are illustrative and can be checked with the linked tools. Read each tool’s assumptions before applying its result. How we verify methods.