What to do
Keep order, dispatch, service, and invoice dates under distinct names when they appear on the same document. Their values can legitimately differ. Selecting the earliest or most prominent date does not establish which one is the invoice issue date.
A delivery-note attachment can introduce another date that belongs to a different source.
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 |
|---|---|---|
| Several events | Ordered 2026-09-01; dispatched 2026-09-03; invoiced 2026-09-04 | Keep three dates and their roles. |
| Order date only | Customer order dated 2026-09-01; issue date absent | Do not substitute the order date into the invoice-date field. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Invoice date | Date explicitly attached to the invoice issue label. |
| Order date | Date explicitly attached to the order reference. |
| Other event dates | Dispatch or service dates retained with their source labels. |
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
- List date candidates with their surrounding labels.
- Describe each requested event explicitly in the schema.
- Compare the exported dates with the corresponding source labels after normalization.
Errors to avoid
- Do not assume the newest date is always the invoice date.
- Do not treat a received-email date as a printed document date.
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