Extract UK P45 Leaver Data to Excel — Tax Code, NI & YTD Pay into One Row per New Starter
Manually entering a new starter's P45 takes about 2 minutes per form — this pulls the same 13 leaver fields into Excel in 5–10 seconds. One mistyped tax code digit and the employee sits on emergency tax for months; here the tax code is read, not retyped.
Enterprise-grade security · TLS 1.3 encrypted
The 13 Leaver Fields You Can Pull from a UK P45
Type the column names you need and the AI finds each value on the P45 by what the box label means, not where it sits — the same columns work on a payroll-software PDF, a scanned paper copy, and a phone photo of Part 2. These are the fields a payroll team actually keys into the new-starter screen.
You define the output — the AI reads the document. Add any field a leaver's P45 carries; this is the set most new-starter records need.
Why P45 Data Entry Fails at the Tax Code — and Works on Meaning
Every payroll software is allowed to render a P45 its own way, so the same tax code appears in a different box on every certificate. The employer who issues the form has no incentive to standardise, and the new starter has no way to make them. Competitor platforms automate this with enterprise APIs and configurable business rules. Here is the difference on the screen a payroll admin actually sees.
The Problem
A payroll admin types "1257L" into the new starter form and the software accepts it. There is no checksum, no second pair of eyes, no cross-check against the P45 image. One transposed digit — 1257L as 1275L — and the employee is on the wrong deductions every payday until HMRC issues a corrected code.
A Sage PDF, a BrightPay export, a creased paper copy, and a smartphone photo of Part 2 all carry the same fields at different coordinates. A template trained on one renderer misreads the others — the exact frustration a new starter describes when their first payslip arrives and "a massive chunk had vanished to emergency tax" — traced back to a missing, late, or mistyped P45.
The P45 carries two "pay" figures — Box 7 cumulative (all employments this tax year) and Box 8 this employment only — and a Week 1/Month 1 flag that stops the new employer from carrying YTD forward at all. A flat OCR text dump blurs these apart, so the admin can't tell which figure to key in.
How Custom Column Extraction Solves This
Custom Column Extraction means you type the columns you want — "Tax Code at leaving," "Total Tax to Date," "NI Number" — and the AI reads each value by what its label means, wherever that label sits on the page. No coordinates, no per-renderer templates, no training data.
Define "Leaving Date," "Total Pay to Date," "Week 1/Month 1 Indicator" once and they pull from a Sage PDF, a scanned Part 2, and a photo alike — another leaver's certificate needs no new setup. You get the column you asked for, not a reading-order blob you have to re-map.
The exported row keeps the tax code, both YTD figures, and the W1/M1 flag as distinct columns. The admin's job shifts from fighting a cursor through 13 fields to spot-checking one decisive tax code against the source image — the verification step manual entry never had.
From a New Starter's P45 to a Payroll-Ready Row, in Three Steps
If you're the one who enters leaver details for a payroll run, here is what the workflow looks like from the moment the P45 lands in your inbox to the spreadsheet (or Google Sheet) your payroll software can ingest.
Get the P45 in, any way it comes
The new starter emails a PDF of Parts 2 and 3, hands over a paper copy on day one, or snaps a photo of Part 2. If employees send files themselves, share a Collection Link — a page where they upload straight into your queue without registering — and the P45 arrives in your processing queue ready to go.
Name the leaver columns once
Type "Tax Code at leaving," "Leaving Date," "Total Pay to Date," "Total Tax to Date," "NI Number," "Week 1/Month 1 Indicator." The AI reads each by label meaning and fills the row. Add a computed column like "Tax Rate (Tax to Date ÷ Pay to Date)" if you want a quick sanity check against the payroll run, and it calculates during extraction.
Hand one clean row to payroll — per starter
Export XLSX or CSV, or land results straight in Google Sheets. Process a batch of new starters and each P45 becomes one row. Review Mode highlights where each value came from on the original page, so confirming the one decisive tax code takes seconds on a batch of thirty.
Where the Tool Helps — and Where to Apply Payroll Judgment
When it works best
Digital and cleanly scanned P45s. Payroll-software PDFs and flatbed scans at 200–300 DPI extract at high accuracy, because the box labels — "Tax code at leaving date," "Total pay to date" — are machine-printed.
Batch new-starter processing. Upload a run of P45s at once and export one spreadsheet with a row per starter — the shape that makes a monthly onboarding cycle practical instead of a day of retyping.
Arbitrary field subsets. Because extraction follows column names, pulling only the NI Number and Tax Code for a quick check is as natural as pulling all thirteen for a full record.
When to be cautious
This extracts data — it does not run your payroll or file with HMRC. The tool produces the structured spreadsheet; applying the tax code and YTD figures in your payroll software, deciding which fields apply this tax year, and submitting the FPS remain your judgment and your system's job.
Prior-tax-year P45s need care. The fields still extract, but the Year-to-Date figures on a P45 from an earlier tax year must not be carried into the current record — you keep the tax code and start YTD at zero, per HMRC guidance. Extraction gives you the values; the tax-year call is yours.
Handwritten or low-quality copies reduce accuracy. A clearly written code extracts well, but small, rushed, or smudged handwriting — and shadowed or angled phone photos — may drop digits. For any doc with handwriting, run Review Mode before the numbers go anywhere.
Frequently Asked Questions
Can I extract data from a scanned or photographed P45?
Yes, as long as the printed or handwritten text is legible to a human eye. The AI reads field labels like "Tax Code at leaving date" and "Total pay to date" by their meaning rather than their coordinates, so a scanned paper P45, a payroll-software PDF and a photo of Part 2 are treated the same way. A clean 200–300 DPI scan performs best; if the only copy is a shadowed phone photo, verify the small figures in Review Mode.
Can I pull just a couple of fields — say the NI Number and Tax Code — instead of all thirteen?
That is exactly how Custom Column Extraction works: you only get the columns you name. Type "National Insurance Number" and "Tax Code" and the output table has those two columns and nothing else — you are not forced to take a fixed field set from a parser. The tax code and NI number both extract cleanly because their labels are unambiguous on every P45 layout.
How does the Week 1 / Month 1 indicator come out, and why does it matter?
It is extracted as its own column — a "Week 1 / Month 1" flag on the P45 — rather than being folded into the tax code. The flag is the most common cause of emergency tax at a new employer: a W1/M1 (non-cumulative) code means each pay period is calculated in isolation, ignoring the employee's prior year-to-date tax. Pulling it as a separate column keeps it from being silently dropped during entry, which is exactly when it should surface for a human decision.
What if the P45 is from a previous tax year?
The fields still extract — but the Year-to-Date figures (Total Pay to Date and Total Tax to Date) on a previous tax year's P45 must not be carried into the new payroll record. HMRC guidance is to keep the tax code and start the current year's cumulative pay and tax at zero. Extraction gives you the values on the form; deciding which ones apply to the current tax year is a payroll judgment the tool deliberately leaves to you.
Does this replace my payroll software, or file the return for me?
Neither. ImageToTable.ai replaces the manual transcription step between the P45 and your payroll record — it reads the form and produces the structured spreadsheet. Applying the tax code and year-to-date figures in your payroll software, and submitting the Full Payment Submission (FPS) to HMRC, remain the job of your payroll system.
Read more: How to Extract UK P45 Leaver Data into Excel for Payroll — the step-by-step workflow behind this page · The Complete Guide to UK P45 Data Extraction — how the four parts and thirteen boxes fit together · Why the P45 Form Costs UK Payroll Teams — the cost of keeping this step manual