Month-End Close in TouteGestion: Review the Period and Lock Posting
TouteGestion currently implements month-end control through regular accounting periods. Closing a period locks that posting window through the accounting-period control; reopening is an elevated action with a mandatory reason. This is deliberately distinct from the richer fiscal-year Soft Close and Hard Close workflow.
What month-end close means in the current application
For normal monthly operations, Finance works with regular accounting periods. An open period permits operational posting subject to the other Accounting controls; closing the period changes that posting window to closed. The current application does not present a separate automated month-end checklist engine, so public guidance should not claim that reconciliations or report signoffs are automatically completed merely because a period is closed.
1. Use fiscal-year periods for the normal accounting calendar
The Accounting Periods page explicitly recommends Fiscal years for governed annual accounting. Fiscal-year workflows create regular periods plus a separate year-end adjustment period. Standalone regular periods remain available for legacy or non-year schedules, and overlapping regular periods are rejected.
2. Review the period before locking it
Before closing a month, Finance should complete the organisation's required operational review using the live Accounting reports and controls that apply to it—for example bank reconciliation, receivables/payables review, Trial Balance and relevant financial reports. These reviews are separate workflows. TouteGestion does not silently mark them complete when the period is closed.
3. Close the regular accounting period
A user with accounting.periods.manage can close an open period. The application calls close_accounting_period and refreshes both Accounting Periods and Fiscal Years. Closing is therefore an explicit control action, not a date automatically becoming locked simply because the calendar month ended.
4. Understand what the closed status protects
The period status is part of the Accounting posting boundary. Once the period is closed, transactions should not be back-posted into that operational window through ordinary posting. This protects already reviewed monthly figures from changing unnoticed after management has treated the period as complete.
5. Reopen only with elevated authority and a reason
Reopening a closed period requires accounting.fiscal_years.reopen rather than the ordinary period-management permission. A reason is mandatory and reopen_accounting_period performs the controlled change. This makes reopening an exception that can be explained, not a routine convenience for correcting late work.
6. Hard-closed fiscal years cannot be reopened period-by-period
If the period belongs to a fiscal year whose status is closed, the Periods page directs the user to Reopen fiscal year instead of exposing ordinary period reopening. The fiscal-year workflow has its own reversal and adjustment-period controls, so a hard-closed year cannot be bypassed by reopening one month independently.
7. Distinguish month-end from year-end
Month-end closes a regular operational period. Year-end adds pre-close checks, Soft Close, a dedicated adjustment period, Hard Close, the profit-and-loss transfer to retained earnings or accumulated fund, and controlled fiscal-year reopening. Those are not interchangeable processes.
Worked example
Finance finishes September bank reconciliation, reviews customer and supplier balances, checks the Trial Balance and investigates material exceptions. The authorised period manager then closes the September regular period. In October a late September adjustment is discovered. An ordinary accountant cannot simply backdate it into the locked month; an elevated user must decide whether reopening is justified and, if so, provide the reason before the period is reopened.
A control Todo is not the same as an implemented system gate
An organisation may require specific signoffs before month close as policy. Unless the application code enforces a dependency, that requirement should be described as an organisational close procedure rather than a TouteGestion automatic prerequisite. This distinction keeps the Knowledge Centre accurate while the close-control architecture continues to mature.
Practical configuration checklist
- regular accounting period belongs to the intended fiscal calendar
- operational transactions for the month reviewed before close
- bank reconciliation and subledger exceptions reviewed where applicable
- Trial Balance and required reports reviewed independently
- period closed by a user with accounting.periods.manage
- late postings not forced into a closed period
- reopening limited to accounting.fiscal_years.reopen authority
- mandatory reopening reason explains the exception
- hard-closed fiscal years reopened only through the fiscal-year workflow
- month-end close not confused with Soft Close or Hard Close at year-end
Connect accounting structure, workflow and reporting.
Explore the product or continue through the Accounting Knowledge Centre.