What to do
Keep a receipt’s payment evidence separate from the invoice’s charge information. Some documents combine both roles; others reference an invoice elsewhere. Record what is actually printed rather than assuming that a familiar layout proves payment or creates a second charge.
A card authorization code and a supplier invoice number are different identifiers.
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 |
|---|---|---|
| Receipt linked to invoice | Receipt RC-5; paid 80.00 for INV-5 | Keep receipt and invoice references separate; link them for review. |
| Invoice without paid status | Invoice INV-6; payment instructions only | Instructions do not establish that payment occurred. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Document title | Exact receipt or invoice heading and status wording. |
| Document reference | Printed identifier belonging to this source. |
| Payment evidence | Printed paid amount, payment date, and method where 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
- Read the document status and payment section independently.
- Keep payment references out of the invoice-number column.
- Review whether another source already represents the underlying charge.
Errors to avoid
- Do not infer paid status from the presence of bank details.
- Do not count a receipt and its referenced invoice as two purchases automatically.
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