What to do
Track the original attempt, failure, retry, and accepted result for each source file. A retry is another processing attempt, not automatically a new invoice. Merge only the reviewed result selected for each source into the final destination set.
A second download of completed files can repeat records already included in the first export.
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 |
|---|---|---|
| Failed file retried | Batch has A complete and B failed; retry later completes B | Add reviewed B once, preserving its link to the failed attempt. |
| Whole batch repeated | A and B both appear in another export | Compare before appending; do not add A a second time automatically. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Source identity | Stable source filename plus reviewed invoice identity. |
| Attempt reference | Attempt number or export reference in your review manifest. |
| Accepted result | Explicit decision selecting the result to use. |
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 outcomes for all original source files.
- Identify exactly which files need retry and why.
- Reconcile the combined accepted set with the original manifest before import.
Errors to avoid
- Do not delete failure evidence merely because a later attempt succeeds.
- A new processing timestamp does not make the same invoice a new transaction.
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