Loading…
Loading…
Most finance teams run between three and eight schedules in spreadsheets. Here is how to find yours and how to judge which one to bring in first.
Ask a controller how many schedules they maintain outside the ERP and the first answer is usually two. The real number, once somebody actually counts, is normally between three and eight.
The gap is not evasion. It is that a schedule stops feeling like a schedule once it has been running long enough. It becomes "the deferred commission file", a thing that exists, that somebody updates, and that nobody thinks of as a subledger even though that is exactly what it is.
A schedule outside the ERP has three properties:
By that definition, the usual suspects:
Revenue schedules where contracts get modified mid-term and the system's reallocation does not match your policy.
Deferred commission amortising over a benefit period that differs from the revenue plan.
Capitalised software cost with the eligibility determination and the evidence held in a project workbook.
Lease schedules, particularly on Acumatica, which lists lease accounting through its marketplace rather than as a native module.
Equity expense, which is outside on every platform, because neither NetSuite nor Acumatica documents a stock compensation module.
Accrual and provision models for rebates, warranties, or variable consideration.
Intercompany allocations run in a model and posted as a journal.
Not all of those apply to you. Three to five of them probably do.
Take your last close and list every manual journal above a materiality threshold. For each, ask where the number came from.
The ones that came from a person's judgement are accruals and are a different problem. The ones that came from a file are your answer.
Then, for each file, record four things: who owns it, how long it takes each period, what it reconciles against, and what happens if that person is unavailable at close. That last column is usually the one that changes the conversation.
Not the biggest balance. Four factors, roughly in this order.
Frequency of change. A schedule that gets rebuilt every period because contracts keep changing costs more than a larger one that only rolls forward. Revenue and commissions usually top this list.
Reconciliation difficulty. If the schedule reconciles to the GL by inspection rather than by construction, a break can sit undetected for months. That is a control issue as much as an efficiency one.
Audit attention. Whatever your auditors asked most questions about last year will be asked about again. The cost of that is real and recurring.
Bus factor. A schedule only one person can run is an operational risk that has nothing to do with accounting.
Balance size is deliberately absent from that list. A large, stable, well-reconciled schedule is not urgent. A small one that changes constantly, reconciles by eye, and has one owner is.
It rarely means moving it into the ERP, because in most of these cases the ERP has nowhere to put it. That is why it is outside in the first place.
It means giving the schedule the three properties it currently lacks: a reconciliation with preparer and reviewer state, a retained version history so a prior period can be explained without rebuilding it, and a link from each journal back to the record that produced it.
The calculation can stay wherever it is calculated. What changes is that it stops being invisible to the close.
Even if nothing follows, the count is worth having. It is the answer to a question you will eventually be asked, either by an auditor, a new CFO, or a diligence process, and constructing it under those conditions is considerably less pleasant than constructing it now.
Not sure where your process sits?
Seven questions on the schedules outside your ERP, and what an auditor request costs today.