What to do
Retain the printed document title when an intake set contains proforma and final invoices. Similar amounts, parties, and item descriptions do not make them interchangeable. Keep the source status visible until the responsible reviewer decides which document belongs in the final register.
This is a document-routing check, not a statement about tax or legal treatment in any jurisdiction.
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 |
|---|---|---|
| Two stages | Proforma PF-8 for 500.00; final invoice INV-98 for 500.00 | Keep both sources traceable; do not post both automatically. |
| Draft watermark | Invoice draft; unassigned number | Flag the document’s status instead of inventing a final identifier. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Document title | Exact title, including Proforma, Draft, or Invoice. |
| Document number | Identifier printed for this specific source. |
| Related final reference | Explicit link to another document if printed. |
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
- Check the heading, watermark, and footer for status wording.
- Record the file and document type in the intake manifest.
- Have the reviewer select the appropriate source before destination import.
Errors to avoid
- Do not infer final status solely from a supplier logo or a total.
- Do not delete a preliminary source without the agreed records process.
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