- Overview
- Getting started
- Building models
- Consuming models
- ML packages
- 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
- 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
- Remittance Advices - document type
- UB04 - document type
- Utility Bills - document type
- Vehicle Titles - document type
- W2 - document type
- W9 - document type
- Public endpoints
- Supported languages
- Insights dashboards
- Data and security
- Licensing
- API Key
- Cloud and on-premises usage
- Metering and charging logic
- How to
- Troubleshooting
Document Understanding Modern Projects User Guide
Metering and charging logic
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 [Preview] Document Understanding and AI Center consumption dashboard page.
For Document Understanding modern projects only one single AI unit is charged, regardless of the operations performed on a page at runtime or if multiple modern projects are used to extract data from the same page. This includes digitization operations - such as OCR - as well as extraction, or classification. This applies to all operations, encompassing both robotic process automation (RPA) and APIs operations.
For AI units consumption when using generative features, check the Generative features section from this page.
There are no AI units charged when training and serving models. This means you can freely train models to improve performance, develop new capabilities, and experiment without concerns about incurring additional AI units charges.
- Activities versions newer
than:
- IntelligentOCR 6.23.2-preview
- DocumentUnderstanding.Activities 2.13.2-preview
- Activities versions up to:
- IntelligentOCR 6.23.2-preview
- DocumentUnderstanding.Activities 2.13.2-preview
- Using the following
activities versions with
PredefinedGenerativeprojects:- IntelligentOCR newer than 6.23.2-preview
- DocumentUnderstanding.Activities newer 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. There is only one single AI unit is charged, regardless of the operations performed on a page at runtime, including Generative Classification and Generative Extraction.
- Using the following activities versions with
PredefinedGenerativeprojects:- IntelligentOCR up to 6.23.2-preview
- DocumentUnderstanding.Activities up to 2.13.2-preview
- Using Document Understanding
API v1.0 with the
Predefinedproject.
Using generative features incur specific charges for each operation, as described in the following table.
| Generative feature | Consumed AI units |
|---|---|
| Generative Classifier | 0.2 per operation |
| Generative Extraction | 1.2 per operation |
| Generative Validation | 1 per operation |
For example, if you are processing a document using extraction and Generative Classifier, the consumption is 1.2 AI units per page.
For the DocumentUnderstanding.Activities package, one AI unit is charged per page, regardless of the operations performed - whether it's digitization, extraction, or classification. This only applies when a pre-defined generative or modern project classifier or extractor is in use. If you use any other classifier or extractor, the respective consumption logic from the classic projects is added to the one AI unit per page. For more information, check the Mixed use section below.
For the InteligentOCR.Activities package, one AI unit is charged per page, whether it's digitization, extraction, or classification. This only applies when a modern project classifier or extractor is in use. If you use any other classifier or extractor, the respective consumption logic from the classic projects is added to the one AI unit per page. For more information, check the Mixed use section below.
If a project is using both classic and modern experience, both pricing models will apply based on their respective consumption.
- Extraction and classification done using classic projects, regardless of the activity package used (IntelligentOCR or Document Understanding).
- Extraction and classification done using the out of the box models included with the pre-defined project, regardless of the activity package used (IntelligentOCR or Document Understanding).
