What to do
Capture column labels that distinguish current-period work, cumulative work, prior billing, retention, and current payment due. These amounts can describe the same project at different stages. Preserve the printed presentation instead of adding every summary value together.
This is a source-data worksheet, not contract interpretation or a recommendation about retention treatment.
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 |
|---|---|---|
| Cumulative display | Earned to date 10000.00; previous billing 7000.00; current 3000.00 | Keep cumulative and current values separate rather than summing to 20000.00. |
| Retention shown | Current work 3000.00; printed retained amount 150.00; due 2850.00 | Capture the labelled reduction; do not determine whether it is contractually correct. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Project and application reference | Printed project, application number, and period. |
| Current and cumulative work | Amounts retained with their exact source headings. |
| Deductions and due amount | Printed prior billing, retention, and current due fields, without inference. |
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 every financial column heading and record its time scope.
- Keep the document’s own references so successive applications can be distinguished.
- Have the project’s accounting reviewer resolve unexplained cumulative or deduction differences.
Errors to avoid
- Do not count cumulative work as a new charge on each application.
- Do not infer contractual approval from a completed extraction.
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: Progress-invoice field context: ServiceTitan 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