Home/Documents/P60

Fake P60 detection: spot edits, forgeries and AI fakes

A P60 is the end-of-year summary HMRC requires every UK employer to give each employee still on payroll on 5 April, totalling the year's pay, income tax, and National Insurance, and lenders and letting agents ask for it as employer-attested annual income. Because it must reconcile with the final payslip of the tax year, inflated totals are exactly the fraud that arithmetic exposes.

Last updated:

Most often edited

total pay in the tax year, total income tax deducted, employer PAYE reference

Reviewed by

UK mortgage lenders, letting agents, and visa financial reviewers

Where forgers attack a P60

Payslip reconciliation
The P60's closing totals must match the final payslip's year-to-date figures for the same employment. Totals that float above the payslips behind them are the inflation pattern this document exists to catch.
Tax-year coherence
The label covers 6 April to 5 April of consecutive years. Mismatched year labels, or totals for a period the employment dates cannot span, point at retyped numbers.
Reference and NI structure
The employer's PAYE reference and the employee's National Insurance number follow fixed formats, and both must agree with the payslips and employment letters in the same file.
Figure-level print forensics
Edited totals betray themselves through font passes, digit spacing, and realigned columns inside the totals table, since amounts are usually the only region a forger touches.

How to check a P60 step by step

  1. 1. Collect the P60 and payslips

    Gather the P60 alongside at least the final payslip of the tax year, since the reconciliation runs between the two documents.

  2. 2. Reconcile the totals

    Compare the P60's pay and tax totals against the final payslip's year-to-date column for the same employment.

  3. 3. Check identifiers and dates

    Confirm the tax-year label, PAYE reference, and National Insurance number agree with the rest of the file.

  4. 4. Run a forensic check on the file

    The reconciliation is arithmetic, but inflated totals still need edited cells to carry them. TamperCheck runs 300+ forensic checks including totals reconciliation and cell-level print analysis, returning a risk score from 0 to 100 with findings tied to specific regions of the image.

Visible warning signs in a P60

  • A total pay in the tax year that breaks the chronology

    Lay the total pay in the tax year against every other date on the document and against when the file says it was created. Backdated and extended dates tend to land in an order no real issuing system would have produced.

  • A total income tax deducted that does not sit with the figures around it

    Work through every number the page lets you recompute. The total income tax deducted is the value a forger most wants to change, and the one a careless edit leaves out of step with the totals and running figures derived from it.

  • Totals that were typed, not calculated

    Add the columns yourself. A document produced by an accounting or payroll system reconciles to the unit, and a hand-edited one often does not.

  • Round numbers where systems produce messy ones

    Real payroll and banking output is full of odd amounts. Suspiciously round figures across a whole document are worth a second look.

  • Layout that differs from the issuer's other documents

    Ask for an earlier document from the same issuer. Column order, field labels and footer wording rarely change between periods, and fakes get them wrong.

The forensic checks that matter most for a P60

  • Arithmetic reconciliation

    Stated totals are recomputed from their components, and running or cumulative figures are checked for continuity across periods. A single edited value breaks the chain even when the page still looks right.

  • Reference and document number checks

    Document, account, and reference numbers are checked for issuer format conformance and against every other place the same value appears on the page.

  • Table structure integrity

    Inserted and deleted rows leave structural artifacts behind: inconsistent spacing, misaligned columns, and formatting the visible table no longer accounts for.

  • And many more checks

    The three above are the layers that carry the most weight on a P60. Every upload runs the full suite of 300+ checks regardless of document class, spanning file structure and metadata, pixel-level forensics, font and text rendering, optical and print characteristics, provenance signals, AI-generation signatures, and many more checks.

Anatomy of a genuine P60

The form covers a single tax year running 6 April to 5 April, and prints the employer's name and PAYE reference, the employee's name and National Insurance number, and totals for pay, tax deducted, NI, and any student loan repayments or statutory payments. Employers must issue it by 31 May following the year end.

The P60's totals must agree with the final payslip's year-to-date column, and the National Insurance number and PAYE reference must agree with the payslips and employment elsewhere in the file. A P60 whose totals float free of the payslips behind it, or whose employer details shift between documents, is the composite signal lenders care about.

Questions people ask about a P60

What is the difference between a P45 and a P60?

The P45 records pay and tax when an employment ends during the year, while the P60 totals a full tax year for employees still on payroll at 5 April. Someone who left mid-year receives a P45 and no P60 for that employment.

Why do lenders ask for a P60 instead of just payslips?

The P60 is an employer-attested annual total, so it summarises the year rather than a month, and it reconciles against the payslips behind it. That reconciliation is exactly what makes inflated annual income hard to fake convincingly.

Can a P60 be reissued after 31 May?

Employers can issue a statement of earnings or a duplicate P60 on request, but the layout and totals must still reconcile with payroll records. A replacement is normal; a replacement whose totals cannot be tied to payslips is not.

How does TamperCheck verify a P60?

TamperCheck reconciles the P60's totals against the final payslip in the file, validates the PAYE reference and NI number formats, and inspects the totals table for figure-level edits. It returns a risk score from 0 to 100 with findings tied to specific regions.

What does TamperCheck look at first on a P60?

It starts where forgeries of a P60 most often break: the tax year and issue date, the employer's PAYE reference, and flattened layers in an editable PDF. After those, the checks that run on every document cover the rest of a P60.

Can the totals on a P60 be wrong even if the maths adds up?

Yes. A careful forger recalculates, so arithmetic alone cannot clear a P60. What recalculation cannot hide is the pixel history under an edited total pay in the tax year and the fact that it was not part of the file's original production pass.

Is a PDF safer to rely on than a scan of a P60?

A native PDF of a P60 carries creation metadata and a text layer you can compare with what is drawn, so it is easier to test. It is also the easiest format to edit. Treat the format as a source of evidence, not as proof.

Does TamperCheck confirm a P60 with the issuer?

No. TamperCheck analyses the file of a P60 itself for edits, composited elements and generation signatures. Confirming a P60 with the issuing body is a separate step, and the two complement each other.

Check a document

Upload a PDF or a photo of P60. TamperCheck returns a risk score from 0 to 100 and marks the region that was edited, usually within seconds.

For developers, the API class is p60. See the API and MCP documentation.

Often checked alongside

All supported document types