- Overview
- Getting started
- Building models
- Consuming models
- Model Details
- Public endpoints for Automation Cloud and Test Cloud
- Public endpoints for Automation Cloud and Test Cloud Public Sector
- 1040 - document type
- 1040 Schedule C - document type
- 1040 Schedule D - document type
- 1040 Schedule E - document type
- 1040x - document type
- 3949a - document type
- 4506T - document type
- 709 - document type
- 941x - document type
- 9465 - document type
- ACORD125 - document type
- ACORD126 - document type
- ACORD131 - document type
- ACORD140 - document type
- ACORD25 - document type
- Bank Statements - document type
- Bills Of Lading - document type
- Certificate of Incorporation - document type
- Certificate of Origin - document type
- Checks - document type
- Children Product Certificate - document type
- CMS 1500 - document type
- EU Declaration of Conformity - document type
- Financial Statements - document type
- FM1003 - document type
- I9 - document type
- ID Cards - document type
- Invoices - document type
- Invoices2 - document type
- Invoices Australia - document type
- Invoices China - document type
- Invoices Hebrew - document type
- Invoices India - document type
- Invoices Japan - document type
- Invoices Shipping - document type
- Packing Lists - document type
- Payslips - document type
- Passports - document type
- Purchase Orders - document type
- Receipts - document type
- Receipts2 - document type
- Receipts Japan - document type
- Remittance Advices - document type
- UB04 - document type
- US Mortgage Closing Disclosures - document type
- Utility Bills - document type
- Vehicle Titles - document type
- W2 - document type
- W9 - document type
- Supported languages
- Insights dashboards
- Data and security
- Logging
- Licensing
- API Key
- Cloud and on-premises usage
- Metering and charging logic (Unified Pricing)
- Metering and charging logic (Flex Plan)
- How to
- Troubleshooting
Document Understanding user guide
The licensing information on this page applies to you if you are on Unified Pricing. If you enrolled in Flex Plan instead, refer to [Flex] Metering and Charging Logic. For general licensing information, refer to Automation Cloud admin guide.
When using UiPath® Document UnderstandingTM modern projects, it's essential to understand the consumption of Platform Units.
Platform tiers
The following table describes the available features in Document Understanding depending on the chosen Platform tier:
| Feature | Feature description | Basic | Standard | Enterprise |
|---|---|---|---|---|
| Opt out of data collection | Allow customers to open support tickets so that they may opt out of data collection. | No | Yes | Yes |
User licenses
The following table describes which user licenses provide access to Document Understanding:
| Unlicensed | Express | Basic | Plus | Pro |
|---|---|---|---|---|
| No | No | Yes | Yes | Yes |
How charging works for modern projects
For Document Understanding modern projects, 0.2 Platform Units are charged per page, regardless of the operations performed at runtime or the number of modern projects extracting data from the same page. The single per-page charge covers:
- Digitization, including OCR
- Extraction
- Classification
This applies to both robotic process automation (RPA) and REST API operations. For full REST API pricing — including how classic-project API calls are charged — see Metering and Charging in the API guide.
For information regarding IXP metering and pricing, visit the IXP Unified Pricing page.
Through Document Understanding activity packages
For both DocumentUnderstanding.Activities and IntelligentOCR.Activities, 0.2 Platform Units are charged per page, regardless of the operations performed (digitization, extraction, or classification).
The 0.2 Platform Units per-page rule applies only when:
- For
DocumentUnderstanding.Activities: a pre-defined generative or modern project classifier or extractor is in use. - For
IntelligentOCR.Activities: a modern project classifier or extractor is in use.
If you use any other classifier or extractor, the respective consumption logic from classic projects is added to the 0.2 Platform Units per page. For more information, see Mixed projects (modern + classic).
Generative features — Activities 24.12-preview and above
This consumption applies in the following situations:
- Using these activity versions with
PredefinedGenerativeprojects:IntelligentOCRnewer than 6.23.2-previewDocumentUnderstanding.Activitiesnewer than 2.13.2-preview
- Using Document Understanding API v1.1 with
PredefinedGenerativeprojects.
There are no additional AI units consumed when using Generative Classification and Generative Extraction. Only 0.2 Platform Units are charged per page, regardless of the operations performed, including Generative Classification and Generative Extraction.
Using Generative Validation consumes an additional 0.2 Platform Units for each processed page. This brings the total to 0.4 Platform Units consumed per page when generative validation runs.
Generative features — Activities up to 24.12-preview
This consumption applies in the following situations:
- Using these activity versions with
PredefinedGenerativeprojects:IntelligentOCRup to 6.23.2-previewDocumentUnderstanding.Activitiesup to 2.13.2-preview
- Using Document Understanding API v1.0 with the
Predefinedproject.
In these versions, generative features incur specific charges per operation, as described in the following table.
Table 1. Generative features Platform Units consumption for activities versions up to 24.12-preview
| Generative feature | Consumed Platform Units |
|---|---|
| Generative Classifier | 0.04 per operation |
| Generative Extraction | 0.24 per operation |
| Generative Validation | 0.2 per operation |
Model training
There are no Platform Units charged when training and serving models. You can train models freely to improve performance, develop new capabilities, and experiment without incurring additional Platform Units charges.
Mixed projects (modern + classic)
When a project uses both classic and modern experiences, both pricing models apply based on their respective consumption.
The pricing model for classic projects applies in the following circumstances:
- Extraction and classification done using classic projects, regardless of the activity package used (
IntelligentOCRorDocumentUnderstanding.Activities). - Extraction and classification done using the out-of-the-box models included with the pre-defined project, regardless of the activity package used.
- REST API calls against classic-project models — classic per-capability rates apply, not the 0.2 Platform Units per-page rule.
For full classic-project metering — including activity-based rates per OCR engine, classifier, and extractor — see the Document Understanding User Guide for Classic Experience. For classic-project REST API rates specifically, see Metering and Charging in the API guide.