As of 13 August 2026, AI cannot apply the correct tax code to an employee.
This still needs a person who signs their name to it.
Can you do it?
15 minutesto a draft.
n/ait cannot be self-verified.
Cost, all in£0
Skill neededpower-user
Who has to check ita professional
What the alternative costsNo comparable human-service price is provided in the available data.
If this goes wrong, the employee can be taxed incorrectly and the employer must correct the payroll and deal with the consequences.
What to actually do
Hand it to a person
The route this page recommends
Someone with a licence or accountable authority has to sign this before it counts.
Use a tool built for this
Second choiceDo it yourself
The distant thirdA chat interface gets you a draft, but you cannot verify it yourself. That is the catch.
How to actually do it
- Open the employee's payroll record and gather the current tax code, pay frequency, employment start date and any recorded benefits or pension information.
- Open the employee's P45 or completed starter checklist and the latest HMRC coding notice, removing unnecessary personal data before sharing copies.
- Paste the documents and the payroll facts into the prompt, keeping the source of each fact labelled.
- Ask the chatbot to compare the current payroll code with the HMRC notice and produce the evidence and discrepancy table requested in the prompt.
- Check that every fact in the chatbot's table appears in the supplied documents and delete any conclusion based on an assumption or missing document.
- Send the flagged discrepancies and source documents to your payroll professional or contact HMRC through the appropriate employer route before changing the code.
- Apply the confirmed code in your payroll system, record the source and date of the confirmation, and retain the review for the payroll audit trail.
Prompt
You are helping an employer review a UK PAYE tax-code change. This is not professional advice. Do not make a final decision or invent any facts. Use only the documents and facts pasted below. Employee details: [employee name or reference, without unnecessary personal data] [employment start date] [pay frequency] [known benefits, pension arrangements or other relevant payroll facts] Documents and notices: [P45 or starter checklist] [current HMRC coding notice] [previous tax code] [latest payroll record] [any employee-provided explanation of a change] Produce a table with these columns: source, relevant fact, possible effect on the tax code, and missing information. Compare the current code with the supplied HMRC notice and identify any discrepancy. State clearly whether the documents support applying the code, whether the case must be held for clarification, or whether it must be referred to HMRC or a qualified payroll professional. Do not calculate tax, guess an emergency or standard code, infer facts from incomplete documents, or advise me to override an HMRC notice. List the exact evidence a payroll professional should check before any code is entered into payroll. If the documents conflict, identify the conflict and do not resolve it yourself.
Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.
What it gets wrong
- AI cannot establish that a tax code is the current authoritative instruction from HMRC.
- AI cannot resolve conflicting or incomplete employee information without a responsible payroll decision-maker.
- AI cannot take responsibility for PAYE errors, employee corrections or employer reporting obligations.
- AI cannot replace a payroll professional's judgement on unusual benefits, multiple employments or changes in circumstances.
- AI cannot safely turn a plausible code into an authorised payroll entry.
What makes this a NO: legal accountability, verification cost and regulated advice.
How we scored this
Five axes, each scored nought to two by hand: ten means AI carries the task cleanly, and the thresholds that turn a total into YES, PARTLY or NO are published in the methodology. Each axis name links to its definition.
| Axis | Score (0–2) |
|---|---|
| Output | 1 |
| Inputs | 1 |
| Verification | 0 |
| Liability | 0 |
| Effort delta | 1 |
| Total | 3 / 10 |
The methodology and its thresholds are published in full.
FAQ
- Can ChatGPT apply a tax code for me?
- No. It can compare a P45, starter checklist, HMRC coding notice and payroll record, but it cannot confirm the authoritative code or carry the employer's PAYE responsibility. This is not professional advice, so refer a serious or unclear case to a qualified payroll professional.
- Can AI check whether an employee's tax code is correct?
- It can perform a document comparison and flag differences or missing information. It cannot reliably verify the underlying tax treatment, so a payroll professional or HMRC must confirm an unclear result before you change payroll.
- What documents does AI need to review a tax code?
- Give it the current payroll code, the HMRC coding notice, the P45 or starter checklist, the employment start date, pay frequency and relevant payroll facts. Remove unnecessary personal data and treat the result as a review aid, not authority to apply a code.
- Who is responsible if the wrong tax code is used?
- The employer remains responsible for operating PAYE correctly and correcting errors in its payroll process. A chatbot does not take on that liability, so refer disputed or unusual cases to a qualified payroll professional.
Nearby answers
Assessed by gpt-5.6-luna (gpt-5.6-luna) on 2026-08-13, second-checked by an independent model. Wrong somewhere? Email [email protected] and it gets re-checked.
The newsletter
AI news, new answers and product picks, straight to your inbox.