How to Extract SA100 Self Assessment Data
into Excel (2026 Guide)

What's Inside an SA100 — and Which Numbers Belong in Your Spreadsheet

The SA100 is HMRC's main Self Assessment tax return form. It captures personal details, a summary of your income sources, pension contributions, Gift Aid payments, and your overall tax calculation — everything HMRC needs to determine your tax liability for the tax year running 6 April to 5 April. The full guidance on completing it runs to the SA150 notes, currently 44 pages, but the form itself follows a six-page structure numbered TR1 through TR6.

The SA100 carries roughly 60 data fields across TR1–TR6. For most freelancers and small business owners, only 10–15 of those fields are dynamic each year — the rest are personal details, checkbox declarations, and yes/no routing questions that need to be correct but don't change annually. Knowing which fields are the moving parts is what determines whether your spreadsheet captures everything your accountant needs in one column layout, or four.

Those 10–15 fields are what your spreadsheet needs to capture. And that is before supplementary pages enter the picture. If you have self-employment income, the SA103 (short or full, depending on whether turnover exceeds the VAT threshold) adds business income, allowable expenses, capital allowances, and net profit or loss. A property landlord adds the SA105 with rental income, finance costs, repairs, and net property income. A capital gain on shares or property adds the SA108. Each supplementary page adds 5–10 more dynamically changing figures to the same spreadsheet. The SA100 alone may produce 8 columns. A self-employed person with property income may need 15–18 columns that all need to agree with the figures submitted to HMRC.

Why SA100 Data Still Ends Up in Spreadsheets Through Manual Typing

If the SA100 were an API — a structured data feed from HMRC's systems directly into your FreeAgent, Xero, or Excel file — there would be nothing to extract. But the SA100 most self-employed people work with is not a data feed. It is a PDF downloaded from the HMRC online portal, an email attachment from your accountant showing the return they prepared for your review, or — for the 3% who still file on paper — a printed form mailed to HMRC and scanned into your records. Every one of those formats is a visual layout of data, not structured data itself.

Software views of the SA100 make this worse in a way that is specific to Self Assessment. An employee's P60 data is baked into a single format: the tax year-end certificate from one employer, one payroll software. An SA100 self-employed filer's data is assembled from multiple sources — the online HMRC portal aggregates figures from your SA103 self-employment pages, your SA105 property income pages, and any employment income reported on SA102 pages, then renders a calculation that may draw from all of them. The rendered PDF you download from HMRC's portal does not export as a spreadsheet. The PDF your accountant sends for review may use different formatting than the HMRC version. The paper SA100 you filed two years ago and kept for records has no digital data layer at all.

The common thread is that all these formats — HMRC's online portal PDF, accountant-review PDF, scanned paper SA100, supplementary page printouts — carry the same named fields: UTR, employment income, dividend income, rental profit, Gift Aid, total tax due. But they arrange them differently. A template-based OCR tool that expects boxes in fixed positions — the traditional approach to form extraction — fails the moment the layout changes. And in Self Assessment, the layout always changes, because HMRC updates the SA100 form annually and different software providers render it differently.

This is where Custom Column Extraction replaces layout-dependent extraction with something that works across every SA100 format. Instead of telling the tool where the UTR sits on each page layout — co-ordinates, bounding boxes, pixel offsets — you tell it what data you want: "UTR," "Employment Income," "Self-Employment Net Profit," "Total Tax Due," "Payments on Account." The AI reads each SA100 by understanding what each labelled field means, not where it appears on the paper. The same column definition works across HMRC portal PDFs, accountant review copies, and scanned paper returns — because the words "Unique Taxpayer Reference" mean the same thing regardless of which quadrant of the page they occupy.

Setting Up Your SA100 Extraction: A Reusable Column Definition

The workflow that replaces manual SA100 transcription has three steps. The configuration step — defining your columns — is what you do once and reuse for every tax year, every SA100 format, and every batch of supplementary pages.

Three SA100 Extraction Scenarios That Repeat Every Tax Deadline

SA100 extraction does not look the same for everyone who needs it. The following three scenarios cover the most common patterns — and each changes what columns you define and how your output spreadsheet gets used.

The Freelancer Keeping Their Own Tax Records

A freelance graphic designer with one self-employment business, modest dividend income from a stocks and shares ISA, and no property income files an SA100 with one SA103 full self-employment page each year. Their column definition is straightforward: UTR, NINO, Self-Employment Turnover, Allowable Expenses, Net Profit, Dividends Received, Pension Contributions, Gift Aid, Total Tax Due, Payments on Account, Balance Refunded. They extract a single SA100 PDF from their HMRC download — one row of data — and save the spreadsheet alongside the PDF in a tax-year-labelled folder.

This scenario is not high-volume, but it is high-stakes. The freelancer needs the figures to be accurate because the spreadsheet is their only structured record of what they filed. If HMRC opens an enquiry 18 months later, the spreadsheet is what the freelancer pulls up to cross-reference against bank statements and invoices. Extraction removes the transcription errors — mistyped digits, transposed decimals, the wrong payment-on-account figure copied from the wrong box — that make that cross-reference unreliable from the start.

The Accountant Processing Client SA100s at Scale

A small accounting practice serving 80 sole-trader and landlord clients receives SA100s in multiple formats during the December-to-January filing window: HMRC portal PDFs from digital-savvy clients, paper SA100 scans from clients who file by post, email attachments from accountants at previous firms, and PDFs generated by the practice's own tax software showing draft calculations. The practice needs one spreadsheet per client — each with the same column layout — that can be reviewed, cross-referenced against underlying records, and filed with the client's working papers.

The batch extraction workflow handles this naturally. The accountant defines a standard column set once — one that covers the SA100 main form plus the most common supplementary page fields — and processes all 80 clients in one batch upload. Each SA100 (and its attached supplementary pages) becomes one row. Because batch extraction merges results into a single spreadsheet, the accountant gets one Excel workbook with 80 rows, identical columns, ready for review. The practice can also issue a Collection Link — a shareable URL that lets clients upload their SA100 PDFs directly into the practice's processing queue without needing to create an account. The client opens the link, enters a verification code, and drops the file — and it lands in the accountant's queue automatically.

Making Tax Digital: Preparing for Quarterly Updates

From 6 April 2026, the most significant change to UK Self Assessment since its introduction in 1996 takes effect. Making Tax Digital for Income Tax Self Assessment (MTD for ITSA) becomes mandatory for sole traders and landlords with qualifying income — combined self-employment and property income — above £50,000. Roughly 780,000 taxpayers fall into this first wave. The threshold drops to £30,000 in April 2027, bringing in another 970,000, and to £20,000 in April 2028.

Under MTD for ITSA, the annual SA100 filing becomes a year-round digital reporting cycle: four quarterly updates summarising income and expenses, followed by a final year-end declaration — the functional equivalent of the SA100 — submitted by 31 January. Each quarterly update has a fixed deadline: 7 August, 7 November, 7 February, and 7 May. The old workflow — collect 12 months of receipts in a shoebox, tally them in January, file once a year — no longer meets compliance requirements.

The practical consequence for extraction is that the SA100 becomes a quarterly exercise, not an annual cram session. Instead of extracting one SA100 PDF in January and being done, the freelancer or accountant extracts four quarterly income-and-expense summaries plus one year-end SA100. Having a reusable column definition — the same one used for the annual SA100, adapted to include quarterly cumulative totals — means the extraction step takes seconds per quarter rather than the hours that manual transcription would demand four times a year.

The HMRC guidance on MTD for ITSA confirms that MTD-compatible software is required — but the data still originates from documents: bank statements, invoices, receipts, payslips, and the SA100 itself. Extraction bridges the gap between the document you receive and the digital record MTD requires you to maintain.

Validating Your Extracted SA100 Data Before It Goes to Your Accountant

Even at high extraction accuracy, the data you send to your accountant or file with HMRC deserves a sanity pass. The checks below are SA100-specific and run column by column in Excel. They are shape checks — designed to surface the handful of rows worth eyeballing against the source SA100 — not full audits.

The value of a validation pass on extracted SA100 data is that it takes seconds per row rather than minutes. You are checking shape, not re-reading every figure on every page of a six-page form. A column of 10 rows — one per tax year since 2016 — takes under a minute to scan with these formulas applied as conditional formats. The one or two flagged rows get manual review against the source PDF, and the rest proceed directly into your records or your accountant's inbox.

SA100 vs P60 and P45: UK Tax Forms That Share a Spreadsheet

The SA100 is one of three major HMRC tax documents that UK self-employed workers and payroll professionals handle at different points in the tax year. Each serves a different purpose, carries different fields, and enters a spreadsheet at a different time — but all three benefit from the same extraction approach.

A P60 (End of Year Certificate) reports an employee's total pay, tax deducted, and National Insurance contributions for the full tax year — one certificate per employer, issued by 31 May each year. A P45 (Details of Employee Leaving Work) carries the leaver's tax code, year-to-date pay and tax figures, and student loan deduction status — issued when someone leaves a job and needed by the new employer to set up payroll correctly. The SA100 aggregates income from all sources — employment (where P60 and P45 figures feed into the employment page), self-employment, property, dividends, and more — into a single tax calculation.

The practical relationship is that a self-employed person who also has employment income needs three documents to complete their SA100: the P60 from their employer (to verify the employment income figure), any P45s from jobs left mid-year, and the SA100 itself (to file the return). Each document feeds a different part of the same spreadsheet.

For payroll professionals who handle both P60 and P45 extraction alongside Self Assessment data, see our guides to extracting P60 data into Excel for payroll reconciliation, extracting P45 leaver data for new starter processing, and the complete guide to P45 extraction for payroll teams. For practices handling P60 batches on behalf of multiple employer clients, the batch P60 audit spreadsheet guide covers the multi-employer reconciliation workflow.

FAQ