When an accounting period is closed, finalised, its accounting should not simply be changed afterward. Lock dates are how Odoo protects that. This piece is about lock dates and period control in Odoo.
Why a closed period must be protected
An accounting period, once closed, is finalised: its financial result is settled, and it may have been reported and built on. If the accounting of a closed period could be freely altered afterward, the closing would mean nothing, the finalised result would not be genuinely finalised, and the reported figures could quietly become inconsistent with what is in the system. So closing a period and protecting it from change go together. A closed period has to be protected, or its closing is not real.
What lock dates do
A lock date, in Odoo, is the mechanism for protecting closed periods. A lock date locks the accounting up to a certain date, so that entries in that period, the closed period, cannot simply be altered. Once a period is closed and locked, its accounting is genuinely protected: it is not freely changeable, and the finalised result stays finalised. Odoo supports lock dates, including separate locks for different aspects, so the protection of closed periods is genuine.
Period control
Lock dates are the heart of period control: the controlling of which accounting periods can still be changed and which are closed and protected. With period control through lock dates, a business has a clear, enforced boundary between the open period, where accounting is still being recorded, and the closed periods, which are finalised and locked. Period control is what keeps that boundary genuine, so the business's accounting is, at any time, an open period being worked and a settled history of closed, protected periods.
The controlled exception
An honest and useful point. A closed period should be protected, but occasionally a genuine need arises to make a correction in a closed period. Odoo supports a controlled, recorded exception to a lock: a deliberate, authorised, audited override that allows a genuine correction in a locked period, rather than the lock being either absolute or freely bypassed. This is the right balance: closed periods are genuinely protected by default, and a genuine necessary correction can be made, but only as a controlled, recorded exception, not as a free alteration. The exception being controlled and recorded is what keeps the protection meaningful even while allowing for the rare genuine need.
Why this matters
Lock dates and period control matter because they are what make a closed period genuinely closed, and so what make a business's finalised financial results genuinely trustworthy. A business with proper period control can rely on its closed periods: their results are settled, protected, and not quietly changeable. A business without it has closed periods that are not genuinely finalised, which undermines the trustworthiness of its financial history. Period control is part of genuine financial discipline.
The takeaway
Lock dates and period control in Odoo protect closed accounting periods from change, so finalised financial results stay finalised. A lock date locks the accounting up to a date, so entries in closed periods cannot simply be altered, with separate locks for different aspects. Period control through lock dates keeps a genuine boundary between the open period and the closed, protected ones. A controlled, recorded exception allows a genuine necessary correction in a locked period without undermining the protection. This is what makes closed periods, and the business's financial history, genuinely trustworthy. For how we approach Odoo, see our ERP practice.