What to do
Capture payment terms as the wording printed on the invoice, including any discount condition or starting event. A phrase such as “30 days from receipt” carries different information from a printed calendar deadline. Keep interpretation separate from extraction.
Terms may be in a small footer, while a payment instruction beside the total describes only the payment method.
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 |
|---|---|---|
| Conditional discount | 2% within 10 days; otherwise net 30 | Retain both conditions; do not reduce the invoice total automatically. |
| Event-based timing | Payment 30 days after receipt | Capture the phrase; the receipt date is not established by the invoice issue date. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Payment terms | Verbatim payment timing and conditions printed on the invoice. |
| Due date | Printed calendar deadline only, if present. |
| Discount condition | Exact early-payment condition; do not assume it has been earned. |
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 footer and summary for timing language and conditions.
- Keep terms text separate from bank-transfer instructions.
- Pass date or discount interpretation to the reviewed destination rules.
Errors to avoid
- Do not treat a suggested payment method as payment timing.
- Do not claim an early-payment discount simply because its condition is printed.
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