UK sole-trader AI stack 2026: which tools are deductible, and what MTD-ITSA breaks

If you are a UK sole trader running a Claude Pro or ChatGPT Plus subscription and you are now within sight of the £90k VAT threshold, or the £50k MTD-ITSA threshold that landed on 6 Apr 2026, the question is which of those subscriptions HMRC will let you deduct, and what the accounting workflow needs to look like before April becomes a problem rather than a deadline.

The short answer is that AI subscriptions are deductible, but only under HMRC’s wholly-and-exclusively test, and only when paid from the business bank account. The cleaner answer, above £50k turnover, is to switch to the business-tier seat (Claude Team or ChatGPT Business), because the personal-use exposure is structurally lower and the audit trail is built for the trade, not for a household. The expensive answer is to mix personal and business use on a consumer-tier account paid from a personal card, then try to apportion at year-end. That is the line HMRC’s BIM37600 dual-purpose guidance was written to catch.

What MTD-ITSA actually changed on 6 Apr 2026

The Making Tax Digital for Income Tax Self Assessment regime moved from voluntary pilot to mandatory for sole traders and landlords with gross trading and property income over £50k. The threshold drops to £30k from Apr 2027 and to £20k from Apr 2028. Most UK sole traders running an AI-augmented service business will be inside one of those windows by Apr 2028 even if they are outside today.

The structural change for the AI-tool stack is that paper or end-of-year-spreadsheet record-keeping no longer satisfies the regime. Every Claude, OpenAI, Microsoft, Cursor, or similar invoice must be captured in MTD-compatible software at the point it lands, not reconstructed in March. The official list of HMRC-recognised software is published at Find software that’s compatible with Making Tax Digital for Income Tax.

Source: HMRC MTD for Income Tax collection, updated 2026.

The two practical implications for an AI-augmented sole trade are unrelated to the tax itself: the software you pick now is the software you will run for a decade, and the expense categorisation you set up now is the categorisation HMRC will sample if a section 9A enquiry runs.

The wholly-and-exclusively test on AI subscriptions, in plain English

HMRC’s BIM37007 wholly-and-exclusively test is older than the AI subscription business model, and it does not need updating for it. The test allows a deduction when an expense is incurred entirely for the trade. A Claude Pro subscription used to draft client proposals, review contracts, and write outreach copy is incurred for the trade. The same Claude Pro account used over the weekend to help a friend with their CV is not exclusively for the trade.

The standard sole-trader move on dual-purpose expenses is apportionment under BIM37600: claim the business proportion only. For AI subscriptions, apportionment is technically available but practically thin. There is no clean way to demonstrate that 73% of your prompts were business-related. HMRC will accept a reasonable basis, but “reasonable” is doing a lot of work in that sentence.

The two structural moves that remove the ambiguity:

Pay from the business bank account, not the personal one. A subscription paid from a personal card and reimbursed via director’s-loan or owner-drawings creates the dual-purpose presumption HMRC’s guidance leans into. A subscription paid directly from the business account, with the invoice in the business name, creates the wholly-and-exclusively presumption in the opposite direction. Neither presumption is conclusive, but the starting position matters.

Take the business-tier seat once turnover supports it. Claude Team is £24/user/month; ChatGPT Business is $25/user/month. The seat is admin-managed, has its own SSO and audit log, and is structurally not your weekend personal account. The price uplift over the consumer tier is $4–7/seat/month, below the noise floor for a single-person trade running anywhere near the VAT threshold.

The threshold we recommend for the switch is VAT registration. If you are about to cross £90k and start charging VAT, you are also about to look more visible on HMRC’s monitoring; the business-tier seat is the move that closes the same audit-trail question on the AI line.

Reverse-charge VAT on AI subscriptions: which entity invoices you

If you are not VAT-registered (turnover under £90k), reverse-charge does not apply. You pay the gross invoice and book it as the deductible expense in your accounting software. Skip the next two paragraphs.

If you are VAT-registered, the question is which legal entity issued the invoice. HMRC VAT Notice 741A on place of supply of services governs this. The 2026 picture for the three most common AI vendors a UK sole trader uses:

Confirm your own OpenAI billing entity on the next invoice. OpenAI has changed the UK invoicing entity once already during the post-Brexit transition, and a small number of UK customers are still on a US-entity invoice. The reverse-charge treatment changes accordingly: US entity → reverse-charge; Ireland entity → reverse-charge (different legal basis, same practical outcome); UK entity → standard input VAT on the invoice.

The mechanics of reverse-charge are routine for any VAT-registered sole trader: enter the supply at the standard 20% UK rate on both the input and output side of the VAT return, with zero net cash impact, and the deductible expense is the gross subscription cost.

FreeAgent, Xero, or QuickBooks for the MTD-ITSA AI stack

All three appear on HMRC’s recognised MTD-ITSA software list. The practical question is which handles AI-vendor invoices with the least setup overhead.

FreeAgent is the practitioner default for UK sole traders under £200k turnover. Its Open Banking feed pulls business-account transactions automatically; the receipt-bank-style PDF capture is included; and its expense-category tagging is reliable on the standard AI vendors after one pass of manual categorisation. Free with a NatWest, Royal Bank of Scotland, or Mettle business account. Otherwise £19/month + VAT for sole traders.

Xero is broadly similar and scales better as headcount appears. Its receipt capture is via Hubdoc, which is a paid add-on at most subscription tiers. For a single sole trader, this is friction Xero does not need; for a sole trader who will hire in the next two years, the same friction is justified by what Xero can run later. £15-£60/month depending on tier.

QuickBooks works and is on the recognised list. Its UK MTD-ITSA module is the youngest of the three (its general ledger predates MTD-ITSA by a decade, but the ITSA-specific submission flow shipped in 2025), and its AI-vendor categorisation defaults are less reliable than the other two. Claude and OpenAI invoices land in “Software & subscriptions” by default, which is fine, but the auto-tagging accuracy on the rest of the receipt is the lowest of the three. £14-£36/month.

Our default recommendation for a UK sole trader running an AI-augmented service trade under £200k: FreeAgent, with the AI subscriptions tagged to a dedicated “AI subscriptions” expense category. The dedicated category is the line HMRC will sample if a section 9A enquiry runs, and a clean category trail is the difference between a one-letter resolution and an extended back-and-forth.

When the business-tier seat starts to pay back

The arithmetic case for switching from Claude Pro (£17/month annual) or ChatGPT Plus ($20/month) to Claude Team (£24/user/month) or ChatGPT Business ($25/user/month) is weak in isolation. The uplift is £4–7/month/seat. At one seat, a year of the difference is £48–£84.

The compliance case is stronger. The business-tier seat has:

• An admin console with user provisioning and deactivation logged in the audit trail.
• A clean separation between the trade account and any personal account on the same email domain.
• A vendor-side trade-purpose indicator that supports the wholly-and-exclusively defence without you having to argue apportionment.
• Data-handling terms that are tuned for business use (no model-training on prompts by default on both Claude Team and ChatGPT Business).

The practical trigger we recommend: switch the same week you register for VAT. At that point the trade is visible enough that the audit-trail benefit is worth the uplift, and you are about to set the categorisation defaults that will run for years on the new accounting software.

If you are not VAT-registered and turnover is under £50k, the consumer tier (Claude Pro or ChatGPT Plus) is the right call. The wholly-and-exclusively defence is straightforward at that scale because the trade volume is small enough that the digital trail in your accounting software speaks for itself.

What we are not recommending

There are three configurations that look reasonable on paper and create avoidable HMRC friction.

Paying AI subscriptions on a personal credit card and reimbursing via owner-drawings. This is the single most common mistake we see in UK sole-trader books. It creates a dual-purpose presumption that requires post-hoc apportionment, and apportionment of an AI subscription is thin defence under BIM37600. Cost of the fix: one billing-portal update per vendor. Cost of leaving it in place: the gap between full deduction and apportioned deduction, plus the friction at any future enquiry.

Apportioning the consumer tier instead of switching to the business tier. Claiming “70% business use” on a Claude Pro subscription is technically permitted under BIM37600 but practically weak. The cleaner answer above £50k turnover is to remove the apportionment question entirely. Move to the business-tier seat, claim 100%, and document trade purpose in the admin console’s user list.

Picking the accounting software at the last minute before the MTD-ITSA quarterly deadline. The MTD-ITSA quarterly cadence runs Q1 (Apr-Jul submitted by 7 Aug), Q2 (Aug-Oct submitted by 7 Nov), Q3 (Nov-Jan submitted by 7 Feb), Q4 (Feb-Apr submitted by 7 May). Software setup, bank-feed connection, and the first quarter of historical invoice categorisation take 4–6 weeks on the practitioner timeline. Picking on 1 Aug for the 7 Aug deadline is the configuration that produces the most rushed categorisation, which is the categorisation HMRC will sample.

What changes this verdict

Cadence on this piece is 21 days through the rest of 2026 because MTD-ITSA secondary guidance from HMRC is still landing and because OpenAI and Anthropic have each changed UK billing-entity arrangements once during the post-Brexit transition. After 1 Jan 2027 the cadence moves to 45 days.

Three triggers move this verdict to Partial:

• HMRC publishes specific AI-tool guidance under BIM37007 or BIM37600. As of 12 May 2026, the wholly-and-exclusively guidance does not name AI subscriptions by category. A specific addendum would either tighten the apportionment standard (verdict tightens) or loosen the business-tier-seat recommendation (verdict loosens).
• OpenAI or Anthropic changes its UK invoicing entity. Each has done this once already during the post-Brexit transition. The reverse-charge mechanics shift with the entity; the deductibility does not, but the VAT line on the return does.
• MTD-ITSA threshold timeline shifts. The Apr 2026 / Apr 2027 / Apr 2028 ladder has been delayed three times historically. A fourth delay would push the urgency on accounting-software selection out, though our recommendation (FreeAgent for sole traders under £200k) is independent of the deadline.

Status: Holding as of 12 May 2026. Next review: 2 Jun 2026.

Related operator reading

The VAT-side companion to this piece is /operators/ai-invoicing-vat-compliance-small-business/, the inverse flow, what changes for sole traders who are themselves selling AI-augmented services. The bookkeeping software comparison for AI receipts in the Netherlands is at /operators/ai-bookkeeping-for-solo-founders/, and the German equivalent (DATEV, sevDesk, Lexware) is at /operators/ai-bookkeeping-de-datev-sevdesk-lexware/. The seat-by-seat ROI question for firms above sole-trader scale (5, 15, 40 people) is at /operators/ai-break-even-headcount-smb/.

Related enterprise reading

The procurement-side framing of the same vendor-billing-entity question at enterprise scale is at /enterprise-ai-agent-vendor-comparison/, and the VAT/place-of-supply intersection with the EU AI Act is touched on in /eu-ai-act-article-50-transparency-disclosure/.