What to do
Retain a chain linking the source document, extraction attempt, exported row, review decision, and destination reference. The chain should survive filename changes and corrections. A processing timestamp helps locate an attempt but does not replace the source invoice identity.
Choose the minimum references needed to reopen the exact evidence behind a questioned value.
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 |
|---|---|---|
| Correction tracked | INV-20 total corrected from 210.00 to source value 201.00 | Retain the original result, correction reason, and accepted value. |
| Filename changed | invoice.pdf becomes clientA-002.pdf | Keep the mapping so the export still leads to the received source. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Source reference | Stable file or intake identifier used to reopen the original. |
| Export reference | Batch/file reference identifying the proposed output row. |
| Destination reference | Identifier assigned after a reviewed record is imported. |
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
- Record source identity before extraction and preserve the original.
- Log corrections separately from the unchanged extraction evidence.
- Add destination references when import succeeds and retain open exceptions.
Errors to avoid
- Do not use row position alone as a stable source identifier.
- Do not discard original values without a review history.
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: CSV import and type handling: Microsoft Support. 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