What to do
Preserve the sign and description of a negative row. It may represent a return, rebate, or adjustment within an otherwise positive invoice. Keep the original notation, including parentheses, until a reviewer has established the normalized representation.
The sign can appear in the quantity, unit price, amount, or a separate credit label. Inspect the complete row.
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 |
|---|---|---|
| Negative amount | Return of example part: amount -15.00 | Retain the reduction; do not convert it to positive 15.00. |
| Double-sign risk | Quantity -1; unit price 15.00; printed amount -15.00 | One negative row is represented; do not negate the amount again. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Raw quantity | Printed quantity including any minus sign. |
| Raw amount | Printed amount with parentheses or sign retained. |
| Adjustment wording | Description explaining return, credit, or reduction 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
- Locate the sign in each relevant source column before normalizing.
- Keep the raw notation and a separate reviewed signed value.
- Check whether the line is already included in the printed subtotal.
Errors to avoid
- Do not apply a second negative sign because the description also says Credit.
- A credit document’s display convention may differ from an adjustment row.
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