document-understanding
latest
false
- Overview
- Getting started
- Activities
- Insights dashboards
- Document Understanding Process
- Quickstart tutorials
- Framework components
- ML packages
- Overview
- Document Understanding - ML package
- DocumentClassifier - ML package
- ML packages with OCR capabilities
- 1040 - ML package
- 1040 Schedule C - ML package
- 1040 Schedule D - ML package
- 1040 Schedule E - ML package
- 1040x - ML package
- 3949a - ML package
- 4506T - ML package
- 709 - ML package
- 941x - ML package
- 9465 - ML package
- ACORD125 - ML package
- ACORD126 - ML package
- ACORD131 - ML package
- ACORD140 - ML package
- ACORD25 - ML package
- Bank Statements - ML package
- Bills Of Lading - ML package
- Certificate of Incorporation - ML package
- Certificate of Origin - ML package
- Checks - ML package
- Children Product Certificate - ML package
- CMS 1500 - ML package
- EU Declaration of Conformity - ML package
- Financial Statements - ML package
- FM1003 - ML package
- I9 - ML package
- ID Cards - ML package
- Invoices - ML package
- Invoices Australia - ML package
- Invoices China - ML package
- Invoices Hebrew - ML package
- Invoices India - ML package
- Invoices Japan - ML package
- Invoices Shipping - ML package
- Packing Lists - ML package
- Payslips - ML package
- Passports - ML package
- Purchase Orders - ML package
- Receipts - ML package
- Remittance Advices - ML package
- UB04 - ML package
- Utility Bills - ML package
- Vehicle Titles - ML package
- W2 - ML package
- W9 - ML package
- Other Out-of-the-box ML Packages
- Public endpoints
- Traffic limitations
- OCR Configuration
- Pipelines
- OCR services
- Supported languages
- Deep Learning
- Data and security
- Data residency
- Data storage
- Legal information
- Licensing
Document Understanding User Guide
Last updated Jul 8, 2025
Data storage
When consuming Document
UnderstandingTM
classic projects, data is stored in the following, depending on the situation:
- Runtime data in Automation CloudTM
- Validation data UiPath Orchestrator
For more information on data usage, check the Use of customer data with Document Understanding page from the Overview guide.
If you are using Document Understanding activities or Document Undertanding APIs, the following
data is persisted in Automation Cloud:
- The digitization result and document referenced by the document ID (either by providing it as input for APIs or using it in an RPA workflow as part of Document Data metadata) is stored for 7 days.
- The extraction or classification result is stored for 24 hours for asynchronous operations. There is no data stored for synchronous extraction and classification. Validation data is not persisted separately, but it is stored in Orchestrator storage buckets.
You can use the preview Delete API to remove
all runtime and validation data related to a given
documentId. For
more information, check the Use the Delete Document Data service page
from the Document Understanding API guide.
If you create classification or extraction validation actions, the system stores the respective assets, unless removed using the corresponding options on the activities (for example, the RemoveDataFromStorage activity from the IntelligentOCR activities package). You can also remove them manually from Orchestrator for the Document Understanding activities package.
You can use the preview Delete API to remove
all runtime and validation data related to a given
documentId. For
more information, check the Use the Delete Document Data service page
from the Document Understanding API guide.
