What to do
Treat repeated invoice numbers as duplicate candidates in context, not automatic deletion instructions. Include supplier identity and inspect dates, amounts, currency, and document version. Two suppliers can legitimately use the same short invoice number.
A corrected source may reuse an identifier while changing the document, which needs an explicit review decision.
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 |
|---|---|---|
| Different issuers | Example A invoice 101; Example B invoice 101 | Do not remove either solely because the numbers match. |
| Resent source | Same issuer and INV-101 arrive twice with identical visible content | Review intake and import history before selecting one accepted record. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Supplier identity | Reviewed issuer reference rather than only a display-name guess. |
| Invoice number | Exact identifier preserving prefixes and zeros. |
| Version and comparison | Dates, amount, currency, and correction notes used for review. |
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
- Form candidate groups using supplier and invoice reference.
- Compare original documents and accepted import history.
- Record retain, exclude, replace, or unresolved decisions with reasons.
Errors to avoid
- Do not remove leading zeros before forming comparison keys without a documented rule.
- A candidate match is not a confirmed duplicate payment.
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