What is your primary use case for UiPath Document Understanding?

We use UiPath Document Understanding to comb through our documents, help us prepare reports, analyze the information, and later combine the information obtained into fact sheets, results, and reports that can be used for online planning and decision-making. We implemented UiPath Document Understanding to build an accurate and intelligent platform. We needed a platform with the necessary tools to help us automate the whole process and reduce the errors involved in document Understanding, which arise from the manual processing of our documents. We use UiPath Document Understanding for project management, which has also been implemented in customer service and production. So it's helping us in several business processes. We have it deployed on the cloud and on-premise. We use the cloud for remote work, and it is used on-premises at the company workstation.

Our old process involved manual data extraction from a large volume of documents with varying types and templates. This labor-intensive task required a significant workforce. We implemented UiPath Document Understanding to automate this process and eliminate the need for hand-coding solutions.

UiPath Document Understanding is a key tool we use to automate document processing for our clients, including tasks like invoice and sales order processing. We can create multiple workflows for different clients and even use it internally. To handle even more complex documents, we've also built custom models for specific data extraction needs. UiPath Document Understanding helps our clients streamline data entry by accurately and consistently extracting information from both paper and digital documents. This extracted data can then be seamlessly integrated into their existing ERP or finance systems, eliminating the need for manual data input.

We use the solution for purchase accounting, where we need a lot of invoices from various vendors.

Our clients use UiPath Document Understanding for their purchase order creations. We need to process invoices received from vendors. This involves posting the data to SAP and creating a virtual file. To extract data from the vendor's PDF documents, we utilize UiPath Document Understanding.

We use Document Understanding to validate invoices during audits. The software reads the invoices in the first step of the process, and we process them before making the payment. You must review the process and validate what's in the invoice that goes into the Oracle ERP system. We cross-check to see if the value matches or not. We use Microsoft Forms to capture and extract the information, so we are executing lots of documents to Microsoft Form and auditing what's in the system, comparing that to the information in the invoices.

We use Document Understanding to process invoices, purchase orders, and addresses. It extracts data from a scanned structured document and converts that in a structured manner to a spreadsheet. Predominantly, we use Document Understanding for payroll, procurement, invoice processing, and also in the finance department. Document Understanding has multiple models for extracting data from receipts. Departments have different use cases, but it's mostly used on the finance side to extract invoice data. The volume of documents varies from customer to customer. When everyone starts using the product, they typically process between 10,000 to 20,000 in the first year. Once you've achieved a stable environment, you might reach around 500,000 pages in the second or third year. It depends on the project and the customer's budget because pricing is based on the number of pages. We are not talking about 100 percent data automation end to end. If our customers work with hundreds of vendors, they deal with various templates. If a new vendor comes in, there is a possibility that the model may not identify that particular document. It's also possible that the upload quality isn't that great because of a bad scan, so there is always a channel for manual processing to handle exceptions. When you implement Document Understanding, we may start with 40 percent automated and 60 percent manual. As it progresses and matures, the percentage gradually improves. We may eventually achieve 80 percent fully automated processing with 10 percent manual so that exceptions can be handled with the help of human intervention.

I work for different clients. Currently, I have three clients, and I use it based on their requirements. We have contract generations, and we extract data from contracts. This is our primary use case. We are receiving documents through an omnichannel, and we extract data based on the business requirements. After that, we automate and upload the data to Salesforce and SAP. We process 1,000 to 1,500 invoices weekly. They are mostly semi-structured contracts. There are also some invoices or printed bills.

In a medical healthcare department, when we need to retrieve digital documents, we need to classify them. The first step is to use AI to understand what type of documents we're dealing with. Once we've identified the template, we can extract information using specific OCR tools. Depending on the confidence of the extracted results, we may need to apply additional OCR, use a more active tool, or pass the document to an agent for review if the AI doesn't recognize a specific element like the "person page of the commission." Finally, the extracted fields are classified within the system and organized into different folders. This is the process I'm using with UiPath Document Understanding.

I used UiPath Document Understanding to create a report by reading invoices and V9 tax documents. I employed specific taxonomies to facilitate document analysis and populate my database with extracted information. The primary objective was to accurately identify and store relevant data from these documents within the database. The idea arose from the observation that many companies lack a centralized repository for essential documents, such as invoices. In response, I created a website where a robot automatically uploads and interprets these invoices, presenting key details about each document on the website.

We are a system integrator in the manufacturing industry and our clients use UiPath Document Understanding for their invoicing cycle processing. Previously, our clients manually entered invoices into their systems, seeking a solution to automate this process while still maintaining controls for verification and audit purposes. We implemented UiPath Document Understanding to address this need.

The primary use case revolves around processing invoices. In Israel, where the solution is region-oriented, the invoices typically involve multiple languages within a single document and may also include various currencies. The capability of handling such diverse linguistic and currency elements is a notable strength of UiPath Document Understanding in this context. Through its implementation, our goal was to minimize manual tasks significantly and reduce the time required for invoice processing.

The use case is related to invoice processing. We extract details from the invoices, and after those details are extracted, we use the UiPath RPA bot to process those invoices. We have installed it on the client's machine and integrated it with the UiPath RPA bot. Document Understanding extracts the details from the document, and the UiPath RPA bot picks up this data and puts it in the system to process the invoice. We are processing 2,00,000 to 3,00,000 invoices received from the vendors. They have structured data. There is no barcode on the invoice. There is structured data with date, invoice number, fax code number, amount, etc. It is a printed invoice.

A recent use case was for an insurance company based in the United States. For that, we were recording or collecting the data from the insurance brokers who used to fill their documents. We had to find a few segments on the basis of them. We were collecting the data and confirming whether those brokers were coming from an authentic source. They had a stamp or a legal insurance number, and we were maintaining a few dictionaries containing the images of their signatures. Once we received a document from a broker, we passed the whole document into different segments, and then we just validated the signature part to see if it was coming from an authentic source. We validated that the signature and the image looked similar, and there was at least 80% similarity. We were extracting the IPIN number from the Microsoft Intelligent OCR. We were able to extract almost 85% to 90% of the numbers. It contained digits that were being imposed on a stamp that we had provided to them, so there was less complexity because there was less human intervention. They were not manually writing those numbers where it could be a bit difficult for us to diagnose whether it was a four or a nine. With a digitized number imposed on the stamp, it was a bit easier for us to read it out. This is the use case that we just finished and deployed, and it is processing 150 to 230 requests on a daily basis. I have mostly been automating banking, financial services, and insurance (BFSI) processes.

In Italy, one of the most prevalent use cases involves automating the processing of invoicing cycles. The issue we aimed to address through the integration of this solution is essentially the manual input of data into systems by humans and the need for checks and balances between invoicing and other physical documents. Our organization is in the manufacturing realm. We primarily use Document Understanding to process invoices, specifically a common document in Italy known as the BDT. Regarding the document format, it includes structural elements like tables, checkboxes, and headers. Some documents may feature large tables, and the header contains essential information that needs to be extracted. In terms of volume, for a medium-sized or small company, we handle approximately ten thousand of these documents annually.

We use UiPath Document Understanding to process purchase orders and order confirmations. We implemented UiPath Document Understanding because we wanted a more efficient way to process the documents we were receiving.

We use UiPath Document Understanding for two purposes: extracting information from medical certificates issued by a prominent university in Singapore and processing invoices for a client in the logistics industry within their ERP systems. We implemented UiPath Document Understanding to significantly reduce the substantial mailout effort. Approximately 20 full-time employees were previously dedicated to these processes, but after implementation, we were able to halve the number of full-time employees required.

I've done multiple projects. A couple of them included invoice processing. It has a machine learning package that works out of the box. For invoices. I use that. It does a very good job. I also use document understanding, which doesn't have any training. I trained it for the extraction of data for some forms like car loan installments. It did a pretty good job. In addition, I used it for a medical department. I use document understanding.

We have processes for purchase orders. We need to analyze the content of these files and some invoices. Based on that, we are able to perform qualifications and post them to the CRM system. Overall, we call this our invoice control process. We wanted to optimize the performance, meaning the time the process takes, and the quality. We had some problems with the quality of transferring the data because people would make mistakes. If they were doing 80 documents per day, there was a high possibility that they would forget to look for some information or they would copy and paste the wrong fields.

Our client has PDF invoices and we use the solution to extract the details from them. We are using it in finance and health care. We have about 16 templates that we process now. The data is in semi-structured format and we mostly process things like signatures and tables. Out of the 16 templates, about 12 are completely processed automatically.

I use the tool for a couple of my client projects. My clients receive physical mail and may need to scan data to run processes like automation on it. Another use case is document classification. The solution helps with processes like classification, data extraction, and automation.

We use UiPath to process HR documents. It helps us with the last mile of the paperwork. We're dealing with a lot of offline legal documents that need to be converted to Word or PDF. We use UiPath to read the documents and process them into a digital form the company can use. We're consultants, so we have to provide invoices for our services. We have a specific layout that's internally defined, and we store the information in SAP. It's processing thousands of documents. Most of them are PDF forms. Our customers and partners usually save these documents and send them to us by mail or email. Almost all of our documents are processed through UiPath.

We are a service-based company, having a team size of 120 RPA developers.

I primarily use Document Understanding to onboard clients and gather information for our databases.

My company has a confidential website where timesheets, salary statements, and other information regarding employee working hours are provided in PDF format. I plan to use UiPath's Doughnut Scatter and Keyword Classifier to extract specific data from these PDF documents.

We are partners with UiPath.