Answer in 30 seconds

Learn how to measure AI OCR accuracy with Dynamite Docs. Compare extracted text with a reviewed transcript using character and word error rates.

Dynamite Docs
The handoff
Scanned page: Compare the charactersBuild ground truth before you test OCR. Calculate character and word error rates. Find the OCR errors that change the data. Illustrative example, not extracted customer data.FROM SOURCE FILE TO A RESULT YOU CAN USEScannedpageReview workspaceCompare thecharacters1Build groundtruth before youtest OCR2Calculatecharacter andword error rates3Find the OCRerrors thatchange the data
  1. 01Build ground truth before you test OCR
  2. 02Calculate character and word error rates
  3. 03Find the OCR errors that change the data
Count substitutions, additions and gaps. Illustrative example.
01

Build ground truth before you test OCR

Choose pages that look like the work you actually receive. Keep digital PDFs, scans and phone photos in separate groups so clean files cannot hide failures on faint receipts or rotated statements. Record the file, page number and reading order for every reference transcript.

Have one person transcribe each page and another check ambiguous text against the image. Mark unreadable regions instead of guessing. Write down how the test treats whitespace, punctuation, capitalization and Unicode, then use those rules for every OCR engine.

02

Calculate character and word error rates

Character error rate, CER, equals substitutions plus deletions plus insertions, divided by the number of reference characters. Word error rate, WER, applies the same edit-distance calculation to words. Lower is better. Extra inserted text can push either rate above 100%.

Worked example: the reference is "Total 125.00" and the prediction is "Total 128.00". Counting the space, there are 12 reference characters and one substitution, so CER is 1/12 = 8.33%. With whitespace tokenization there are two words and one wrong word, so WER is 1/2 = 50%. This is an illustrative calculation, not a Dynamite Docs benchmark result.

For a corpus score, add all edit counts and reference lengths before dividing. Keep the page-level results too. If a reference is empty, the denominator is zero, so report inserted text separately and state the scorer convention rather than recording a perfect score.

03

Find the OCR errors that change the data

A wrong digit in a total can matter more than dozens of harmless punctuation errors. Keep a separate error register for account numbers, dates, amounts and identifiers. Do not strip decimal points or minus signs during normalization simply to improve the score.

CER and WER cannot tell whether a value landed in the right field or table row. A transcript may contain every word and still mix two columns. Use the extraction accuracy guide to score field assignments, then use the LLM benchmark guide for complete pipeline comparisons.

Dynamite Docs
The review
Scanned page: Compare the charactersBuild ground truth before you test OCR. Calculate character and word error rates. Find the OCR errors that change the data. Illustrative example, not extracted customer data.SOURCE DOCUMENTScanned pageRead the sourceCheck against the sourceReview the resultCheck against the sourceExport checked dataCheck against the sourceReview before exportRead the sourceCheck against thesourceCompare with the source on the leftAccept after reviewCount substitutions, additions andgaps.Original stays…
Read the source
Check against the source
Review the result
Check against the source
Export checked data
Check against the source
Count substitutions, additions and gaps. Illustrative example.

Method reference: Hugging Face CER metric definition and limitations. The worked examples and proposed test protocol above are illustrative guidance.

Test a document against ground truth

Choose what to measure

Text recognition, model behavior and structured field quality answer different questions. Use the same reviewed documents to connect the results.

All accuracy testing methods

Model comparison / repeated runs

Benchmark field extraction using LLMs

Learn how to benchmark LLM document extraction with Dynamite Docs. Compare field errors, failed runs, latency, costs, and correction time on the same files.

Apply the test in Dynamite Docs

Choose a document workflow, run your sample, and compare the result with your reviewed answer.

  • Invoices

    Check identifiers, tax, totals and line items.

  • Receipts

    Test faint text, tips, dates and merchant names.

  • Bank statements

    Check transaction coverage, signs and balances.

  • PDFs

    Separate text-layer, scanned and mixed-page results.

  • API

    Retain outputs and track failures across repeatable runs.

  • PDF tables

    Check table boundaries, page breaks, row counts and totals.

  • Statement to Excel

    Test transaction coverage, signs and balance reconciliation.

  • BUSY invoices

    Verify GSTIN, HSN or SAC, tax splits and bill totals.

Loading Dynamite Docs… This page is taking longer than expected. Reload page.