What to do
Choose stable filenames that distinguish source documents and connect them to the intake manifest. Keep original names in a mapping if you rename files. Avoid putting unnecessary personal or sensitive information in names that will appear in exports or shared review notes.
A filename is a handling reference; the printed invoice number remains a separate source fact.
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 attachment names | Two suppliers each send invoice.pdf | Assign distinct working names and retain both original-name mappings. |
| Corrected source | Supplier sends a revised copy of INV-8 | Preserve the version relationship rather than overwriting the only original. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Original filename | Name received from the sender. |
| Working filename | Unique name used in the prepared batch. |
| Document identity | Reviewed supplier and invoice reference, kept in the manifest. |
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
- Assign an intake reference before processing files with colliding names.
- Keep the rename mapping and source version in the manifest.
- Verify exported Filename values point back to the intended originals.
Errors to avoid
- Do not infer invoice identity exclusively from a manually typed filename.
- Do not overwrite two different attachments that happen to have the same name.
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: CSV import and type handling: Microsoft Support. 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