What to do
Review the end of one page and the start of the next as a single table boundary. Repeated headers, carried-forward totals, and a description split across pages can be mistaken for items or omitted entirely. Count rows independently from the source.
Keep all pages of one invoice together in the source PDF before requesting extraction.
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 |
|---|---|---|
| Repeated header | Page 2 begins Description / Qty / Amount | Exclude the column heading from the item count. |
| Carried subtotal | Page 1 carried forward 180.00; page 2 brought forward 180.00 | These repeat the same subtotal; they are not two new charges. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Line reference | Printed item number or code, retaining page context in review notes. |
| Continuation text | Text completing a description across the page boundary. |
| Carried-forward amount | Subtotal explicitly labelled as carried forward, not a new item. |
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
- Confirm source page order and invoice identity before reviewing the table.
- Compare the last priced row and next page’s first priced row.
- Reconcile the complete item count and record unresolved page-boundary issues.
Errors to avoid
- Do not add both carried-forward and brought-forward amounts as charges.
- A totals-only final page can still be necessary for review.
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 structure: Microsoft Document Intelligence 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