4.1 Fiscal Calendars, Period Statuses & Module Access Control
Key Takeaways
- A fiscal calendar is shared across legal entities, while the ledger calendar applies that calendar to one legal entity and holds its per-module period statuses.
- Period statuses are Open, On hold, and Permanently closed; Permanently closed is irreversible and cannot be reopened by any configuration or security change.
- Module access control on the ledger calendar lets you close a period for Accounts payable while leaving General ledger open for closing adjustments.
- Stopped periods block posting for all users; access can also be granted to specific user groups per module for controlled soft-close windows.
4.1 Fiscal Calendars, Period Statuses & Module Access Control
Quick Summary: In Microsoft Dynamics 365 Finance, time and accounting segregation form the operational boundary of financial recordkeeping. Organizations define Fiscal Calendars to establish standardized accounting years and period intervals. The Ledger Calendar provides entity-specific operational control over those periods, enabling accounting teams to open, hold, or permanently close periods by individual subledger module and user group. Concurrently, Posting Layers (Current, Operations, Tax, and Custom layers) allow organizations to maintain parallel accounting records—such as local statutory GAAP, IFRS, and tax reporting—within a single legal entity without duplicating master data.
1. Architectural Foundations: Fiscal Calendars vs. Ledger Calendars
A critical distinction in Dynamics 365 Finance is the separation between the global structural calendar definition and the legal entity-specific transactional calendar controls.
+-----------------------------------------------------------------------------+
| CALENDAR ARCHITECTURAL SEPARATION |
+-----------------------------------------------------------------------------+
| 1. Shared Fiscal Calendar (Global Definition) |
| - Navigation: General ledger > Calendars > Fiscal calendars |
| - Shared across multiple legal entities |
| - Defines Fiscal Years, Start/End dates, and Period Types |
| - Contains NO transactional status or posting security controls |
| |
| 2. Ledger Calendar (Legal Entity-Specific Operational Control) |
| - Navigation: General ledger > Ledger setup > Ledger calendar |
| - Specific to ONE legal entity linked via the Ledger form |
| - Controls Period Status: Open, On hold, Permanently closed |
| - Enforces Module-Level Access Control (AP, AR, GL, Bank, Fixed Assets) |
| - Assigns User Group posting restrictions per subledger |
+-----------------------------------------------------------------------------+
The Shared Fiscal Calendar Model
- Global Scope: A fiscal calendar is created once and can be referenced by multiple legal entities, depreciation books, budget cycles, and project fiscal definitions.
- Standardization: Facilitates consolidated reporting by ensuring all operating subsidiaries share identical period start and end dates.
- Multi-Calendar Support: Organizations with entities operating under disparate fiscal year-ends (e.g., US entities on a calendar year ending December 31 vs. Australian or UK entities ending June 30 or March 31) can define multiple distinct fiscal calendars.
System Navigation
- Fiscal Calendar Definition:
General ledger > Calendars > Fiscal calendars(orBudgeting > Setup > Basic budgeting > Fiscal calendars) - Ledger Calendar Management:
General ledger > Ledger setup > Ledger calendar - Ledger Form Setup:
General ledger > Ledger setup > Ledger
2. Fiscal Calendar Design & Period Types
When creating a fiscal calendar, the functional consultant specifies the Fiscal year name, the start date, the end date, the length of periods, and the number of periods.
+-----------------------------------------------------------------------------+
| FISCAL YEAR PERIOD COMPOSITION |
+-----------------------------------------------------------------------------+
| Period 0: OPENING | 2026-01-01 -> 2026-01-01 (Duration: 1 Day) |
| | Dedicated strictly to Year-End Close Opening Balances |
+---------------------+-------------------------------------------------------+
| Period 1: OPERATING| 2026-01-01 -> 2026-01-31 (Regular January Postings) |
| Period 2: OPERATING| 2026-02-01 -> 2026-02-28 (Regular February Postings) |
| ... | ... |
| Period 12: OPERATING| 2026-12-01 -> 2026-12-31 (Regular December Postings) |
+---------------------+-------------------------------------------------------+
| Period 13: CLOSING | 2026-12-31 -> 2026-12-31 (Duration: 1 Day) |
| | Dedicated to Audit / Statutory Year-End Adjustments |
+-----------------------------------------------------------------------------+
Detailed Breakdown of Period Types
Dynamics 365 Finance enforces three distinct period types within every fiscal year:
| Period Type | Typical Period Number | Date Span | Primary Functional Purpose | Subledger Posting Allowed |
|---|---|---|---|---|
| Opening | Period 0 | Exactly 1 day (matches first day of fiscal year) | Dedicated exclusively to receiving opening balance roll-forwards generated by the automated Year-End Close routine. Transactions posted here do not distort operating balances. | No (System GL close only) |
| Operating | Periods 1..12 (or 1..13 / 1..52) | Date ranges spanning months, 4-4-5 weeks, or bi-weeks | Standard periods for recording day-to-day business transactions across all subledgers (AP, AR, Inventory, Bank, Projects, GL). | Yes (Subject to security) |
| Closing | Period 13 (or final period) | Exactly 1 day (matches last day of fiscal year) | Dedicated to post-close audit adjustments, statutory tax entries, and auditor adjustments. Segregates closing entries from ordinary month 12 operational numbers. | Yes (Manual GL journals only) |
[!IMPORTANT] Consultant Best Practice: Period 0 vs. Operating Period 1 Notice that Period 0 (Opening) and Period 1 (Operating) both share the start date of
2026-01-01. When posting standard transactions on January 1, the system automatically assigns them to Period 1 (Operating). Period 0 is reserved exclusively for the Year-End Close balance carryforward vouchers, preventing opening balances from distorting January revenue/expense reports.
Calendar Structure Options
- 12 Monthly Periods: The standard calendar structure (e.g., Jan 1 – Dec 31 with 12 operating periods plus Opening and optional Closing periods).
- 13-Period Calendar (4-Week Periods): Often used in retail and hospitality where each period contains exactly 28 days (4 weeks) to ensure consistent period-over-period comparative analysis.
- 4-4-5 / 4-5-4 / 5-4-4 Retail Calendars: Quarters divided into two 4-week months and one 5-week month, maintaining alignment with retail accounting cycles.
3. Period Statuses & Lifecycle Governance
Period statuses govern whether transactions can be posted into a given period within a specific legal entity. Statuses are managed exclusively in the Ledger calendar form (General ledger > Ledger setup > Ledger calendar).
+------------------------------------------+
| Period Status States |
+------------------------------------------+
|
+---------------------------+---------------------------+
| |
v v
+--------------+ +--------------+
| OPEN | <====================================> | ON HOLD |
+--------------+ (Freely Reversible at any time) +--------------+
| |
| |
+---------------------------> +-------------------------+
|
v
+----------------------+
| PERMANENTLY CLOSED |
+----------------------+
| CRITICAL: CANNOT BE |
| REOPENED EVER! |
+----------------------+
Comprehensive Period Status Comparison
| Status | Transaction Posting Allowed? | Can Status Be Changed? | Typical Operational Use Case |
|---|---|---|---|
| Open | Yes (by all users or designated user groups) | Yes (can be changed to On hold or Permanently closed) | Active financial periods currently undergoing normal operational processing. |
| On hold | No (all transactional postings blocked) | Yes (can be toggled back to Open at any time by an authorized finance user) | Temporarily closed periods during month-end closing, pre-close reviews, or pending audit reconciliations. |
| Permanently closed | No (all transactional postings blocked forever) | NO (IRREVERSIBLE) | Historical fiscal years where statutory audits, tax filings, and final year-end closes are 100% complete. |
[!CAUTION] Exam Trap: The Permanently Closed Status is Irreversible Setting a period status to Permanently closed is a permanent, non-negotiable database operation. Microsoft Dynamics 365 Finance provides no mechanism in the user interface, periodic tools, or standard workflows to reopen a permanently closed period. If an auditor requires a prior-year adjustment in a permanently closed period, the adjustment must be posted in an open subsequent period or closing period. Never permanently close a period until all external audits and statutory filings are finalized!
4. Module-Level Access Control & Period Closing Security
In enterprise finance operations, month-end closing does not occur instantaneously across all departments. Accounts Payable might close on the 2nd business day of the new month, Accounts Receivable on the 4th business day, Inventory on the 5th, while General Ledger remains open for controller adjustments until the 10th business day.
Dynamics 365 Finance enables granular control over this staggered closing process through Module access levels in the Ledger calendar:
+-----------------------------------------------------------------------------------------+
| LEDGER CALENDAR: MODULE-LEVEL ACCESS CONTROL GRID |
+-----------------------------------------------------------------------------------------+
| Fiscal Year: 2026 | Period: 2026-08 (August) | Status: Open |
+-------------------+-----------------------+---------------------+-----------------------+
| Module | Access Level | Access User Group | Practical Effect |
+-------------------+-----------------------+---------------------+-----------------------+
| Customer (AR) | None | | Invoicing blocked |
| Vendor (AP) | None | | AP Invoices blocked |
| Bank | None | | Bank journals locked |
| Inventory | None | | Inventory closed |
| Fixed assets | None | | FA journals locked |
| Project | None | | Timesheets locked |
| Tax | None | | Tax entries locked |
| Payroll | None | | Payroll locked |
| General ledger | Specific user group | FIN-CONTROLLER | ONLY Controllers post |
+-----------------------------------------------------------------------------------------+
Available Subledger Modules
The Ledger calendar provides individual access toggles for:
- Customer (Accounts Receivable transactions and Free Text Invoices)
- Vendor (Accounts Payable invoices, purchase order receipts, and payment journals)
- Bank (Cash and bank management entries and reconciliations)
- Fixed assets (Acquisitions, depreciation, and disposal journals)
- Inventory (Inventory adjustments, transfer journals, and item postings)
- Project (Project timesheets, item requirements, and fee journals)
- Payroll (Payroll disbursements and expense distributions)
- Tax (Sales tax settlement and tax adjustments)
- General ledger (Direct General journal vouchers and closing adjustments)
Access Level Options
- All: Any user with standard security role privileges can post transactions in this module for this period.
- None: No user (regardless of administrative privileges) can post transactions in this module for this period.
- Specific user group: Only users who belong to the selected User group (defined in
System administration > Users > User groups) can post transactions in this module for this period. All other users are blocked.
A financial controller needs to execute month-end close for March 2026. The controller wants to prevent accounts payable clerks from entering vendor invoices into March, while allowing the corporate accounting team (user group FIN-CORP) to post general journal accruals and adjustments into March. How should the controller configure the system?
During an annual audit review, an accounting manager accidentally sets the status of the entire 2025 fiscal year to 'Permanently closed' in the Ledger calendar. Two weeks later, the external auditors request a final adjusting journal entry to be posted on December 31, 2025. What action can the system administrator take to allow posting to December 31, 2025?