What to do

Keep unavailable values distinct from legitimate zeros. An empty cell, N/A, a missing source label, and a printed 0.00 describe different evidence. Decide how the receiving system represents missing data before replacing markers or enforcing numeric types.

Parzable’s extraction prompt requests N/A when a requested field is not available, but every returned value still needs review.

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
Real zeroSource explicitly prints Delivery 0.00Keep the zero as a confirmed amount.
Unavailable deliveryNo delivery field printed; extraction says N/ADo not replace N/A with 0.00 without a reviewed rule.

Suggested review columns

ColumnDefinition or instruction
Raw valueValue returned or printed, including a missing marker.
Source availabilityWhether the requested fact is present and readable.
Reviewed valueConfirmed value or explicit unresolved status.

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. Check the source whenever a required exported field is missing.
  2. Separate not printed, unreadable, and extraction missed it in review notes.
  3. Apply the destination’s missing-value policy only after that distinction is clear.

Errors to avoid

  • Do not let a spreadsheet silently convert missing values into zeros.
  • A blank result does not prove the underlying business amount was zero.

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