The close is a system

We keep meeting the same close. Three batch jobs. A workbook with the real logic. Two people who have not taken the same vacation in years. Audit asks a question that can only be answered by one of those people opening last month’s file. Leadership calls it “technical debt.” It is not debt. It is an operational process that was never allowed to become a system.

A close you can defend has three properties. Every posted amount has a source. Exceptions have a queue and an owner, not a sidebar conversation. The people who used to rebuild the month are reviewing the residuals, not performing the rebuild. Until those are true, buying a new general ledger or a new warehouse will only move the workbook.

The tempting rewrite is a streaming platform and a real-time narrative. We have yet to meet an examiner who asked for real-time. They ask for provenance. File-based ingest that posts through explicit rules will beat an elegant pipeline that still dumps into a spreadsheet at the end.

If your close depends on two people, the work is not to make them faster. The work is to make their knowledge executable, visible, and boring. That is unglamorous. It is also the difference between a company that can hire a controller and a company that can only hire another hero.