Buying Operations Software in the UK: A Straight Guide
A guide written by a vendor who does not file your return, has no UK payroll engine and no UK reference customer — which is a strange sales position and a useful vantage point, because it leaves nothing to protect except the argument.
Most buying guides for operations software are written by vendors who would like to sell you everything on the list. This one is not, and it is worth saying why before anything else: we do not connect to HMRC, we do not run UK payroll, and we have no UK customers you could ring. If a UK reference matters to your decision — and it reasonably might — that is a good reason to buy something else, and you should not have to reach paragraph forty to find it out.
What we do have is a fairly unusual view of the problem, because we built a live tax-authority integration in another market and therefore know exactly what the work costs and what it does not solve. That is the perspective this guide is written from. Nothing in it is tax advice.
The mistake that shapes every other decision
The mistake is to treat VAT as a filing feature and shop for it as one. Vendors will show you a submission screen, and it will work, and it will be almost irrelevant — because Making Tax Digital does not really ask you to submit electronically. It asks you to submit figures that reached the return through an unbroken chain of digital links from the underlying records. Transcription anywhere in that chain breaks it, and the submission screen is downstream of every place where transcription happens.
So the question is not "does it file". The question is "which of the nine boxes can this system produce from records rather than from a person". Those are different questions with different answers, and only one of them is hard.
Shopping for a filing button is shopping for the last five per cent of the problem. The other ninety-five is whether your purchase records can answer a question about tax at all.
The sales half is easy and nearly everyone passes
Tax due on sales, and total sales excluding tax, are derivable from any system that stores a tax rate on an invoice line. That is most of them, ours included. When a demo dazzles you on VAT, check which half it was demonstrating, because this is the half that always works and it is not the half you have a problem with.
The purchase half is where systems differ, and it is nearly never demonstrated
Reclaimed input tax is the box that decides what you pay. To produce it from records, a system has to know more about a purchase than how much tax was on it: the rate, the kind of tax, whether the recorded value included it. Systems that store only an amount can show you a total and cannot tell you whether any of it is recoverable — and a populated column that cannot answer the question is more dangerous than an empty one, because it looks like an answer.
We come out badly on this and say so on our market page: our purchase orders carry no tax at all, and our expenses carry an amount with no rate beside it. It is the first thing we would build for a UK customer and the reason we recommend, today, that the system owning your purchase ledger should own your return.
What to actually evaluate, in the order the decisions bind
-
Decide which system owns the return before you shortlist anything
Usually the one holding the purchase ledger. Settling this first converts a long integration argument into a short conversation about which exports need to exist, and it stops you paying twice for overlapping VAT features.
-
Then test the chain, not the feature list
Take last quarter's input tax figure and follow it back to individual purchases using only system links and exports. Wherever you have to read a number and type it somewhere else, you have found your compliance risk, and it will be in the same place next quarter.
-
Then ask what happens to adjustments
Corrections, partial exemption, reclassifications. If adjustments are typed over derived figures, the chain breaks precisely where the numbers move most. If an adjustment is itself a record with a reason, it holds.
-
Then look at the operational work, which is where the time actually goes
Procurement approvals, receipting, stock, projects, job costing, document retention. This is the majority of what an operations system does for you and it has nothing to do with VAT — which is why leading with VAT is how buyers end up with compliance software and an unsolved operations problem.
-
Then payroll, separately and sceptically
UK payroll means income tax tables, National Insurance, real-time submissions on or before each payday, and pension auto-enrolment assessment. It is a maintained statutory engine rather than a calculation, and it needs updating every year by somebody contractually obliged to. Ask who that person is. We do not have a UK payroll engine, and cost attribution to projects — which we do have — is not the same thing and should not be sold to you as if it were.
Where a Nairobi-built product is and is not a sensible answer
Being straightforward about distance is more useful than pretending it away. The interface is English-only, which is not a blocker here — one of few markets where that sentence is short.
| Reasonable to consider us for | Reasonable to rule us out for |
|---|---|
| Operational work — procurement with real approval trails, receipting, stock, projects, cost attribution | Anything where the VAT return itself must be produced and filed by this system today |
| Multi-currency operations where purchases happen in several currencies and the rate used must stay on the document | UK payroll of any kind |
| A UK head office coordinating African operations, which is the shape we are genuinely built for | A business whose procurement policy requires an in-region reference customer |
| Commissioning a specified build, where the precedent matters more than the feature list | A buyer who needs the capability now rather than specified, priced and built |
| Organizations who would rather read a published gap than discover it in month three | Anyone for whom "no UK customers" is disqualifying — which is a legitimate position |
Questions worth asking every vendor on your list
Six, and none of them take long to answer
Which of the nine boxes can you produce from records without a person assembling anything?
A good answer
A specific list, including the ones they cannot.
What a bad answer tells you
A vendor who answers "all of them" either has not understood the question or is describing a workbook.
Where is the tax rate stored on a purchase order?
A good answer
A named field, on screen, in the demo.
What a bad answer tells you
If the answer drifts to invoices or expenses, purchase commitments carry no tax and your input-side reporting starts later than you think.
Show me a figure in the return drilled back to individual transactions.
A good answer
A drill-down that reconciles.
What a bad answer tells you
If it cannot be drilled, the figure is a summary of a summary and nobody can defend it under question.
Who updates the payroll tables each year, and what happens if they are late?
A good answer
A named responsibility with a contractual shape.
What a bad answer tells you
Vagueness here is the single most expensive vagueness in the whole evaluation.
Can our data be held in a specific region, and is that a setting or a deployment?
A good answer
A straight answer either way — both are legitimate.
What a bad answer tells you
Anyone describing residency as a per-organization switch should be asked to show you the switch. Ours is a deployment, priced as work, and our compliance matrix said otherwise until we audited it.
What would you decline to do for us?
A good answer
A real list, delivered without discomfort.
What a bad answer tells you
A vendor with no boundaries has not thought about where their software stops, and you will find the edge later and at your own cost.
On the strange sales position
A guide that tells you to buy your VAT return elsewhere and rules us out of two of the five things on the list is not a negotiating tactic. It is what happens when you write the page from measurements rather than from a positioning document. If the operational work is what you need, that is the conversation to have, and it will be a better one for having had this paragraph first.
The one-line version
Decide which system owns your purchase ledger, buy your VAT return from that one, and evaluate everything else on the operational work. Then ask every vendor — us included — to trace one input tax figure back to a transaction without retyping it.
