What to do
Record which field definitions were used for each batch when you change a schema. A rename, new description, or changed field meaning can affect both extraction and downstream imports. Keep stable meanings and test revisions on representative documents before replacing an established workflow.
Version notes are an external working record here, not a claim that Parzable provides a schema-version history 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 |
|---|---|---|
| Rename only | Invoice ID renamed Invoice number with unchanged meaning | Update the destination mapping explicitly and test the header. |
| Meaning changed | Total changes from grand total to balance due | Treat it as a semantic change; do not merge historical values under one meaning. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Schema version | Your recorded version label and effective date. |
| Field change | Old and new name, meaning, or description. |
| Affected batches | Batches requiring a different mapping or controlled rerun. |
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 the current field dictionary before editing a working schema.
- Test a small sample using the revised descriptions.
- Document compatibility and rerun only sources that require the new definition.
Errors to avoid
- Do not assume two columns mean the same thing because their names match.
- Do not overwrite historical exports just to match the newest schema.
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