What to do
Create an explicit mapping between source column meaning and the destination’s required fields. Matching column positions is unsafe when exports or templates change. Some destination fields, such as account codes, are reviewed business mappings rather than facts printed on the invoice.
CSV output does not by itself establish compatibility with an accounting system’s import format.
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 wording | Source Invoice number maps to target BillReference | Map by documented meaning and verify a sample imported record. |
| Absent master data | Target requires VendorID; source only has Vendor name | Use a reviewed lookup; do not invent an identifier from the invoice text. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Source column | Exact exported header and its meaning. |
| Destination column | Required target field from its current template. |
| Mapping rule | Reviewed rename, transformation, or manual-assignment rule. |
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
- Obtain the current destination template and required-field instructions.
- Document every mapping and any unresolved transformation.
- Test a small reviewed set and inspect resulting destination records.
Errors to avoid
- Do not map Total to Amount due solely because both contain amounts.
- Do not assume the target column order matches the source order.
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