Business calendar

The business calendar defines working days and the date cursor used by transactions, end-of-day processing, interest, and other date-sensitive operations.

Open Organization → Org Structure → Calendar.

Access and lifecycle

• Read Work Day Year shows calendar years and their months.
• Create Work Day Year permits a new year.
• Update Work Day Year permits draft changes and Authorized amendments.
• Delete Work Day Year permits deletion when the calendar is not the active COB calendar and no integrity rule blocks it.

A Work Day Year uses maker-checker. Submission follows the required approval count on the role permission, and each checker needs the matching L1, L2, or L3 authority. A maker cannot authorize their own calendar.

Create a calendar year

1. Select Create Work Day Year.
2. At L0, select the target company.
3. Enter a year from 2000 through 2100.
4. Enter Last Working Day, Current Working Day, and Next Working Day so that last < current < next.
5. Create the year.

The Current Working Day must be in the selected year. At a year boundary, the Last Working Day may be in the selected year or the preceding year, and the Next Working Day may be in the selected year or the following year.

remoteEaze then attempts to create all 12 months with Saturday and Sunday as weekend days and no public holidays. If month initialization is incomplete, the year is still created; configure the missing months before submission.

Configure months

Open the year and select a month. In the month editor:

• Weekend Days applies the selected weekdays throughout that month;
• Public Holidays marks individual calendar dates as non-working days.

Past dates cannot be changed. A new public holiday also cannot be added on or before the deployment's protected date, calculated from the current working day and the configured holiday-change buffer. An existing holiday can still be removed when the record state and amendment rules allow it.

The holiday-change buffer can be configured from 0 through 30 calendar days and defaults to 1. With the default, the current working day and the next calendar day are protected. The earliest date on which a new holiday can be added is two calendar days after the current working day. Use the validation message as the exact protected date for the current deployment.

Before submission, confirm that all 12 months exist and that the last, current, and next working days are ordered and are genuine working days under the configured weekends and holidays.

Submit and authorize

Submit the completed year and complete its required approvals. Calendar authorization validates all 12 months and the working-day cursor again. If a boundary date belongs to an adjacent year, an Authorized calendar for that adjacent year must already exist so remoteEaze can validate it.

The first Authorized calendar for a tenant becomes the active calendar used by COB. Authorizing a future year does not activate it early. At the year boundary, the COB Advance Workday step moves the active pointer to the Authorized successor and advances the last, current, and next dates.

The Active state shown on the calendar record refers to whether the record has been deleted; it is not the active-for-COB pointer.

Amend an Authorized calendar

The last, current, and next working dates cannot be edited manually after authorization. Changing an Authorized month's weekend or holiday configuration creates and submits an amendment. The current configuration remains effective until the amendment receives its required approvals.

An active COB calendar cannot be deleted. Deleting or restoring another Authorized year also follows the amendment lifecycle.

Complete this setup before processing the first transaction or running the first COB.