What to do
Keep the supplier’s invoice identifier and the buyer’s purchase-order reference in separate fields. They identify different records. A PO reference can occur on several invoices, so substituting it for an invoice number can create misleading duplicate candidates.
Look for the label attached to each value rather than selecting the longest number near the page heading.
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 |
|---|---|---|
| Both references printed | Invoice INV-0042; Your order PO-730 | Retain INV-0042 and PO-730 in separate columns. |
| PO repeated across invoices | INV-0042 and INV-0043 both refer to PO-730 | Two invoice records can legitimately share this purchase-order reference. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Invoice number | Printed supplier invoice identifier, preserving prefixes and zeros. |
| PO number | Printed purchase-order reference, not the invoice identifier. |
| Vendor | Name of the business issuing this document. |
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
- Locate Invoice, Invoice no., or an equivalent explicit document label.
- Find the PO or customer-order label independently and preserve its exact value.
- Compare the reviewed invoice key with prior records using supplier plus invoice number.
Errors to avoid
- Do not copy a purchase-order number into a missing invoice-number field.
- A repeated PO does not by itself establish a duplicate invoice.
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-field reference: Amazon Textract 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