Extract UK P60 Data to Excel — Pull Pay, Tax & NI into a Reconciliation-Ready Sheet
Most P60 extraction tools return a text blob you still have to re-sort — this keeps Pay in This Employment, Tax Deducted and the NI Category Letter as labelled columns you can reconcile directly. A 150-certificate batch that cost five hours of May typing now processes in under half an hour.
Enterprise-grade security · TLS 1.3 encrypted
The Year-End Fields You Can Pull from a UK P60
Type the column names you need and the AI finds each value on the P60 by what its field label means, not where it sits — the same columns work on a Sage PDF, a Xero export, a BrightPay printout, and a scanned paper certificate from a previous employer. These are the fields a year-end reconciliation spreadsheet keys off.
You define the output — the AI reads the document. Add any field a P60 carries; this is the set most year-end reconciliation workbooks need.
Why P60 Reconciliation Fails on a Text Dump — and Works on Field Meaning
A P60 is not read — it is reconciled. The figure in "Pay in This Employment" has to match the year's Full Payment Submissions (FPS) and the final payslip, the National Insurance category letter sets contribution rates for the whole year, and the 31 May deadline carries a £300 penalty per certificate behind it. Position-based OCR reads the characters and stops — and that is exactly where P60 extraction breaks.
The Problem
"Pay in This Employment" is cross-checked against your FPS totals and the March payslip at year-end, but payroll software accepts any number you type into the spreadsheet. One mistyped digit passes silently — the mismatch only surfaces weeks later when the reconciliation will not balance, and someone has to re-read every certificate to find it.
The NI Category Letter — one character from a set of 13 (A, B, C, F, H, I, J, L, M, S, V, X, Z) — decides the contribution rates applied to that employee's earnings all year. A misread S as F, or I as J, is silently accepted and shifts both employee and employer National Insurance through your records.
"Pay in This Employment" and "Total Pay for Year" (likewise "Tax Deducted" and "Total Tax for Year") both print as bare pound amounts. For an employee who started mid-year, the "Total" figure carries forward the previous employer's figures from the P45 — and every employment issues its own certificate, which is exactly the situation a job-switcher describes as being "stuck between 2 employers" when the previous one says they were not on the payroll on 5 April. A flat OCR dump returns two identical-looking numbers with no way to tell which is which.
How Custom Column Extraction Solves This
Custom Column Extraction means you type the columns you want — "Pay in This Employment," "Total Pay for Year," "NI Category Letter," "Employee NI Contributions" — and the AI reads each value by what its field label means, wherever that label sits on the page. No coordinates, no per-provider templates, no model training.
Define the columns once and they pull from a Sage PDF, a Xero export, a BrightPay printout, a QuickBooks file, and a scanned paper P60 from a previous employer alike — another certificate needs no new setup, and a template trained on one renderer never has to be retrained on the others.
Each figure lands in its own labelled column, and statutory payment rows that are absent on the certificate stay blank rather than reading 0 — so your totals do not silently inflate. Review Mode highlights where every value came from on the original page, turning the audit check into a spot-check instead of a re-read.
From the Year-End P60 Folder to a Reconciliation-Ready Spreadsheet, in Three Steps
If your payroll or finance team compiles the year-end reconciliation — P60 figures against FPS totals and the P32 (the employer's monthly PAYE payment statement) — here is the workflow from the moment the certificates are generated to a spreadsheet that balances.
Upload the whole May folder, formats mixed
Drop in the payroll-generated PDFs from Sage, Xero, BrightPay, or QuickBooks, the scanned paper P60s leavers brought from previous employers, and the occasional phone photo — batch processing runs them as one job and merges the results into a single spreadsheet. If employees upload their own previous-employer certificates, share a Collection Link — a page where they drop files straight into your queue without registering.
Name the reconciliation columns once
Type "Employee Name," "National Insurance Number," "Employer PAYE Reference," "Pay in This Employment," "Total Pay for Year," "Tax Deducted," "Total Tax for Year," "NI Category Letter," "Employee NI Contributions," "Final Tax Code." The AI reads each by label meaning and fills the row. Add a computed column like "Tax Rate (Total Tax for Year ÷ Total Pay for Year)" — the AI runs the calculation on the extracted figures during the same pass — and outlier figures get flagged before the balance breaks, not after.
Export one row per employee, then tie out
Export XLSX or CSV, or land the results straight in Google Sheets. Sum the "Pay in This Employment" column against the year's FPS totals and the P32, and each employee's NI category letter sits beside their contributions for a rate check. Review Mode highlights the source of each value on the certificate, so the audit file's evidence is one hover away.
Where P60 Extraction Helps — and Where the Figures Still Need Your Judgment
When it works best
Payroll-software PDFs and clean scans. Sage, Xero, BrightPay and QuickBooks exports, plus 200–300 DPI flatbed scans of paper certificates, extract with high accuracy because the field labels are machine-printed.
Batch year-end processing. Upload the full certificate run at once and export one spreadsheet with a row per employee per tax year — the shape that makes the 31 May reconciliation practical instead of a week of retyping.
Arbitrary field subsets. Because extraction follows column names, pulling only the NI Category Letter and Pay figure for a quick rate check is as natural as pulling the full statutory set for the audit file.
When to be cautious
This extracts the certificate — it does not run your payroll or file with HMRC. The tool reads the P60 and produces the structured spreadsheet; calculating employer NI, reconciling against the P32, and submitting the FPS remain your payroll software's and your team's job. The certificate, not the extraction tool, is the compliance artefact.
Multiple P60s per employee are not auto-merged. Each certificate is extracted to its own row, because each covers one employment only. Summing two rows to build a full-year figure for a mortgage or tax return is a deliberate spreadsheet step you control — the tool will not silently combine records by National Insurance number.
Folded, faded, or handwritten copies reduce accuracy. A clean digital or scanned P60 extracts at high accuracy; a paper certificate that spent three years in a filing cabinet, or a shadowed phone photo, may blur small figures. Run Review Mode before those numbers feed the reconciliation.
Frequently Asked Questions
Can I pull the NI earnings bands — LEL, PT, UEL — as separate columns, or only the total contributions?
Either, because you define the columns. Name "Earnings at Lower Earnings Limit," "Earnings LEL to Primary Threshold," "Earnings PT to Upper Earnings Limit," and "Employee NI Contributions" and each band comes out as its own labelled column — which is the granularity an audit reconciliation actually compares against your payroll reports. Name only "Employee NI Contributions" and you get the single total. Custom Column Extraction only returns the columns you ask for; the P60's NI section has no hidden fixed schema you are locked into.
What's the difference between "Pay in This Employment" and "Total Pay for Year" — will both come out?
Both come out as separate labelled columns. Pay in This Employment is the gross pay this employer paid you over the tax year. Total Pay for Year aggregates pay from previous employments in the same tax year, carried forward from the P45 when the employee started mid-year. The two figures print as identical-looking pound amounts, which is why a text dump blurs them — naming both columns is what keeps them distinct in your spreadsheet.
Does it handle a scanned paper P60 from a previous employer?
Yes, as long as the printed text is legible to a human eye. The AI reads the field label by meaning rather than by coordinates, so a scanned paper certificate is treated the same as a payroll-software PDF — and it uses the same column set, so a leaver's previous-employer P60 does not need separate setup. A clean 200–300 DPI flatbed scan performs best; if the only copy is a folded or shadowed photo, verify the small figures in Review Mode rather than trusting them at face value.
What if an employee has two P60s from two different jobs?
Each P60 is extracted to its own spreadsheet row, because each certificate only covers one employment — an employee with a full-time role and a side job receives two certificates, and each is correct on its own. The tool does not silently merge records by National Insurance number; summing the two rows to arrive at the full-year figure is a deliberate spreadsheet step you control, which keeps every figure traceable to the certificate it came from.
Does this replace my payroll software, or file anything with HMRC?
Neither. ImageToTable.ai replaces the manual transcription step between the P60 and your reconciliation spreadsheet — it reads the certificate and produces structured rows. Issuing the P60 in the first place, calculating employer National Insurance, reconciling against the P32, and submitting the Full Payment Submission (FPS) to HMRC all remain the job of your payroll software and your team. What the tool gives you is the certificate's figures in a form you can tie out.
Deeper on UK P60 data: How to Extract UK P60 Data into Excel for Payroll Reconciliation — the step-by-step column workflow behind this page · The Complete Guide to UK P60 Data Extraction for Payroll Teams — how the RD1 field set and substitute layouts fit together · UK Payroll's May Problem: The Hidden Cost of P60 Data Entry — what keeping this step manual actually costs