OCR form processing: a step-by-step guide to OCR for forms

OCR form processing uses optical character recognition (OCR) to read filled-in forms, such as loan applications, tax forms and insurance certificates, and turn every field into structured data. Plain OCR only turns the page into text. Form processing also ties each value to its field, reads handwriting and checkboxes, checks the values and sends them to the system that needs them.

This guide covers the kinds of forms, what OCR has to read on them, how the process works step by step, and what to look for in form processing software.

Structured vs semi-structured forms#

How a document is laid out decides how hard it is to read automatically.

• Structured forms

  Every copy has the same fields in the same place, like Form 1003, Form W-2 and ACORD 25. Templates can read them, as long as the layout and the scan stay put.

• Semi-structured forms

  The same information in a different layout from every sender, like invoices, bank statements and pay stubs. Fields have to be found by their labels, not their position.

• Unstructured documents

  Free text with no fields, like letters, contracts and notes. Values come out of sentences, which takes language models rather than templates.

Even a standard form varies. Copy A of Form W-2, the one employers file with the Social Security Administration (SSA), is printed in red OCR dropout ink, and any substitute must copy its layout exactly because SSA scanners read it electronically. The copies employees get, the ones borrowers hand to lenders, can leave out unused boxes, move the name and address boxes and run in a vertical layout, all within IRS rules.

What OCR has to read on a form#

A single form can mix four kinds of content, each with its own reader: printed text (OCR), hand-printed characters in boxes (intelligent character recognition, ICR), cursive handwriting (handwriting recognition, HWR), and checkboxes and bubbles (optical mark recognition, OMR). Form processing runs all four on the same page.

Good form design helps: one box per character, a request for capital letters, and boxes in a dropout color. Handwriting still reads less reliably than print, so values the engine isn't sure about should go to a person. Our guide to intelligent character recognition covers the handwritten part in depth.

How OCR form processing works#

Most form processing systems run these stages. What sets one apart is how each stage copes with a form that doesn't match the sample.

1. CaptureForms arrive by email, upload, scanner or API. Each image is straightened and cleaned up before it's read.
2. ClassifyThe system works out which form each page belongs to, such as a W-2, page 3 of a 1003 or an ACORD 25, and splits packets that hold several.
3. ReadOCR reads the printed text, ICR the hand-printed entries, handwriting recognition the notes and OMR the checkboxes.
4. Map to fieldsEach value is tied to a field, such as borrower name or policy number: by position on a fixed form, by label and context on a varied one.
5. ValidateDates must be real dates and tax IDs the right format, totals must add up and required fields can't be blank.
6. Review and exportValues below a confidence threshold go to a person. The rest go to your system through an API, or as JSON, CSV or Excel files.

Form processing use cases#

These are the forms lending, tax, insurance, onboarding and healthcare teams handle every day, plus form-like documents such as pay stubs.

• Mortgage applications

  Form 1003, the Uniform Residential Loan Application, and Form 1008, the Uniform Underwriting and Transmittal Summary, read alongside the income documents in the loan file.

• IRS tax forms

  W-2s, 1040s and 1099s, often in one mixed packet, plus Form 4506-C, the borrower's signed consent for a lender to get IRS transcripts.

• ACORD insurance forms

  Standard forms from ACORD, the insurance industry's standards body, such as ACORD 25 (certificate of liability insurance), 125 (commercial insurance application) and 126 (commercial general liability section).

• Pay stubs

  Gross pay, deductions, net pay and year-to-date totals, in a different layout for each payroll provider. See pay stub extraction.

• Onboarding and KYC forms

  Account opening forms, vendor forms and W-9s, where the name, address and tax ID have to match other records.

• Healthcare and benefits forms

  Patient intake forms, often partly handwritten, plus claim forms and explanation of benefits (EOB) statements. See healthcare.

Template OCR vs AI form processing#

Traditional form OCR, often called zonal or template OCR, reads each field from a fixed spot on the page. It works well on one clean, fixed layout and needs a new template for every other. AI form processing finds each field by its label and context, so one setup covers many layouts.

What to look for in OCR form processing software#

Most form recognition software reads a clean printed form well. The differences show on handwriting, unfamiliar layouts and the values the engine isn't sure about.

• Handwriting and checkboxesReads hand-printed entries, cursive notes and ticked boxes in the same pass as printed text.
• New layouts without new templatesCopes with new form editions, substitute forms and skewed scans.
• Classification and splittingRecognizes each form in a mixed packet and splits it before extraction.
• A confidence score on every fieldLets you set per field how sure the engine must be before a value skips review.
• Validation rulesChecks formats, required fields and totals, and flags every value that fails.
• Review and outputShows reviewers each flagged value next to its place on the page, and sends approved data to your systems by API or webhook.

Test any tool on a sample of your own forms, including the worst scans and the messiest handwriting, before you commit.

How to automate form processing with Docsumo#

Docsumo, our product, is an intelligent document processing platform for this kind of work. It reads printed and handwritten text on any form, sorts and splits mixed packets (on the Business plan), and extracts fields and tables, joining tables that run across pages into one. Fields it isn't sure about go to your own reviewers: you set the confidence threshold per field, clicking a field highlights its source line on the page, and corrections improve the model.

Checked data goes to your systems through the API and webhooks. Docsumo runs in the cloud only, and it isn't a desktop tool for editing PDFs or making searchable files. See the platform for the full workflow.

• 99%99%field-level accuracy across 250+ document types
• 95%+95%+of documents processed straight through, without manual review
• <5 min<5 minper document, down from 2+ hours

Play video: A 5-minute guide to OCR software

The bottom line#

OCR form processing turns a filled-in form into data your systems can use, with little or no manual data entry. Structured forms can be read with templates until an edition or a scan changes; semi-structured documents and handwriting need software that finds fields by context and knows when it isn't sure. Choose a tool by how it handles your worst forms, and have people review only the values it flags.

Book a demo with a few of your own forms, or start a free trial.

Frequently asked questions#