Fiscal Calendar
What It Is
A fiscal calendar supplies the years and monthly periods used to date a business unit’s accounting work. It begins in the month selected for that unit. A January start produces a familiar calendar year; a July start produces a year spanning parts of two calendar years. The calendar is a continuing sequence rather than a collection of unrelated date ranges staff assemble independently.
A newly created unit receives its initial years. Later generation extends the sequence with complete years and their monthly periods. Staff see the year names and can inspect the period dates and standing beneath them. This gives invoice, batch and scheduled work a common answer about which period contains a date. The year’s internal identity remains stable when staff replace its display name with terminology familiar to their finance team.
What It Is Not
Calendar setup does not perform month-end close. It establishes the periods that closing workflows operate on. A fiscal year is not necessarily a calendar year, and a current accounting period is not necessarily the month containing today. Open work can remain in an earlier period until the separate close process advances it. A requested date outside the generated calendar does not authorize lookup to extend that calendar automatically.
How It Is Used
Controllers review upcoming coverage and generate years before transaction and recurring work need them. They can rename a year while retaining its dates and period labels. Removing an accidentally generated year is a different action, limited by the calendar’s order and the standing of its periods. Good maintenance keeps enough future coverage for scheduled work without treating generation as an unlimited forecast.
Staff issuing or processing financial work use period lookup rather than constructing period names themselves. When a roll reaches an uncovered date, its failure identifies the calendar gap. The controller extends coverage and retries the work instead of relying on a background process to choose new fiscal setup.
Its Facets
Years. A year is the annual reporting span beginning in the unit’s selected month. Generation gives it an initial name that staff can later adjust.
Monthly periods. Each year contains its complete ordered months. The period combines a readable label, dates and standing, supplying the smaller interval that transactions and close use.
Current accounting work. The current-period lookup follows the earliest open work. It helps defaults and policy checks refer to the accounting state rather than the computer’s calendar alone.
Generation reach. The allowed horizon bounds a year’s start date relative to the workspace’s local date. The whole request is checked before incomplete future coverage can be saved.
Year standing. The year summarizes its periods’ open or closed state. Staff do not change that summary through a calendar edit; it follows the periods managed by close.
How It Relates
The calendar belongs to the business unit and uses its founding start month. Financial documents, batches and scheduled rolls locate periods from it. Month-end close governs period transitions, while the unit’s accounting-method guard uses the current open period to determine whether a policy change is permitted.
What It Could Become
The product should keep calendar maintenance and close clearly connected without combining their authority. Better advance warnings could show when a recurring schedule will outgrow generated coverage. Any future non-monthly calendar would need a recorded product decision because the present model assumes complete monthly years.