What to do
Keep annotations separate from the printed invoice fields unless a reviewer explicitly establishes their role. A handwritten date, total, or account code can be an internal note rather than a supplier correction. Capture its wording and location without assuming authority.
This workflow does not claim reliable handwriting recognition for every note or writer.
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 |
|---|---|---|
| Internal coding note | Printed total 180.00; handwritten office supplies beside it | Retain the printed amount and the annotation as different fields. |
| Crossed-out date | Printed date crossed out with an unclear handwritten replacement | Hold the date for clarification; do not silently choose the annotation. |
Suggested review columns
| Column | Definition or instruction |
|---|---|
| Printed value | Original printed value under its source label. |
| Annotation text | Handwritten wording only where legible, kept separately. |
| Annotation review | Reviewer decision about the note’s role and authority. |
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
- Identify printed facts before transcribing nearby annotations.
- Mark illegible handwriting as unresolved rather than completing it from context.
- Have the authorized reviewer decide whether any correction should be used.
Errors to avoid
- Do not present a handwritten approval mark as a verified authorization.
- Do not overwrite a printed amount based only on an unexplained annotation.
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: Image-quality considerations: Tesseract 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