How do you turn a PDF report into Excel?

What this question usually means

The person asking usually closes the month with a stack of PDF statements and a spreadsheet template nobody wants to fill by hand. Retyping forty rows invites typos, and copying a table out of a PDF viewer mangles columns silently. What they want is the table, structured, with enough visibility to catch the places where extraction had to guess.

You can open these pages and sign in to the workspace today. That does not mean external platform accounts are connected, and it does not mean the product has formally launched. What works right now is the convert-and-check workflow described below, running on the PDFs you supply.

What you need before you start

The source PDFs, and the Excel layout you intend to work in afterward: which sheet, which columns, and which totals feed another formula downstream. Known trouble spots help too. If you already know that Q2 is blank on some rows or the period header spans three columns, say so when you start.

Decide who reviews the numbers. Conversion removes the retyping, not the review, so name the person who compares the sheet to the source before anything leaves the desk.

Step 1: Convert one representative report first

Pick the messiest month, not the cleanest one. If the engine handles the report with the ragged header and the half-empty table, the tidy ones will follow. Converting the whole batch before looking at a single result is how thirty subtly wrong sheets get produced in one sitting.

Step 2: Read the extracted grid beside the source page

Open the spreadsheet next to the original PDF and walk one table top to bottom. Column count, row count, and where the period labels sit. You are calibrating your eye to what this document class extracts like, which takes one careful pass and pays off for every file after it.

Step 3: Fix flagged gaps deliberately

An empty column usually means the source really is empty there, and padding it with zeros would be a fabrication. Fill a flagged cell only when the source PDF shows a value; otherwise leave the gap and say why. Every fix should be traceable to a spot on the page.

Step 4: Reconcile the totals

Total the sheet and compare against the grand total printed in the report. When they disagree, the difference lives in a flagged cell or a misread header almost every time. Fixing the cause beats adjusting a plug number, because the plug survives into next month's file.

Step 5: Batch the rest once one file passes

With the pattern verified, convert the remaining reports and repeat the spot check on each. Two minutes per file comparing row shapes against the source catches nearly everything the first pass missed. Then hand the workbook to whoever reviews the numbers.

Verification

The file is done when a colleague can point at any number in the sheet and find it in the source PDF within seconds. If tracing a figure requires explaining what the converter probably did, the sheet is not ready, no matter how clean it looks.

Limits worth stating plainly

Tables are not cell-perfect. Check every number against the source page before you rely on it. A whole multi-page report converted in one pass is not reliable today. Rows from different periods can land in one cell and a column can be dropped. Work one table at a time. Audit-style statements with dollar signs, em-dash blanks, and parenthesised negatives are not handled. Data rows can be lost. Scanned PDFs with no text layer are refused rather than guessed at. There is no OCR path you can rely on here today. A document with no printed table is not something to convert. If you are handed a sheet built out of running prose, discard it and tell us.

Tablefold shows you where the grid was uncertain instead of filling the gaps quietly. There is no claim of lossless or audit-ready output here, and nothing in this workflow replaces opening the source PDF yourself.

What Tablefold does in this workflow

Tablefold takes the PDF batch, detects the report tables, and produces an Excel file whose structure mirrors what it found, including the empty spans and the multirow period headers. Flags mark the cells most likely to need your eyes before download.

You keep the judgment: which flagged cells are real gaps versus detection noise, what belongs in the sheet, and whether the totals reconcile. The product's job is making the checking fast, not making it optional.