What to do
Preserve the subscription period, item description, seat or usage quantity, and any printed proration. A software invoice can combine renewal, usage, credits, and adjustments. Do not infer plan entitlements or future billing terms from one invoice.
A subscription identifier can persist across invoices and should not replace the invoice number.
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 |
|---|---|---|
| Seat change | 10 seats renewal 100.00; extra-seat proration 6.00 | Retain the proration separately from the recurring line. |
| Credit applied | Subscription charge 100.00; credit applied 20.00; due 80.00 | Preserve the charge and credit without replacing both with the balance. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Invoice and subscription references | Distinct identifiers under their printed labels. |
| Service period | Dates explicitly associated with the billed item. |
| Seats, usage, and adjustments | Printed quantities and charge descriptions, keeping units and signs. |
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
- Identify invoice, subscription, and customer references independently.
- Keep each billed period and usage unit with its corresponding item.
- Review credits and balances before mapping the invoice into a purchase register.
Errors to avoid
- Do not assume a renewal line proves service was used.
- Do not project next month’s charge from a prorated current invoice.
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