
Fixing payroll mistakes after you send an FPS is usually straightforward: if the error is in the current tax year, you correct it in your next regular pay run, and the next Full Payment Submission carries the right year-to-date totals to HMRC. Only mistakes in an earlier tax year need a separate correction. What causes real problems is fixing the same error twice, or quietly changing a payslip without updating the figures HMRC holds.
Key takeaways
- Current year errors are corrected through the next regular FPS using year-to-date figures.
- Earlier year errors need an additional FPS or, for older years, an Earlier Year Update.
- Overpayments can generally be recovered, but agree the plan with the employee.
- Pay any extra tax and National Insurance with your next payment to HMRC.
- Keep a short note of every correction and why it was made.
What is a Full Payment Submission?
A Full Payment Submission, or FPS, is the report your payroll software sends to HMRC on or before each payday under Real Time Information. It lists what each employee was paid in that period and their running totals for the tax year so far: pay, tax, National Insurance, student loan and pension deductions. Because each FPS restates the year-to-date figures, a later FPS can overwrite an earlier mistake. Our guide to payslips and RTI covers the reporting cycle in more detail.
Which fix applies to your mistake?
| Mistake | Spotted in the same tax year | Spotted after 5 April |
|---|---|---|
| Employee underpaid | Pay the difference in the next pay run; next FPS shows correct totals | Pay the difference now; correct the old year’s figures if they were wrong |
| Employee overpaid | Agree recovery; correct year-to-date figures in the next FPS | Agree recovery; send an earlier year correction |
| Wrong tax code used | Apply the correct code from the next pay run | HMRC usually adjusts through the employee’s tax code or a calculation |
| Payment left off an FPS | Include it, with correct totals, in the next FPS | Send an earlier year correction |
| Wrong figures on an EPS (for example statutory pay recovered) | Send a corrected EPS with the right year-to-date figures | Follow HMRC’s earlier year EPS guidance |
HMRC’s page on fixing problems with running payroll sets out the method for each tax year, including which earlier years use an additional FPS and which still use an Earlier Year Update. Check it before correcting anything from a previous year, as the route depends on the year.
Worked example: a double-counted overtime payment
Illustrative example. “Harbour Street Bakery Ltd” is an invented employer paying staff monthly. All figures are made up.
- In October 2026 (month 7), the owner enters 20 hours of overtime twice for one baker. The baker is paid £2,300 gross instead of £2,100, and the October FPS goes to HMRC with year-to-date pay £200 too high.
- The baker spots the larger payment and mentions it. The owner checks the timesheet, confirms a £200 gross overpayment and explains it in writing.
- They agree to recover it in the November pay run. The payroll software records a £200 negative adjustment to gross pay, so the November FPS shows the correct year-to-date pay. Tax is recalculated automatically on the cumulative figures.
- National Insurance is worked out per pay period rather than cumulatively, so the owner checks the software has adjusted it correctly and that the baker is not left worse off.
- The owner keeps the timesheet, the written agreement and a note of the correction with the payroll records.
No separate submission is needed, because the error and the fix are in the same tax year. Had the owner spotted it in May 2027, the 2026 to 2027 figures would already be final and an earlier year correction would be needed instead.
Step by step: correcting a payroll error
- Stop and identify exactly what went wrong, for whom and in which pay period.
- Work out the correct figures for pay, tax, National Insurance, student loan and pension.
- Check which tax year the error falls in.
- Talk to the employee before changing their pay, especially for an overpayment.
- Make the correction once, in your payroll software, so the year-to-date totals are right.
- Check pension contributions, as an auto-enrolment scheme may also need correcting.
- Pay any extra amount owed to HMRC with your next payment. Our guide to PAYE payment deadlines gives the dates.
- Record what happened and what you changed.
Telling the employee
Whatever the error, the employee should hear about it from you before they see it on a payslip. Explain what happened in plain terms, show the before and after figures, and confirm what will change on their next payslip. For an underpayment, say when the balance will be paid. For an overpayment, offer a sensible repayment schedule rather than taking it all at once, particularly from someone on modest pay. Put the agreement in writing and keep a copy. A short, honest message usually prevents a grievance and saves time for everyone.
Late reporting is a different problem
A mistake on an FPS that was sent on time is an inaccuracy. Sending an FPS after payday is a late filing, and that has its own penalty regime based on the number of employees. HMRC explains this on its page about what happens if you do not report payroll information on time. If a mistake was caused by missing information, such as a new starter’s details, report the pay on time with what you have and correct it later, rather than delaying the FPS.
Common mistakes
- Fixing it twice. Correcting the year-to-date figures and also entering a separate adjustment doubles the change.
- Editing a payslip outside the software. HMRC’s records will not match what the employee sees.
- Recovering an overpayment without warning. It damages trust and can cause hardship.
- Forgetting the pension scheme. Contributions usually follow pay, so they may need correcting too.
- Using the wrong year’s method. Earlier years have their own route, so check GOV.UK.
- Holding back an FPS to avoid an error. Late filing creates a separate problem. If you are new to this, see our first employee payroll guide.
Found a payroll error you are not sure how to unpick? Our payroll service runs from £25 a month per employee and includes corrections and RTI submissions. Contact us and we will look at it with you.
Frequently Asked Questions
How do I fix a payroll mistake after sending an FPS?
If the mistake is in the current tax year, correct the pay or deductions in your next regular pay run and send the next Full Payment Submission with the right year-to-date figures. HMRC replaces the old totals with the new ones. You do not usually send a separate correction unless the error affects an earlier tax year.
How do I correct a payroll mistake from last tax year?
For recent tax years, HMRC’s guidance is to send an additional FPS for that year showing the corrected year-to-date figures, using your payroll software’s earlier year option. Older years may need an Earlier Year Update instead. The process depends on the year affected, so check GOV.UK’s payroll errors page before you submit.
Can I take back money I overpaid an employee?
Generally yes. The law allows an employer to recover an overpayment of wages, but handle it fairly: explain the error, show the figures and agree a repayment plan in writing, especially if the amount is large. Correct the year-to-date figures in payroll so the employee’s tax and National Insurance records are right.
Will HMRC fine me for a payroll mistake?
HMRC says penalties for inaccuracies apply where you did not take reasonable care or the error was deliberate. Correcting a genuine mistake promptly and keeping a note of what happened puts you in the best position. Late filing and late payment are separate, and have their own penalty rules.
What if I forgot to put a new starter on the payroll?
Add them straight away with their starter information and report their pay on the next FPS, including any payments already made. Pay any extra tax and National Insurance due to HMRC with your next payment. If you paid them without reporting it on or before payday, that FPS may count as late.
Related reading
How Berber Accounts & Tax helps
We are a London-based, specialist gig-economy and MTD accounting practice working with fixed monthly fees. If you would like this handled for you rather than doing it yourself, we can help.
Schedule a consultation →Written by the Berber Accounts & Tax team, 124 City Road, London EC1V 2NX, United Kingdom.
Last reviewed: 6 November 2026.
This article is general information, not personal tax advice. Speak to a qualified accountant about your own circumstances before acting on it.
