What to do

Review the document type, printed sign, and column meaning before producing a normalized signed amount. Parentheses, a minus sign, and a Credit label can each carry context. Keep the raw representation so later reviewers can reconstruct the decision.

This check covers document-level sign normalization, distinct from aligning individual negative item rows.

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
Parenthesized amountAdjustment (25.00) in a reduction columnPreserve the notation and confirm its role before normalizing.
Credit note plus minusCredit note amount -25.00Do not automatically apply another negative sign merely because it is a credit note.

Suggested review columns

ColumnDefinition or instruction
Raw amount notationSource amount including sign or parentheses.
Document and column roleInvoice, credit, balance, or adjustment wording.
Reviewed signed amountDestination value with an explicit reviewed sign 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

  1. Read the document title and amount-column labels together.
  2. Keep raw and normalized values in separate staging columns.
  3. Confirm the receiving system’s representation before import.

Errors to avoid

  • Do not normalize solely from the presence of the word Credit.
  • Do not strip parentheses and lose the only sign evidence.

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: Financial fact-level OCR evaluation: FinCriticalED. 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