- Overview
- Document Understanding Process
- Quickstart tutorials
- Framework components
- ML packages
- Overview
- Document Understanding - ML package
- DocumentClassifier - ML package
- ML packages with OCR capabilities
- 1040 - ML package
- 4506T - ML package
- 990 - ML Package - Preview
- ACORD125 - ML package
- ACORD126 - 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 India - ML package
- Invoices Japan - ML package
- Invoices Shipping - ML package
- Packing Lists - ML package
- Passports - ML package
- Payslips - ML package
- Purchase Orders - ML package
- Receipts - ML Package
- Remittance Advices - 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
- Hardware requirements
- Pipelines
- Document Manager
- OCR services
- Deep Learning
- Document Understanding deployed in Automation Suite
- Install and use
- First run experience
- Deploy UiPathDocumentOCR
- Deploy an out-of-the-box ML package
- Offline bundles 2023.4.11
- Offline bundles 2023.4.10+patch1
- Offline bundles 2023.4.10
- Offline bundles 2023.4.9
- Offline bundles 2023.4.8
- Offline bundles 2023.4.7
- Offline bundles 2023.4.6
- Offline Bundles 2023.4.5
- Oflline bundles 2023.4.4
- Offline Bundles 2023.4.3
- Offline Bundles 2023.4.2
- Offline Bundles 2023.4.1
- Offline Bundles 2023.4.0
- Use Document Manager
- Use the Framework
- Document Understanding deployed in AI Center standalone
- Licensing
- Activities
- UiPath.Abbyy.Activities
- UiPath.AbbyyEmbedded.Activities
- UiPath.DocumentProcessing.Contracts
- UiPath.DocumentUnderstanding.ML.Activities
- UiPath.DocumentUnderstanding.OCR.LocalServer.Activities
- UiPath.IntelligentOCR.Activities
- UiPath.OCR.Activities
- UiPath.OCR.Contracts
- UiPath.OmniPage.Activities
- UiPath.PDF.Activities

Document Understanding User Guide
Install and use
This page describes how to deploy and configure Document UnderstandingTM, as well as special instructions on how to use Document UnderstandingTM on Automation Suite.
Document Understanding has a dependency on AI Center, meaning that AI Center always needs to be installed if Document Understanding is installed.
Also, Orchestrator must be activated before using Document Understanding.
Before starting the Document Understanding installation, make sure to check and satisfy all requirements for Automation Suite for single-node and for multi-node here.
A GPU is strongly recommended for Document Understanding in one of the following scenarios:
-
If you retrain the Document Understanding models (DocumentUnderstanding - the general model, Invoices, Receipts, etc.) on AI Center.
Training on CPU is 5-7 times slower and model performance degrades compared to training on GPU.
-
If you run UiPathDocumentOCR (non-edge version) on AI Center to process more than 2 million pages a year.
If you do not use a GPU, slow performance may impact the product experience.
For more details about how to provision a GPU, see Adding a dedicated agent node with GPU support.
Document Understanding requires the FullTextSearch feature to be enabled on the SQL server. Otherwise, the installation fails without an explicit error message.
Check the Document Understanding configuration file here.
Access Form Extractor and Intelligent Keyword Classifier, with the below public URL:
<FQDN>/du_/svc/formextractor
<FQDN>/du_/svc/intelligentkeywords
<FQDN>
placeholder with the actual environment information.For example <FQDN>/du_/svc/formextractor
becomes https://servicefabricserver.domain.com/du_/svc/formextractor
when used in a workflow.
As a post-installation operation, you can enable or disable Document Understanding. More details can be found here.
If you want to use the OCR for Chinese, Japanese, Korean endpoint in an offline environment, you need to install the offline bundle by following these instructions, and once the bundle is installed, you have to enable the OCR in ArgoCD.
To enable or disable the Chinese, Japanese, Korean OCR, check the instructions from the Automation Suite Admin Guide.
To enable or disable the Extended Languages OCR, check the instructions from the Automation Suite Admin Guide.
Check the Document Understanding-related issues here.