HMRC AI Chatbot Tax Rules: What the New Powers Really Mean
Key Takeaways
- HMRC AI chatbot tax rules are proposed changes, not rules already in force: they would take effect on and after Royal Assent to Finance Bill 2026–27, and no commencement date had been confirmed as of 12 November 2026.
- The proposal does not create a new standalone power for HMRC to read private chatbot conversations. GOV.UK states that Section 114 of the Finance Act 2008 would continue to operate only as a supporting provision, applying where HMRC already has a lawful basis to require information under Schedule 36.
- What would change is how HMRC can obtain and understand digital information: the draft would modernise Section 114 so it reflects how tax information is now created, stored and processed using software, automated systems and cloud-based services, including information about how relevant tax figures have been produced.
- The draft legislation does not explicitly mention ChatGPT, Claude, Copilot or any other generative AI chatbot. The chatbot angle comes from how tax advisers and reporters have interpreted the broader wording, not from a chatbot-specific clause.
- Whoever files the return stays responsible for it. HMRC told Which? that customers "remain responsible for the accuracy of their tax return", including those who use AI, and should check it carefully before filing.
- A careless error can carry a penalty of 0% to 30% of the extra tax due, according to HMRC factsheet CC/FS7a, as reported by Nacionale on 11 November 2026. No tribunal has yet ruled on whether relying on a chatbot's figures counts as reasonable care.
- In January 2026, HMRC published separate guidelines for software developers using generative AI in tax products. Those guidelines warn about inaccurate answers, which HMRC calls "hallucinations", and say products should support, not replace, human judgement.
What Happened on 11 November 2026
On 11 November 2026, reporting about HMRC and AI chatbot conversations spread quickly in the UK, and the topic rose to the top of UK trending searches the following day. The reporting was summarised in headlines such as "New rule lets HMRC snoop on taxpayers' AI chat history", published by iNews on 11 November 2026. That framing — a tax authority reading private chats — is what made the story travel. It is also, on the evidence in the official documents, an overstatement of what has actually been proposed.
The underlying document is not new. The UK government published a policy paper, "Reforming information powers and modernising computer records law", on 13 July 2026, alongside draft legislation, and updated the paper on 3 November 2026. A technical consultation on the draft legislation closed on 7 September 2026. The 11 November reporting picked up the implications of that draft for people who use AI tools to work out tax figures, at a moment when the Finance Bill 2026–27 was in Parliament and the Budget on 28 October 2026 had confirmed the reforms.
That timing matters. The story is not that HMRC announced a chatbot surveillance programme on 11 November. It is that a months-old modernisation of information powers, written in general language about digital records, was read — by tax advisers, campaigners and reporters — as potentially covering the records left behind when a taxpayer uses an AI chatbot or automated tax software to produce a figure. HMRC pushed back on the broadest reading the same day. An HMRC spokesperson said, in comments reported on 11 November: "This is about updating our existing information powers to reflect how tax information is now stored and processed digitally. It is not about going through everyone's use of large language models. We can only request information where we already have a lawful basis to do so."
Readers searching for hmrc ai chatbot tax rules therefore need two things at once: what the draft actually says, and what it does not say. This article sticks to that distinction throughout, and attributes every figure and quotation to its source.
What HMRC Actually Proposed
The GOV.UK policy paper describes a package of reforms to HMRC's civil information and inspection powers under Schedule 36 of the Finance Act 2008, and to Section 114 of the same Act, which deals with computer records. The paper's general description is worth quoting in full, because it is the anchor for everything that follows:
"Updating s114 so that it works effectively in a modern, digital tax system and reflects the way tax information is now created, stored and processed using software, automated systems and cloud-based services. The changes enable HMRC, where it already has the legal right to request information, to obtain and understand relevant information held within digital systems."
The paper adds that this includes "information about how relevant tax figures have been produced including where they are generated using software or automated processes to support more accurate tax reporting and strengthen compliance."
That sentence is the heart of the chatbot debate. If a tax figure was produced by software or an automated process, HMRC wants to be able to understand how it was produced — not merely to receive the final number. A chatbot conversation that was used to work out a figure could, in principle, be part of that trail. But the paper does not say that it will be, in every case or even in most cases. It says the power would be used where HMRC already has the legal right to request information, and that existing safeguards — including the condition that information or documents are reasonably required to check a tax position — would continue to apply.
The paper is explicit on the point that has been most often lost in the headlines: "These changes do not create a new standalone information power. Section 114 will continue to operate only as a supporting provision, applying where HMRC already has a lawful basis to require information under Schedule 36."
The background: a consultation that began in 2023
The reforms did not appear out of nowhere. According to the GOV.UK paper, HMRC launched a Call for Evidence on updating its information and inspection legislative powers in 2023, alongside engagement with stakeholders including software providers and industry representatives. It asked about the wording of Section 114 and the principle of extending HMRC's powers to allow for investigation of commercial taxation software. Some respondents, while not objecting to sharing how tax software information produces a tax calculation, raised considerations around the mechanism, including issues relating to intellectual property. That led to further policy development and the announcement at Tax Update 2026 of a consultation on the draft legislation.
Draft legislation for the measure was published at Legislation Day 2026 for a technical consultation. The consultation closed on 7 September 2026. The policy paper was first published on 13 July 2026 and updated on 3 November 2026, when revised information about the number of businesses affected was added, according to analysis of the paper published on 9 November 2026.
The Budget on 28 October 2026 confirmed the direction. Budget 2026 documents confirm plans to update civil information and inspection powers under Schedule 36 and computer-record provisions under Section 114, as summarised in reporting on the measure. The same Budget announced investment in additional HMRC compliance officers — 670 more, building on previous commitments to recruit 5,500 by 2029–30, according to a Budget note summarised on 29 October 2026 — although that staffing figure is a separate announcement from the information-powers legislation itself.
Section 114 and Schedule 36, Explained in Plain English
To understand what could change, it helps to separate the two pieces of law involved.
Schedule 36 of the Finance Act 2008 is the framework under which HMRC can issue information notices. In plain terms, it is the route by which HMRC can require a taxpayer, or in defined circumstances a third party, to provide information or documents that are reasonably required to check a tax position or collect a tax debt. That power already exists. It is subject to conditions, approvals and appeal rights, and a notice can be challenged where it goes beyond what the law allows.
Section 114 of the Finance Act 2008 is a supporting provision about computer records. It deals with references to documents, including those held in electronic form, in any statutory provision relating to an HMRC matter that requires production or inspection of documents. Its current wording still reflects an older picture of computing: references to a computer and associated apparatus or material. The draft legislation would retitle the section "Digital information" and replace that older language with broader wording, including substituting "anything" for "any computer and any associated apparatus or material" in one place, and "thing with which subsection (3) is concerned" for "computer" in another, according to the accessible version of the draft legislation on GOV.UK.
The practical effect, as GOV.UK explains it, is that where a notice under Schedule 36 is issued to a third party or intermediary, the requirement may extend to relevant information held or managed by that third party or intermediary in digital or electronic form, "including whatever is needed to understand how relevant tax figures have been produced."
That is a deliberately general formulation. It is written to cover cloud accounting, automated bookkeeping, tax software and other digital systems, not one named product. That generality is exactly why it has been read as potentially covering AI chatbot histories: a chatbot conversation is digital information, and if it was used to produce a tax figure, it could be relevant to understanding how that figure was produced. But generality cuts both ways. Because the draft does not name chatbots, it also does not define which chatbot records, if any, would be in scope, how far back a request could go, or how HMRC would distinguish a conversation that produced a figure from an unrelated chat in the same account. Those questions are not answered in the policy paper, and they are a reason to treat confident claims in either direction — "HMRC will read all your chats" or "HMRC will never ask for a chat" — with caution.
Can HMRC Read Your ChatGPT Chats?
The short answer, on the documents available as of 12 November 2026, is: not routinely, not without a lawful basis, and not under a new chatbot-specific power.
The longer answer has four parts.
First, HMRC must already have a lawful basis. The GOV.UK paper repeats this in several places. The Section 114 changes "enable HMRC, where it already has the legal right to request information, to obtain and understand relevant information held within digital systems." A Schedule 36 notice must be reasonably required to check a person's tax position. That is a test, not a blank cheque, and notices can be challenged where they exceed it.
Second, the approach to third parties is staged. GOV.UK states that the approach to examining software "would continue to be on a voluntary basis first", and that only when an approach to a taxpayer fails is a third party approached for information or documents. In other words, the route to a software provider's records is not the first step; it follows a failed approach to the taxpayer. That does not remove the concern — a taxpayer who cannot or will not provide the information could still see HMRC go to the provider — but it does contradict the idea of HMRC routinely sweeping providers' systems.
Third, the draft does not explicitly mention ChatGPT, Claude, Copilot or other generative AI chatbots. That point was made in reporting on 11 and 12 November 2026, and it is confirmed by the draft legislation's accessible version, which speaks in terms of digital information and "relevant things" rather than named products. The phrase "relevant thing" in the draft covers digital systems containing information HMRC is legally entitled to request, according to that reporting, but it is a general legal concept, not a chatbot power.
Fourth, HMRC itself has denied the broadest reading. The spokesperson's statement quoted above — "It is not about going through everyone's use of large language models" — was reported by iNews on 11 November 2026 and repeated in other coverage the same day. A separate report of the same statement put it as: "We can only request information where we already have a lawful basis to do so."
None of that settles the privacy debate. The TaxPayers' Alliance warned that the change would be an invasion of privacy, according to iNews reporting on 11 November 2026, and tax professionals have raised concerns about how far the new wording could reach in practice. The concern is not fanciful: once a power is written in general terms, its scope in practice depends on how HMRC uses it, how tribunals interpret it, and what guidance HMRC publishes alongside commencement. GOV.UK says "any necessary updates to guidance will be made in due course and published alongside the commencement of the measure." Until that guidance exists, the practical boundary is genuinely uncertain.
What can be said with confidence is what the proposal is not. It is not a ban on using ChatGPT or other AI platforms for tax purposes. The legislation does not prohibit taxpayers from using those tools. It is not a live power today. It is not a power to monitor everyone's AI use. And it is not, on the face of the draft, a power to demand a person's entire chatbot history. A request would need to be tied to a tax check, reasonably required for that check, and made under the existing Schedule 36 framework.
What about the £300 and £3,000 figures?
Some reporting on 11 November 2026 said that people who fail to respond to HMRC information requests could face an initial fine of £300, rising to £3,000 for people who do not report inaccuracies. Those figures were not in the GOV.UK policy paper summary reviewed for this article, and they should not be treated as a settled statement of what the new measure itself imposes. Schedule 36 already carries penalties for failure to comply with an information notice, but the amounts and conditions depend on the specific notice and circumstances. This article does not present the £300 and £3,000 figures as verified facts about the new proposals, because they could not be verified against the official paper. If a reader sees them quoted elsewhere, they should check whether the source is describing the existing Schedule 36 penalty regime, the new measure, or a conflation of the two.
What Else Is in the Package
The chatbot question has dominated the headlines, but it is only one part of the measure. The GOV.UK paper lists several other reforms, and they help to put the Section 114 change in context. The package is a modernisation of an information-gathering framework, not a single chatbot clause.
- Financial Institution Notices and cryptoassets. The scope of the Financial Institution Notice would be expanded to capture cryptoasset service providers, and payment service providers that facilitate payments in connection with those services. The number of businesses affected by the Financial Institution Notice changes is expected to be fewer than 100, according to GOV.UK, and most notices to date have tended to go to larger and more established institutions.
- Deceased persons. Currently, an information notice given to check the tax position of a person who has died cannot be issued more than four years after the person's death. That limit would be lifted, subject to tribunal approval for all notices except Financial Institution Notices, where an HMRC authorised officer's approval is required under the current process. GOV.UK says the change is needed to bring the UK in line with international standards and to help the UK continue to meet them.
- Identification notices. Updates would allow any HMRC officer to issue an identification notice, while an authorised officer would continue to approve it. The identifying information that can be requested would be extended to include other unique identifiers such as National Insurance numbers and email addresses.
- Annual reporting. The statutory requirement to produce the annual Parliamentary report on HMRC's use of the Financial Institution Notice power, under Section 126(5) to (8) of the Finance Act 2021, would be repealed. HMRC says it will continue to publish Financial Institution Notice data for transparency and scrutiny.
The paper also states that the measure is not expected to have an Exchequer impact — the table for 2025–26 to 2030–31 shows "Nil" for each year from 2026–27 onwards — and is not expected to have significant macroeconomic impacts. The administrative impact on business is described as negligible overall, with one-off familiarisation costs and possible ongoing costs for some third parties in responding to notices.
That context matters for two reasons. First, it shows that the government's stated purpose is framed in terms of keeping existing powers workable as records move into cloud systems and automated software, tackling evasion and avoidance, and meeting international exchange-of-information standards. The OECD is cited as a driver for part of the Schedule 36 changes. Second, it shows that the chatbot implication is a consequence of general wording, not the stated purpose. The paper's policy objective is to ensure HMRC "continues to have access to the information it needs, in a timely manner to support domestic compliance checks", to drive casework efficiency, to make sure the correct amount of tax is collected, and to tackle evasion and avoidance. Whether that objective justifies the breadth of the wording is a policy question, and it is the question campaigners and advisers are now debating.
You Still Own the Return: Reasonable Care and Penalties
Separate from whether HMRC can ask for a chatbot conversation is the question of what happens if the chatbot gets the tax wrong. Here the position is clearer, and it is less favourable to the taxpayer than many users assume.
HMRC told Which? that customers "remain responsible for the accuracy of their tax return", including those who use AI, and that they should check it carefully before filing. That statement was reported by Nacionale on 11 November 2026, and it is consistent with HMRC's long-standing position on agents: using someone — or something — else to prepare a return does not move responsibility off the person who files it.
The test HMRC applies is reasonable care. HMRC does not charge a penalty for an error if the taxpayer took reasonable care to get things right, according to HMRC factsheet CC/FS7a, as summarised by Nacionale. An error is "careless" when the taxpayer failed to take that care. There is no fixed checklist. HMRC's Compliance Handbook says reasonable care depends on the person's abilities and circumstances, and that bigger, more complex matters call for more care than simple ones. When dealing with something unfamiliar, HMRC expects the taxpayer to find out the correct treatment or seek appropriate advice, and if still unsure, to point out the entry and the uncertainty when filing.
Neither the factsheet nor the handbook mentions AI chatbots. That absence is important. It means there is no HMRC rule that says "relying on ChatGPT counts as reasonable care" or "relying on ChatGPT never counts". Nacionale reported that it found no tribunal decision on whether relying on a chatbot's figures counts as reasonable care, so there is no ruling yet. The answer, for now, has to be inferred from how HMRC treats reliance on other people: in one of HMRC's own worked examples of careless errors, a man whose agent prepared his return was judged at least careless because he did not ask how the figures arose or check the return himself. Paying for help did not change that. The factsheet says the same about anyone acting for the taxpayer: the taxpayer must do everything they reasonably can to prevent mistakes.
The penalties, as set out in factsheet CC/FS7a and summarised by Nacionale, are a percentage of the extra tax due, on top of the tax itself:
| Behaviour | Penalty if the taxpayer tells HMRC first | Penalty if HMRC finds the error first |
|---|---|---|
| Reasonable care taken | No penalty | No penalty |
| Careless | 0% to 30% | 15% to 30% |
| Deliberate | 20% to 70% | 35% to 70% |
| Deliberate and concealed | 30% to 100% | 50% to 100% |
Within those ranges, HMRC reduces the penalty for telling it about the error, helping it work out the correct figure, and giving access to records. If a taxpayer sent a return they believed was correct and later spots a careless error, HMRC may cut the penalty to nil, but only if the taxpayer tells HMRC before HMRC has found the error. Careless penalties are the only kind HMRC can suspend, for up to two years, if it can set conditions the taxpayer is likely to meet.
The Harber case: AI-generated cases that did not exist
The best-known UK example of AI going wrong in a tax context did not involve a tax return itself. In Harber v HMRC, a taxpayer appealed a £3,265 penalty for failing to tell HMRC about capital gains tax due on a property sale, Legal Futures reported in December 2023. She cited nine earlier tribunal decisions that nobody could find. The First-tier Tribunal found they had been generated by an AI system such as ChatGPT.
The tribunal accepted she had not known the cases were fake, Simmons & Simmons noted, but it still found she had no reasonable excuse and upheld the penalty. According to Legal Futures, the tribunal found her mental health would not have stopped a reasonable person in her position from contacting HMRC, and that not knowing about the rule was not objectively reasonable.
Harber is not a ruling on chatbot tax calculations. It is a ruling on fabricated case law in a tribunal appeal. But it illustrates the pattern HMRC and the tribunals have followed so far: the fact that an AI system produced the material does not, by itself, excuse the person who relied on it. That pattern is the reason tax advisers are warning users not to treat a confident chatbot answer as a safe harbour.
The same caution applies to hallucinations in tax software. HMRC's January 2026 guidelines for developers, discussed below, use the word "hallucinations" for inaccurate answers produced by generative AI. The risk is not only that a chatbot invents a figure; it is that it invents a figure fluently, with a plausible explanation, and the user has no easy way to tell.
HMRC's January 2026 Guidelines for AI Tax Software
The November debate is often presented as if HMRC had only just noticed AI. In fact, HMRC published guidance on generative AI in tax products in January 2026, months before the draft information-powers legislation.
The guidance, "Guidelines for using generative artificial intelligence if you're a software developer", is addressed to developers who build commercial software products using generative AI to help customers with their taxes, such as submitting information to HMRC. It sets out HMRC's expectations for what good use of generative AI looks like in those products. It does not mention general-purpose chatbots such as ChatGPT, and Nacionale's reading is that it is aimed at tax products, not at those tools. That distinction should be kept in mind: the January guidelines are about products built for tax, while the November debate is about general-purpose chatbots used for tax.
HMRC says in the guidance that it recognises the opportunities generative AI offers software developers and encourages innovative use of AI in tax software products. At the same time, it expects products that use generative AI to be transparent, reliable, subject to human control, and designed with strong data-security and privacy measures. Users should be able to identify the source data used, and be aware of the possibilities of bias and inaccuracies — an example of the latter being called "hallucinations", where the generative AI system produces information that appears to make sense but is factually incorrect or made up.
On reliable source data, HMRC expects any software enhanced by generative AI to use data sources that are high quality and reliable, including up-to-date HMRC guidance, legislation and case law. The Institute of Chartered Accountants in England and Wales, summarising the guidance on 29 January 2026, put the three expectations as transparency, reliability, and human control: developers should ensure users know the software is enhanced by generative AI and understand its capabilities and limitations; software that supports the production of tax returns should use reliable source data; and the software should prompt users to check results, particularly in areas involving nuanced tax rules, complex scenarios or specific guidance, and remind them it is their responsibility to make sure their tax returns are accurate. HMRC's formulation, as quoted by ICAEW, is that the software "should support, not replace, human judgment".
In the same month, the seven professional bodies responsible for Professional Conduct in Relation to Taxation published joint guidance on the ethical use of AI in tax work. That guidance, published in January 2026, states that AI outputs must not be used as authoritative tax or legal advice, and that professional judgement, due care and verification remain the responsibility of the adviser. Members are ultimately responsible for any work they, their staff and others under their supervision produce, irrespective of the use of AI tools in its creation.
Taken together, the January guidance and the November proposals point in the same direction, but they do different things. The January guidance tells developers what good looks like. The November proposals would give HMRC a clearer route to ask how a figure was produced, where it already has a lawful basis to ask. Neither tells an individual taxpayer that a chatbot answer is safe to file unchecked.
Making Tax Digital: The Other HMRC Deadline in the Same Week
The chatbot story arrived in the same week as a separate HMRC deadline that affected many of the same taxpayers. Sole traders and landlords with qualifying income above £50,000 had to send their second Making Tax Digital for Income Tax quarterly update to HMRC by Saturday 7 November 2026. Making Tax Digital for Income Tax became mandatory from 6 April 2026 for sole traders and landlords whose income from self-employment and property is above £50,000.
HMRC set out five common misunderstandings ahead of the deadline. A quarterly update is a short summary of income and expenses sent through compatible software, with no tax calculation and no payment due; overall tax is calculated only when the return for the 2026 to 2027 tax year is submitted. People do not need to contact HMRC to check that an update was received; submission history can be checked in an HMRC online account or through the software. Only specialist accounting software is not required; recognised options range from products built for sole traders and landlords to more advanced packages, and some are free. The second update, for those using standard update periods, covers 6 April to 5 October and was due by 7 November; the third update is due by 7 February 2027 and the fourth by 7 May 2027, according to HMRC's timeline as reported on 3 November 2026. HMRC said it would not apply penalty points for late quarterly updates during the 2026 to 2027 tax year.
The Making Tax Digital deadline is not part of the chatbot proposals, but it explains why the chatbot story landed with such force. Many sole traders and landlords were already using software, and in some cases AI tools, to assemble quarterly figures in early November. A proposal that HMRC could ask how those figures were produced felt immediate, not theoretical. It also explains why the distinction between a quarterly update and a tax return mattered: an update is a summary, not a calculation, and no tax is due when it is sent. A chatbot that offers to calculate the tax due on a quarterly update is offering something the update does not require.
What to Do Now: A Practical Checklist
This article is not tax advice, and it does not replace advice from a qualified adviser. The steps below are drawn from HMRC's own guidance and from the reporting cited in this article. They are practical habits, not legal guarantees.
Use a chatbot to learn, not to file. A chatbot can be useful for explaining unfamiliar tax terminology, organising financial information, and helping a taxpayer understand complicated rules. That is how tax advisers quoted in the 11 November reporting described the legitimate use. The risk begins when the chatbot's output is copied into a return without checking it against the taxpayer's own records and against HMRC guidance.
Check every figure against your own records. Payslips, P60s, bank statements and invoices are the source of truth for a return. HMRC expects taxpayers to keep enough records to make a correct and complete return. If a chatbot figure does not match those records, the records win, and the discrepancy should be investigated before filing.
Keep personal details out of chatbots. Which? advises against entering a National Insurance number or full bank details into a chatbot, and advises checking each service's terms on how chats are stored. That advice matters twice over in the current debate: once for privacy, and once because a chat that contains personal details and tax figures is a record that could, in principle, become relevant to a check.
Keep the trail. If an AI tool was used to work out a figure, keep a note of what was asked, what was produced, and what was checked. That does not guarantee that HMRC will accept the figure, and it does not create a reasonable-care defence by itself. But it does make it possible to explain, months later, how a figure was arrived at — and to correct it quickly if it was wrong.
Note uncertainty on the return. HMRC's Compliance Handbook expects a taxpayer who is unsure about an entry to point out the entry and the uncertainty when filing, or to seek appropriate advice. Hiding uncertainty is worse than disclosing it.
If a mistake is found, correct it promptly. A Self Assessment return can be amended within 12 months of the filing deadline, so changes to a 2024 to 2025 return usually have to be made by 31 January 2027, according to Nacionale. After that, the taxpayer writes to HMRC. Telling HMRC before it finds the error is the route to the lowest penalty band, and in some careless-error cases to no penalty at all.
Do not assume a chatbot conversation is private from HMRC in a check. The proposal does not give HMRC routine access, but it would, if enacted, make it easier for HMRC to obtain relevant digital information where it already has a lawful basis. A taxpayer who is already subject to a check should assume that any record used to produce a figure could be asked for, and should seek advice before responding to a notice.
For software providers and advisers, read the January guidance. The HMRC developer guidelines and the PCRT guidance are the closest thing to a standard that exists today. They expect reliable source data, transparency about AI use, human oversight, and a reminder that the user remains responsible for accuracy.
HMRC AI Chatbot Tax Rules: Myths Versus What the Documents Say
Much of the confusion around this story comes from headlines that compress a conditional, future, general power into a present, specific one. The table below separates the claims that are circulating from what the documents reviewed for this article actually support.
| Claim | What the documents support |
|---|---|
| HMRC can now read all ChatGPT chats | Not supported. The proposals are not yet in force, and GOV.UK states they do not create a new standalone information power. |
| HMRC will routinely monitor AI use | Not supported. HMRC said it is "not about going through everyone's use of large language models", and a lawful basis is required. |
| The draft names ChatGPT, Claude and Copilot | Not supported. The draft legislation does not explicitly mention those products. The chatbot reading is an interpretation of general wording about digital information. |
| HMRC could ask how a tax figure was produced | Supported, in principle. GOV.UK states the changes would enable HMRC, where it already has the legal right, to obtain information about how relevant tax figures have been produced, including where they are generated using software or automated processes. |
| The taxpayer stays responsible if AI gets it wrong | Supported. HMRC told Which? that customers remain responsible for the accuracy of their tax return, including those who use AI. |
| Using AI is now banned for tax | Not supported. The legislation does not prohibit taxpayers from using ChatGPT or other AI platforms for tax-related purposes. |
| A chatbot answer counts as reasonable care | Unresolved. No tribunal has yet ruled on whether relying on a chatbot's figures counts as reasonable care, according to Nacionale. |
| The changes take effect in 2027 | Plausible but not confirmed. The measure would have effect on and after Royal Assent to Finance Bill 2026–27, and reporting has said the timetable points to 2027 if the Bill is passed in the usual way. No exact commencement date had been confirmed as of 12 November 2026. |
The pattern in that table is the pattern of the whole story: the direction of travel is real, the scope in practice is not yet fixed, and the most alarming version is not what the paper says.
For readers who want background on why AI-generated material is so risky in formal proceedings, aiera.blog's guide to AI hallucinations in legal filings sets out the verification problem in detail, including how fabricated citations have already caused trouble in tribunals. The same verification habit — checking every citation and figure against a primary source — is the habit that matters for a tax return. Choosing between general-purpose chatbots is a separate question, and aiera.blog's comparison of ChatGPT, Claude and Gemini explains how the three systems differ in ways that affect what they are good for. And for a sense of how chatbot regulation is developing elsewhere, aiera.blog's report on the New York AI chatbot law for children shows a different legislature taking a different approach — direct rules for chatbot design, rather than a general information power.
What to Watch Next
Three dates and documents will determine how this story develops.
First, the passage of Finance Bill 2026–27. The measure will have effect on and after Royal Assent, and until the Bill passes, nothing in the proposal is law. Parliamentary debate may amend the wording, narrow it, or leave it as drafted. The Bill's progress is the single most important thing to follow.
Second, the guidance HMRC publishes alongside commencement. GOV.UK says updates to guidance will be made in due course and published alongside commencement. That guidance is where the practical questions — which records, how far back, what format, what safeguards — are most likely to be answered. Until it exists, advisers' interpretations will fill the gap, and they will differ.
Third, the first cases. If HMRC does ask for AI-related records under the new wording, the first tribunal decisions on whether a request was reasonably required, and on whether reliance on a chatbot counted as reasonable care, will set the practical boundary. Nacionale found no such decision as of 11 November 2026. That absence is itself a fact worth remembering: the law in this area is being written in policy papers and draft clauses, not yet in case law.
Other developments to watch include whether HMRC publishes more about how it will handle software providers' intellectual property — an issue raised in the 2023 Call for Evidence — and whether the Financial Institution Notice expansion to cryptoasset service providers draws separate debate. Both are part of the same measure, and both could affect taxpayers who never use a chatbot at all.
Frequently Asked Questions
Does the proposal mean HMRC will ask for my ChatGPT history?
Not as a routine matter, on the evidence available. HMRC would need a lawful basis under Schedule 36, the information would need to be reasonably required to check a tax position, and the Section 114 changes would operate only as a supporting provision. A taxpayer who is not subject to a check has no reason, on the current documents, to expect a request. A taxpayer who is subject to a check, and who used a chatbot to produce a figure under enquiry, should seek advice and assume the conversation could be relevant.
Can I still use ChatGPT to help with my tax return?
Yes. Nothing in the proposal prohibits using ChatGPT, Claude, Copilot or any other AI tool for tax purposes. The risk is not in using the tool; it is in filing its output unchecked. HMRC's position, as told to Which?, is that the filer remains responsible for accuracy.
What if I already filed a return based on a chatbot answer?
Check it against your records and HMRC guidance now. If you find a mistake, correct it. A return can generally be amended within 12 months of the filing deadline, and telling HMRC before it finds an error is the route to the lowest penalty. If the position is complex, seek advice from a qualified adviser before amending.
Does deleting my chatbot history protect me?
This article does not advise deleting records, and deleting records after a check has begun could create separate problems. The GOV.UK paper states that individuals will only be required to provide information if they have it in their power and possession, and that existing safeguards will continue to apply. Anyone facing a notice should take professional advice on what must be preserved and produced, rather than acting on a headline.
Is this the same as Making Tax Digital?
No. Making Tax Digital for Income Tax is a separate requirement to keep digital records and send quarterly updates through compatible software. It became mandatory from 6 April 2026 for sole traders and landlords above the £50,000 threshold. The information-powers proposals are about HMRC's ability to request information in a check, not about how often a taxpayer must report.
Where can I read the official documents?
The primary sources for this article are the GOV.UK policy paper, "Reforming civil tax information and inspection powers (Schedule 36 Finance Act 2008) and modernising the definitions about computer records (s114 Finance Act 2008)", and HMRC's "Guidelines for using generative artificial intelligence if you're a software developer". Reporting that informed this article includes Nacionale's "AI tax errors: careless mistakes can cost 30% extra" (11 November 2026) and the Londoner News report "HMRC AI Chatbot Tax Rules: Can HMRC Read ChatGPT Chats?". The iNews report of 11 November 2026, "New rule lets HMRC snoop on taxpayers' AI chat history", is the reporting that brought the story to wide attention; the HMRC spokesperson quotation in this article is as reported there and in subsequent coverage.
The Bottom Line
The hmrc ai chatbot tax rules story is a story about a gap between what a law says and what people fear it could mean. The law, as drafted, modernises the language of computer records so that HMRC can obtain and understand digital information where it already has a lawful basis to ask. The fear is that "digital information" is broad enough to include a private chatbot conversation, and that HMRC will use it that way. HMRC denies that it intends to go through everyone's use of large language models. Tax advisers and campaigners are not reassured, because the wording does not, on its face, rule out the narrower version of the fear: a targeted request, in a live check, for a conversation that produced a figure under enquiry.
That narrower version is the one taxpayers should prepare for. It does not require panic, and it does not require abandoning AI tools. It requires the habits that HMRC has been asking for all along: keep records, check figures against those records, do not put sensitive personal details into a chatbot, note uncertainty, and correct mistakes promptly. Those habits protect a taxpayer whether or not the Finance Bill passes in its current form, and whether or not HMRC ever asks for a chat.
The most important sentence in the GOV.UK paper, for an ordinary taxpayer, may be the least dramatic one: "These changes do not create a new standalone information power." The most important sentence from HMRC, for the same taxpayer, may be the one told to Which?: the filer remains responsible for the accuracy of the return, including where AI was used. Between those two sentences lies the whole of the current position — a power that is broader in form, narrower in its stated limits, not yet in force, and still waiting for the guidance and the first cases that will show what it means in practice.
This article is for general information only and is not tax advice. Tax rules change, and individual circumstances differ. For advice on a specific tax position, consult a qualified tax adviser or HMRC guidance.
Sources
- GOV.UK, "Reforming civil tax information and inspection powers (Schedule 36 Finance Act 2008) and modernising the definitions about computer records (s114 Finance Act 2008)", policy paper first published 13 July 2026, updated 3 November 2026.
- GOV.UK, "Guidelines for using generative artificial intelligence if you're a software developer", HMRC guidance, January 2026.
- GOV.UK, "Reforming information powers and modernising computer records law", policy paper collection, published 13 July 2026, updated 3 November 2026; draft legislation (accessible version).
- Nacionale, "AI tax errors: careless mistakes can cost 30% extra", 11 November 2026.
- Londoner News, "HMRC AI Chatbot Tax Rules: Can HMRC Read ChatGPT Chats?", 11–12 November 2026.
- iNews, "New rule lets HMRC snoop on taxpayers' AI chat history", 11 November 2026, as reported in subsequent coverage.
- ICAEW, "HMRC sets expectations for AI in tax software", 29 January 2026.
- AccountingWEB, "New guidance sets out ethics for AI use in tax", 30 January 2026; "Managing AI Tax Risks: Resources and Training".
- ABC Money, "Sole traders and landlords face 7 November Making Tax Digital update deadline: five myths", 3 November 2026.