What to do
Retain supplier item codes, pack descriptions, quantities, price bases, and return rows. Wholesale tables often contain several identifiers and unit conventions. A consistent review table needs those relationships preserved before any conversion to inventory units.
The suggested structure is a review target, not a guarantee that complex items become separate native CSV rows.
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 |
|---|---|---|
| Pack-based price | 3 cases, 12 units per case, 24.00 per case | Preserve 3 cases and the pack description; any pieces conversion is a separate rule. |
| Return row | Returned case, quantity -1, amount -24.00 | Retain the negative row rather than dropping it as an anomaly. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Supplier item code | Exact printed SKU or part reference as text. |
| Pack and billed quantity | Printed quantity with pack or unit wording. |
| Price and adjustment detail | Price basis, discount, and signed row amount as shown. |
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 the supplier code and pricing-unit columns.
- Compare extracted row alignment on a table with both sales and returns.
- Normalize item data in a separate reviewed sheet if the destination needs it.
Errors to avoid
- Do not assume a case has a universal unit count.
- Do not convert every digit-heavy code into a number.
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