Skip to main content

Command Palette

Search for a command to run...

Month-end reporting takes three days because of a problem that was solved ten years ago

Updated
5 min read
Month-end reporting takes three days because of a problem that was solved ten years ago

Every month, without fail, the same thing happens.

The month closes. Someone opens the reporting template, the one that's been used for two years, modified four times, and saved under three different names across two different folders. They open the accounting software. They start copying numbers. Column by column, tab by tab, the same data that exists in one place gets manually transferred to another place so it can be formatted in the way the client or the partner expects to see it.

This takes the better part of a day. Sometimes two. For practices with multiple clients on the same reporting cycle, it takes three days and a lot of evenings.

The technology to automate this has existed since at least 2015. The problem isn't the tools. It's that nobody has connected them, and doing so has always felt like a project for next quarter.

Next quarter never comes.


To be precise about what the problem actually is: it's not that the data is hard to get. It's that the format it lives in isn't the format the report needs it in.

The accounting software knows the numbers. The client wants them in a specific layout, perhaps grouped differently, perhaps with commentary, perhaps with a comparison to prior periods that requires pulling from two places. So someone does it manually. Every month. Despite the fact that the layout is identical to last month's, and the month before that, and every month going back to whenever the reporting relationship started.

This is not skilled work. It is careful, accurate, time-consuming work but the care and accuracy required are exactly the kind that software is better at than humans, not worse. Software doesn't transpose figures. Software doesn't accidentally pull from the wrong column. Software doesn't get to Thursday afternoon of a busy month-end and start making the small errors that come from tiredness and repetition.


The knock-on effects are underappreciated.

When month-end reporting takes three days, it compresses everything else. The client queries that come in after the report goes out, and they always come in, arrive during the recovery period when the team is already behind. The work that was displaced during the reporting push gets picked up late. The billing for the month is delayed because billing requires time to sit down and do it.

There's also the talent dimension. Qualified accountants doing manual data transfer are not being used well. Most of them know it. Some of them find it demoralising. The practices that can't retain good people are often the ones where a significant part of the working week involves tasks that have no connection to accounting skill or judgement.


There's also the client document problem, which compounds month-end.

Before the numbers can be processed, someone has to chase them. Receipts that haven't been uploaded. Bank statements for accounts the client forgot to mention. Approval on an entry that needs sign-off before it can be posted. This chasing is invisible in the way that all pre-work is invisible, it doesn't show up in the hours billed, but it consumes the time of someone who could be doing something billable.

In the week before close, one person in most practices does little else. Not because the practice is poorly run. Because clients are clients, they have businesses to run and their accountant's month-end cycle is not their primary concern.


The practices making genuine progress on this have stopped treating it as an IT project and started treating it as a workflow problem.

The workflow is: data exists in software → data needs to be in a report → report needs to reach the right person on schedule. Each of those steps can be automated or semi-automated with tools that connect to the software you already use. The report gets generated. It gets formatted to the client's requirements. It gets sent or queued for review, depending on the matter without anyone spending a Tuesday afternoon copying cells.

Client document collection works on sequences. The client gets a request at the right time. If they don't respond, they get a reminder. If they still don't respond, the escalation goes to the right person. Your team is notified when the pack is complete. They are not notified before it's complete, they don't manage the chasing.


Three days of month-end reporting is not a staffing problem. It is not a software problem. It is a configuration problem, the tools exist, they haven't been connected, and the person who could connect them is busy doing the manual work that the connection would replace.

That's a loop worth breaking.

The practices that break it don't necessarily bill more in the short term. But they stop dreading the last week of every month. Their senior people spend those three days on client work. Their junior people stop doing tasks that have nothing to do with why they studied accountancy.

Month-end should be the point in the month where your practice demonstrates what it knows. Not where it demonstrates how fast it can copy a spreadsheet.


A free assessment identifies exactly where your practice is losing time each month — written report, 48 hours, no charge.

https://switchtoai.ai/

More from this blog

S

SwitchToAI Blog — AI Automation for UK Businesses

12 posts