What to do
Separate unrelated invoices into individual files before a workflow that returns one result per uploaded file. Keep continuation pages with the invoice they belong to. Splitting every page individually can lose tables, totals, and references needed for review.
Parzable’s batch export represents completed files; it does not promise automatic splitting of unrelated invoices inside one PDF.
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 |
|---|---|---|
| Two documents | Pages 1–2 show INV-A; page 3 shows INV-B | Prepare a two-page file for A and a one-page file for B. |
| Continuation only | Page 2 has no invoice heading but continues page 1’s items | Keep it with page 1 after reviewing continuity. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Output filename | Unique prepared file assigned to one invoice. |
| Original page range | Page range in the original combined PDF, recorded in your manifest. |
| Invoice identity | Printed supplier and invoice number used to check grouping. |
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 every page and mark document boundaries before splitting.
- Retain the original combined PDF and a page-range mapping.
- Check each prepared file’s page order and final totals page before upload.
Errors to avoid
- Do not assume a new page always starts a new invoice.
- Do not upload a combined archive expecting separate records without testing that workflow.
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 and receipt field roles: Amazon 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