What to do
A description can occupy several printed lines while representing one billed item. Use the row’s quantity, code, and amount to understand its boundary. Preserve meaningful continuation text instead of either dropping it or turning every text line into a new item.
Indented specifications and serial numbers can be part of the preceding item even when they lack their own amount.
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 |
|---|---|---|
| Continuation | Line 1: Example filter; next line: model Q, pack of 6; one amount 30.00 | Keep the specification within the first item. |
| Real next item | Line 2: Example seal; separate code and amount 8.00 | Start a second item because the row has its own evidence. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Full item description | Description with its continuation text kept in order. |
| Row anchor | Printed item code or line number tying the text to a row. |
| Printed row amount | Amount belonging to the complete item, not each text line. |
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 source’s row anchors and spacing around the wrapped description.
- Compare extracted item count with billed rows, not visible text lines.
- Check that continuation text has not shifted the following quantity or price.
Errors to avoid
- Do not count every line break as a new invoice item.
- Do not concatenate two priced rows merely because their descriptions are similar.
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