What to do
A repeated Description / Quantity / Amount header is table structure, not a purchased item. Identify it from the source before excluding it. A genuine product can contain words such as “description” or “total,” so word matching alone is unsafe.
Headers may reappear after a page break or between shipment and department sections.
Two worked review cases
These cases are fictional teaching data, not measured extraction results. Use the source excerpts to practise deciding what belongs in the reviewed output.
| Case | Fictional source excerpt | Review decision |
|---|---|---|
| Structural header | Page 2: Description | Quantity | Unit price | Amount | Classify as a repeated heading and exclude from billed-item count. |
| Genuine description | Item: Total care service; amount 45.00 | Retain the priced item; the word Total alone does not make it a summary. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Row text | Complete candidate row for comparison with the source. |
| Row role | Reviewer classification: header, item, subtotal, or unresolved. |
| Source page | Page reference recorded in the review worksheet. |
These are suggested staging-sheet columns. Printed facts can inform field descriptions in Parzable’s Schemas view; source references, review statuses, and decisions must be supplied by your own review process.
A practical review sequence
- Compare the candidate with the printed column heading and its position.
- Check whether it has a genuine item code, quantity, and charge.
- Recount billed items after classification and retain an explanation for exclusions.
Errors to avoid
- Do not delete rows merely because they contain familiar header words.
- A subtotal row is a different structural role from a repeated column heading.
Use the case worksheet with a small sample
Download this page’s worked-case worksheet. It contains the two fictional cases above and a blank row for your own review exercise. Keep any real source documents in your agreed storage process.
For the broader product workflow, see the related guide. Parzable accepts PDF/image inputs and downloads CSV. Suggested structures here are review targets; nested item rows, automatic approvals, and destination integrations are not guaranteed.
Reference and scope
Further reading: Invoice structure: Microsoft Document Intelligence documentation. External documentation provides background for the topic; it does not establish Parzable’s implementation or performance. References checked 18 October 2026.
Examples and review decisions on this page are authored illustrations. Confirm unresolved business, payment, or accounting decisions through the responsible reviewer.
Put the workflow to work
Try your own invoice in Parzable
Create an account, define a schema, and test a small sample. Review extracted values before using them. See current plans and page allowances.
Try Parzable