AI can help a sole trader with the preparation for a Making Tax Digital quarterly update: sorting transactions into categories, spotting oddities and summarising the quarter. It cannot send the update. Submission has to come from compatible software linked to your HMRC account, and the accuracy of the figures stays with you.
The useful question is therefore where, between a pile of bank lines and a submitted update, AI earns its place and where it creates risk. The way to find out is to test it on one real quarter, against a result you already trust, before you rely on it, and to be clear from the start about the eight duties that stay yours whatever the tool does. Thresholds and dates were read from GOV.UK in November 2026; confirm them again before you act, as they are set by HMRC and change.
What a quarterly update actually is
Much of the fear around Making Tax Digital for Income Tax disappears once you see how small a quarterly update is. HMRC describes it as a summary, not a tax return. Your compatible software adds up your digital records for each business and produces totals of income and expenses by category. HMRC does not receive individual receipts or invoices. You do not need to make accounting or tax adjustments before sending one.
Three facts shape everything AI can do here.
- Each update is cumulative. It covers the tax year so far, from 6 April to the end of the update period. The second update contains the first quarter's figures plus the second, so a mistake in quarter one is still sitting there in quarter two.
- The categories are fixed. They are the same income and expense categories used in Self Assessment, so a tool that invents its own categories gives you something you must translate.
- A nil quarter still needs sending. If you had no income and no expenses in the period, you still tell HMRC.
Dates and who must use it
With standard update periods, the deadlines are 7 August (covering 6 April to 5 July), 7 November (to 5 October), 7 February (to 5 January) and 7 May (to 5 April, in the following year). If your accounting period runs 1 April to 31 March you can choose calendar update periods instead, and the deadlines stay the same. You must choose that in your software before you send your first update; after that, you cannot change it for the rest of the tax year.
Who has to use the system depends on qualifying income, meaning gross self-employment and property income before expenses, not profit. GOV.UK sets it at over £50,000 for those who needed to start in April 2026, over £30,000 from April 2027 and over £20,000 from April 2028. HMRC checks your Self Assessment return and writes to people who need to join. If you are near a threshold, read the GOV.UK page on qualifying income, because what counts is gross and it counts across all your self-employment and property income.
On late updates: for the 2026 to 2027 tax year HMRC says it will not apply penalty points for late quarterly updates, though the updates still have to be sent before you can submit your tax return using software. From the following year, a missed deadline earns a penalty point and four points bring a £200 penalty. That is a published rule at the time of writing, so check the current page if it matters to you.

The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowThe test: run AI on one real quarter, side by side
Do not judge a tool on a demo. Judge it on your own transactions, against a quarter you have already completed by hand or in your software. Here is the method, which takes an evening.
- Pick a finished quarter whose figures you trust, ideally one that has already been sent. Export the bank transactions for those three months as a spreadsheet.
- Remove what the tool does not need. Delete account numbers, and replace any personal names in the descriptions with initials. Keep date, description and amount.
- Give the tool the exact category list from your software, and ask it to assign each line to one, flagging any it is unsure of rather than guessing.
- Compare line by line with the finished quarter. Count agreements, disagreements and flagged lines.
- Total each category both ways and compare the totals, because the update sends totals, not lines.
- Decide in advance what is good enough. A reasonable bar for something that will save you time is, say, 95% of lines agreeing and no category total off by more than a few pounds, with every disagreement explained.
The prompt below is a template for step 3. Replace the bracketed items with your own.
You are helping a UK sole trader prepare bookkeeping records. I will paste bank
transactions (date, description, amount; money out is negative).
Allowed categories, and nothing else:
[paste your software's exact category names here]
For each line return: date | description | amount | category | confidence (high,
medium or low) | one-line reason.
Rules:
1. If a line could be personal spending or business spending, mark it "Needs my
decision" instead of choosing.
2. Transfers between my own accounts, loan drawings, owner's drawings and card
repayments are not income or expenses. Mark them "Not a business item".
3. Never merge or split lines. Never invent a missing amount.
4. After the table, give totals per category and a list of every line you marked
low confidence or "Needs my decision".
Transactions:
[paste]
What an illustrative run looks like
These figures are made up to show the pattern. Say a kitchen fitter's quarter has 84 bank lines. The tool agrees with the finished quarter on 71 of them (85%), flags 9 as "Needs my decision", and puts 4 in the wrong category. Of the wrong four, two are a fuel station purchase that included a meal (split purchase), one is a tool supplier whose name sounds like a clothing shop, and one is a refund from a supplier, treated as income instead of a reduction in the expense.
The totals tell the more useful story. Because the misfiled lines were small, the vehicle and materials totals differ from the trusted quarter by £14 and £38. Fine for a sense-check, not fine for a submission. The nine flagged lines, which would have been the ones to look at anyway, include a £420 transfer labelled "tools" that was actually a payment to a personal account. A chatbot that confidently categorised it would have inflated expenses by £420. A tool that asked, saved the trader from that.
Notice what that test teaches. The AI was not "accurate" or "inaccurate" as a whole. It was reliable on repeated, well-described items (a regular materials supplier, a monthly insurance debit), weak on mixed purchases and refunds, and most useful when allowed to say "I do not know". That gives you the rule for the next section: let it propose, and make every doubtful line a human decision.
Jobs AI does well in a quarter
Categorising repeat items
A supplier you pay every week is a pattern a tool picks up quickly. Accounting software with bank feeds does this with rules you set once; chatbots do it per upload. For a kitchen fitter, a timber merchant and a hardware chain account for most of the materials lines. For an online clothing store run by one person, payment-processor payouts, courier labels and fabric suppliers repeat constantly. The benefit is real because repeat items are most of the lines.
Catching what looks odd
Ask the tool to list anything unusual compared with the previous quarters you give it: a supplier you have never paid, an amount three times the usual, two identical payments on one day, an expense with no matching income. These are prompts for you to look, not conclusions.
Here are my categorised transactions for this quarter and the totals for the
previous two quarters (pasted below). List only:
1. Any category whose total is more than 40% above or below the previous quarter
average, with the amount of the difference.
2. Any payee that appears for the first time.
3. Any pair of identical amounts on the same date.
Do not explain tax treatment. Do not suggest changes to the categories.
An illustrative reply for a craft brewery supplier running as a sole trader might say that "Packaging" is 62% above its two-quarter average (£1,380 against £850), that a payee called "Sack Barrow Hire" is new, and that two payments of £96.00 appear on 3 September. Each one is a question for the owner: a bulk bottle order, a one-off hire, a duplicate card payment. The tool found them in seconds. Only you know which is true.
Writing a plain-English summary for yourself
Once the totals are confirmed, you can ask AI to turn them into a two-paragraph summary: income against the same quarter last year, the biggest expense categories, cash left in the account. That is useful for running a business. It is not part of the submission, and a summary that reads well can still be wrong, so give it only the checked totals and ask it to quote the numbers it uses.
Reading and filing receipts
Receipt-capture tools that read a photo and pull out supplier, date, amount and category are the most mature use of AI in bookkeeping. They fail on faded thermal paper, receipts with several items taxed differently, and handwriting. Keep the photo, because HMRC still expects you to hold the original records or copies, as well as the digital ones. The tutorial on receipt capture and bank categorisation covers setting this up.
The duties AI cannot take off you
This is the part no tool changes. Each item is something you, or an adviser you appoint, must do.
| Duty | Why a tool cannot do it |
|---|---|
| Signing up and authorising software | You sign in to your own HMRC account and grant the software permission. Nobody can do it on your behalf without your authority. |
| Choosing the update periods | The choice between standard and calendar periods must be made before the first update and then stays fixed for the year. |
| Deciding what is business and what is personal | Only you know that the van was used on a family trip. A tool sees a fuel payment. |
| Keeping the original records | The statements, invoices and receipts must exist and be kept. A summary is not a record. |
| Checking the figures before sending | HMRC says it is your responsibility to check that your digital records are accurate, including where a bank feed fills them in. |
| Sending the update, including a nil one | It goes from compatible software under your account, by the deadline. |
| Year-end adjustments and the tax return | After the fourth update you check whether adjustments are needed, then submit the return with your software. Accounting judgement and tax advice sit with you or an accountant. |
| Answering HMRC | Letters, queries and penalties go to you. |
The digital-link rule that a chatbot can break
One rule deserves its own warning because it is where a helpful AI workflow collides with the system. HMRC's guidance says that if you use more than one software product, the records must be digitally linked. Once a record has been created and sent in a quarterly update, you must not manually move it within your record-keeping software or to other software. The examples given include copying information by writing it out in another cell or in other software, and cut and paste or copy and paste.
That matters because the obvious chatbot routine is: export from the bank, paste into the chatbot, copy the answer back into a spreadsheet, and enter totals into the submitting software. A copy-and-paste step in the middle may be exactly the break the rule describes. The guidance allows linking by methods such as linked cells in spreadsheets, importing and exporting CSV or XML files, and automated or API transfers. I would not decide for you whether a particular chatbot routine counts as a break. Before you design the workflow around a chatbot, read HMRC's page on creating digital records, and ask your software provider how they expect AI-assisted records to be imported. If the answer is unclear, use AI inside your accounting software, where the data never leaves the digital chain, or use the chatbot for checking and summarising only, leaving the source records untouched.
Where AI goes wrong with a sole trader's money
These are the failure patterns to expect, each with its tell.
- Owner's drawings treated as expenses. A transfer to your personal account is not a business cost. Tell: a large round-number payment categorised as "other expenses".
- Refunds treated as income. Money back from a supplier normally reduces that expense. Tell: income in the quarter that matches an earlier purchase.
- Split purchases forced into one category. A supermarket shop with materials and lunch. Tell: a retailer's name with a mixed basket and no receipt.
- Payment-processor payouts counted as sales. The payout is net of fees. If you record the net figure, the fees disappear from your expenses and your income is understated. Tell: a payout that does not match the sales report.
- Invented context. The model "explains" a payment it cannot know about. Tell: a reason column that sounds certain about something only you could know.
- Silent changes. Rerunning the same prompt on the same data and getting a different category. Tell: totals that move when nothing in the data has.
A realistic slip the weekend before a deadline
A sole-trading online clothing seller leaves the quarter until the weekend before the deadline. She pastes three months of card and bank transactions into a chatbot, asks for category totals, and types the totals into her software. The chatbot treats a £1,200 supplier deposit as fully an expense, when the stock was not yet delivered and she pays the balance next quarter; it also puts a £300 transfer to her savings account under "bank charges".
Nothing looks wrong, because the totals are plausible. The mistakes surface two months later, when she runs the same export through her accounting software's bank rules and sees two categories £300 apart. Because every update shows the year so far, she can correct the records and the following update picks up the fix, but she has spent an evening untangling it that the check would have saved. The cure is dull: ask the tool to list low-confidence and non-business lines first, reconcile the category totals to the bank balance change, and keep a two-line note of anything you decided.
A reconciliation you can do in five minutes
Before sending, check the quarter's figures against the bank. Add every business income line and every business expense line, plus any non-business movements you excluded, and check that the net equals the change in the account balance over the period.
Opening balance (6 Apr): £4,210.00
+ Business income lines: £11,940.00
- Business expense lines: -£6,785.50
- Owner's drawings (not business): -£2,000.00
+ Transfers in from savings (not business): £500.00
= Expected closing balance (5 Jul): £7,864.50
Actual bank balance (5 Jul): £7,864.50 OK
Illustrative figures. If the totals do not tie, something is miscategorised, missing or duplicated, and the gap tells you roughly how large. For this to work the tool must not have merged or dropped any lines, which is why the prompt above forbids it. This check is also the best protection against a tool that confidently produces tidy totals.
Choosing where AI lives: chatbot or your accounting software
There are two sensible places for AI in this workflow, and they carry different risks.
- Inside your compatible software. Bank rules, receipt capture and categorisation suggestions sit next to your records. The data stays in the digital chain and the submission is one click away. The cost is the software subscription you may need anyway, and you must still review suggestions before accepting them. The comparison of Xero and QuickBooks AI features is a starting point, though check which products are approved for Making Tax Digital for Income Tax on HMRC's software list.
- In a general chatbot beside it. Flexible and often cheaper, good for checking, summarising and explaining. Weaker for the records themselves, because of the digital-link rule above and the data you must send out of your records. A side-by-side test of two chatbots on bank data shows how to compare them.
For most sole traders the cleanest split is: software for records and submission, chatbot for explanation and second-opinion checks, with nothing copied by hand from one to the other.
Data you should keep out of a chatbot
Bank data identifies you and the people you pay. Before pasting anything into a chatbot, remove account and sort numbers, your tax reference, your National Insurance number and customer names. Use a plan whose settings stop your conversations being used to train models, and read the provider's terms for how long chats are kept. If you are unsure, what to check in an AI tool's privacy policy gives the questions to ask. Nobody needs your HMRC sign-in details for any of this, and no AI tool should ever ask for them.
A monthly routine that keeps the quarter small
The less you leave to the last week, the less AI has to guess. A routine that works for a sole trader with moderate volume takes about 30 minutes a month.
- Week one of the month: export last month's transactions, run the categorisation prompt, accept the high-confidence lines, and resolve every "Needs my decision" line while you still remember the context.
- Photograph or forward any receipts missing from the month. A receipt you cannot find in November is a guess in February.
- Run the odd-items prompt against the previous quarters.
- Reconcile to the bank balance as shown above.
- Note anything you want to ask an adviser, such as a large equipment purchase.
By the time the update period closes, the update is a review of totals you already trust, and sending it takes minutes.
When to bring in a person
An accountant or bookkeeper is worth paying when your records are messy, when a year-end adjustment looks complicated, when you have both self-employment and property income, or when you simply want someone else to take the deadline off your list. HMRC allows agents to act for you once authorised. The tutorial on what AI bookkeeping still leaves to an accountant sets out where that line usually falls. None of this is tax advice: it describes where AI fits the process, the rules and thresholds belong to HMRC, and your own circumstances may differ.
Questions sole traders ask about AI and quarterly updates
Can ChatGPT or Claude send my quarterly update to HMRC?
No. Quarterly updates have to be sent from software that is compatible with Making Tax Digital for Income Tax and linked to your HMRC account. A general chatbot can help you sort and check the figures beforehand, but the submission comes from your recognised software, and you are the one who sends it.
Is it safe to upload my bank statement to a chatbot?
Only after you have checked the plan's data settings. Strip names, account numbers and anything unrelated to the business, and prefer a plan that does not train on your content by default. Accounting software with built-in AI keeps the data where it already lives, which avoids the question for most sole traders.
Do I still need to keep receipts and invoices?
Yes. HMRC says you must carry on keeping the records you would normally keep for Self Assessment, such as bank statements and invoices, as well as the digital records that feed your quarterly updates. A quarterly update sends category totals, not the documents, but the documents must still exist.
What if I send a quarterly update with a mistake in it?
Each update shows your income and expenses for the tax year so far, so corrections to your records flow into the next one. HMRC's guidance also covers resending the fourth update after the year ends. Check your software's help for the exact route, or ask an accountant if the error is large.
Do I have to be in Making Tax Digital at all?
It depends on your qualifying income, which is gross self-employment and property income, not profit. The threshold was over £50,000 from April 2026, drops to over £30,000 from April 2027 and over £20,000 from April 2028. Check the figures and your own letter on GOV.UK.
Further reads
- How to Categorise Transactions With AI and Check Its Work — How to categorise transactions with AI and check its work.
- Making Tax Digital With AI: Chase Quarterly Records From Clients — How a bookkeeper chases quarterly records, seen from the other side.
- AI Bookkeeping in the UK: What Works With MTD and VAT — Which AI bookkeeping tools work with the digital tax rules.
- AI Expense Management: Receipts, Mileage, and Approvals — Receipts, mileage and approvals with AI help.
- AI Bookkeeping Software vs a Human Bookkeeper: Accuracy and Cost — Accuracy and cost of AI against a human bookkeeper.
- Making Tax Digital for Landlords: Keep Rental Income Records With AI — The same duties for rental income records.
- QuickBooks or Xero for a Sole Trader: Which Plan Includes AI? — Plan-by-plan prices for Xero and QuickBooks for a self-employed sole trader, what AI each tier includes, and which fits common volumes.
- How to Use AI for Self-Employment Tax: A Monthly Set-Aside Sheet — A spreadsheet that turns income, expenses and your tax authority's published rates into one set-aside percentage, built and checked with AI.
- Eight Jobs a Sole Trader Can Hand to AI, With Cost and Checks — Eight admin jobs a one-person business can give to AI, each with the tool, its monthly cost and the check that stops mistakes.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: GOV.UK guidance on using Making Tax Digital for Income Tax (send quarterly updates; create digital records), GOV.UK guidance on who needs to use Making Tax Digital for Income Tax, accessed November 2026.