Descriptions that stay together
Handle wrapped descriptions without treating every printed line as a new item.
InvoiceLineLab / How it works
Designed around the line, not just the document
The product direction is structured invoice data with human review. The example illustrates the intended output; it does not validate extraction quality.
Amounts with their meaning
Distinguish quantity, unit price, line discounts and net amounts.
A source for every review
Keep document and page references beside the values you need to check.
Excel and CSV, with clear columns
Preserve identifiers as text and document decimals, currency and missing values.
Difficult invoices deserve visible limits
Scans and broken tables
Blur, rotation and page breaks can change what is readable. OCR support is still to be evaluated.
Discounts, credits and totals
A matching total alone does not prove that every line is correct. Document-level charges need separate treatment.
Structured data first
If a native export or useful invoice XML is available, it may be the better starting point.
The workflow we are building toward
Bring a supplier invoice
Supported files, limits and data handling must be defined before real processing opens.
Review the lines in context
Check ambiguous values and follow their source. No silent replacement of missing data.
Export a useful table
Take reviewed data into Excel or CSV. No bookkeeping entries or ERP posting.
See the rows. Keep the context.
Explore the example →Synthetic example. No user file is opened, uploaded or analysed.