Correction policy

What happens to a report

1. It is read and acknowledged. You get a reply saying the report has landed, before any decision is made about it.
2. It is checked against the primary source. Not against what the page says, and not against another calculator: against the HMRC, legislation.gov.uk or Revenue.ie publication the figure is supposed to come from.
3. A position comes back to you. Either the page is corrected, or we explain why we read the rule differently and link the source we relied on. Disagreeing with you and telling you why is a valid outcome; going quiet is not.
4. If we correct, the page changes in public. See what gets published, below.

Wrong numbers jump the queue. A rate, threshold or worked example that does not reconcile is fixed ahead of a broken link or a clumsy sentence, because that is the error that can cost you money.

How reports are classified

Factual error

A rate, threshold, statutory figure or date that does not match the source. Treated as urgent.

Procedural error

The steps to do something are wrong or out of date, for example how to claim a refund or challenge a tax code. Treated as urgent.

Interpretive disagreement

We describe a rule one way and you read it another. Treated as a discussion, and the answer is reasoned against the source rather than asserted.

Presentation

A broken link, a confusing sentence, a heading that promises something the page does not deliver. Fixed on the next pass over that page.

What gets published when we correct

• A changed number: the page is updated, a correction note is added at the foot of it giving the date, the old wording and the new wording, and the last-reviewed date is bumped. The note is not quietly deleted later; it moves to the corrections log.
• A changed procedure: the page is updated and the last-reviewed date is bumped.
• A presentation fix: corrected without a note. Nothing a reader relied on has changed.

Correcting a figure silently would leave anyone who acted on the old one with no way to find out. That is why the note carries the old wording as well as the new.

Corrections log

A rolling twelve-month log of published corrections is planned. It is not live, because no correction has yet been published under this policy and a log with nothing in it says less than saying so plainly. When the first correction note ages off a page it will go there, and this section will carry the link.

If your own check was wrong

A wrong result from the payslip checker is handled differently from a wrong page. Tell us what you entered and what came back, and if the calculation logic is at fault it is fixed for everyone. Individual results are not published, because they are built from data you supplied: you get the answer privately, and the underlying fix is what becomes public.

PayslipIQ is an educational estimate, not your tax record. Where money has actually gone wrong, when to contact HMRC sets out who can actually change it.

What this address is not for

Security issues go to security disclosure, data-protection requests to the contact named in the privacy notice, and questions about your own tax position to HMRC or a qualified adviser. We cannot see your tax record, your coding notice or your employer’s submissions.