What to do
An account number can identify a continuing customer relationship, while an invoice number identifies a specific billing document. Capture both under their printed labels. Reusing an account number across monthly invoices is expected in many workflows and is not a duplicate-invoice finding by itself.
Statements and utility bills may also have service-agreement identifiers distinct from both references.
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 |
|---|---|---|
| Monthly bills | Account AC-8; invoice SEP-8 and later OCT-8 | Keep the same account with two different invoice identities. |
| Several account references | Customer account AC-8; service agreement SA-2 | Preserve each role rather than choosing one generic Number field. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Account number | Persistent account identifier as printed, retained as text. |
| Invoice number | Reference belonging to this specific billing document. |
| Service reference | Separately labelled service or agreement identifier when present. |
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 labels and establish the role of each identifier.
- Keep identifiers as strings through CSV import.
- Form invoice duplicate candidates from document identity rather than account alone.
Errors to avoid
- Do not use a persistent account reference as the only invoice key.
- Do not combine service and customer account references merely because both look numeric.
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