- Overview
- About Document Understanding™
- Introduction
- Document types
- Fundamental capabilities
- Key concepts
- Getting started
- Choosing the deployment type
- Enable Document Understanding™
- Role-based access control
- Choosing the automation type
- Document Understanding Process template
- Building models
- Introduction
- Create a project
- Import documents
- Build
- Measure
- Publish
- Migrating modern projects
- Monitor
- Infrastructure
- Known limitations
- Consuming models
- Automations in Document Understanding™
- Activities
- API calls
- Consuming models from different environments
- Model Details
- Public endpoints
- Pre-trained document types
- 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
- Overview
- OCR
- ML models and capabilities
- Data and security
- Customer-Managed Keys
- Legal information
- Licensing and Charging Logic
- API Key
- Metering and charging logic
- How to
- Annotate documents
- Tables and group table rows
- Checkboxes and signatures
- Annotation best practices
- Classify documents automatically
- Retrain extractors
- Train a classifier
- Troubleshooting
- About troubleshooting
- Moving Document Understanding™ modern projects between tenants or organizations
Document Understanding User Guide for Automation Cloud Dedicated
Before you begin the annotation process, it's important to create a comprehensive list of all the necessary fields for the particular type of document. Define each field clearly to prevent any confusion. Depending on your preference, you can use a sample document and annotate it as an example, or you can create a detailed table that explains each field.
- Column fields
- Regular fields
If you notice a field appearing multiple times in the same document and with the same value, make sure to annotate each instance of this field. For instance, if the invoice number appears both at the top and bottom of the document, you should annotate both instances.
In cases where values differ, you should only annotate the correct value. This can also apply to instances where the value varies across different documents from the same vendor or variation. In such situations, always prioritizing vendor consistency is key, even if this means ignoring values that occasionally differ.
An important principle is to maintain consistency when annotating across similar layouts. This ensures clean and uniform data.
Additionally, make sure all annotated data is complete. Double-check to avoid missing words in addresses or other critical information.
Date: 28-11-2022 as the date, make sure to remove Date:. This keeps your information succinct and precise.
If you are working with multiple tables, remember that each column in every table needs its own column field. This process is important to accurately and effectively capturing data.
Enter hotkey. This will tie the fields together and enable more efficient processing of the table.
CTRL+Left Click, and then select Enter to achieve this group. This enables the system to read rows seamlessly, even when they span multiple pages.