A MICR software solution turns an E-13B or CMC-7 control-line read into structured routing, account, and cheque-number fields that downstream systems can use. Chequedb accepts scanner signals or cheque images, returns confidence and mismatch signals, and sends uncertain reads to review through an API-connected workflow.
The walkthrough covers your scanner or image input, required output fields, confidence thresholds, and exception-review handoff.
Read
E-13B or CMC-7 from magnetic scanner output or a cheque image.
Return
Structured routing, account, and cheque-number fields with confidence output.
Control
Route low-confidence and conflicting reads to review before downstream handoff.
Performance depends on the scanner, document, image, and workflow configuration; review thresholds should be tested against your own cheque samples.
Need scanner capture first? Start with cheque scanning software. Looking for the full extraction and OCR layer? See the bank check OCR API or follow the full lifecycle in cheque processing software overview.
Chequedb product reference · Reviewed
Chequedb reference answer
MICR — magnetic ink character recognition — reads specially shaped characters printed in magnetic ink on cheques and other payment documents. The ASC X9 E-13B specification defines character shapes, magnetic signal levels, and tolerances for U.S. MICR printing.
For the terminology, font standards, and a field-by-field walkthrough, read what MICR technology is and how it works.
Routing, account and cheque identifiers are common MICR fields. The complete format depends on the clearing scheme.
A 9-digit number that identifies the specific bank and branch where the account is held. The first 4 digits represent the Federal Reserve routing symbol.
Identifies the account. Length and format vary by institution and clearing scheme. Preserve leading zeros when mapping the value.
A sequential number identifying this specific cheque. Helps track payments and detect duplicate or fraudulent cheques.
MICR software (and the broader MICR software solution it belongs to) reads, validates, normalises, and routes control-line data into downstream workflows — before the cheque reaches posting or reconciliation.
MICR software extracts the routing, account, and cheque numbers from the MICR line. It normalises the data regardless of font (E-13B or CMC-7) and source (magnetic scanner or optical image). The same MICR software solution handles both inputs.
MICR software validates the routing number against bank databases and cross-checks the magnetic read against the optical read of the same MICR line. A mismatch between the two is a fraud signal — the MICR line may have been altered.
With validated MICR data, the software routes the cheque through the right processing path — auto-post for low-risk items, exception queue for mismatches, or fraud review for altered MICR lines. Every decision is logged for audit.
The key distinction: a MICR reader device performs the physical or optical read. MICR software is what turns that read into an operational decision — normalising the data, validating it, posting it, or routing it to a review queue. A complete MICR software solution combines reading, validation, workflow routing, and an audit trail in one pipeline.
Two complementary technologies ensure reliable MICR data extraction
Traditional MICR Technology
Magnetic MICR readers use a specialized read head to detect the magnetic field produced by the iron oxide ink. As the cheque passes over the read head, each character generates a unique waveform pattern based on its geometric design.
AI-Powered Recognition
Optical MICR readers use computer vision and machine learning to recognize MICR characters from images. Image preprocessing and confidence scoring help the workflow distinguish clear reads from items that need review.
MICR content and field order vary by country and clearing scheme
The MICR line — sometimes called the MICR band — is the stripe of magnetic-ink characters printed along the bottom of a cheque. It can contain routing, account and cheque identifiers, as well as other scheme-specific data. Some formats include an encoded amount or processing information. Three common field types are:
Routing number (or sort code)
Identifies the bank or branch under the relevant scheme. U.S. routing numbers have nine digits; UK sort codes have six. Other countries use their own formats. Confirm the control-line specification rather than applying one country's parser everywhere.
Account number
Identifies the account. Length and position vary by institution and clearing scheme. Preserve leading zeros and the raw control line when mapping it to a downstream system.
Cheque number
The sequential number printed on the cheque. Used for tracking, reconciliation, and duplicate detection. Compare it with bank and account context and other transaction evidence; a cheque number alone is not a globally unique identifier or proof of duplicate presentment.
Read the cheque body separately: The visible payee, written amounts, date, memo and signature require separate extraction or inspection. An encoded MICR amount, where present, is distinct from reading the written amounts. Neither a control-line read nor OCR alone establishes authenticity, funds availability or bank acceptance.
A magnetic MICR read requires a device with a magnetic read head. Optical MICR software can instead attempt the control line from a scanner image or mobile photo. The integration can combine the supplied device read, image crop, and capture metadata for normalization, confidence output, and review.
Desktop single-feed units, production scanners, departmental scanners, and specialist kiosk devices expose different drivers and data contracts. Compatibility depends on the exact model, operating system, driver or OEM SDK, output format, and deployment; confirm each scanner model and deployment in a pilot.
Browse the cheque scanner hardware catalog
Compact USB scanners for branch, back-office, or low-to-mid volume environments. Connect over USB; driver outputs front image, rear image, and MICR line string per item.
Higher-volume units with accept and reject pockets for automated sorting. Magnetic read head plus optical fallback. Used in bank operations centres and high-volume back-office environments.
Examples
Departmental flatbed scanners for high-volume batch capture, plus specialist kiosk and ATM-embedded units for self-service deposit. Output is image + MICR record, connected over Ethernet or USB to the platform API.
Use cases
The scanner handles capture. Chequedb handles the rest.
1. Check MICR scan
Front image, rear image, magnetic MICR read per item — the check MICR scan returns routing, account, and cheque number
2. Capture adapter
The agreed adapter passes images, device reads and capture metadata into the processing contract
3. Platform processing
MICR normalization, OCR/ICR field extraction, amount and date validation, duplicate check
4. Review queue
Confident items post; mismatches and low-confidence items surface in the workflow for review
A scanner may expose a TWAIN, ISIS, OEM SDK, or middleware interface. The integration adapter should be selected and tested for the exact model rather than assuming one driver or code path works across every MICR reader.
A compact guide to the role each recognition layer plays in cheque processing
| Question | MICR | OCR | ICR |
|---|---|---|---|
| What it reads | Encoded E-13B or CMC-7 control line | Visible machine-printed characters | Handwritten characters and words |
| Typical fields | Routing, account, cheque number | Printed labels and printed fields | Payee, date, written amount |
| Main dependency | Print or signal quality; MICR layout | Image quality and printed layout | Handwriting and image quality |
| Workflow role | Clearing control data | Printed-document extraction | Handwriting extraction for review |
Learn more about MICR vs OCR — Modern systems like Chequedb combine both technologies for complete check processing.
Reading the MICR line tells you where the item belongs in clearing. It does not tell you whether the payee is correct, whether the written and numeric amounts agree, whether the date is enforceable, or whether any field was altered after the cheque was issued. None of those fields are in the MICR line.
Full cheque validation requires layering MICR with OCR for machine-printed fields, ICR for handwritten fields (payee, legal amount, memo), courtesy and legal amount recognition for the amount boxes, and date-rule validation. MICR is the entry point. The rest of the cheque is the actual validation problem.
This is also why MICR and OCR are routinely run in tandem to flag discrepancies. When the magnetic read disagrees with the optical read of the MICR line, or when OCR pulls a payee that doesn't match positive pay records, or when numeric and written amounts conflict — each is a potential fraud signal. Washed cheques, counterfeits, and altered amounts often reveal themselves through these cross-layer mismatches before they post. A complete cheque management workflow surfaces these disagreements in a review queue with reason codes, rather than letting them pass silently.
Chequedb combines capture, recognition, validation, and controlled exception handling
High-resolution scanning or mobile photo capture of the check
AI locates and isolates the MICR line from the cheque image
Dual-mode recognition identifies E-13B or CMC-7 characters
Routing number verification against bank databases
Move control-line data into processing and review without relying on a blanket accuracy claim
Move routing, account, and cheque identifiers into a structured workflow without re-keying every item.
Use confidence and mismatch signals to set review thresholds for your documents and risk policy.
Flag magnetic-versus-optical mismatches, duplicate identifiers, and routing exceptions for investigation.
Optical MICR can attempt a control-line read from standard scanner images or mobile photos when no magnetic signal is available.
Normalize either MICR format when the country scheme, field order, image or signal, and required validation rules are configured.
Agree normalised MICR fields, read signals and response mapping, then confirm the capture adapter and device path in a representative pilot.
Compare the two control-line formats and configure parsing for the clearing scheme in scope
Used in North America, UK, Australia, and parts of Asia
Used in Europe, Latin America, and parts of Asia
Chequedb reviewed this product reference against standards-body and first-party technical material. Product performance still depends on the scanner, document, image, and workflow configuration.
Last reviewed .
Not sure which scanner to use?
Browse desktop, production, and kiosk scanner models — current and legacy — with MICR capability noted for each.
Bring your scanner model or image source, required MICR fields, and exception rules. We'll map the E-13B or CMC-7 read, confidence output, API handoff, and review path.