What to do
Compare logical CSV records with the completed-file list, then account for failed, held, and retried sources separately. Parzable’s batch download includes completed results; the presence of a CSV does not establish that every received file is represented.
Use a CSV-aware count because a quoted description can contain a line break.
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 |
|---|---|---|
| Expected exclusion | 15 sources; 13 complete; 2 failed; 13 exported rows | The export count matches completed files, while two sources remain unresolved. |
| Unexpected omission | 13 complete but 12 exported rows | Compare filenames and identify the missing or misparsed record. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Files received | Count from the independent intake manifest. |
| Files completed | Observed successful extraction count. |
| Export records | Logical data-record count excluding the header. |
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
- Keep the expected source list outside the extraction output.
- Count parsed CSV records and compare the filename set.
- Resolve differences and document held sources before marking the batch finished.
Errors to avoid
- Do not count CSV header rows as invoices.
- Do not treat physical text-line counts as record counts when fields contain newlines.
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