
No, this isn’t a song by a Village People tribute band. (Although I kind of wish it was.)
Nor is it a reference to the art and science of macroeconomics. I work with a fine group of people who are vastly more qualified to write on that topic than I am. So I’ll leave that to the experts.
Rather, the article title refers to those tricky little things in Microsoft Excel called “macros” which are essentially a way of automating a sequence of activities so that something which used to take hours to do manually can be done with just a couple of mouse clicks.
Before we go any further, however, don’t despair – I’m not going to teach you how to write Excel macros or run through a list of my favourite macros of all time. This article is all about efficiency gains and automation (bet you’re wishing it was about my favourite macros of all time now…).
In the old days…
I consider myself fortunate because I’m just old enough to, at the very start of my career, have experienced what it was like to keep a set of accounts entirely manually. Handwritten ledgers. Manual extended trial balances. Reconciliations written out longhand.
I didn’t do a lot of it as computers were fast making inroads into the world of accounting. A year or two after I started work, keeping your accounts by hand seemed anachronistic, but once upon a time…and not even all that long ago…it was how everybody kept their accounts.
Now, accounting is an easy thing to computerise. It’s all about facts, numbers, and surface-level logic – a perfect match for the digital world because that’s exactly how a computer runs. And still do – while they’re a lot flashier and generally more reliable than early PCs, the underpinnings of a modern computer are exactly the same as the prehistoric models we used in the late 1980s and early 1990s.
The reason I consider myself fortunate to have kept a set of accounts manually is because it gave me a perspective most accountants today don’t have – because they never worked in a manual bookkeeping environment, they have no baseline for comparison.
It also gave me a level of understanding of the nuts and bolts of the accounting process which are mostly invisible to users of modern computerised accounting systems, where many things just take place “as if by magic” in the background. In the old days, I’d have had to enter all of that manually somewhere.
While I’m not pretending this has been a skill I’ve used very often in the last 30 years or so, nonetheless there have been a few pivotal moments where I’ve worked out the answer to a particularly thorny problem faster because I understood exactly what was going on in the background from when I had to make those entries manually.
Occasionally, that got businesses I’ve worked for out of some sticky corners.
Then came computers
When computers came along, they fairly quickly got to grips with accounting thanks to the fact-based, surface-level logic required to prepare a set of accounts.
While modern packages like Sage and Xero are much easier to use than those early ones, and considerably more helpful than their historic equivalents, they all do essentially the same things as a manual set of accounts used to.
All the debits still go on the left and all the credits still go on the right – that’s been at the heart of double-entry bookkeeping for over 500 years.
But what computers did bring to accounting was massive efficiency gains. A Finance Department which might have had 20 people in the 1980s would probably have 4 or 5 people in it now.
The cost savings for finance teams have been massive. A whole swathe of accounts assistants, ledger clerks, and document processors were no longer necessary.
However the point came where it was much more challenging to make further cost savings. After you take 75% of the people out of your accounting department, it becomes less likely that you’ll save another 75% of the remaining staff complement moving forward.
So finance professionals shifted away from automating the “grunt work” of ledger processing, because that had already largely been done. The opportunities for further cost savings were very limited, if they existed at all, so the RoI on pursuing every fine little detail was low.
They did, however, recognise that one area of accounting which had been largely untouched up to that point was report production.
Not reports as in P&Ls and balance sheets – they come off the computerised accounting system just fine already. But the sort of summary reports you might give to the board, perhaps, or a department head – people who don’t need all the details that a professional accountant might need, just a summarised version.
Until fairly recently, that sort of reporting was largely manual still, and involved lots of spreadsheets and keying data into cells so that information could be manipulated inside Microsoft Excel and formatted appropriately for its intended purpose.
That’s where macros came in.
Although macros had existed in some form inside Excel for quite a while beforehand, it’s only been in the last 20 years or so, as Microsoft introduced the version of Excel we still use today, pretty much, that macros have been more widely used.
In the early days, they were clumsy and hard to use unless you had a background in computer programming. Microsoft, to give them credit, have made macros vastly easier to use in the last 20 years or so.
Now most finance departments use macros to automate some or all of the processes for extracting data and compiling regular daily/weekly/monthly reports.
Here’s the funny thing
Here’s the funny thing, though.
Macros were originally billed as making finance departments more efficient. Tasks which might have taken a day beforehand could be done in an hour. I’m sure some people were salivating at all the cost savings which could be generated from introducing macros into their financial reporting processes.
Yet their actual impact on efficiency and cost saving has been more or less zero.
“Wait!” I hear you say. “How come introducing a technology which makes compiling reports more efficient hasn’t allowed us to make cost savings in our finance department?”
(Don’t feel too bad if that was your immediate thought. Most accountants would have thought he same when macros were brought in to financial reporting systems.)
There are two main reasons for this:
Reason 1
If you have a finance department of 4 people (down from 20 people 30-odd years ago), it’s extremely unlikely that you have any single person who spends all their time on financial reporting.
It’s probably 10% of everyone’s job – simple reports being done by a junior person, board reports being done by a senior person, etc – and you’re unlikely to get all 4 of those people to switch to a contract where you only pay them 90% of their previous salary even if you do automate all of the reporting (which I doubt).
So what probably happens is that you keep all 4 people on full-time salaries, meaning a cost saving of £0.
Reason 2
Because writing reports became “easy and simple” people started demanding a lot more of them. The volume of reporting on often trivial details in organisations today would have been considered genuinely jaw-dropping 30+ years ago.
Never mind a finance team of 20, you’d have needed a finance team of 100 to get through what would be considered a normal reporting load nowadays.
It’s a separate topic for another day, but far too high a proportion of the reporting done inside most organisations is either recording trivialities which don’t need to be recorded, or is so widely ignored that it’s a complete waste of time and effort creating the report in the first place.
The combined effect of either or both of those is that, despite introducing lots of ways of making finance teams “more efficient” in the last 30 years, there has often been little or no positive bottom line impact as a result of all this extra efficiency.
Productivity
People often mistake productivity for efficiency and assume the bottom-line results are self-evident. Well, except in rare situations, they’re not.
You could, for example, say that the accounts person who is churning out 100 reports a month instead of 1 is being 100x more efficient than they were in report production.
While that maths is superficially tempting (and, to be fair, a lot of software sales have been made on the back of exactly that maths), if the extra 99 reports are on trivial matters and/or are rarely read by the people who get them that might be seen as more productive from the perspective of the person producing the reports.
However it isn’t more efficient, as far as the business is concerned, because there is no bottom-line impact.
In fact, there has probably been a negative bottom-line impact – not only do you still have the salary you had before, you also have extra software costs you didn’t have before, and no offsetting efficiency gains to factor in. So the bottom-line performance is actually worse than it was before you became “more productive”.
It’s like all those people on Twitter who claim AI makes them 10x more productive in writing software.
In the very narrow sense that they are using technology to write more lines of code, that’s correct. But it’s highly likely that they are writing code to carry out functions which have little or no real-world bottom line utility, in which case how productive they are (in terms of lines of code written) is irrelevant.
From a more strategic viewpoint, it’s all been a complete waste of time.
The questions to ask
Given what I do for a living I get pitched all the time by people who want to make X, Y, or Z more efficient in my business.
I’ve got to say, at the risk of appearing like a jaded old curmudgeon, I can tell at a glance that their claims are mostly garbage.
Most of them are, on the very kindest interpretation, productivity improvements which will have zero real-world impact on the bottom line, like the accountants using macros for reporting above. They do more, perhaps, but it makes no difference to the cost base because we will still be employing as many accountants as we were before, so there is no bottom line impact (apart from the negative one due to the cost of additional software licences).
Alternatively the claimed theoretical “efficiency” turns out to make absolutely zero difference to my life, never mind my cost-base, and is completely pointless.
My favourite example of this at the moment are those services which claim to save you time by getting AI to summarise documents so you don’t need to read them.
I get two sorts of documents.
- Documents I can read in 10 seconds or less – it takes AI longer to summarise those than it takes me to just read them (I know – I’ve timed them). And anyway who needs a summary of a 3-para document? Just read the darned thing, for goodness’ sake.
- Documents, often legal in nature, which run to 30 or 40 pages. The last thing in the world I want are those documents summarising as there are far too many nuances which need careful consideration – a summary tool would skip over those details because they don’t look important enough, even though often the success or failure of an entire agreement turns on those details (or lack thereof) in a contract.
So given that 95% or more of the documents I receive are not suitable for a summary tool, that means the cost saving any system brings must deliver a positive RoI on the 5% of the documents I receive which could be considered candidates for a service like this.
Whilst that isn’t completely impossible, it’s a tough benchmark to reach and, in practice, none of the tools software companies are desperate to sell me come close to it.
So when you get a pitch from someone promising to make your business more efficient by automating some task or other, ask yourself these questions:
- Never mind automating that task – does it need to be done at all? If not, your lowest cost outcome is to eliminate that task completely, not to automate it.
- Is it more productive or more efficient? Efficiency is good because that translates into bottom line impact. Productivity isn’t a bad thing, but if it’s just people doing a pointless task faster, you’re kidding yourself if you think that’s going to transform your business.
- Where exactly are the cost savings? Unless you know precisely who you’re firing, or exactly which existing service you’re going to cancel your subscription for when you bring in a new service, you’ll never make any cost savings – you just end up with the same cost base you have now, with the added cost of some new software or service on top.
What people selling productivity and efficiency solutions forget is that the last 30 years has seen a huge increase in productivity for most organisations. That 20 person finance department of 30 years ago is now a department of 4 or 5 people, so generating incremental cost savings isn’t impossible, but it’s an order of magnitude harder than it used to be.
That’s largely because people selling productivity and efficiency solutions are just selling a product – they don’t understand how real businesses operate.
They fantasise that summarising all my emails will save me 2 hours a day when the reality is I wouldn’t get 95% of my emails summarised anyway, so at most they might save me 5 minutes a day and the amount of time, energy and hassle I’m prepared to put up with to save 5 minutes a day is pretty much zero.
I’m certainly not giving anybody’s vibe-coded AI app access to all my emails in order to save me 5 minutes a day – I’m just going to spend that “extra” 5 minutes.
It turns out that the biggest efficiency gains you can make to deliver a positive bottom line impact are cutting out pointless, low value-adding tasks, not automating them – all that does is paper over the cracks of a fundamentally broken system.
And being clear on exactly what costs you are, in the real world, going to eliminate by bringing on board some system for improving productivity and efficiency. If you keep all the same costs, and add in an extra layer of new costs for software on top, you’re losing money, not making money, on that transaction.
To paraphrase the Village People, every accountant wants to be a macro man (or lady). You need to be clear that “doing more stuff” translates into bottom line benefit, or the best decision you can take for your bottom line is – paradoxically – not trying to be “more productive”.
Don’t fall into the traps set by software companies in particular – productivity and efficiency are not the same thing – productivity is a measure out output (100 reports vs 1 report), efficiency is a measure of bottom line impact.
While software companies hope you don’t spot that slight distinction, I promise that it’s better for your bottom line if you do.








