What to do
Preserve the invoice total, payments shown, and remaining balance as separate facts. The source may show a partial payment without describing every historical payment event. Capture printed information and use the reviewed payment record for any broader reconciliation.
A balance-due summary can be smaller than the underlying charge even when the invoice itself is unchanged.
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 |
|---|---|---|
| One payment shown | Total 900.00; paid 300.00; due 600.00 | Keep all three values under distinct field names. |
| Unexplained balance | Total 900.00; due 550.00; no adjustment detail | Hold the unexplained difference rather than inventing a 350.00 payment. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Invoice total | Full charge shown on this invoice. |
| Payments shown | Printed paid amount or payment entries with their labels. |
| Remaining balance | Explicit balance or amount due after displayed adjustments. |
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
- Inspect the summary for payment, credit, and balance labels.
- Preserve raw values before performing a separate arithmetic check.
- Review the destination mapping so invoice value is not confused with outstanding balance.
Errors to avoid
- Do not infer a payment date when only a paid amount is printed.
- Do not create a negative invoice record simply to force the balance to match.
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 and receipt field roles: Amazon 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