You've just spotted it. The pension figure is wrong, the payroll code is off, or a self assessment line was entered from the wrong schedule, and now you're staring at a return that's already gone in. In the UK, that doesn't mean you file a separate “amended tax return” form and hope for the best. It means you use HMRC's correction route, and you use the right one first time.
The mistake many make is importing a US mental model into a UK system that doesn't work that way. HMRC expects online amendments for Self Assessment where possible, and payroll teams fix RTI data at source through FPS or EYU depending on the year and the error. Get the route wrong, and you create avoidable delay, extra admin, and messy records that don't reconcile later.
Why UK Tax Corrections Work Differently
A payroll lead notices a miscoded expense claim after year end. The instinct is to look for a neat “amended tax return” button, because that's how plenty of overseas guidance talks. In the UK, that instinct is half right and half wrong. HMRC's system is built around Self Assessment amendments for individuals, RTI corrections for payroll, and HMRC-led action where the department itself later identifies an issue.
The UK route is usually a correction, not a fresh filing
HMRC's online correction model is deliberately practical. For a Self Assessment return filed online, the normal move is to reopen the submitted return, change the figures, and resubmit inside the correction window. That's very different from a US-style formal amended return process, and it's why UK searchers often end up reading irrelevant material when they really need a filing workflow they can use today. HMRC's online-first design is also why the 12-month correction window matters so much in practice, because after it closes you're no longer in the normal amendment lane. freelancer MTD preparation guide
Different correction problems need different routes
If the issue sits in a personal tax return, you normally look at Self Assessment. If the issue sits in payroll reporting, you're in RTI territory, where the fix is made at source rather than by re-filing some mythical master return. If HMRC later raises a discovery issue, that's a different administrative world again, because the correction is no longer your voluntary amendment. That distinction matters because it stops HR and finance teams from trying to force every problem through the same channel.
Practical rule: if the mistake sits in the tax return you submitted, amend that return. If it sits in payroll data sent to HMRC, fix the RTI submission instead.
UK compliance works better when you route the error to the right process on the first attempt. That's the discipline HMRC's system rewards.
Knowing When an Amendment Is Actually Needed
Not every error justifies an amendment. Some figures are maths issues that HMRC may already have picked up, some are missing reliefs, and some are wrong data that needs correcting before the position becomes bigger than it needs to be. The worst habit is double-correcting a figure that HMRC has already adjusted, because then your records diverge from theirs for no good reason.
Start with the type of problem
A missed income item usually does need action. So does an omitted deduction, a wrong filing status equivalent in the UK context, or a tax liability figure that plainly doesn't match the underlying records. If the original return contained a simple transposition or calculation mistake, check whether HMRC has already processed a correction before you touch it again. The point is to correct the position, not to create a new mismatch.
The other trap is assuming every change must be handled by online amendment. That's not true. If the return is outside the online correction window, or if you're dealing with a route that HMRC expects to be handled by direct contact or additional information, using the online amendment path can waste time. The practical rule is blunt. Use the online amendment window for an online return filed inside the time limit, use the additional information route or write to HMRC when that window has closed, and don't force a payroll issue into Self Assessment just because it feels familiar.
A quick decision check
- Is the issue in a submitted Self Assessment return? If yes, amend the return if you're still inside the online window.
- Is the issue in payroll reporting? If yes, use the RTI correction route, not Self Assessment.
- Has HMRC already changed the figure? If yes, don't duplicate the correction unless you have clear evidence of a remaining error.
- Are you outside the online amendment window? If yes, use the additional information route or write to HMRC with the correction details.
If you want a practical example of how Self Assessment facts are usually handled in real filings, the examples of a Self Assessment page is a useful internal reference point.
Keep the evidence trail beside the return. If you can't show why the number changed, you're not finished.
That's the line I give teams again and again. Correct only what needs correcting, and make sure the new figure is defensible.
Correcting a Self Assessment Return Online
The online process is straightforward if you stay disciplined. HMRC expects you to log in to the Self Assessment account, open the submitted return, choose the amendment option, update the relevant entries, and resubmit. That sequence matters, because the amendment is built around the original filing, not around a separate duplicate return.
Only use the online route when the filing and timing both fit
HMRC's online correction route applies only if the original return was filed online and the correction is made within 12 months of the Self Assessment filing deadline. That's the point people miss. If you filed on paper, or if the 12-month window has gone, the online amendment screen isn't your route anymore. In practice, this means you need to check the filing method and the deadline before anyone touches the figures.
Once you're in the return, make only the entries that changed. Don't overwrite figures just because the screen is open. I've seen too many avoidable errors caused by someone scrolling through a return and “tidying” fields that were already right. If one item changes, recalculate the tax due from that change, then check the knock-on effect on the overall return before resubmitting.
What to do after you resubmit
After submission, review the updated calculation and keep a clean copy of the revised return with your working papers. HMRC also expects supporting records to be retained for at least 22 months after the end of the tax year for online returns, and longer where the records relate to self-employment, property, or partnership activity. That isn't admin for admin's sake. It's what protects you if HMRC later asks why the figures moved.
For teams that need to align payroll and tax records as well, the correction should be logged against the employee file or finance file immediately after submission. I'd treat the post-submission checklist as essential:
- Check the revised tax calculation and confirm it matches the supporting evidence.
- Save the corrected return copy with the working papers.
- Record who approved the change and when.
- Note any employee-facing impact if the revised figures change the tax outcome.
The correction is only done when the paper trail is done.
Handling RTI Corrections Through FPS and EYU
Payroll mistakes need their own lane. HMRC's RTI correction process is not a full amended return, and that's where a lot of employer teams go wrong. If the error is in current-year payroll data, you correct it with an additional Full Payment Submission (FPS). If the tax year is closed and the final FPS has already gone in, you use an Earlier Year Update (EYU) where that route applies.
Choose the correction channel by tax year, not by convenience
Payroll teams need to be firm. If the mistake sits in the current tax year, submit an additional FPS and correct the data at source. If the issue belongs to a previous tax year and the final declaration has already been filed, move to EYU where appropriate. Using the wrong channel is a classic operational error, especially when the issue spans a year-end boundary or someone assumes the latest payroll run can somehow repair a closed year on its own.
The reason HMRC cares about the source data is simple. Late or inaccurate RTI updates can affect employees' PAYE records, Class 1 NIC calculations, and year-end totals. That means a payroll typo isn't just a payroll typo. It can ripple into the employee's record and the totals you rely on later.
Reconcile before you resubmit
Don't fire an update into HMRC without checking the control totals. Reconcile the correction against payroll reports, confirm the gross pay, tax, and NIC figures, and make sure the corrected submission matches the payroll ledger. If the figures don't tie back, the mismatch will come back to bite you when employee records, P60 totals, or internal reconciliations fail to line up.
If you're mapping the wider payroll process in your organisation, the process of payroll reference is useful because RTI correction only works properly when the upstream data capture is clean.
The mistake I see most often is treating payroll correction as a clerical edit. It isn't. It's a compliance action.
Use FPS for in-year fixes. Use EYU for the closed year route where it applies. Reconcile first, submit second, and confirm the downstream records afterwards.
Deadlines, Penalties and Record Retention Rules
The UK correction timeline is a tight combination of deadline control and evidence control. HMRC allows online Self Assessment corrections inside the 12-month amendment window, but that's only part of the picture. You also need the records to prove the change later, because the right to amend is useless if nobody can show why the numbers moved.
One deadline governs the amendment, another governs the file
For online Self Assessment returns, keep the supporting records for at least 22 months after the end of the tax year. For self-employment, property, and partnership records, keep them longer. That longer retention is not optional in practice, because those records are the backbone of any correction discussion if HMRC asks questions later.
Penalties are where people become complacent and then regret it. A correction can reduce an error's impact, but it can also increase or trigger penalties if the original filing was wrong and HMRC treats the issue as more serious once corrected. That's why I always tell teams to fix the return promptly and document the reason at the same time. Delay rarely improves the outcome.
UK amendment deadlines and record retention at a glance
| Filing Route | Correction Window | Correction Method | Record Retention Period |
|---|---|---|---|
| Online Self Assessment return | 12 months from the Self Assessment filing deadline | Amend the submitted online return | At least 22 months after the end of the tax year for online returns |
| Self Assessment after the online window | Outside the online correction window | Use the additional information route or write to HMRC | Keep supporting records for the relevant tax activity, longer for self-employment, property, and partnerships |
| RTI payroll reporting | Depends on whether the year is current or closed | Additional FPS for current-year corrections, EYU for closed-year corrections | Retain payroll evidence long enough to support employee records and year-end totals |
The practical read-across is obvious. If your record retention schedule is shorter than your correction risk, your compliance process is too thin. The new tax year dates page is a sensible reference for teams that want their payroll calendar, filing windows, and review dates aligned.
Use the deadline to force the correction. Use the retention rule to protect the correction later. That's the framework.
Building a Practical Correction Workflow for HR and Payroll
Corrections go smoother when named people own them. In the teams I've worked with, the best results come from a simple chain. One person spots the issue, one person checks it, one person approves it, one person submits it, and one person confirms the downstream effect. Without that structure, amendment work drifts, and drift is where compliance problems start.
Build the process around evidence, not memory
Start with a correction request form. It should capture the error type, the tax year, the source record, the proposed fix, and the approval status. Then pair it with a payroll reconciliation checklist that shows the original value, the corrected value, and the document that supports the change. That gives you a clean audit trail instead of a thread of emails nobody wants to reconstruct later.
A short employee communication template also helps. When a correction affects pay, tax, or a statutory record, the employee should know what changed, why it changed, and whether they need to do anything. That keeps surprise to a minimum and stops preventable escalations to HR or payroll.
Use systems that reduce the need for corrections in the first place
This is where integrated HR and payroll data matters. If absence, onboarding, benefits, and personal data live in separate places, someone will eventually key a wrong figure into a tax return or RTI submission. Systems that keep employee data connected, including Hubdrive's HR Management for Microsoft Dynamics 365, reduce those handoff errors by keeping the core record tighter from the outset.
If you want another practical reference point for keeping self-employed data organised, the self employed accounting tools article is a useful comparison when you're thinking about record quality and control.
A correction workflow is only strong if the evidence lands before the submission, not after the mistake is discovered.
That is the standard I'd use in any UK organisation. Detection, verification, approval, submission, confirmation. Keep each stage visible, and corrections stop being panic work.
Common Mistakes and How to Avoid Them
The biggest myth is that a quick email to HMRC solves everything. It doesn't. If the error belongs in Self Assessment and you're inside the window, amend online. If it's payroll data, correct it through RTI. If the online window has closed, use the additional information route or write to HMRC with the correction details. Informal contact is not a substitute for the proper record.
Another mistake is assuming a paper amendment can always be filed once the online route is gone. That's the wrong assumption in the UK context. The system is built around online correction where possible, then structured follow-up where the online path no longer fits. A corrected PAYE record also does not magically update every employee tax code on its own, so payroll teams still need to confirm the downstream effect.
The habit that prevents repeat errors is boring, and that's exactly why it works. Reconcile control totals before resubmission, keep a correction log, and review year-end summaries before any final declaration goes out. Corrections are part of UK compliance. They're not a sign that the team has failed, they're a sign that the team is paying attention.
DynamicsHub helps UK organisations tighten the data flow between HR, payroll, and compliance, so corrections are easier to manage and less likely to happen in the first place. If you need a cleaner way to handle HMRC submissions, employee records, and Microsoft Dynamics 365 workflows, visit DynamicsHub or phone 01522 508096 today.
