What to do

A printed item amount may include tax or exclude it. Capture the source label alongside the amount, and keep any tax breakdown separately. This prevents adding a tax summary again to item amounts that already include it.

The purpose here is faithful transcription and reconciliation, not choosing tax rates or accounting treatment.

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
Tax includedItem gross 120.00, includes tax 20.00The gross remains 120.00; adding the displayed 20.00 again is wrong.
Tax separateItem net 100.00; tax summary 20.00; total 120.00Keep net and tax in distinct columns.

Suggested review columns

ColumnDefinition or instruction
Printed line amountAmount with its source heading preserved.
Tax basis wordingText such as including tax, excluding tax, net, or gross.
Printed tax detailTax amount or rate shown for the item, without inference.

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. Read table and summary headings together to establish the displayed basis.
  2. Preserve qualifiers instead of normalizing every amount to a column called Total.
  3. Reconcile using the source presentation and refer unresolved treatment to the reviewer.

Errors to avoid

  • Do not assume every invoice uses net item prices.
  • A tax breakdown can be informational rather than an additional charge.

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 structure: Microsoft Document Intelligence 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