What to do
Keep the print job reference, run quantity, price basis, setup, finishing, and delivery charges distinguishable. Prices per sheet, per item, or per thousand can produce very different arithmetic. Preserve specifications with the job they describe.
A specification such as paper weight or page count is not automatically the billed quantity.
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 |
|---|---|---|
| Per-thousand pricing | 2000 leaflets; price 30.00 per 1000; print charge 60.00 | Preserve the price basis instead of multiplying 2000 by 30.00 directly. |
| Setup added | Print 60.00; setup 20.00; finishing 10.00 | Keep each charge row distinct for a reviewed 90.00 summary. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Job reference and specification | Printed job ID, product description, and relevant specification. |
| Run quantity and price basis | Billed quantity with per-unit or per-thousand wording. |
| Setup and finishing charges | Separately printed one-time or additional charge rows. |
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
- Identify quantity, specification, and pricing basis from their labels.
- Keep setup and finishing rows separate from run-based charges.
- Compare printed row amounts with the job summary before destination mapping.
Errors to avoid
- Do not use paper weight as the quantity column.
- Do not assume a repeated job specification represents a second charge.
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: Document and invoice structures: Microsoft 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