Keep the purchase detail
Descriptions, product references, units and prices belong together.
Invoice line items, made useful
A clearer route from supplier PDFs to reviewable Excel and CSV rows. Keep descriptions, quantities and prices together, with the source close at hand.
Explore a synthetic example. File processing is not available yet.
Descriptions, product references, units and prices belong together.
Follow a row back to its page and keep missing values visible.
A flat export is easier to filter, group and compare in a spreadsheet.
01 / Line items
Switch views, inspect the two flags, and download a fixed example. These are prepared data, not the result of a PDF parser.
↔ Scroll horizontally to see every column. You can also use the keyboard.
| # | Description | Qty | Unit price | Net amount | PDF page | Reference |
|---|---|---|---|---|---|---|
| 01 | 12 | €8.50 | €102.00 | 1 | P-0042 | |
| 02 | 4 | €14.00 | €56.00 | 1 | BX-010 | |
| 03 | 3 | €18.00 | €48.60 | 1 | LB-220 | |
| 04 | 1 | €35.00 | €35.00 | 1 | SV-001 | |
| 05 | — | €9.00 | €9.00 | 1 | — | |
| 06 | -2 | €8.50 | -€17.00 | 1 | P-0042 |
Select a row to see the review note.
Synthetic example. No user file is opened, uploaded or analysed.
02 / How it works
The product direction is structured invoice data with human review. The example illustrates the intended output; it does not validate extraction quality.
Handle wrapped descriptions without treating every printed line as a new item.
Distinguish quantity, unit price, line discounts and net amounts.
Keep document and page references beside the values you need to check.
Preserve identifiers as text and document decimals, currency and missing values.
03 / PDF
Explore a synthetic example. File processing is not available yet.
Blur, rotation and page breaks can change what is readable. OCR support is still to be evaluated.
A matching total alone does not prove that every line is correct. Document-level charges need separate treatment.
If a native export or useful invoice XML is available, it may be the better starting point.
04 / How it works
Supported files, limits and data handling must be defined before real processing opens.
Check ambiguous values and follow their source. No silent replacement of missing data.
Take reviewed data into Excel or CSV. No bookkeeping entries or ERP posting.
Build a list of items, quantities and supplier prices for a specific review.
Compare like-for-like references and units, instead of comparing invoice totals.
Prepare a traceable table from a historical lot, without changing accounting software.
InvoiceLineLab needs to earn its place through useful review and export. It is not the only way to get a table.
Prefer the structured source when it already includes the detail you need.
A good option for readable PDF tables. Expect cleanup when layouts or wrapped rows vary.
MicrosoftA free, local tool for text-based PDF tables. It does not recognise scanned documents.
Tabula05 / Pricing
A proposed model to evaluate. The service and purchases are not open.
Pricing →No. This website shows a fixed, interactive example. It does not receive or process your documents.
No. The supplier, invoice and rows are synthetic. The controls only change prepared data on this page.
Invoice lines: descriptions, references, quantities, units, prices, discounts and net amounts when present, plus invoice and page context.
That remains to be evaluated. A scanned image and a text-based PDF need different handling. No OCR accuracy is claimed.
Synthetic example. No user file is opened, uploaded or analysed.