Controls
Period locking: why audit-ready books start with controls
· 6 min read
Locking each period isn't bureaucracy — it's how you keep restatements, surprise adjustments, and quiet edits out of your books for good.
Unlocked books are a restatement machine
If last March can still be edited in August, your comparative reports are a suggestion. Someone recodes a vendor, a late invoice is backdated, and the board pack no longer matches what you presented. Nobody intended to restate. The system allowed it.
Audit-ready does not mean 'we hired a Big Four firm.' It means a reviewer can see what posted, who posted it, and that the period could not be silently rewritten afterwards.
Locking is the close, not a ceremony after the close
Treat the lock as the definition of done. Review, sign off, lock. Prior-period adjustments then become a visible, approved event rather than a quiet edit. That single change is what makes flux analysis trustworthy.
Teams that skip the lock usually do it because they are still waiting on information. That is a cutoff problem. Set a cutoff, estimate the residue, and lock. You can post a documented adjustment next period. You cannot keep the books open forever and call it control.
Traceability beats screenshots
When an auditor or an incoming finance lead asks why revenue moved, the answer should be the journal, the invoice, and the user — not a Slack thread. Controlled posting with validation before an entry hits the ledger is how you avoid cleaning up invalid data at review time.
Modern Accounting AI makes period locking and an audit trail defaults, because books that can still be rewritten are not books you can defend.