- Overview
- Getting started
- Activities
- Insights dashboards
- Document Understanding Process
- Quickstart tutorials
- Framework components
- Overview
- Document Understanding activities
- Document classification validation overview
- Classification Station
- Document classification validation related activities
- Data consumption
- API calls
- ML packages
- Overview
- Document Understanding - ML package
- DocumentClassifier - ML package
- ML packages with OCR capabilities
- 1040 - ML package
- 1040 Schedule C - ML package
- 1040 Schedule D - ML package
- 1040 Schedule E - ML package
- 1040x - ML package
- 3949a - ML package
- 4506T - ML package
- 709 - ML package
- 941x - ML package
- 9465 - ML package
- ACORD131 - ML package
- ACORD140 - ML package
- ACORD25 - ML package
- Bank Statements - ML package
- Bills Of Lading - ML package
- Certificate of Incorporation - ML package
- Certificate of Origin - ML package
- Checks - ML package
- Children Product Certificate - ML package
- CMS 1500 - ML package
- EU Declaration of Conformity - ML package
- Financial Statements - ML package
- FM1003 - ML package
- I9 - ML package
- ID Cards - ML package
- Invoices - ML package
- Invoices Australia - ML package
- Invoices China - ML package
- Invoices Hebrew - ML package
- Invoices India - ML package
- Invoices Japan - ML package
- Invoices Shipping - ML package
- Packing Lists - ML package
- Payslips - ML package
- Passports - ML package
- Purchase Orders - ML package
- Receipts - ML Package
- Remittance Advices - ML package
- UB04 - ML package
- Utility Bills - ML package
- Vehicle Titles - ML package
- W2 - ML package
- W9 - ML package
- Other Out-of-the-box ML Packages
- Public endpoints
- Traffic limitations
- OCR Configuration
- Pipelines
- OCR services
- Supported languages
- Deep Learning
- Licensing
Document Understanding User Guide
Document classification validation overview
After automatic classification, one optional (but highly recommended) step is that of classification validation.
This refers to a human review step, in which knowledge workers can review the classification results and correct them when necessary.
Using Classification Validation ensures that, downstream, all next steps within the Document UnderstandingTM Framework and run on the correct classification information.
It is strongly recommended to use the Document Classification Validation components when:
- you are dealing with multiple document types within a single file. This is a particularly important case, because if the automatic classification is wrong, or reports too few / too many pages within a class, if data extraction is also required downstream, then the data extraction component would be applied to the wrong content.
- you need 100% accuracy in classification and there are no other ways of validating that the classification results are correct.
Validating the classification results can be done by a human input through the use of Classification Station.
The Classification Station is available both
- as an attended activity, through the use of the Present Classification Station activity, or
- as Action Center tasks, through the use of the Create Document Classification Action and Wait for Document Classification Action and Resume activities.
