What to do
Keep quantity, pricing basis, unit price, and printed line amount attached to the same description. Multiplication can reveal a mismatch, but only after you establish the pricing unit, discounts, and whether the amount includes tax.
A correctly read set of numbers can still be wrong when neighbouring rows have been interleaved.
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 |
|---|---|---|
| Simple row | 3 each × 20.00; printed line amount 60.00 | The displayed relationship is consistent. |
| Price per pack | Quantity 12 each; price 24.00 per dozen; line 24.00 | Do not multiply 12 by 24 without accounting for the price basis. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Item description | Full printed description and item code for this row. |
| Quantity and pricing unit | Printed quantity with its unit or price basis. |
| Printed line amount | Amount shown for the row; do not manufacture a missing value. |
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
- Trace each row horizontally on the source before accepting extracted columns.
- Read pricing-unit and discount headings that affect the displayed relationship.
- Flag an unexplained difference instead of overwriting a printed amount.
Errors to avoid
- Do not use a subtotal carried forward as an item price.
- A matching multiplication does not prove the item description belongs to that row.
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