Metering and charging logic

When using UiPath® Document Understanding^TM modern projects, it's essential to understand the consumption of AI units. Modern projects use one AI unit per page, regardless of the processing form (digitization, classification, extraction, and any combination of these on the same document).

AI units charges per page

A unique feature for modern projects is that regardless of the operations performed on a page at runtime - be it digitization, extraction, or classification - only one single AI unit is charged. This applies to all operations, encompassing both robotic process automation (RPA) and API operations.

Check the examples below for AI units consumption depending on the operations done per page:

• OCR only → 1 AI unit / page
• OCR and classification → 1 AI unit / page
• OCR, classification, and extraction → 1 AI unit / page

Document Understanding activity packages

For the DocumentUnderstanding.Activities package, the following metering and charging policies apply:

• If you use the Classify Document activity to process a document, triggering digitization and the result is stored in a Document Data → 1 AI unit / input page
• If you then use the Extract Document Data activity to:
  • Process a document using the file itself as input, triggering digitization → the total cost is 2 AI units / page
    Note: You can also process a document using the file itself with the Extract Document Data activity without classifying it previously. In this case, the total cost is 1 AI unit / page.
  • Process a document using Document Data, the output of Classify Document, as input → the total cost is 1 AI Unit / page

For the InteligentOCR.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 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.

AI units and model training

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.

AI units charges per 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.

AI units and model training

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.

Generative features

Depending on the version of the activity package you are using, there are slight differences related to AI units consumption. The consumption models are detailed in the sections that follow.

Activities version 24.12-preview and newer

This consumption is applied when using PredefinedGenerative projects with the following::

• IntelligentOCR newer than 6.23.2-preview.
• DocumentUnderstanding.Activities newer than 2.13.2-preview.
• Document Understanding API v1.1.

Consumption:

• 1 AI Unit per processed page (includes Generative Classification and Generative Extraction)

Activities version older than 24.12-preview

This consumption model is applied when using:

• IntelligentOCR up to 6.23.2-preview with PredefinedGenerative projects;
• DocumentUnderstanding.Activities up to 2.13.2-preview with PredefinedGenerative projects;
• Document Understanding API v1.0 with Predefined projects.

AI Units consumption for generative features in activity versions older than 24.12-preview is detailed 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 process a document using extraction and Generative Classifier, the consumption is 1.2 AI units per page.

Document Understanding activity packages

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.

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.

Mixed use

If a project is using both classic and modern experience, both pricing models will apply based on their respective consumption.

The pricing model for classic projects applies under the following circumstances:

• 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).

For more information on the metering and charging logic applicable for classic scenarios, check the Document Understanding User Guide for Classic Experience.