Try our new research platform with insights from 80,000+ expert users
Sr Software Developer
Real User
Offers multiple types of extractors, saves us time, and reduces human errors
Pros and Cons
  • "UiPath Document Understanding offers multiple types of extractors, which we can use to extract information from documents in a variety of ways."
  • "UiPath Document Understanding has difficulty identifying handwritten documents, and there is room for improvement."

What is our primary use case?

I use UiPath Document Understanding to extract data from digital invoices.

We implemented UiPath Document Understanding to eliminate the need for manual invoice data extraction.

We process 50 invoices per day for a logistics organization. We receive the invoices from the user, and a bot reads them one at a time, extracts the details and stores them in an Excel file. If the extraction does not match the confidence score, we send the invoice to the Action Center for manual validation. Once the data is extracted, the bot enters it into SAP and validates it against the system information.

How has it helped my organization?

We used machine learning to train a model to process the different formats we were receiving.

Seventy percent of the documents we process are completed automatically without any manual intervention.

The AI and machine learning capabilities of UiPath Document Understanding are good.

Once trained on a large dataset, AI can save us significant time by performing tasks that are beyond our capabilities.

Human validation is required for about 25 percent of the documents we process. For smaller documents, it takes a human a few minutes to validate the information.

Our average handle time after implementing UiPath Document Understanding is five minutes.

UiPath Document Understanding has helped reduce human error.

UiPath Document Understanding has helped free up our staff time.

We can see results as early as two months, and definitely by six months.

What is most valuable?

UiPath Document Understanding offers multiple types of extractors, which we can use to extract information from documents in a variety of ways. Machine learning is a particularly useful method, as it allows us to train custom models to meet our specific needs.

What needs improvement?

UiPath Document Understanding has difficulty identifying handwritten documents, and there is room for improvement.

Some of the invoices we process are stamped, and the AI has difficulty understanding them because the stamp format varies between a square and a circle. Resolving this issue will allow us to process more complex documents using UiPath Document Understanding.

Buyer's Guide
UiPath Document Understanding
October 2024
Learn what your peers think about UiPath Document Understanding. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,763 professionals have used our research since 2012.

For how long have I used the solution?

I have been using UiPath Document Understanding for one year.

What do I think about the stability of the solution?

UiPath Document Understanding is stable.

What do I think about the scalability of the solution?

UiPath Document Understanding is scalable.

What other advice do I have?

I would rate UiPath Document Understanding eight out of ten.

The solution was deployed in a single department for multiple users.

Maintenance is required for continuous training whenever an invoice format changes or a new vendor is added.

I recommend conducting a POC with the community to ensure that UiPath Document Understanding meets the organization's requirements before fully implementing it.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Integrator
PeerSpot user
RPA Developer at a non-tech company with self employed
Real User
Reduces development time and improves productivity and accuracy
Pros and Cons
  • "The machine learning (ML) extractor is valuable. It helps in extracting information from even unstructured documents. It can sometimes also extract information from a written document. Without much manual intervention, it is able to process the documents. This is a unique feature of UiPath Document Understanding."
  • "There could be a feature similar to ChatGPT where when you ask about a document, you get an answer about what is there in that document. If possible, this kind of feature can be incorporated so that you do not need to open a file and take the value. It should directly detect that instead of opening and validating the document. Such a feature will speed up the process."

What is our primary use case?

I have been using it for processing invoices, receipts, and multiple forms of documents. We have structured and unstructured documents. Structured documents include forms, and unstructured documents include written documents and receipts. For identifying the type of document and for processing those documents, we use UiPath Document Understanding. It helps to identify the type, extract the information, and process the information.

How has it helped my organization?

We are able to process multiple documents and extract information from them. We can put that information into an Excel or a PowerPoint file. We can also put that on a website or in an application such as SAP. We can generate a PDF. We can do all this with UiPath Document Understanding. So far, I have only exported information into an Excel file. I have not integrated it with any other system.

UiPath Document Understanding can extract information from unstructured or handwritten documents. It can extract information from structured documents such as forms. It can process invoices. I have mostly tried it with structured documents, and I have not had any problems with it.

UiPath Document Understanding makes the work easy. It can classify a document and capture the information. It is able to process a document quicker than a human. Its AI and ML capabilities improve productivity and accuracy. If we have a lot of invoices of a certain pattern, we can feed that pattern. It can then process multiple documents of that pattern. This way machine learning helps us to easily process more documents.

We can now design or develop a process much faster. Previously, we had to do string manipulation to extract information from invoices, which required a lot of coding knowledge, but with UiPath Document Understanding, that is not required. It automatically identifies the type of document and extracts information. It saves time and improves accuracy. It is a low-code or no-code solution, and even someone who is not skilled in programming can design a process. From half an hour to one hour, process designing now takes 10 to 15 minutes. 

Human validation is required for certain business processes. The Present Validation Station activity enables you to review and confirm whether correct values are extracted or not.

UiPath Document Understanding reduces human errors. Humans can make mistakes while extracting information or while coding. To avoid all those problems, we are using UiPath Document Understanding. It helps us reduce human errors because no coding is involved. We are directly teaching the system how to identify a document. It automatically identifies a document and extracts information from it. Because the system does that by itself, we can reduce a lot of human error. There is a 40% to 50% reduction.

What is most valuable?

The machine learning (ML) extractor is valuable. It helps in extracting information from even unstructured documents. It can sometimes also extract information from a written document. Without much manual intervention, it is able to process the documents. This is a unique feature of UiPath Document Understanding.

What needs improvement?

There could be a feature similar to ChatGPT where when you ask about a document, you get an answer about what is there in that document. If possible, this kind of feature can be incorporated so that you do not need to open a file and take the value. It should directly detect that instead of opening and validating the document. Such a feature will speed up the process.

For how long have I used the solution?

I have been using this solution for the past two or three months. I have been using it only for practicing. I am not using it for any industrial purpose.

How are customer service and support?

UiPath is giving very good support. They also have some webinars, which are very helpful in developing our solution. I would rate their support a nine out of ten.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

Before UiPath Document Understanding, I was using string manipulation and screen scraping methods for extracting values from invoices. It used to take more time to build a solution. 

How was the initial setup?

It is deployed on-prem. Its deployment was straightforward. It took 10 to 15 minutes.

In terms of maintenance, bots require some maintenance. Bots can fail, so continued maintenance may be required.

What about the implementation team?

I deployed it myself. I am using it on my own.

What's my experience with pricing, setup cost, and licensing?

I have only been using its free version.

What other advice do I have?

It is a very good solution. It improves productivity and accuracy. It reduces development time.

You can use UiPath Document Understanding even when you do not have programming knowledge. You just need to know the pattern of documents. It has ML capabilities, and the bot will automatically learn and start to identify and process documents. It is very easy.

Overall, I would rate UiPath Document Understanding a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Buyer's Guide
UiPath Document Understanding
October 2024
Learn what your peers think about UiPath Document Understanding. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
814,763 professionals have used our research since 2012.
VivekMishra - PeerSpot reviewer
AVP, Technology & Solutions at Cygnet Infotech
Real User
Top 5Leaderboard
A solution offering a flexible pricing model that can benefit small businesses
Pros and Cons
  • "The solution is quite stable, and I am happy with its performance in my programs and processes."
  • "One area of improvement for UiPath Document Understanding is the accuracy of handwritten documents. While the solution supports handwritten documents, the accuracy percentage is not as high as desired."

What is our primary use case?

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

What is most valuable?

The core technology of UiPath Document Understanding is OCR, which can be either ABBYY or Google Vision. The drag-and-drop facility, decision-making accuracy, and user-friendly actions make UiPath Document Understanding helpful for users.

UiPath Document Understanding offers a feature that allows users to process specific documents, such as purchase orders or invoices. The tool provides the ability to define and segregate actions and highlight fields using something similar to rubber band techniques. This means, in an invoice, users can easily highlight specific fields within the document and train the model accordingly. The process is user-friendly and can be easily executed even by those with basic knowledge of flow.

What needs improvement?

One area of improvement for UiPath Document Understanding is the accuracy of handwritten documents. While the solution supports handwritten documents, the accuracy percentage is not as high as desired. Therefore, it would be preferable if UiPath could focus on improving the accuracy of handwritten documents in their next release. Although they currently support handwritten documents, the accuracy is still low.

Also, the documents for the solution are lengthy, and because of this, I say that the solution should incorporate some video sessions.

For how long have I used the solution?

I have experience with UiPath Document Understanding, in which the users are provided with multiple types of Document Understanding and a process-wise range of available documents. Overall, I have been using the solution for three to five years. Also, I am using the latest version.

What do I think about the stability of the solution?

The solution is quite stable, and I am happy with its performance in my programs and processes. I would rate the solution's stability an eight out of ten

What do I think about the scalability of the solution?

The solution's scalability with the cloud version is really good. I rate the solution's scalability an eight out of ten.

Around 30-40 people work on UiPath Document Understanding in our company. The extent to which we use the solution, particularly in terms of utilization of bots or document processing, is dependent upon the volume of usage. In other words, if there is an increase in the number of customers, we will likely increase the usage of the solution.

How are customer service and support?

UiPath's technical support is good. Even in emails, they are responsive and helpful. They also have a very good library of troubleshooting documents and other resources. Overall, I am happy with the solution's technical support.

Which solution did I use previously and why did I switch?

I have experience with Automation Anywhere. Also, UiPath Process Mining is a pretty good tool since they have documents which provide its users with a clear understanding. On top of that, they also provide videos. So it's quite easy for an end-user to understand.

How was the initial setup?

Although the solution's initial setup is not overly complex, UiPath could work to make it more understandable for a layperson. They could improve the setup process by creating a more structured flow.

The time needed for deployment varies, depending on factors like the use of cloud services. With a Plug and Play model, UiPath provides cloud services and a link, after which we can begin using the solution. However, deploying on a private cloud may take longer, up to three to five days or even two weeks, depending on the hardware readiness.

In terms of the maintenance of the solution, let's consider a scenario where we need to initiate a programming project to develop a bot that can help in invoice transactions. Typically, this process can take anywhere from three to five weeks and requires at least one project manager who oversees a team member who understands UiPath and business processes. To successfully develop the bot, we need to first analyze and understand the relevant business processes. Once we have derived the business processes, we need to document the solution, including creating a PDD. This document outlines the process and how it will appear once automated. Apart from that, you should have a good set of developers who understand UiPath.

What about the implementation team?

In our organization, we implemented the solution with the help of integrators.

What was our ROI?

The ROI from using UiPath Document Understanding is really good, and we currently see a return on investment of around 40% to 50%.

What's my experience with pricing, setup cost, and licensing?

For the licensing part, in our company, we initially started off with a monthly plan, but yearly plans are also there. Cost-wise, UiPath  Document Understanding is good since it provides flexibility in its pricing. So, smaller firms, especially MSMEs, can opt for monthly or yearly plans based on their budget. As an end user, I wish they reduce the price of their pro version to 300 dollars since UiPath Pro starts somewhere around 400 dollars per month. UiPath's competitor, Automation Anywhere, offers a plan for 99 dollars per month.

What other advice do I have?

I can definitely recommend the solution to other users. Overall, I rate this product somewhere around eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
RPA Developer at a tech services company with 10,001+ employees
Real User
Helps reduce human error, can handle multiple document formats, and can be trained
Pros and Cons
  • "The most valuable feature is the ability for humans to train the bot."
  • "The extraction and classification process should be simplified."

What is our primary use case?

UiPath Document Understanding allows us to extract information from documents, classify the document type, and optionally validate the data with a human. We also train the bot to learn from the mistakes it makes.

We extract data from boxes and tables, as well as handwritten words.

How has it helped my organization?

UiPath Document Understanding helps us extract from certificates, the names, addresses, states, dates, taxpayer identification numbers, and signatures. We also extract information from health insurance documents such as the name, patient's address, code, and contact information. Additionally, we have invoices that we have to extract from a table with rows.

UiPath Document Understandings' ability to handle different document formats depends on which extraction tool we use and the clarity of the documentation.

I am very satisfied with UiPath Document Understanding AI and machine learning.

UiPath Document Understanding integrates well with other tools. Some of my colleagues have integrated the solution with ABBYY.

It has helped reduce human error.

What is most valuable?

The most valuable feature is the ability for humans to train the bot. It can learn from human experience, so if we include steps in our framework for humans to validate extraction or classification, the bot can learn from them to improve document understanding and precision in future document processing.

What needs improvement?

The extraction and classification process should be simplified.

For how long have I used the solution?

I have been using UiPath Document Understanding for six months.

What do I think about the stability of the solution?

UiPath Document Understanding is stable.

What do I think about the scalability of the solution?

UiPath Document Understanding is scalable.

How are customer service and support?

The technical support is good.

How would you rate customer service and support?

Positive

How was the initial setup?

The initial deployment was straightforward. The deployment took three hours to complete.

What about the implementation team?

I implemented the UiPath Document Understanding myself.

What other advice do I have?

I would rate UiPath Document Understanding eight out of ten.

Our organization also uses ABBYY.

We saw the time to value within the first three days of using UiPath Document Understanding.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Ronei Marton Lima - PeerSpot reviewer
Senior Solution Partner at AOXTI CONSULTING
Real User
Top 20
You don't need to map out specific fields because machine learning predicts where in the form the data is expected
Pros and Cons
  • "I like UiPath's machine-learning capabilities. My first impressions were good, but we only use it in a few processes. We intend to expand our use of these features in other situations, but we're still learning how to use the AI functions. We use the OCR much more."
  • "Sometimes we have challenges when we need to read something like a barcode, so we must use the Cisco algorithm to solve the issue, or I have to ask developers for help specifically to capture this kind of information. There are other processes, such as refunds, that we still must do manually because there is no way to use automation to solve this issue."

What is our primary use case?

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.  

How has it helped my organization?

UiPath has saved us a lot of time because 90 percent of our document processing is now automated. I can't give an estimate of how much we have reduced human error or the number of resources needed, but I can say that we are using time more efficiently. The solution makes work easier for our staff and frees up time. When we automate most of the documents, staff has more time to focus on issues in the remaining 10 percent. 

What is most valuable?

I like UiPath's machine-learning capabilities. My first impressions were good, but we only use it in a few processes. We intend to expand our use of these features in other situations, but we're still learning how to use the AI functions. We use the OCR much more. 

You can use machine learning with OCR to read and interpret documents. You don't need to map out specific fields because machine learning predicts where in the form the data is expected. Machine learning can identify various types of data in different sectors. UiPath is easy to integrate. We have only integrated the solution with two systems so far, but it's working well. 

What needs improvement?

Sometimes we have challenges when we need to read something like a barcode, so we must use the Cisco algorithm to solve the issue, or I have to ask developers for help specifically to capture this kind of information. There are other processes, such as refunds, that we still must do manually because there is no way to use automation to solve this issue. 

For how long have I used the solution?

We have used UiPath Document Understanding for nearly two years.

How are customer service and support?

I rate UiPath's support an eight out of ten. When we call their support team, they always solve our problems. That's what matters. 

How would you rate customer service and support?

Positive

What other advice do I have?

I rate UiPath Document Understanding an eight out of ten. It's an excellent product that's stable and feature-rich. We also have the option to augment it with some external features. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Vijay Nagendra  Sai - PeerSpot reviewer
RPA Junior Consultant (ELT- L1) at Ennuviz LLc
Reseller
Top 10
We can train documents using a machine-learning classifier, extract specific data from PDF documents, and easily deploy
Pros and Cons
  • "The best feature, in my opinion, is, we can train the document using a machine-learning classifier."
  • "Currently, we have to train multiple templates because the column size and row size change in each PDF."

What is our primary use case?

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.

What is most valuable?

The best feature, in my opinion, is, we can train the document using a machine-learning classifier. For example, if the PDF documents are of different sizes and formats, we can train all six templates with the Keyword Classifier and the Template. 

What needs improvement?

Currently, we have to train multiple templates because the column size and row size change in each PDF. My solution is to improve the process by training only one particular template so that the information can be extracted regardless of the row size and column size variations in the PDF. This way, we won't need to train each and every template.

For how long have I used the solution?

I have been using the solution for two months.

What do I think about the stability of the solution?

The solution is stable.

What do I think about the scalability of the solution?

The solution is scalable and this is the main reason we are using UiPath in our company.

How was the initial setup?

The initial setup is straightforward and easy to understand.

What other advice do I have?

I give the solution a nine out of ten.

We have a team of six developers that use the solution.

I recommend the solution. UiPath has recently added OCR capabilities to its Document Understanding feature, previously unavailable. This new feature is called UiPath OCR.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Mrs at a manufacturing company with 11-50 employees
Real User
Gives us a complete, unattended process for extracting details from PDFs, saving us hundreds of hours
Pros and Cons
  • "In UiPath Document Understanding, I use two extractors. One is the Intelligent Form Extractor and the other is the Machine Learning Extractor. The first one is very useful and user-friendly. When we have a single template or two to three templates, Intelligent Form Extractor is much easier to use. But if we have multiple templates, it's better to go with ML Extractor as you can train the model with different templates."
  • "There are also problems with handwritten documents. The results from those are not 90 percent accurate. With scanned and native PDFs, it is 90 to 99 percent accurate, but the accuracy of handwritten documents is somewhat less. If they could improve on that, it would also be helpful."

What is our primary use case?

Our use cases are in the banking sector. We have certain PDFs that contain customer data, and we have to extract data from them and compare it with the data provided earlier. The PDFs can be scanned, handwritten, or native PDFs.

How has it helped my organization?

It gives us a complete, unattended process for extracting details from PDFs. Otherwise, that would been redundant work done by specialists. It is saving us around 800 workers.

For one record, we used to take about half an hour, but Document Understanding completes things in seconds. It's very quick. It has also reduced human error a lot.

What is most valuable?

In UiPath Document Understanding, I use two extractors. One is the Intelligent Form Extractor and the other is the Machine Learning Extractor. The first one is very useful and user-friendly. When we have a single template or two to three templates, Intelligent Form Extractor is much easier to use. But if we have multiple templates, it's better to go with ML Extractor as you can train the model with different templates.

The artificial intelligence features are very good. The more you train it, the more you will benefit from it.

Also, integrating Document Understanding with other systems or applications is not complex. It's quite easy. Even for attended processes, if you combine UiPath Document Understanding with Action Center, it's almost like unattended processing.

What needs improvement?

Document Understanding is a combination of the extractor and OCR. Depending on the taxonomy that you give and the classification that you define, it is accurate. But there are multiple OCRs and I find UiPath Document Understanding to be as accurate as Microsoft or Textract OCR. If the accuracy was improved, it would be much better.

There are also problems with handwritten documents. The results from those are not 90 percent accurate. With scanned and native PDFs, it is 90 to 99 percent accurate, but the accuracy of handwritten documents is somewhat less. If they could improve on that, it would also be helpful.

Also, in the banking sector, we can't use the cloud-based Orchestrator or cloud endpoints for OCR. Getting approval for ML Extractor takes a lot of time for us. Instead, if we could go with Intelligent Form Extractor, it would save a lot of approval time. If they could improve and add features to Intelligent Form Extractor, it would make our lives easier.

For how long have I used the solution?

I have been working with UiPath for five and a half years and with Document Understanding for one and a half years.

What do I think about the stability of the solution?

I have not experienced it crashing or lagging.

What do I think about the scalability of the solution?

The scalability is good. I haven't seen any waste of money.

How are customer service and support?

We have not contacted their technical support very much.

How was the initial setup?

We do not use UiPath in the cloud; we have our own internal version, so the initial setup took time for us. But that had nothing to do with UiPath. It was because of our company's policies.

It took time for people to understand it, but once they got it, it went well.

What was our ROI?

It took some time because Document Understanding is pricey compared to other tools in UiPath. After 10 to 15 days, when there were fewer errors, that's when we started to see profits.

What other advice do I have?

I would suggest combining other technologies with UiPath. That's when you see more benefit from Document Understanding.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Regional Solution Architect at a tech vendor with 10,001+ employees
MSP
Top 10
Does not support the Arabic language, though it shortens the time of extracting data and reduces human errors
Pros and Cons
  • "It shortens the time of extracting data by 70 to 80%."
  • "The solution must localize the built-in features for supporting Arabic scripts so we do not rely on third-party tools."

What is most valuable?

The product is very, very nice. The tool relieves the data entry team from manipulating data. It shortens the time of extracting data by 70 to 80%.

What needs improvement?

UiPath should localize the built-in features for supporting Arabic scripts so we do not rely on third-party tools. It will take some investment. Sometimes, when we use third-party tools, we need to collect multiple samples of the same document in Arabic. It creates some errors in understanding. 

Sometimes, we need to do multiple formats for the same document. It happens due to the nature of the Arabic language. For the same document in English, we only supply one template. The output of handwritten documents in Arabic is very poor, regardless of the solution. For computer-printed documents, we need to tune the system.

For how long have I used the solution?

I am using the solution currently.

What do I think about the stability of the solution?

The product is stable.

What do I think about the scalability of the solution?

The tool is scalable.

Which solution did I use previously and why did I switch?

We were using our own intelligent business processing solution. It is more convenient to use because it's our own product, and we rely on Amazon Web Services. It provides big advantages for Arabic scripts. It is more understandable.

How was the initial setup?

The product is easy to implement to an extent. If we are familiar with the input, processing, output, and how to declare variables, it's easy. If we are new to UiPath, it would be somewhat difficult to understand. UiPath Academy and certifications are very important.

The difficulties in implementation depend on the environments, document sources, document types, and customer understanding. Sometimes, customers think the product can pass anything without configuration, which is not true in some cases. We have to be very clear with the customer about the type of documents and layout they can expect. Two working days are sufficient for configuring, extracting, and linking the process. One person is enough to deploy the solution.

What's my experience with pricing, setup cost, and licensing?

The pricing depends on the context of the project. UiPath is a pricey tool for small customers. If the customer agrees on the cloud product, we discuss the cost accordingly. In some cases, even though the customer sees value in the product, return on investment, productivity, and enhancements of their processes, they decide not to choose UiPath due to budget constraints. They choose a different vendor.

What other advice do I have?

Sometimes, the customer is small, but we could see the potential for using the tool because they might have multiple processes. The price we offer is based on the context and the size of the opportunity we get for references. Document Understanding has helped us automate processes like contract management, reconciliation of invoices against purchase orders, claims management, and HR processes.

We process 100,000 to 500,000 documents in a year. We also had a project for Dubai Customs to reconcile the customs clearance, which involved 500,000 to 1,000,000 documents. These documents contain tables, bar codes, dates, and checkboxes. Tables might span over multiple pages, and we must capture it completely. It becomes challenging sometimes. If there is an invoice of three pages, everything must be captured, but sometimes the values are inaccurate.

Around 70% of our organization’s documents are completely processed automatically. We haven't used the product for signatures. Customers often see from a productivity point of view. If their employees process ten documents an hour, and the tool processes 50 documents an hour, using the tool is an advantage for them.

The tool does not work for integrations. It extracts data. When we extract data successfully, we rely on other business tools for integration. Document Understanding serves as a first milestone in the process. The tool at the second milestone would pick up the extracted data and post it according to the processes or applications used.

We need human validation of Document Understanding outputs three out of ten times. It does not take more than 20 to 30 seconds per document. An employee would take ten documents per minute. RPA could handle 30 to 40 documents per minute. Document Understanding has helped us reduce human errors by 70% to 80%.

Document Understanding has helped free up staff’s time for other projects. From a development point of view, it has freed up 70% of staff's time. From an employee's point of view, it has freed up 80 to 90% of their time. We saw the value of the product after a couple of projects, especially when we implemented it and saw the value for ourselves. As a customer, vendor, or implementer, when we see the execution, we see the value.

If someone wants to take advantage of this technology, they must think multiple times about different scenarios. They must centralize the capture or the source of data. They can use any product that is easy to use and configure and link it to the processes. They must sync the templates and the configuration multiple times and link it to the automation strategy.

Overall, I rate the solution a five out of ten.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Buyer's Guide
Download our free UiPath Document Understanding Report and get advice and tips from experienced pros sharing their opinions.
Updated: October 2024
Buyer's Guide
Download our free UiPath Document Understanding Report and get advice and tips from experienced pros sharing their opinions.