What to do

If every value appears in one spreadsheet column, inspect the delimiter selected during import. A comma-separated file and a semicolon-separated file need different interpretation. Do not globally replace punctuation inside the file because commas may belong to names or amounts.

A quoted supplier name can contain a comma without creating an additional column.

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.

CaseFictional source excerptReview decision
Comma file"Vendor","Invoice number","Total"Choose comma as separator; three header columns should appear.
Embedded punctuation"Example Supplier, Ltd","INV-2","15.00"Keep the vendor name in one field rather than replacing its comma.

Suggested review columns

ColumnDefinition or instruction
DelimiterActual field separator used in the source file.
Expected headersColumn names that should appear in the preview.
Preview widthNumber of columns visible after import settings are selected.

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

  1. Inspect the header and identify separators outside quoted fields.
  2. Choose the matching separator in the spreadsheet import dialog.
  3. Check both the header count and a row with embedded punctuation.

Errors to avoid

  • Do not split quoted CSV text using a simple comma search.
  • A decimal comma inside a quoted value is not necessarily a column separator.

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