A financial month lock lets you close a month’s books and keep them closed. When you finalize a month, its sales, expenses, labour, and purchases become read-only, so numbers you have already reported can’t be changed by accident later.
Finalizing a month
Finalizing a month submits it — that is what locks it. Once a month is finalized, the finance screens for that month switch to read-only, and the lock is enforced in the database itself, not just in the interface: an edit to a locked month is refused even if it is attempted directly.
Both owners and admins can finalize a month — it is a routine month-end task.
What to review before finalizing
A month that has not started cannot be finalized. A truly empty month is also blocked until it contains at least one sales, expense, or ingredient-purchase record.
For a non-empty month, the reports area can flag missing sales days, no sales value, missing food cost or labour, and a purchase ledger that does not line up with booked food cost. These are review warnings, not automatic blockers. Finalizing after a warning is an explicit operator decision; the lock records that decision but does not certify that the accounting is complete or correct.
Reopening a month
Sometimes a closed month needs a correction. Reopening a finalized month unlocks it so editing can resume. Because reopening reverses a financial-control decision, it is restricted to the workspace owner — admins can finalize, but only an owner can reopen.
The store reports area keeps a list of finalized months, so an owner can find and reopen a specific month even when they are not currently viewing it. The reopening is recorded in the audit trail.
Locks and exports
Locking is a status, not a wall around your data. Owners and admins can still export a locked
month. Financial CSV rows include a month_locked value of locked or open, so a reviewer can distinguish closed periods from editable ones.
Related
- Roles & permissions — who can finalize and reopen.