Correcting a payroll reporting error

A payroll reporting error should be corrected using the method appropriate to the tax year, affected field and submission type. Identify whether the problem concerns pay, employee details, payment dates or HMRC settlement before changing the payroll record.

Preserve the submitted version and reconcile year-to-date figures. Avoid creating a duplicate employment record while trying to correct an existing one.

Describe the error before changing anything

Write down the employee, pay period, tax year, affected field and the evidence showing the correct position. Distinguish an incorrect calculation from an accurate payroll followed by a wrong bank payment or HMRC allocation. Those problems may look similar in a total balance but require different action. Save the original report and acknowledgement so the reviewer can see exactly what was sent, rather than relying on the current software screen.

HMRC provides different correction instructions for pay and deductions, payment dates, personal details, National Insurance categories and EPS amounts. Current-year and earlier-year cases can also differ. Follow the branch that matches the actual error and check the software's implementation of it. A blanket instruction to resend everything with the preferred figures can create duplicate records or move the problem into another period. ^[1]

Reconstruct the correct calculation

Start with the authorised pay instruction, timesheet or relevant notice. Calculate what should have been processed and compare each affected component with the original result. Show the difference in gross pay, deductions and net pay separately. An employee being £100 short in their bank account does not establish that gross pay should simply be increased by £100; the cause and tax treatment need to be understood first.

Check whether the error affected other employees or periods. A single mistyped overtime amount may be isolated, while a wrong rate or category setting can have a wider effect. Limit the review to the concrete risk identified, but do not assume a recurring setup problem ended with the first complaint. Keep a list of affected records and the calculation supporting each proposed amendment.

Choose the reporting route deliberately

Record the correction method selected and why it applies to the tax year and field concerned. If the software cannot perform the required action clearly, seek guidance from the provider or payroll adviser before creating manual workarounds. Retain the relevant instruction with the file. A later operator should be able to distinguish a deliberate correction from an unexplained change to the employment record.

Be particularly careful with start or leaving dates and personal details, where an apparently simple resend may have unintended consequences under the reporting rules. Maintain continuity of the employee identifier and avoid creating a new employment record to make the old one disappear. If a duplicate already exists, investigate the proper resolution rather than adding a third version in an attempt to restore the expected total. ^[1]

Coordinate the employee and HMRC positions

Tell the employee what has been identified, what remains under review and when a confirmed correction will be explained. Where money is owed to the employee, arrange the payment and reporting consistently. Where an overpayment may be recoverable, assess the lawful process and communication separately; payroll arithmetic alone does not settle every employment-law question about a deduction from future wages.

After submitting the correction, retain acceptance evidence and reconcile the revised year-to-date totals. Check the employer account and any payment adjustment needed, allowing for the relevant processing timetable. Do not assume that an accepted report has immediately resolved every displayed balance. Keep the matter open until the calculation, employee payment and HMRC position have each been checked against the intended outcome.

Document the cause and the prevention step

A useful correction note records the original error, evidence, approved calculation, reporting action and resulting settlement. Add one practical prevention measure linked to the cause. If the problem was an outdated salary instruction, improve change authorisation; if it was an import mapping issue, correct that mapping before the next run. A general reminder to 'be more careful' does not explain how recurrence will be prevented.

Use Real Time Information payroll submissions for the normal RTI control process and Payroll administration to discuss a payroll correction. State the affected tax year, submission type and field in the initial enquiry. Provide identifiable employee records only through the agreed secure route. This allows the adviser to assess the appropriate scope without inviting unnecessary circulation of the full payroll database.

Review the next ordinary payroll for the corrected employee, especially where cumulative figures or a changed setting carry forward. Confirm that the same amendment has not been applied twice and that the original problem has not reappeared through a recurring import or template. Keep that follow-up check with the completed correction record.

Illustrative scenario

An employee’s bonus is entered twice. Payroll reverses the duplicate through a controlled correction, checks the reporting route and explains any payment recovery separately to the employee.

Preparation checklist

• Define the error
• Identify the tax year
• Check the correction method
• Reconcile payroll and payment effects