The close depends on you
Not because nobody else is capable, but because the sequence, the workarounds, and the judgement calls are undocumented and live in your head.
By role
In most mid-market companies the controller is the system. The consolidation workbook, the accrual schedules, the coding conventions, the reason the close finishes — all of it lives with one person, and everybody knows it and nobody has time to fix it.
The situation
Not because nobody else is capable, but because the sequence, the workarounds, and the judgement calls are undocumented and live in your head.
Prepaids, accruals, and depreciation recomputed in a workbook that has been carried forward for years and that nobody else can safely modify.
You look at the entries that seem odd and the accounts that have caused trouble before, because that is what fits in the time. It misses systematically rather than randomly.
Fourth reminder to the same colleague about the same accrual, every month, and it is nobody’s favourite part of the role.
The conventions are yours. A week of holiday produces a month of cleanup, which is why holidays get taken around the close.
Assembling the same twelve extracts every year and reconstructing why something was treated the way it was eleven months ago.
Almost everything that makes a controller indispensable is judgement — knowing that this vendor should be coded differently, that this accrual needs a conversation, that this variance is timing rather than movement. None of that is automatable and we would not want it to be.
What is automatable is everything surrounding it: preparing the schedules, running the reconciliations, checking every entry against pattern, chasing the owner of a blocked task, and assembling the evidence. Those consume most of a controller’s month and produce none of the value the role exists for.
The Controller Agent checks every journal entry against the pattern for that account, vendor, department, and period. It stays at Level 1 permanently and deliberately — an agent that both prepares an accrual and posts it is not performing a review, it is one party doing both halves of the job the control exists to separate.
What it surfaces is rarely dramatic. A recurring vendor coded differently this month, an accrual that reversed twice, an intercompany entry with no matching side. Individually small, collectively the difference between a clean close and an awkward conversation.
Level 2 automation means an agent acts inside rules somebody wrote. Those rules are yours to author, in a condition builder rather than in code, and every draft policy simulates against your last quarter before you enable it — showing what it would have auto-posted and how many of those your team subsequently corrected.
Policy authorship sits with the controller and authority grants sit with an administrator, deliberately different permissions. If one person could both grant an agent Level 2 and define what Level 2 permits, that is an unreviewed ability to automate postings.
Closing a period asserts the numbers are right, on your authority, to an auditor or a board. It is absent from the agent permission model entirely — not a default an administrator can lower. Everything up to it can be prepared; the assertion remains a person’s.
Questions
Your checklist and last three close dates is enough to show you which tasks are waiting and which are rework.