What to do
Establish whether the printed unit price is gross or already discounted. Retain the discount column and printed net line amount as separate evidence. A displayed percentage may describe a reduction already reflected in the unit price or amount.
Read the price column heading before attempting row arithmetic.
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 |
|---|---|---|
| Gross price | 2 × 50.00 less 10%; net 90.00 | The reduction is already represented in the net 90.00. |
| Net unit price | 2 × net price 45.00; discount info 10%; amount 90.00 | Do not subtract another 10% from 90.00. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Printed unit price | Value as printed, retaining gross or net heading. |
| Row discount | Printed row reduction with percent or monetary unit. |
| Net line amount | Printed amount after the row discount, when labelled. |
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
- Preserve gross/net qualifiers in the schema description and review sheet.
- Match each discount to its own item rather than the following row.
- Compare with the printed line amount and hold unexplained differences.
Errors to avoid
- Do not apply a header discount to every item unless the source explicitly does so.
- A percent field and a currency field cannot be combined without identifying their basis.
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