# OCR Accuracy Calculator

> Source: https://netray.co/tools/ocr-accuracy-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Turn a reviewed sample of documents into field accuracy, document level accuracy and the correction effort hiding behind them.

## Category

ai-automation

## Audience

- AP manager
- Quality engineer
- Document control

## Tool

**Kind:** calculator

**Inputs:**

#### Documents in reviewed sample

**Key:** docs

**Type:** number

**Default:** 200

**Min:** 1

**Step:** 10

**Unit:** docs

#### Fields checked per document

**Key:** fields_per_doc

**Type:** number

**Default:** 14

**Min:** 1

**Step:** 1

**Unit:** fields

**Help:** Count only the fields you actually need downstream.

#### Fields extracted wrongly or missed

**Key:** field_errors

**Type:** number

**Default:** 96

**Min:** 0

**Step:** 1

**Unit:** fields

#### Documents with at least one error

**Key:** docs_with_error

**Type:** number

**Default:** 58

**Min:** 0

**Step:** 1

**Unit:** docs

#### Minutes to correct one bad document

**Key:** fix_min

**Type:** number

**Default:** 3

**Min:** 0

**Step:** 0.5

**Unit:** min

#### Monthly document volume

**Key:** monthly_docs

**Type:** number

**Default:** 4000

**Min:** 0

**Step:** 100

**Unit:** docs

**Outputs:**

#### Total fields checked

**Key:** total_fields

**Expr:** docs * fields_per_doc

**Format:** integer

#### Field level accuracy

**Key:** field_acc

**Expr:** (1 - field_errors / total_fields) * 100

**Format:** percent

**Primary:** true

**Description:** Share of individual fields that were correct.

#### Document level accuracy (straight through)

**Key:** doc_acc

**Expr:** (1 - docs_with_error / docs) * 100

**Format:** percent

**Primary:** true

**Description:** Share of documents with zero errors, the number that drives touchless processing.

#### Errors per 1,000 fields

**Key:** err_per_1000

**Expr:** field_errors / total_fields * 1000

**Format:** decimal

#### Average errors per bad document

**Key:** errs_per_bad_doc

**Expr:** field_errors / max(docs_with_error, 1)

**Format:** decimal

#### Monthly correction effort

**Key:** monthly_fix_hours

**Expr:** monthly_docs * docs_with_error / docs * fix_min / 60

**Format:** hours

**Disclaimer:** Accuracy from a small sample carries uncertainty. Use a few hundred documents and a random draw before quoting the figures externally.

## Content

**Intro:** A vendor claim of 98 percent OCR accuracy can coexist with only 70 percent of invoices passing without a touch. The difference is field level versus document level accuracy, and this calculator shows both from one reviewed sample, along with the correction hours they imply.

**Sections:**

#### How to use the calculator

**Body:** Draw a random sample of documents, run them through your capture tool, and have a person compare each extracted field with the source. Count the fields checked per document and the fields that were wrong or missing. Also count how many documents contained at least one error. Enter those numbers with your correction time per bad document and monthly volume. The calculator returns field accuracy, document accuracy, errors per thousand fields and monthly correction hours.

**Bullets:**

- Sample at random, not only the clean documents
- Count a missing field as an error
- Check only fields used downstream
- Keep the same field list when you re-measure

#### The formulas

**Body:** Field accuracy equals one minus errors divided by total fields checked. Document accuracy equals one minus documents with errors divided by documents sampled. If errors were independent across fields, document accuracy would be roughly field accuracy raised to the number of fields, which is why 98 percent per field over 14 fields gives only about 75 percent of clean documents. Real errors cluster on poor scans and unusual layouts, so measured document accuracy is often better than that theoretical figure.

#### Reading the result

**Body:** Use document accuracy to forecast touchless rate and staffing, and field accuracy to decide where tuning pays off. Break results down by vendor, document type and scan quality before acting, because a handful of suppliers usually cause most errors. Compare the correction hours with the cost of the tool: if hours stay high after tuning, the issue is often layout variety rather than model quality, and a template or supplier change request can be cheaper.

**Bullets:**

- Under about 90 percent document accuracy, plan for large review capacity
- Look at errors by field to find the one or two worth fixing
- Re-measure after any model, template or scanner change

**Cta:** If you want accuracy measured continuously from your real documents and ERP outcomes instead of one-off samples, we can wire up a private extraction pipeline and a review queue on your own infrastructure.

**Faq:**

#### What is the difference between field and document accuracy?

**Answer:** Field accuracy counts each extracted value separately. Document accuracy counts a document as correct only if every field is right. Document accuracy is always lower and is the better predictor of how many documents can post without human review.

#### How big should the sample be?

**Answer:** At least 200 documents is a reasonable minimum for a headline figure, more if you want per vendor results. Fewer documents leave wide uncertainty, so treat small samples as indicative only.

#### Is confidence score the same as accuracy?

**Answer:** No. Confidence is the tool's own estimate for a value. Accuracy is what you measure against the source. A well calibrated tool has confidence close to actual accuracy, but you must verify that on your own data.

#### Does a character error rate matter?

**Answer:** Character error rate is useful for comparing raw OCR engines, but business outcomes depend on whole field correctness. A single wrong digit in an invoice number or amount makes the field wrong, so field level measurement is the better business metric.

## Search terms

ocr accuracy calculator, how to calculate ocr accuracy, field level accuracy vs document accuracy, ocr error rate, straight through processing rate, invoice ocr accuracy measurement, document extraction accuracy, ocr benchmark sample size

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json