What to do
Give each column a distinct meaning and name before converting rows into records. Repeated headers such as Total can cause a converter to overwrite one value with another. Preserve the original and resolve the meanings rather than silently adding arbitrary suffixes.
Check headers after trimming accidental spaces and comparing case, as well as checking their literal text.
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 |
|---|---|---|
| Two totals | Headers Total, Total contain subtotal and grand total | Rename only after confirming which source fact each column holds. |
| Whitespace collision | Headers Vendor and Vendor followed by a space | Flag the collision before lookup or JSON conversion. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Original header | Raw column label from the export. |
| Column position | Position needed to distinguish repeated labels. |
| Resolved meaning | Reviewed unique field name based on source evidence. |
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
- Inspect the full header row before merging or converting exports.
- Compare repeated columns with the source schema and sample values.
- Resolve mappings and retain the original header-to-column record.
Errors to avoid
- Do not let a dictionary conversion keep only the last repeated key.
- A unique technical suffix does not establish a column’s business meaning.
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 format conventions: RFC 4180. 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