What to do
A quoted CSV field can contain a line break, so the number of physical text lines need not equal the number of records. Use a CSV parser to count exported invoices. Splitting a file at every newline can turn one description into several malformed records.
Parzable’s batch export is file-based; a wrapped description inside one field is not automatically a separate item row.
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 |
|---|---|---|
| One multiline field | Quoted description contains Example service then a line break then Phase one | Treat the quoted text as one field in one record. |
| Real next record | A newline occurs after the closing field quote and record delimiter | Start the next CSV record according to the parsed structure. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Description | Full decoded value, retaining meaningful internal line breaks. |
| Logical record count | Number of data records returned by a CSV-aware parser. |
| Filename | Source-file reference attached to each exported record. |
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
- Use a parser or spreadsheet import rather than manual newline splitting.
- Compare logical record count with completed source files.
- Review any descriptions whose line breaks changed during import.
Errors to avoid
- Do not equate a text editor’s line counter with invoice count.
- Do not remove line breaks without deciding whether they carry useful structure.
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 format conventions: RFC 4180. 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