What is intelligent document processing?
Intelligent document processing is the category name for turning submitted documents into structured data a system can accept. It covers classification of the document before extraction of its fields; validation of those values against rules then decides what reaches a person. The term describes an outcome, which is why two products answering to it can work very differently.
Also called: IDP, Document understanding
Why the category label tells a buyer very little
Intelligent document processing is a procurement category before it is an engineering description. Two platforms can both answer to the label while one of them stops at extraction and the other validates against the rules its destination system enforces. The difference surfaces in the first week of production, when documents that extracted cleanly are rejected downstream for reasons no accuracy figure predicted. A buyer evaluating this category is therefore evaluating validation and exception handling rather than the extraction demonstration.
- The label covers classification and validation as well as extraction.
- Accuracy quoted for extraction says nothing about what the destination system accepts.
- Exception handling is where most of the operating cost of a document pipeline lies.
- Two products matching the category description can differ enormously in effort.
How intelligent document processing works
- Incoming documents are classified by type before any field is read.
- Layout analysis establishes the regions of each page and their relationship.
- Text is recovered by character recognition and attributed to the regions holding it.
- Named fields are extracted and coerced into the schema of the destination record.
- Values are validated against business rules and against reference data already held.
- Anything failing validation or confidence is queued for human correction.
How intelligent document processing is evaluated
Intelligent document processing is measured end to end, since a clean extraction that fails validation has achieved nothing. Examine the following on production volume:
- share of documents processed with no human touch
- field level accuracy after validation rather than before it
- classification accuracy across every document type accepted
- rate at which downstream systems reject accepted output
- cost per document including the exception queue
Limitations, risks and common failure modes
- Vendor accuracy figures are quoted on clean samples that intake does not resemble.
- Validation rules are inherited from a legacy form and nobody can explain them.
- Document types absent from training arrive within weeks of go live.
- Exception queues grow quietly until correction costs more than manual entry did.