The month-end close is one of those finance processes that nobody loves but everyone tolerates — until the pressure builds enough to demand a fix. The typical mid-market close takes somewhere between 8 and 15 business days. That means a significant portion of your finance team spends more than two weeks of every month doing retrospective accounting rather than forward-looking analysis.
There's a version of this problem that gets solved by adding a staff member. There's also a version that gets solved by process re-design and better data discipline. This article is about the second version — specifically, five changes that routinely cut close time by 30 to 50% without expanding headcount.
Before getting into the changes: we're not saying the close can or should be eliminated. The close exists for good reasons — it's how you verify that your books are accurate, your reconciliations are clean, and your numbers can stand up to an audit. The goal isn't a shorter close at the expense of integrity. The goal is a faster close that's equally reliable.
Change 1: Map Every Close Task to the Day It Can Start
Most close processes have a hidden problem: tasks that could start on day 2 are being started on day 5 because no one has defined the earliest possible start date. The result is that the close becomes a sequential queue when it could be partially parallel.
Take bank reconciliations. If your bank data is available the morning after month-end, there's no reason bank recs can't begin on the 1st of the month. Yet in many teams, bank recs start on the 4th or 5th — not because of a genuine dependency, but because that's when the controller "gets to it" after completing other tasks.
The most effective first step in close re-design is building an explicit task map: every close task, its earliest possible start date (based on real data dependencies), and its actual start date from the last three closes. The gap between these two columns is your re-design opportunity. In our experience working with growing finance teams, the gap is typically two to four days for a standard 10-day close. That's recoverable time — without process changes, just schedule changes.
Change 2: Pre-Clear Accruals Before Month-End
Accruals drive a significant portion of close delays — particularly large recurring accruals like employee bonuses, commissions, or consulting fees that depend on data from operational systems outside finance. The standard approach is to wait until day 1 or 2 of the close, then chase the relevant business units for the numbers.
The faster approach is to run accrual estimates in the final week of the month and flag exceptions early. For recurring items with predictable patterns — a monthly software licence, a standing consulting arrangement, an office lease — there's no reason to calculate these fresh each close. Build the standing accrual entries in your ERP and review them for accuracy rather than creating them from scratch.
For variable items like commissions, establish a reporting deadline with Sales: they submit a preliminary figure by the 25th of the month, finance posts the accrual on the 26th, and any adjustment posts in the first two days of the close once the final number is confirmed. This pre-clearing approach moves perhaps 20–30% of accrual work out of the close window entirely.
Change 3: Automate the Reconciliation Triggers
Reconciliation is the mechanical backbone of the close, and it's also where significant time is lost to manual data-matching that could be automated. When a finance team is exporting bank statements into Excel and manually ticking off matched transactions, they're doing work that an ERP rule-set should handle.
The investment required here depends on your ERP configuration. In Fortnox, Visma, and similar Nordic mid-market platforms, bank transaction matching rules can be configured to auto-reconcile recurring items — payroll runs, standing orders, supplier direct debits — that match predictable patterns. The reconciliation work that remains is exceptions: unmatched transactions, split payments, currency differences.
Consider a distribution business that processes roughly 300 bank transactions per month. Of those, perhaps 80% are recurring or rule-matchable (payroll, supplier DDs, utility payments). That leaves 60 transactions requiring manual review — down from 300. Reconciliation time drops accordingly, and the quality of the review improves because the controller is focused on genuine exceptions rather than mechanical matching.
Change 4: Establish a Hard Cut-Off Policy and Enforce It
One of the most consistent findings in close optimisation is that the close extends partly because of late-arriving transactions rather than process inefficiency. Purchases posted on day 3 of the close. Expense reports submitted on day 5. Invoices dated last month arriving on the 8th.
A hard cut-off policy — documented and enforced — eliminates most of this. The policy is simple: transactions dated in month M must be submitted to finance by a specific time on the last working day of month M. Anything arriving after that point is posted to month M+1, with a note in the accounting records if material.
This sounds obvious, but it requires both executive support and consistent enforcement. The first month you reject a late invoice submission and make a department head wait, there will be friction. The second month, the pattern changes. Within a quarter, late-arriving transactions typically drop significantly.
The counter-argument — that an invoice shouldn't move months just because it arrived late — has merit for material items. Those should be handled as adjusting entries with appropriate documentation. But for immaterial items (most late submissions are immaterial), the cost of processing them in the close is higher than the accounting benefit of matching them to the "correct" period.
Change 5: Build a Close Checklist with Time Budgets, Not Just Task Names
Most close checklists are lists of task names: "bank rec," "AR aging," "intercompany," "payroll accrual." They confirm that tasks were completed but provide no information about whether the close is running on schedule.
A more useful format adds time budgets to each task — not just deadlines, but expected duration. If the payroll reconciliation should take 90 minutes and it's taking four hours, something is wrong with the underlying data, not with the controller's effort. That's a signal to investigate the root cause, not to work faster.
Adding task durations also makes it possible to identify your close's critical path — the sequence of tasks where delay will cascade into a later finish date. For most mid-market companies, the critical path runs through the consolidation step, particularly if you have multiple legal entities. If entity-level closes are running late, the consolidation can't start, and everything shifts right. Knowing which tasks are on the critical path tells you exactly where to focus process improvement effort first.
The Data Problem Underneath All of This
Each of the five changes above has a common thread: they all depend on clean, timely data. The bank rec automation requires a live bank feed. The accrual pre-clearing requires accurate preliminary figures from operational teams. The reconciliation triggers require that the ERP's chart of accounts is properly configured and maintained.
A close that takes 12 days typically reflects both process problems and data quality problems. The process problems are more visible — you can see the task map and spot the gaps. The data quality problems are less visible but often larger. If your ERP has accumulated inconsistent account mappings, duplicate supplier records, or manual journal workarounds that nobody can fully explain, any process improvement will hit a ceiling until those are cleaned up.
The practical implication: if your close is currently above 10 business days, start with a data quality audit before redesigning the process. Map every manual workaround in your close and ask what data problem caused it. Fixing those underlying issues often produces close time reduction without any process change at all — and it makes every subsequent improvement faster and more durable.