Skip to main content
When your financial year starts, how it is divided, and which periods are closed to new postings.

​
One calendar per company

A fiscal calendar belongs to a legal entity, not to the organisation as a whole — a group with more than one company can run a fiscal year starting in April for one and January for another. Each calendar has:

​
Generating periods

A calendar with no periods cannot be used — nothing can post into a year that has not been broken into periods yet. Generate FY<year> builds this year’s and next year’s periods from the calendar’s own settings, and you generate the next year again each time one is needed rather than generating far in advance.

​
Closing a period

Each period steps forward through three states: A month closes when everything that posts against it has — which is why the calendar sits apart from any one book: a budget, a capex plan, and a depreciation book can all be counted against the same fiscal year, and the day they disagree about when April starts is a reconciliation nobody wins.

​
Where this is used

This is the one piece of financial setup that does not belong to any single module. Whichever of these your organisation has, they all read the same calendar:
  • Budgets — see budgets
  • Capex plans
  • Depreciation books
A tenant that has bought Budgets alone still needs a fiscal calendar, which is why it has its own settings screen rather than living inside a module you might not have.

​
Who can use this

Reading and changing calendars needs the accounting book permission — the same one that governs depreciation books — rather than the general configuration permission most of Administration uses. An account without it sees nothing on this screen, because nothing here says whether your organisation has any calendars at all.