Avoid a dangerous default
A blank field may mean the document does not contain the information, the extraction missed it or the value is unreadable. Zero is a different statement. Replacing all blanks with zero can make an incomplete output appear valid. Agree on a missing-value representation and a separate reason where the destination supports it. If it does not, hold the record for review rather than hiding uncertainty in a convenient default.
Define the permitted inference
Some workflows allow a reviewer to derive a value from other explicit fields; others require the value to appear in the source. Write that rule before evaluation. For a fictional quantity field, do not assume one because a description is present. If a unit is omitted, do not borrow a unit from a previous row unless the document meaning and approved rule support it. A plausible completion is not evidence.
Make absence testable
Include three synthetic cases in the acceptance pack: the field is present and zero, the field is absent, and the field is visually unreadable. Expected outputs should differ. Add a case where a similar label appears elsewhere so that the method cannot satisfy the check merely by finding any number. This is an editorial test design; it does not claim that Parsio or another parser will fail or pass these cases.
Keep the next action specific
Route absence to the person who can resolve it: obtain a clearer document, confirm the intended interpretation or accept a documented omission. Record the decision without placing private source data in a public worksheet. If a required value cannot be established, leave the record unaccepted. Continue to field contracts for the representation or exception queues for ownership. A lower apparent completion rate can be more honest than fabricated completeness.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Parsio: documented parsing options — Merchant documentation · parsio.io · Merchant-controlled · checked 2026-09-30
- Docparser: documented feature set — Merchant documentation · docparser.com · Merchant-controlled · checked 2026-09-30