What to do

Capture the explicit currency code where the document provides it, and retain the original symbol as evidence when it does not. Symbols such as $ are shared by multiple currencies. An address alone is not enough to select a currency code.

Some invoices display a transaction currency and a secondary reference amount. Label those values separately.

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.

CaseFictional source excerptReview decision
Code is explicitTotal CAD 420.00; approximate USD equivalent 305.00Keep CAD with the invoice total; do not replace it with the reference currency.
Symbol onlyTotal $420.00; no code or currency wordingRetain $ and hold currency-code selection for confirmation.

Suggested review columns

ColumnDefinition or instruction
Transaction currencyExplicit code attached to the invoice amounts; preserve unresolved symbols.
Printed currency textOriginal symbol or currency wording beside the total.
Reference amountSeparately labelled converted or informational amount, if shown.

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

  1. Inspect column headings, summary labels, and currency notes together.
  2. Keep any conversion illustration separate from the source transaction amount.
  3. Group reviewed reports by confirmed currency before summing amounts.

Errors to avoid

  • Do not assume every dollar sign means USD.
  • Do not add amounts expressed in different currencies into a single unqualified total.

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: Invoice-field reference: Amazon Textract documentation. 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