ERP for controllers

The situation

Six things that land on the controller.

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.

Schedules rebuilt every month

Prepaids, accruals, and depreciation recomputed in a workbook that has been carried forward for years and that nobody else can safely modify.

Review is sampling by necessity

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.

Chasing is the job

Fourth reminder to the same colleague about the same accrual, every month, and it is nobody’s favourite part of the role.

Coding drifts when you are away

The conventions are yours. A week of holiday produces a month of cleanup, which is why holidays get taken around the close.

Audit prep is archaeology

Assembling the same twelve extracts every year and reconstructing why something was treated the way it was eleven months ago.

The point is not to replace your judgement

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 parts of your job that make you indispensable are not the parts consuming your month. That gap is the entire opportunity.

Review of everything, rather than review of a sample

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.

You write the policies

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.

Sign-off is still yours

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

What people ask.

Will this replace part of my team?

In twenty-three deployments we have measured, none reduced finance headcount in the first year. What changed was what the team did — closing faster, chasing collections, and doing analysis that had been permanently deferred.

Can I stop it doing something?

Any agent can be dropped to draft, per workflow, instantly, by you. Work in flight falls back rather than failing, and that is the correct first response to anything that looks wrong.

How much configuration does this need from me?

Half a day a week for the first six weeks, mostly on chart of accounts and coding conventions. It is real time and we put it in the scope rather than discovering it later.

What if our coding has been inconsistent?

The agent will surface it rather than picking a side. Most controllers resolve a dozen inconsistencies in the first month, and that cleanup usually improves reporting more than the automation does.

Does it change how my auditor works?

They get a read-only role with drill-down from any balance to source and to the agent action behind it. Most controllers tell us the bigger win is that the close file already exists.

For controllers who are the single point of failure