What to do

A purchase order and an invoice describe different stages of a transaction. Extract their own identifiers, quantities, and amounts separately if you plan to compare them. A shared product description does not prove that ordered and billed quantities match.

This guide prepares evidence for a human comparison; Parzable does not provide an automatic purchase-order matching control.

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
Partial billingPO requests 10 units; invoice bills 4 unitsRetain both quantities and their source roles; do not replace 4 with 10.
Reference absentInvoice has no printed PO numberFlag the missing link rather than choosing the closest known order.

Suggested review columns

ColumnDefinition or instruction
Source typePrinted Purchase order or Invoice heading.
Source numberIdentifier belonging to the current document.
Referenced orderExplicit purchase-order reference on the invoice, if present.

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. Keep orders outside a batch intended only for invoice records.
  2. Capture explicit matching references without inventing absent values.
  3. Compare reviewed item quantities and references in a separate staging sheet.

Errors to avoid

  • Do not substitute ordered quantities for billed quantities.
  • A matching total alone does not establish a correct order-to-invoice match.

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 and receipt field roles: Amazon 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