What to do
Align columns by reviewed header meaning, keep one header row, and review overlap between source exports before appending data. A repeated header and a repeated invoice are different problems. Preserve export provenance so any overlap can be explained.
Two batches can have the same number of columns in a different order, or share records after a retry.
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 |
|---|---|---|
| Different order | Export A: Vendor,Total; export B: Total,Vendor | Map by meaning before appending; do not concatenate raw positions. |
| Overlapping retry | A second export includes an invoice already present in the first | Review the source identity and select the accepted record once. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Export reference | Filename and batch identity of each source CSV. |
| Header mapping | Reviewed correspondence between source and combined columns. |
| Overlap decision | Which candidate repeated records are retained or excluded and why. |
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
- Validate each file’s headers and record widths independently.
- Document the canonical column layout and map each export to it.
- Review overlap, then reconcile combined records with accepted source files.
Errors to avoid
- Do not remove every repeated invoice number without considering supplier identity.
- Do not delete a data row merely because a value resembles a column heading.
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