What to do
Keep the quantity’s unit and the unit-price basis visible. Each, case, hour, kilogram, and a price per hundred are not interchangeable. Preserve the source notation before attempting any conversion for inventory or reporting.
An abbreviation should not be expanded into a conversion factor unless the source or an approved item record establishes it.
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 |
|---|---|---|
| Case-based sale | 4 cases; 18.00 per case; 72.00 | Retain quantity 4 and unit cases. |
| Unstated pack size | 2 CTN; no pieces-per-carton detail | Retain CTN; do not invent a count of individual pieces. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Quantity | Printed quantity without converting its scale. |
| Unit of measure | Printed unit or abbreviation adjacent to the quantity. |
| Price basis | Printed unit or pack basis attached to the unit price. |
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
- Read the table headings as well as the individual quantity cells.
- Keep pack size and quantity in separate columns if both are printed.
- Document any later approved conversion independently of the raw extraction.
Errors to avoid
- Do not assume a carton always contains the same number of pieces.
- A supplier’s item code may contain digits that are unrelated to the quantity.
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