Using a fake P60 form to inflate income and spoof mortgage applications is not a rare occurrence. Even members of the popular tv show UK apprentice have attempted this kind of fraud.
Fraudsters know these documents carry weight. They’re official, employer-issued year-end summaries, making them prime targets for manipulation. If a convincing fake slips past manual checks, it can lead to wrongful approvals and costly payouts.
In 2025, Generative AI and document fraud templates have only made the fake P60 problem worse. With polished documents now easily available online, organizations that rely on these documents as proof of income and tax compliance are more exposed than ever.
Read on to learn what a P60 is, why it matters, how fake P60 scams work, and how AI-powered verification can help you spot them automatically.
Check out our "How to spot fake documents" blog to learn about more common document forgeries.
A P60 is an official document issued by UK employers at the end of each tax year. It provides a record of an employee’s pay and the tax deducted under the Pay As Your Earn (PAYE) system.
The PAYE system is a His Majesty’s Revenue and Customs (HMRC) mechanism for collecting income tax and National Insurance directly from wages, so the P60 serves as the year-end confirmation that these deductions have been correctly applied. It must be given to every employee working on 5 April (the last day of the tax year).
Key elements of a P60 form include:
Together, these details confirm proof of employment, income earned, and taxes paid in a specific year.
An example of a P60 form for illustrative purposes only
Employers use P60 forms to summarize annual pay, income tax, and National Insurance contributions under PAYE for each employee at year-end.
Employees use them to confirm their total earnings, file or reconcile their taxes with HMRC, and provide trusted proof of income in processes like mortgage applications or benefit claims.
Here’s how they’re used for document verification across industries:
Because P60s come directly from employers and are tied to HMRC records, they’re widely trusted as reliable proof of both income and tax compliance.
If you’d like to know how fraudsters are creating all these fake P60 forms, check out our “Types of fraud” blog to learn more about their tactics.
Overlooking a fake P60 isn’t a small mistake. It can distort affordability checks, let applicants access benefits they’re not entitled to, or create a false history of employment.
Fraudsters know that many reviewers skim these documents, so they exploit small but telling mistakes. The best way to spot fakes is with document fraud detection software.
But many institutions still try to spot fake P60s manually. Here are the key red flags to look out for:
Real P60s follow HMRC’s standard template, with rigid tables and box structures. Deviations stand out quickly.
Errors in core identifiers and HMRC references are a common giveaway.
P60s summarise an entire year of pay, tax, and deductions. Unrealistic figures are often the clearest fraud signals.
Some giveaways are unique to the P60 format itself.
The digital trail of a P60 can reveal more than the visible content.
Disclaimer: While manual reviewers can catch obvious mistakes, sophisticated fakes often blend in with authentic payroll outputs. At volume, these errors can evade controls, making AI-powered document fraud detection essential for organizations relying on P60s.
Banks, mortgage lenders, immigration authorities, government benefits teams, and corporate HR departments check p60s in two ways: manual and automated.
Manual checks can struggle to catch the subtle errors hidden in fabricated P60s, especially when reviewing them at scale.
That’s why organizations are shifting toward AI-powered verification, which can analyze a document for fraud in seconds.
Still, manual review persists.
If you’re checking P60 forms manually, begin by using the red flags we mentioned above. Once you’ve exhausted those, you can turn to the following resources:
Keep in mind: Manual checks can help catch obvious fakes, but they don’t scale. Fraudsters operating at volume produce near-perfect templates that look identical to genuine payroll outputs. Without automation, even skilled reviewers risk approving fraudulent submissions hidden among a pile of legitimate entries.
AI doesn’t rely on static templates or database lookups, it can adapt to new layouts, content updates, and even generative AI forgeries in real time.
Benefits of AI-powered P60 verification include:
Basic automation can perform useful checks on P60s — confirming that required fields exist, numbers add up, or a tax year is correctly formatted. But automation breaks when fraudsters generate polished forgeries that follow the rules on the surface while altering core values underneath or use new tactics your rules weren't prepared for.
AI goes further. By learning how genuine P60s are structured and adapting to new fraud tactics, it can flag anomalies that humans and scripts would miss. From linking reused templates across multiple applications to spotting subtle manipulations, AI provides a defense that keeps pace with evolving fraud tactics.
Fake P60s are a direct threat to financial integrity, immigration processes, and public benefits. Fraudsters exploit the document’s trusted status to slip inflated incomes, fabricated employment, or false tax histories into high-stakes workflows.
Manual checks might catch a typo or missing field, but they won’t scale against professional forgeries designed to mimic HMRC-compliant payroll outputs.
Resistant documents, our document fraud detection software, brings a structural, document-agnostic approach that spots patterns, links fraud across submissions, and adapts to your decision flows (all the AI benefits we described above).
Want to see it in practice?
Scroll down to book a demo and explore how your organization can detect fake P60s before they cause financial or reputational harm.
Hungry for more fake P60 content? Here are some of the most frequently asked fake P60 questions from around the web.
If you spot mistakes (wrong NI number, gross pay mismatch with your payslips, incorrect employer details), you should first contact your employer and ask them to issue a corrected form or provide a written erratum.
If your employer refuses or you can’t resolve it, you can raise the issue with HMRC. Some lenders or authorities may accept a corrected statement plus correspondence as interim proof.
At a glance, both seem similar — same layout, same fields. But genuine P60s:
Automation (rules, templates) checks surface-level correctness — e.g. “does box 1 exist?” or “is the tax year in range?.” They can also account for pre-existing/well known tactics, but fraudsters can create forgeries that pass those rules.
AI goes deeper: it learns how genuine P60s are built, catches mismatches across multiple documents, spots anomalies, and adapts to new fraud patterns as they emerge.
You should keep records about your pay, tax, and related documents for at least 22 months after the end of the tax year (if you’re not filing Self- Assessment)
If you are filing, or if your tax return is late, HMRC requires longer retention periods.
Additionally, many advisors suggest holding onto them for 4 to 6 years as proof for audits, loan applications, or tax disputes.
Yes. You can ask your employer to re-issue it (or issue a statement of earnings). You can also view and print the equivalent figures via your HMRC personal tax account.
AI analyses how the P60 was built. Layout logic, payroll-system fingerprints, and hundreds of other indicators can expose forgeries in seconds.
P60s and P45s are both tax-related documents but serve different purposes and jurisdictions. They’re both issued by one’s employer but the P60 is a yearly income tax deduction while P45 is only issued once an employee is terminated.
Yes. Resistant AI analyses document construction rather than contents and scales verification across thousands of P60s in real time.
Several industries rely on them as proof of income and compliance:
Yes. Creating or using a forged P60 is fraud under the UK Fraud Act 2006. Penalties can include fines, liability for false claims, and prison sentences of up to 10 years.