- 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
- Data and security
- Licensing and Charging Logic
- API Key
- Metering and charging logic
- How to
- Troubleshooting
Document Understanding User Guide
Metering and charging logic
When using UiPath® Document UnderstandingTM 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).
A unique feature for modern projects is that regardless of the operations performed on a page at runtime - be it digitization, extraction, or classification - or if multiple projects are used to extract data from the same page, only one single AI unit is charged. This applies to all operations, encompassing both robotic process automation (RPA) and API operations.
- OCR only → 1 AI unit / page
- OCR and classification → 1 AI unit / page
- OCR, classification, and extraction → 1 AI unit / page
- OCR, classification, extraction, and Generative Validation → 2 AI units / page
- 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
- 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.
