What to do
Keep service dates, descriptions, hours, rates, fixed fees, and reimbursable items distinct. A professional-services invoice can mix hourly work with fixed-price milestones. Quantity-times-rate checks only apply after you identify the relevant billing basis.
Capture printed project or matter references without inferring confidential work details absent from the document.
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 |
|---|---|---|
| Hourly work | 4 hours × 75.00; line amount 300.00 | Retain the relationship for a separate arithmetic review. |
| Fixed fee | Milestone review fee 500.00; no hours shown | Do not invent hours by dividing the fee by an assumed rate. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Project reference | Printed project or engagement identifier. |
| Service period and description | Printed dates and wording for each billed service. |
| Hours, rate, and amount | Values retained with hourly or fixed-fee 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
- Classify each row’s billing basis before selecting numeric fields.
- Keep expenses and reimbursable items separate from labour lines.
- Review the printed project reference and amounts against the original.
Errors to avoid
- Do not treat every quantity as hours.
- Do not infer time entries or approval merely from a fixed fee.
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: Document and invoice structures: Microsoft 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