What to do
Group amounts by their confirmed currency before reporting totals. A numeric sum across currencies does not produce a meaningful combined amount. Retain unresolved currency values in an exception group rather than silently assigning a default code.
Any currency conversion needs an explicit rate source, date, and approved policy outside this extraction workflow.
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 |
|---|---|---|
| Mixed currencies | Invoice A: USD 100.00; Invoice B: EUR 100.00 | Report separate USD and EUR subtotals rather than one 200.00 total. |
| Ambiguous symbol | Invoice C: $50.00 with no confirmed currency | Keep it out of a confirmed USD subtotal until reviewed. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Confirmed currency | Reviewed currency code established from source evidence. |
| Invoice amount | Reviewed amount paired with that currency. |
| Currency exception | Reason a symbol or code could not be resolved. |
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
- Review currency identity before building grouped totals.
- Keep unresolved and missing currencies visible as exceptions.
- Record any later conversion independently from the original extracted amounts.
Errors to avoid
- Do not use a supplier’s country as the sole currency rule.
- Do not label an unconverted mixed-currency sum as revenue or spending in one currency.
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