Picture this: 9 PM, a stack of supplier invoices, and a spreadsheet waiting to be filled. Column by column. Row by row. Copy, paste, scroll back, repeat. For three years straight.
That’s exactly what a Reddit user in r/PromptEngineering described doing with every PDF that crossed their desk. Financial statements, contracts, research reports. All of them had tables. All of them needed to be in Excel. And every single one got processed manually.
Then the original poster uploaded a PDF to Claude and asked it to extract the data directly into a spreadsheet. The result: a clean .xlsx file with proper columns, consistent formatting, and every line item in the right place. Time taken: 40 seconds.
🤔 Why This Is a Bigger Deal Than It Sounds
PDFs have always felt like read-only objects. You can open them, read them, maybe search them. But actually getting data OUT of them and into something you can sort and filter? That’s always felt like work for a developer or a dedicated tool.
The shift the author describes is treating PDFs as data sources rather than static documents. Any PDF with structured information (tables, line items, pricing schedules) can be turned into something you can actually work with. No third-party app. No developer. One prompt.
📋 The Prompt That Works
The original poster shared the exact prompt they use reliably. Here it is in full:
I’m uploading a PDF that contains [describe what’s in it: invoice, financial statement, research report, contract table, whatever].
Extract the following data from it into a structured spreadsheet:
- [Field 1 you want, e.g. “line item description”]
- [Field 2, e.g. “quantity”]
- [Field 3, e.g. “unit price”]
- [Field 4, e.g. “total”]
- [Add as many fields as relevant]
Return a downloadable .xlsx file with:
- Clean column headers matching the fields above
- One row per item/entry/record
- Consistent formatting throughout
- A total row at the bottom where relevant
If you find data that doesn’t fit cleanly into the columns, flag it in a separate notes column rather than dropping it.
If anything looks like a data error (duplicate entries, impossible values, missing required fields), flag it in a separate column before I review.
The PDF is attached.
Two instructions carry the real weight: asking Claude to flag uncertain data in a notes column, and asking it to surface potential errors before you review. Without those, Claude makes quiet judgment calls about messy data and you never know. With them, you see exactly where it was uncertain before trusting the output.
💡 Tips and Tricks Worth Knowing
The poster now runs this workflow on three document types every week. Here’s how each plays out:
- Financial statements. Upload a PDF annual report, ask for revenue, expenses, and margin by quarter in a comparison table. Used to take 45 minutes of manual data entry. Now takes 2 minutes plus a verification read.
- Research papers with tables. Upload the study, extract the data into a filterable spreadsheet. Especially useful when a single PDF has multiple tables you want consolidated into one place.
- Contracts with pricing schedules. Upload the contract, ask Claude to extract every pricing clause, rate, and escalation term into a structured table. A 40-page document becomes a 10-row spreadsheet you can actually compare against other contracts.
A few caveats the author flags:
- PDF quality matters. Clean digital PDFs work reliably. Scanned PDFs with poor resolution sometimes miss data or misread numbers. For scanned documents, add “this is a scanned document, flag anything you’re uncertain about” and verify column by column before using.
- First pass isn’t always perfect. Expect one round of corrections along the lines of “column 3 should be split into two columns.” Still faster than manual extraction by a wide margin.
- Complex multi-page PDFs with inconsistent formatting sometimes need the extraction broken into sections. Tell Claude to focus on specific pages for better results on messy documents.
One community commenter made a sharp point: the dangerous errors are usually the clean-looking ones. The rows that appear fine but are just slightly wrong. The error-flagging instructions exist exactly to catch those before you act on the data.
🚀 Try It This Week
If you only test this once, try it on whichever PDF you most recently had to manually copy data out of. That first moment when a clean spreadsheet comes back in 40 seconds is when the mental model shifts for good.
The full thread, including extra tips from the community, is worth reading in the original r/PromptEngineering post.
I didn’t realise Claude could extract data from PDFs and turn it into a working spreadsheet. Been copying numbers manually for years.
by u/Professional-Rest138 in PromptEngineering