Depreciation schedules
PDF to Excel is the easy half. The columns are the hard half.
You can already convert a PDF to a spreadsheet — Acrobat does it, and the result is famously thirty columns collapsed into one. The problem was never extracting text; it's knowing that the fourth number on a row is prior depreciation and the fifth is current.
Layout-aware, not just text extraction
A depreciation schedule has no standard layout. Every suite prints its own, some print two variants, and scanned copies drift. We read by meaning: which column is basis, which is prior depreciation, which activity a block of rows belongs to — and score each row for how confident that reading is.
The output isn't 'an Excel file', it's an import file
A spreadsheet you still have to reshape is most of the work still to do. The file you get is already in your destination's exact contract — Drake's positional order, Lacerte's CSV, Intuit's 17 columns — so the next step is running the import, not another hour of cleanup.
And it tells you when it's wrong
A generic converter has no idea whether it dropped a row. This one checks its own output against the totals printed on the document and refuses to hand you a file that doesn't tie.
Questions
- Can I get a plain spreadsheet instead?
- The destination file is a spreadsheet — you can open it, read it, and edit it before importing. It's simply already shaped the way your software expects.
- Does it handle multi-page schedules?
- Yes, including rows that wrap across a page break — a common source of a total that doesn't tie in hand conversions.