What happens when untxt. is unsure about a receipt?
untxt. flags uncertain fields for human review instead of silently posting bad data into the books.
What it means
Uncertainty is normal in structured document intake. Blurry totals, missing invoice numbers, handwriting, unusual layouts, and ambiguous account choices should all become review signals.
02 · Example
A receipt clearly shows the vendor and total, but the tax amount is partly cut off. untxt. extracts what it can and marks the tax field for review.
Where review matters
A good workflow does not ask the bookkeeper to recheck everything. It routes only the uncertain parts that need judgment.
Who this helps
This helps teams that want intake convenience without losing control. The reviewer should spend attention on unclear fields, ambiguous categories, possible duplicates, and missing context rather than reprocessing every document by hand.
What untxt. does
untxt. keeps uncertainty visible. It can extract the fields it understands, mark low-confidence values, and keep the record reviewable before any downstream bookkeeping workflow uses it.
What it does not pretend
It does not turn every blurry receipt or context-specific account choice into a fake confident answer. Review is part of the trust model.