PDF to Excel, with evidence

PDF to Excel you can verify.

Recover table structure, trace reviewable values back to the PDF, and stop when the result cannot be trusted.

No customer logos. No accuracy claims. Just current-build evidence.
One public tagged PDF, rerun on the current build.The recovered counts match the document's own semantic Table / TR / TD structure.
10Tables
30Rows
150Cells
Why normal conversion is not enough

The dangerous errors are the ones that still look successful.

A workbook can open cleanly and still contain structural mistakes.

01

Row shift

A value can land in the wrong row without making the workbook look obviously broken.

Illustrative failure mode
02

Cross-page break

Continuation rows and repeated headers can become real data errors after conversion.

Illustrative failure mode
03

Needs review

A single uncertain value can matter more than a spreadsheet that is 99% visually correct.

Illustrative failure mode
Real business file · Sanitized

A borderless supplier quotation, checked against its own arithmetic.

This quotation has no table lines. In the earlier conversion, numeric fields were fragmented: amounts spread across multiple columns, currency symbols became separate cells, and the grand total did not sit on the Total row.

19Line items checked
$71,816.00PDF total matched
×No table lines
✓Arithmetic self-check

What the current route proves on this file

Each priced line must satisfy Quantity × Unit Price = Amount, and the line amounts must add up to the document total. On this sanitized quotation, all 19 line items reconcile and the total is $71,816.00, matching the PDF.

If that arithmetic proof does not hold, the text-aligned priced-table route does not return this table. PDflow falls back to the existing routes and surfaces a warning instead.

Limit: this route has been tuned and validated on two real priced documents so far. That is evidence of feasibility, not proof of generality. It currently targets quotations and invoices with Quantity, Unit Price, and Total/Amount-style headers.

Real source check

Click a value. See exactly where it came from.

This is current-build output from a public tagged PDF — not a mockup.

Public tagged PDF used in the PDflow source-linked review
Real public sample

Current build · Tagged Structure

Page 6 · source coordinates captured during extraction
Evidence shown here comes from the current build: source page + bounding box + extraction method.
What this provesPDflow can preserve provenance for this supported tagged-PDF case.
What this does not proveIt is not an accuracy percentage and does not imply every PDF behaves the same way.
Real test

If the structure cannot be trusted, PDflow stops.

A public annual report failed PDflow's structure checks in the current build. No Excel file was produced.

01Structure check
02Confidence insufficient
03No output
Online Beta workflow

What happens when you run a PDF online.

The Online Beta is automatic: your browser uploads one PDF to the hosted worker, PDflow selects a supported route, runs its checks, and returns READY, REVIEW, or NO OUTPUT.

Step 01

You upload one PDF to the Online Beta.

The hosted worker receives the PDF and queues it if another conversion is already running.

ScopeIs my PDF a fit?

Built for

  • Supplier quotations
  • SKU / price tables
  • Catalog tables
  • Multi-page business tables

Not built for

  • General PDF editing
  • Signing
  • Watermarks
  • Merge / split
Manual sample review

Have a difficult PDF the Online Beta cannot handle?

If the Online Beta returns NO OUTPUT or REVIEW, or the Excel still looks wrong, send a redacted sample and a short note. This is a separate manual review flow.

A manual review of the current-build resultWhat PDflow recovered reliablyWhat failed or still needs review
01Contact
Used only to return your test result.
02PDF sample
No file selected
03Failure mode
What makes this PDF difficult?
04Permission
Ready to submit for manual review?Your email is used only to return this review result.
Redacted samples are welcomeUsed only for PDflow testing and evaluationContact email is used only to return the result