What to do
Choose the file’s actual encoding in the import preview and compare names with the source. Parzable’s CSV code creates UTF-8 text. Garbled accents after opening an export can indicate an interpretation problem rather than an extraction error.
Keep the original file while testing import settings so repeated resaving does not obscure the cause.
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 |
|---|---|---|
| Correct interpretation | Teaching supplier name: Café Exemple | The imported accented character should match the source. |
| Incorrect interpretation | The same name displays as Café Exemple | Check the UTF-8 import setting before editing the data manually. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Raw supplier name | Name from the source document. |
| Imported supplier name | Name displayed after the chosen encoding is applied. |
| Encoding selected | Import setting recorded for reproducibility. |
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 the CSV in an importer that provides an encoding preview.
- Choose UTF-8 for a Parzable UTF-8 export and confirm representative names.
- Reopen the saved destination file to ensure the characters remain intact.
Errors to avoid
- Do not remove accents simply to hide an import problem.
- A valid-looking filename does not establish the encoding of its contents.
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