- 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
When using UiPath® Document UnderstandingTM modern projects, it's essential to understand the consumption of AI units.
- For licensing information for classic projects, check the Metering and charging logic page from the Document Understanding User Guide for classic projects.
- To track your AI units consumption at organization and tenant level, check the AI units consumption overview dashboard pages.
- To track AI units consumption for Document Understanding and AI Center projects, check the IxP AI Unit consumption dashboard page.
How charging works for modern projects
For Document Understanding modern projects, AI units are charged per operation. You pay only for the operations you run on each page:
| Operation | AI units per page |
|---|---|
| Digitization (including OCR) | 0 |
| Classification | 0.2 |
| Extraction (with prior classification) | 0.8 |
| Extraction (without prior classification) | 1 |
Per-page cap: A page that is both classified and extracted never exceeds 1 AI unit in total. Digitization is always free.
The per-operation rate is the same regardless of which classifier or extractor you use, including:
- Classifiers: Generative, Predefined, ML, and Helix Classifier 1.0.
- Extractors: Generative, Predefined, Legacy, Helix Extractor 1.0, and Helix Extractor 2.0.
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.
If multiple extractors are applied to the same page, each extraction is counted separately and charged at 0.8 AI units, or 1 AI unit without prior classification. Applying the same model multiple times to the same page does not multiply the charge.
Through Document Understanding activity packages
For both DocumentUnderstanding.Activities and IntelligentOCR.Activities, the per-operation rates apply, based on the operation performed.
The per-operation rates apply 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 per-operation charge. For more information, see Mixed projects.
Generative features — Activities 24.12-preview and above
This consumption applies in the following situations:
- Using activities version 24.12-preview and above with
PredefinedGenerativeprojects. - Using Document Understanding API v1.1 with
PredefinedGenerativeprojects.
There are no additional AI units consumed when using Generative Classification and Generative Extraction. They follow the same per-operation rates as any other classifier or extractor, which means 0.2 AI units for classification and 0.8 AI units for extraction with prior classification, capped at 1 AI unit per page.
- Generative features are included in the per-operation rate when using
IntelligentOCR.Activitiesversions newer than 6.23.2-preview, orDocumentUnderstanding.Activitiesversions newer than 2.13.2-preview. On earlier versions, generative features use the separate consumption logic described in the following section. - Using Generative Validation consumes an additional 1 AI unit per processed page, bringing the total to 2 AI units per page when it runs.
Generative features — Activities up to 24.12-preview
This consumption applies in the following situations:
- Using activities version up to 24.12-preview with the
Predefinedproject. - 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 AI units consumption for activities versions up to 24.12-preview
| Generative feature | Consumed AI units |
|---|---|
| Generative Classifier | 0.2 per operation |
| Generative Extraction | 1.2 per operation |
| Generative Validation | 1 per operation |
Model training
There are no AI units charged when training and serving models. You can train models freely to improve performance, develop new capabilities, and experiment without incurring additional AI 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 1 AI unit 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.