What to do
Separate extraction status from review status. A completed result may still contain an unreadable reference or unresolved total. Give each held record a reason, an owner, and the next action so exceptions do not disappear inside a successful batch count.
The queue described here is a review worksheet, not an automatic Parzable approval-routing feature.
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 |
|---|---|---|
| Missing evidence | Extraction complete; invoice number clipped in source | Hold for a replacement source, with an assigned follow-up owner. |
| Corrected record | Reviewer confirms a misread decimal against the original | Record the correction and mark ready only after required checks pass. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Review status | Ready, held, or not yet reviewed in your worksheet. |
| Exception reason | Specific unresolved field or source issue. |
| Owner and next action | Responsible reviewer and evidence needed to proceed. |
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
- Define clear review statuses before processing the batch.
- Record field-level exception reasons instead of generic Failed notes.
- Reconcile ready and held records with the complete source set before handoff.
Errors to avoid
- Do not equate Completed in the extractor with Approved in your review process.
- Do not clear a hold merely because the file can be opened.
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