document-understanding

latest

false

Importante :

La localización de contenidos recién publicados puede tardar entre una y dos semanas en estar disponible.

Guía del usuario de proyectos modernos de Document Understanding

ENTREGA:

Última actualización 24 de mar. de 2026

Divisor entrenable (vista Previa)

Información general

The trainable splitter uses the Helix Classifier model to split and classify multi-document packets. It detects document boundaries automatically and assigns a document type to each detected sub-document.

The model is available only for tenants in Europe and the US.

Cuando usarlo

Use the trainable splitter in the following scenarios:

Mortgage applications: Split packets containing IDs, application forms, and bank statements.
Healthcare onboarding: Verify the presence of required documents such as medical certificates, NPI forms, and IDs.
Insurance claims: Separate claim forms, medical records, and receipts.
Invoice processing: Handle multi-vendor invoice packets.
Document cleanup: Remove irrelevant pages so that only relevant content is processed downstream.

Crear un nuevo proyecto

When creating a new project, tenants located in Europe and the US may enable the new splitter and classifier model. This trainable model can be trained to split and classify complex documents, enabling you to process document packets.

Follow the instructions on this page to create a Document Understanding^TM project and enable the new splitter and classifier model.

Requisitos previos

Before you begin, make sure the following conditions are met:

Your tenant is located in Europe or the US.
IntelligentOCR.Activities version 6.27.0 or later is installed.
Modern Projects is enabled in your Automation Cloud tenant.
You have sample document packets representative of your production use case.

Abre Document Understanding.
Selecciona Crear proyecto.
Enter the desired project name.
Selecciona Moderna para utilizar la experiencia moderna.
Configura las Opciones avanzadas si es necesario.
1. Switch on the Enable splitting toggle to allow the model to split documents into individual files before classification. You can also enable this option from the Project settings screen.
  Important: When the Enable splitting option is turned off, the model runs in classification-only mode:
  - The splitting annotation interface is unavailable.
  - Documents cannot be split manually.
  - For training, upload single-page or multi-page documents of the same type.
  - All other functionality remains unchanged.
2. Select the OCR method from the OCR method drop-down list.
3. Enter the OCR API Key.
  Note: This field is populated automatically if you select a UiPath® OCR.
4. Enter the OCR URL. For the full list of URLs for UiPath OCRs, see the Public Endpoints page.
5. Choose whether to Apply OCR on PDFs. The default is Auto.
Selecciona Crear.

Resultado

Your project is created. The Build section becomes available, where you can upload documents for extraction or classification.

Elige una de las dos opciones disponibles:

Extract data from documents: Pulls specific fields from your documents, such as invoice numbers, dates, and totals. Use this option when you need to extract fields from documents.
Classify and split documents: Sorts documents by type and separates multiple documents within a single file. Use this option when you need to split and classify documents.

Extraer datos de documentos

Selecciona un tipo de documento.
Selecciona Cargar o arrastra y suelta tus archivos dentro del nuevo tipo de documento. Espera a que finalice la carga.

Clasificar y dividir documentos

Certain complex files contain multiple document types. The trainable splitter detects where each sub-document starts and ends, and classifies each section accordingly.

Select Classify and Split Documents.
Upload your document packets. Wait for the upload and processing to finish.
Select a document from the upload section.
Select Split. The splitting annotation interface opens.
Note: If the project already has a trained model, uploaded documents are pre-annotated using that model. This helps speed up annotation and lets you review prediction results on new documents.
Select New document type to create a document type for each item in your taxonomy. Choose a predefined document type or create a custom one.
For custom document types, provide the following:
- Name: A clear, descriptive name for the document type.
- Description: One to three sentences explaining the document's purpose and what makes it distinct from similar types.
- Key indicators: Comma-separated fields or terms that uniquely identify this document type.
Descriptions and key indicators directly affect model accuracy. If classification scores are low, refine descriptions before adding more training data.

Example for an Invoice document type:
- Description: A formal payment request issued by a seller to a buyer, listing line items, quantities, and total amounts due.
- Key indicators: invoice number, invoice date, total amount, seller information, buyer information, payment terms
Tips for writing effective descriptions:
- Include terminology specific to the document type.
- If two document types are frequently confused, add distinguishing details to both descriptions.
Assign pages not needed for downstream processing to the Unknown type. This includes cover pages, blank pages, and separator sheets. The model predicts these pages as Unknown at runtime.
Select the boundaries between document types to indicate where each document starts and ends.
Assign each page range to a document type using the drop-down menu.
Select Confirm when you have finished annotating the document.

Resultado

Each sub-document appears under its corresponding document type in the Build section. Each sub-document is pre-annotated with the schema of its assigned document type.

Training best practice

Train on original, unsplit production document packets — not on pre-split individual documents.

The model learns document-bundling patterns from the context around each document type: what appears before it and after it in a real packet. Training on pre-split documents removes this context and reduces splitting accuracy.

Enfoque recomendado:

Upload production packets that contain multiple document types.
Include packets that represent the range of orderings and document counts seen in production.
Aim for a balanced dataset across all document types.

Note: Training on pre-split documents produces a working model, but splitting accuracy is lower than when training on original packets.

Entrenamiento del modelo

Model training starts automatically after both of the following conditions are met:

At least five sub-documents have been created and annotated.
Note: For example, if you are using a single PDF, it must contain at least five sub-documents. If you are using two PDFs, one must contain at least two sub-documents and the other at least three.
se ha confirmado un documento.

The training status is visible in the upper right corner of the Classification pane.

Training data requirements

Requisitos	Detalles
Minimum document types	1
Minimum total samples	5 documents across all document types
Minimum samples per type	1
Recommended for reliable results	50 to 100 packets
Maximum document size	160 MB or 500 pages
Train/test split	Automatic: 80% training, 20% test

Improving training results

When performance is unsatisfactory, use one of these approaches:

Refine the descriptions and key indicators of underperforming document types.
Add more training samples for document types with low accuracy.

Predicciones de división y clasificación

Whenever a new model is trained, all documents in the project receive predictions from the trained model. This lets you review the performance of the classification model.

The Type column displays the ground truth — the document type as annotated. The Predicted type column shows the type predicted by the model.

By default, only document packets are displayed. To view sub-documents within each packet, select View and check Include sub-documents.

Predictions are also available in the annotation interface by enabling the Show Prediction toggle.

Understanding metrics

Select the Measure tab to review model performance.

Métrica	What it measures	What to do if low
Splitting F1	Accuracy of document boundary detection, independent of classification	Add training data with more varied boundary examples
Classification F1	Accuracy of document type assignment, independent of boundaries	Add more training pages for underperforming document types
Overall F1	Combined score: boundary and type assignment must both be correct	Identify whether splitting or classification is lower and address that first

A sub-document is counted as correct only when both the boundary detection and the type assignment are correct.

Note: Large documents with many Unknown pages in the test set can lower scores disproportionately. If scores appear unexpectedly low, check whether outlier documents are skewing the test set.

Consuming the model at runtime

Via IntelligentOCR activities

Use the Document Understanding Project Classifier activity from the IntelligentOCR package. When splitting is enabled in the project, the activity returns multiple ClassificationResults — one per detected sub-document. Iterate over the results to perform validation or extraction on each sub-document.

Via DocumentUnderstanding activities

Use the Classify Document activity.

Via API

Use the classify endpoint. When splitting is enabled in the project version, the endpoint performs splitting and returns classification results for each identified sub-document.

Importing and exporting

Exporting a trained model dataset

If a project version contains a trained splitter classifier, two export options are available:

Document Type Dataset Export: Standard export of annotated data.
Splitter and Classifier Export: Full project export including the trained model.

Only project versions with a trained splitter classifier appear in the Splitter and Classifier Export drop-down list.

Importing into a new project

The import option is available on the empty classification page. Importing a zip file assigns documents to their document types and triggers training automatically.

Limitaciones

Available only in tenants located in Europe and the US.
Pages cannot be reordered or deleted in the annotation interface.
Splitting information is not available in the Monitor page.
Retraining from the Action Center is not supported for splitting and classification models.

En esta página

Información general
Cuando usarlo
Creating a new project
Extracting data from documents
Classify and split documents
Training best practice
Entrenamiento del modelo
Splitting and classification predictions
Understanding metrics
Consuming the model at runtime
Importing and exporting
Limitaciones

¿Te ha resultado útil esta página?

AnteriorCrear un proyecto

Sig.Importar documentos