What to do
The invoice date records when the document was issued; the due date is a separately stated payment deadline. Extract both when printed. Do not replace an unclear issue date with a clearer due date or silently calculate one from payment terms.
A date near a payment stub can be a due date even when it is larger than the issue date in the heading.
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 |
|---|---|---|
| Two clear dates | Issued 2026-09-01; Pay by 2026-09-30 | Keep issue date 2026-09-01 and due date 2026-09-30. |
| Terms without a date | Invoice date 2026-09-01; Net 30; no printed deadline | Capture Net 30 and hold the absent due-date value for the downstream process. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Invoice date | Issue date labelled on the invoice; preserve unresolved day/month ambiguity. |
| Due date | Explicit printed payment due date; do not derive it. |
| Payment terms | Verbatim terms that accompany the printed dates. |
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
- Read the label and neighbouring text for every candidate date.
- Store the original date text before normalizing a reviewed value.
- Compare each exported column with its own source label after import.
Errors to avoid
- Do not treat the file-created timestamp as an invoice date.
- Terms calculation belongs to a separately reviewed rule, not source transcription.
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-field reference: Amazon Textract 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