This route returns a text draft rather than invented structured fields. Use the source beside the result, pair labels with values, and recalculate financial totals independently.
The tool returns reviewable text rather than claiming validated fields. This page focuses on relationships and arithmetic because readable prose is not sufficient for financial data.
Recognition is only the first stage. Use Receipt, Invoice and Table OCR: A Field-First Workflow for the relevant control checks and Numeric OCR Validation for Dates, Totals and Identifiers for values that must be exact. If the output structure changes, compare Form to JSON with Table to Markdown.
Check fields, rows, currencies, and arithmetic
| Review point | Likely failure | Validation action |
|---|---|---|
| Amounts | Decimals, signs, or separators change value | Verify each token and retain its currency and unit |
| Rows | A price moves to the wrong line item | Trace values horizontally and check wrapped descriptions |
| Totals | Recognized numbers appear internally plausible | Recalculate subtotal, discount, tax, and final total |
Map labels to values before data entry
Capture the full document including supplier and currency context.
Pair each value with its visible label before data entry.
Recalculate line items, discounts, tax, subtotal, and total independently.
Invoice control scenario
For a thermal receipt, capture the merchant and currency context as well as the totals. Map each recognized amount to its line label, distinguish a discount from a negative quantity, and calculate the expected total. Flag faded digits instead of correcting them from arithmetic alone.
When validated accounting capture is required
Use an approved accounting capture system when tax rules, approvals, fraud controls, and audit trails are required. Keep sensitive financial documents offline when policy or authorization does not permit third-party upload.