- Overview
- Getting started
- Building models
- Consuming models
- ML packages
- Public endpoints
- 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
- Data and security
- Licensing and Charging Logic
- How to
- Troubleshooting

Document Understanding User Guide
Retrain extractors
linkYou can use documents that were validated in Validation Station to further improve the performance of your models.
You can currently only retrain documents that were processed using the UiPath.DocumentUnderstanding.Activities package. All documents that were processed using this activity package and were validated in Validated Station are collected automatically and can be used for retraining.
When there is at least one document collected, the Exceptions for review button is available for the corresponding document type within the Build section.
Exceptions for review
linkDocuments are not collected for validation tasks with a duration greater than 7 days.
-
Select the Exceptions for review button.
Figure 1. Exceptions for review button
-
Check the exception documents from the Exceptions for fine-tuning
menu.
The following information is available for each document:
- File name: the file name of the document containing an exception.
- Status: the status of the document.
- Pages: the number of pages that the document contains.
- Project version: the project version that contains the document.
- Processed date: the date when the document was processed.
- No of extracted fields: the number of extracted fields for the document containing an exception.
- No of corrected fields: the number of modified fields during validation step.
- Validator name: the username of the person who validated the document.
Figure 2. Exceptions for fine-tuning menu
-
Select the document you want to use for fine-tuning from the list.
The following information is available for each document:
- All extracted fields are displayed, along with their model confidence. If the confidence value is N/A, this indicates that the field was not automatically extracted and was instead manually added by the validator.
- Corrected fields are marked with a yellow point next to extracted field name.
- The following information is available for all corrected fields:
- Predicted value: the value predicted by the model.
- Corrected value: if changed manually, the value after validation. If the document type was not changed after validation, the value will be N/A.
- Reference: the original value that is highlighted on the document. This value is used for annotation if you decide to use the document for fine-tuning.
- You can easily sort by confidences to check fields with low confidences without corrections.
- You can filter by corrected fields to only focus on them.
Figure 3. Exceptions for fine-tuning menu
-
Choose Annotate if you want to further annotate this document or choose
Use for fine-tuning if you want to use this document to retrain your
model.
- Use for fine-tuning:
- Choose this when the document is a good example for the model fine-tuning and all fields are correctly referenced within the document.
- The document is imported in the training with the Exception tag and all annotations confirmed. The document will be used for fine-tuning.
- Annotate:
- Choose this the document is a good example for the model fine-tuning, but there are some validation errors, for example not all fields are correctly referenced wihtin the document and further corrections are needed.
- The document is imported in the training set with the Exception tag and all annotations unconfirmed. Annotations must be confirmed in the Build section in order for the document to be used to fine-tune the model.
- If you choose to further annotate your document, check the Annotate documents page for more information on how to annotate documents.
- Exclude:
- Choose this when the document is not a good example and you want to remove it from the list of exceptions for review and you do not need to review it in future review sessions.
- You can change the status of the document to revert the changes.
Figure 4. Selected document used for fine-tuning or annotation
- Use for fine-tuning:
You can create a new project version and use the Compare model feature from the Measure section to compare the performance of your model.