What "Closing the Books" Means, and Why Locking a Period Matters

"Closing the books" gets used to mean two genuinely different things, and it's worth being precise about which one applies here. Some accounting systems perform ceremonial closing entries at year-end — actual journal entries that zero out every income and expense account and roll the net result permanently into a retained earnings balance. Other systems, and BalanceMCP among them, mean something simpler: declaring a period finished and refusing to let anything post into it after the fact. Those are not the same operation, and confusing them leads to the wrong expectations about what happens when you lock a month.

BalanceMCP does the second one, not the first. Locking a period through a given date doesn't touch your income or expense accounts at all — it doesn't zero anything out, and it doesn't post any special entry. The balance sheet's Retained Earnings figure is calculated fresh from all-time income minus all-time expenses every single time the report runs, regardless of whether anything has ever been locked. Locking and Retained Earnings are unrelated mechanisms that happen to both live in the neighborhood of "end of period" — locking is purely about what can and can't be posted going forward.

Why bother locking at all, then, if nothing gets zeroed out? Because once you've reported a period's numbers to someone — an accountant, a lender, a tax filing, a business partner — those numbers need to stay exactly what they were when you reported them. If a new entry could still quietly post into January after you've already told your accountant what January looked like, the two of you are no longer looking at the same set of books, and neither of you would necessarily know it.

The mechanism is a single "locked through" date on a book. Once set, no entry dated on or before that date can be posted — enforced by the database itself, not merely by the application's user interface, so it holds even against something that tried to write around the ordinary workflow entirely.

The lock only ever moves forward. You can extend it — lock through February after having locked through January — but you can never move it backward to reopen a month you've already closed. That's deliberate, not a missing feature: the entire point of locking is that a closed period stays closed, and a lock that could be casually reversed wouldn't actually protect anything.

Locking doesn't have to happen only once a year. Most of the value comes from locking monthly, right after you've reconciled and reviewed — the same discipline a business running monthly filings or investor updates already needs, since "final" numbers that could still silently shift underneath a report you already sent somewhere aren't actually final. A book can have many lock dates over its life, each one moving the boundary further forward as you finish reviewing another month.

The practical monthly order is: reconcile your bank accounts first, categorize everything that's left, review the P&L for the period to make sure it looks right, and only then lock through the last day of that period. Locking is the last step of the routine, not the first — it's what you do once you're confident the numbers are correct, not a substitute for making sure they are.

Finding a mistake after a period is already locked doesn't mean you're stuck — it means the fix happens in the currently open period instead of being smuggled backward into the closed one. A reversing entry, dated after the lock, corrects the effect going forward; the month you originally locked will still look, on its own, exactly the way you locked it, and the correction shows up with its own date and its own memo explaining what it's fixing. That's genuinely what "closed" is supposed to mean — not "can never be wrong," but "can't be silently changed after the fact."

Locking is also a useful signal to share with anyone else who touches your books — an accountant, a bookkeeper, a business partner. Telling them "everything through the end of March is locked" is a concrete, verifiable claim, not just a verbal assurance that you're done reviewing that month; the database backs it up regardless of who's asking or when.