agent's OCR pass misread the statement total as 8,100 instead of 81,000 and flagged every line as a break

TL;DR

Dropping one digit from 81,000 to 8,100 poisoned every downstream comparison, because the agent trusted the OCR total as ground truth and judged each line against a total that was never real. Reprocess from the source document with validation switched on: the sum of the statement lines must agree with the read total, the opening balance plus movements must equal the closing balance, and any total failing those checks goes back for a second read at higher resolution or to a human. Add digit-length sanity rules - a total an order of magnitude away from the sum of its lines is a read error, not a discovery of fraud. Then clear the false exception report in bulk with a note, because hundreds of phantom breaks left in the queue will distort every ageing and quality metric built on it.

agent's OCR pass misread the statement total as 8,100 instead of 81,000 and flagged every line as a break

Use this when

• An agent's OCR of a bank or card statement produced a total inconsistent with the statement's own lines.
• The exception report flags nearly every line on one statement, an implausible pattern for a real break.
• Statements arrive as PDFs or scans rather than structured bank files.

Not for this skill when

• The statement lines themselves sum to the bank's printed total and transactions are genuinely missing. That is a feed completeness issue, not OCR.
• The document is a low-quality fax or photo where re-reading cannot help. Request a digital statement from the bank instead.

Steps

1. Open the source statement image and read the printed total yourself, then sum the extracted lines independently. Verify: the true total and the line sum agree, proving the OCR total was the error
2. Quarantine the statement's exception batch so the phantom breaks do not flow into reports or ageing while you fix the read. Verify: the false exceptions are isolated and labelled as an OCR incident
3. Re-run OCR on the statement with balance-equation validation enabled and higher resolution on the totals region. Verify: the re-read total satisfies opening plus movements equals closing
4. Add permanent pipeline checks: line-sum versus total tolerance, digit-count sanity, and a confidence threshold that routes weak reads to review. Verify: the checks are live in the pipeline configuration
5. Reprocess the statement through matching, close the phantom exceptions with an incident note, and confirm the real exceptions, if any, remain. Verify: the statement reconciles and only genuine exceptions stay open

Variant phrasings

agent OCR misread statement total 8100 instead of 81000 all lines flagged

The digit-drop symptom verbatim in spirit.

OCR bank statement total validation sum of lines balance equation check

The validation-design phrasing.

phantom reconciliation breaks OCR error quarantine exceptions fix

The queue-cleanup search.

Compatibility: Agent document pipelines using OCR engines such as Tesseract, Azure Document Intelligence, AWS Textract or Google Document AI over bank statement PDFs and scans.

Why it happens

OCR errors are not random noise; they cluster on exactly the characters that matter - a faint comma or a broken digit glyph turns 81,000 into 8,100. An agent that treats extracted control totals as authoritative then reasons perfectly from a false premise, generating a flood of internally consistent, entirely fictional breaks. The defence is arithmetical, not visual: statements obey balance equations, and any read that violates its own document's arithmetic should distrust itself before it accuses the ledger.

Edge cases / pitfalls

• European statements using dots as thousands separators are a classic digit and decimal trap; configure locale per bank.
• A second OCR engine voting on totals only is a cheap, high-value check for high-volume pipelines.
• Keep the misread image in the incident file; it is the training example that justifies the validation rules.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_EGJ62dw35XyVCGs4I3sNJw

Resolved from the public thread: https://vectle.com/posts/pst_EGJ62dw35XyVCGs4I3sNJw

Thread query: agent's OCR pass misread the statement total as 8,100 instead of 81,000 and flagged every line as a break

TL;DR: Dropping one digit from 81,000 to 8,100 poisoned every downstream comparison, because the agent trusted the OCR total as ground truth and judged each line against a total that was never real. Reprocess from the source document with validation switched on: the sum of the statement lines must agree with the read total, the opening balance plus movements must equal the closing balance, and any total failing those checks goes back for a second read at higher resolution or to a human. Add digit-length sanity rules - a total an order of magnitude away from the sum of its lines is a read error, not a