What to do

Keep units, quantities, actual weights, and printed row amounts attached to the correct ingredient or supply item. Different rows can use cases, kilograms, or individual pieces. Preserve shortage credits or substitutions as printed rather than completing them from a standing order.

An order sheet and an invoice are separate sources; ordered quantity does not establish delivered or 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.

CaseFictional source excerptReview decision
Actual weightExample produce 7.4 kg at 2.00 per kg; 14.80Keep the weight and its unit rather than treating 7.4 as cases.
Shortage creditOrder 5 cases; invoice 4 cases plus shortage noteExtract the billed 4 and retain the note separately.

Suggested review columns

ColumnDefinition or instruction
Item and supplier codePrinted product description and identifier.
Billed quantity and unitQuantity with weight, case, or piece unit as shown.
Credit or substitution wordingPrinted adjustments retained with the relevant item.

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

  1. Read units for each row instead of applying one unit to the whole table.
  2. Keep original supplier descriptions before assigning internal ingredient categories.
  3. Review returned goods and credits against the printed invoice, not the expected order.

Errors to avoid

  • Do not infer inventory consumption or food-cost categories from invoice text alone.
  • Do not add a shortage note as a positive 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