Why Xero, QuickBooks, Sage and FreeAgent don't handle partial exemption (and what HMRC actually expects)

There's a curious gap in the UK accounting software market. The four major small-and-mid-market platforms — Xero, QuickBooks Online, Sage Business Cloud, and FreeAgent — collectively serve more than 90% of UK SMEs. None of them automate partial exemption. This isn't a feature roadmap miss; it's an architectural decision, and HMRC has quietly accommodated it for years through the digital-link allowance for spreadsheets.

If you've ever filed a partial exemption return on a cloud ledger, you already know the ritual. Run a transactions-by-tax-rate report. Export it. Open the spreadsheet from last quarter, update the figures, recompute the recovery percentage, eyeball the de minimis test, post a manual journal back to the VAT control account. Three days a quarter, every quarter, for every affected client. And once a year, an annual adjustment that pulls together all four quarters and posts a single corrective figure that everyone hopes nobody asks too many questions about.

It's worth understanding why the major platforms work this way, what HMRC actually requires, and where the workflow falls apart in practice. The answers explain a lot about why partial exemption remains one of the most error-prone areas of UK VAT compliance — and why every practitioner you talk to has war stories.

The architectural reason: software vendors don't want to give tax advice

Partial exemption is fundamentally different from standard VAT. Standard VAT is a calculation: you charge 20% on sales, you reclaim 20% on costs, you submit the difference. Software can do this without an opinion. Partial exemption requires choices:

• Which method are you using — Standard, Simplified, or a Special Method approved by HMRC for your specific business?
• For each input transaction, is it directly attributable to taxable supplies, directly attributable to exempt supplies, or residual?
• For residual costs, what's the appropriate basis for the recovery percentage — values of supplies, floor area, headcount, transactions?
• Has the de minimis test been passed at quarter-end? At year-end?
• Has the override calculation been considered for clients in property or financial services?

These aren't questions software can answer without giving tax advice. And no software vendor is going to write code that gives tax advice. Xero said this explicitly on their own product ideas board: "Although Xero won't automatically calculate the adjustments needed for Partial Exemption calculations, you'll be able to easily adjust the boxes on the VAT Return for yourselves, before lodging through Xero." Translation: we're not going to do the calculation for you.

This isn't laziness. It's risk management. If the software calculates partial exemption wrong, the user is out of pocket, but so is the software vendor under negligence claims. Every vendor has decided the calculation belongs in the practitioner's hands.

What HMRC actually requires (and accepts)

Making Tax Digital for VAT requires a "digital link" between source records and the figures submitted to HMRC. In theory this means no manual re-entry, no copy-paste, no breaks in the chain from invoice to VAT return.

In practice, HMRC has made an explicit carve-out for spreadsheets. From VAT Notice 700/22:

A digital link includes linked cells in spreadsheets, for example, if you have a formula in one sheet that mirrors the source's value in another cell, then the cells are linked.

HMRC will also accept digital links as: emailing a spreadsheet containing digital records to a tax agent so that the agent can import the data into their software to carry out a calculation (for instance, a Partial Exemption calculation).

Read that twice. HMRC explicitly contemplates the workflow where you email a spreadsheet to a tax agent who runs a partial exemption calculation, then sends the answer back. They named partial exemption as the example. They built the rule around the fact that the major accounting platforms can't do the calculation.

This is the legal foundation that makes the standard workflow defensible. It's also a tacit admission, by HMRC, that Xero/QBO/Sage/FreeAgent don't handle this and they don't expect them to.

The practitioner consensus

If you scroll through AccountingWEB threads going back a decade, the answer is consistently the same. From a thread that surfaces almost any time you search for partial exemption help:

"There is no way that you are going to get Sage, Xero etc to correctly handle partial exemption. Essentially you will need to do it outside of the software, i.e. on a spreadsheet and enter the adjustment as a journal in the software — which is often easier said than done. Makes the MTD thing look a bit pointless."

The "easier said than done" part is the bit that catches new practitioners out. Posting a manual journal to the VAT control account in Xero is technically simple — three clicks. Doing it correctly so that the figures reconcile, the audit trail makes sense, and the next quarter's working paper still reconciles to the ledger is harder than it looks. And once you have ten clients on partial exemption, you have ten spreadsheets, ten manual journals, ten sets of working papers, and a strong incentive to keep doing it the way you've always done it because at least it's familiar.

Where the workflow breaks in real life

The standard workflow is defensible. It's also fragile in three specific ways.

First, the spreadsheet is a snapshot. It captures the state of the ledger at a moment in time. Any transaction backdated, recategorised, or amended after the spreadsheet was built doesn't update the spreadsheet automatically. If your client's bookkeeper makes corrections during quarter-end review, your spreadsheet is wrong by the time you submit. Most of the time these errors are small and don't change the answer. Sometimes they do.

Second, the annual adjustment compounds the problem. Partial exemption is provisional all year — each quarter uses the prior year's recovery percentage (or a best-guess for new businesses). At year-end you redo the calculation using actual figures for the whole year, post the difference as an adjustment on the first return of the next VAT year, and live with it. By year-end, your Q1 spreadsheet is twelve months stale. The transactions that supported your provisional Q1 figures may have moved. The single corrective journal you post is mathematically correct but doesn't have a clear audit trail back to which transactions caused which movement.

Third, the digital link breaks invisibly. HMRC accepts the spreadsheet workflow as compliant only if the digital link is unbroken. In practice, this requires perfect discipline: never copy-paste, always use cell references, always export from the ledger rather than retyping. In a busy practice with junior staff doing the legwork, the discipline lapses. The compliance failure isn't visible until HMRC asks.

What good looks like

The honest answer is: a connected calculation. Tax rates assigned in the ledger flow into a calculation engine that handles the partial exemption logic. The recovery percentage updates when the underlying transactions change. The de minimis tests run automatically with the full Test 1 / Test 2 / Test 3 working visible. The annual adjustment runs against the actual transactions in the ledger as they stand at year-end, with a working paper that shows exactly which transactions drove which figures. The adjustment journal posts back to the ledger with the working paper attached — so the audit trail lives with the figures.

This is what specialist tools are starting to offer. It's what OneSixth was built for. And it's what the major platforms will probably never do, because the architectural decision was made years ago and the risk-management calculus hasn't changed.

What this means for your practice

If you're handling partial exemption clients today, three observations:

1. Document your spreadsheet methodology. When HMRC asks (and they do ask), you need to be able to show the workings, the source data, the calculation method, and the journals posted. A well-organised spreadsheet workflow is defensible. A messy one isn't.
2. Watch for backdated changes between quarter-end and submission. Build a habit of running the spreadsheet on the date of submission, not the date of quarter-end. Lock the period in the ledger after submission to prevent further changes.
3. Treat the annual adjustment as a serious working paper. The single journal at year-end deserves a full reconciliation, not just a number copied from a spreadsheet.

If you'd rather not handle this in a spreadsheet at all, it's worth knowing there are now connected alternatives that handle the calculation in the same way the major ledgers handle standard VAT: automatically, with an audit trail, with the figures linked to the underlying transactions.