Accounting Process Improvement Starts With the Ledger, Not the Tool
- Maria Mor, CFE, MBA, PMP
- Jul 23
- 6 min read
A consulting firm walks in, maps what they see, and recommends a platform. Weeks later, the platform is installed, the dashboard looks clean, and the same duplicated entry that has been quietly overstating a cost center for two years is still sitting there, now running through new software instead of old software.
Even at the highest levels of the market, the pattern is showing up in public. According to a Wall Street Journal report on how McKinsey is adapting to AI, fewer companies want to hire a consulting firm for strategy advice alone anymore. As one consulting CEO quoted in the piece put it, clients no longer want a "suit with PowerPoint." They want a consultant who helps put new systems in place and manages the change through to the end, not just the diagnosis. If that shift is happening at the scale of the biggest name in consulting, it exists just as plainly at the scale of a growing company closing its books every month.
Table of Contents
Accounting Process Improvement Has Two Layers
Most outside help operates at one layer: the tool layer. Someone comes in, looks at the workflow from the outside, and recommends a system. That is a real skill, and it solves a real problem. It is also incomplete.
Here is the distinction that matters: accounting process improvement. That work sits underneath the tool layer, at the level of the actual entries. It is the difference between someone who has observed a close and someone who has run one. The person who has sat inside the entries knows what a duplicated transaction looks like before it becomes a variance. They know which reconciliation was forced to balance instead of explained. That knowledge does not live in a framework. It lives in having touched the work.
This is not a knock on firm size or a comment on fees. A team can be excellent at the tool layer and still never touch the ledger layer, regardless of how large or small they are. The two are simply different skills, and most engagements only staff for one of them.
What the Tool Layer Catches, and What It Misses
A tool implementation answers a specific question well: which platform should carry this workflow forward. It rarely answers a different question: what is currently happening inside this workflow that the new platform will now carry forward exactly as broken as before.
In accounting specifically, the things that get missed at the tool layer tend to be the same handful of patterns, repeated across industries and company sizes.
The same journal entry booked three different ways by three different people, none of them wrong on their own, all of them inconsistent together
A reconciliation that balances on paper because a difference was plugged, not because the difference was explained
Two departments touching the same transaction with no record of who has final ownership of it
A close calendar built around when people are available, not around when the numbers are needed
Manual work that has been quietly absorbed into someone's job so completely that nobody remembers it used to be a decision, not a habit
None of these show up as a system problem. They show up as a person problem, a timing problem, or a training problem, right up until someone traces them back to where they actually start.
A Paper Close Turned Structured, With No New Platform
A regional hospitality operation running 23 locations was closing its books on paper. Reconciliations lived in binders. Documentation existed only in the memory of whoever had been there longest. The fix was not a new system. It was standardizing how reconciliations were built, adding visibility into what had been done and what had not, and rebuilding the close using tools the operation already owned.
The result was a structured, paperless close and materially stronger audit readiness, without a single new platform purchased. The work was in the process. The technology was already sitting there, unused, because nobody had organized the operation around using it.
A Late Close Turned On Time, Through Ownership, Not Software
A separate close transformation involved a team that had been reporting late for as long as anyone could remember. Leadership assumed the fix was more staff or better software. Neither was true. The fix was standardizing journal entry practices, eliminating duplicated work, and rebuilding the close calendar around clear ownership of each step.
Within two close cycles, the same team was reporting on time, consistently. No system changed. The people did not change either. What changed was the structure they were operating inside.
Both of these outcomes came from someone who understood the work at the transaction level, not someone who recommended a tool and moved on to the next engagement.
Why You Cannot See This From Inside It
AI documents what you describe. It cannot see what you left out. A tool can produce a clean, organized workflow map based on what an owner or a finance team tells it. What it cannot do is recognize the control gap nobody mentioned, because nobody knew to mention it.
This is not a failure of intelligence, in a person or in a piece of software. You cannot see clearly what you built and live inside every day. That is a structural limitation, not a character flaw, and it applies whether the person looking is the owner, the controller, or an AI tool asked to summarize the process. Output that looks complete but hides a control gap is more dangerous than no documentation at all, because it creates confidence without protection. The same blind spot shows up well beyond the close, in back office financial controls more broadly, where a policy can look complete on paper and still miss where the real risk sits.
Why Outside Perspective Helps
The gap in accounting process work is almost never about effort. It is about proximity. The team running the close every month is too close to the process to see where it has quietly drifted from what it was supposed to be. That is not a criticism of the team. It is the same limitation anyone has toward a system they built and operate daily.
An outside perspective that has actually run a close, not just mapped one, finds in days what an internal team has been circling for years. The value is not in the recommendation. It is in knowing what the recommendation needs to account for, because the person making it has done the work themselves. That is the starting point of business process improvement done at the ledger level, not the tool level.
Free Resource: System Leak Audit
If you want a starting picture of where your own accounting process may be leaking time or accuracy before you bring anyone in to look at it, the System Leak Audit walks through five categories of hidden operational drains, including the ones that show up first in the close.
Frequently Asked Questions
What does accounting process improvement actually mean?
It means examining how the close, reconciliations, and journal entries actually move through your organization, not just which software carries them. It looks at ownership, timing, and consistency at the transaction level, then rebuilds the structure so the same gaps stop repeating every month.
Is this the same as switching accounting software?
No. A new platform can make a broken process faster without making it correct. This work addresses what is happening inside the workflow first. In some cases the existing tools are enough once the process around them is fixed.
How is this different from what a general operations advisor does?
Many operational reviews stay at the level of workflow diagrams and platform recommendations. This work goes further, into the actual entries and reconciliations, because that is where duplication, forced balances, and ownership gaps actually live.
Can our internal team fix this without outside help?
Sometimes. The limitation is not capability, it is proximity. A team that runs the same close every month has a harder time seeing where the process has drifted, because the drift happened gradually and became normal along the way.
Where should a growing company start?
Start with a clear picture of what is currently happening in the close, not with a new tool. A focused diagnostic is a useful first step, and a deeper process engagement goes further once the initial picture is in hand.
Ready to Look at Your Own Close?
If any of this sounds like your monthly close, the next step is a conversation, not a tool decision. A discovery call is where we look at what is actually happening in your process and whether there is a fit for the work.
The Back Office Brief
Get a weekly insight connecting back office operations to profit. Delivered every week, free.
Comments