UiPath IXP Reviews

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.

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.

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.

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.

I have been using UiPath Document Understanding for one year.

UiPath Document Understanding is stable.

UiPath Document Understanding is scalable.

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.

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.

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.

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.

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.

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.

Positive

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. 

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.

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

I have only been using its free version.

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.

I use UiPath Document Understanding to extract data from scanned images using OCR technology. For example, when we have invoices, we can extract data from them by creating a model for that particular template using OCR technology, artificial intelligence, and machine learning. Every invoice has its own template, so we can create a template model and implement it in UiPath to run a bot for the data extraction process. After extracting the data, we can store it in an Excel file or database, whichever we prefer.

We deploy UiPath Document Understanding in the cloud and then integrate it with our on-premises architecture using a single key.

UiPath can automate any repetitive task, such as data entry, data extraction, file downloading, and file uploading, in any financial services, banking, or health insurance sector. The document formats include tables and checkboxes.

It can extract handwriting and signatures as long as they are legible.

Machine learning capabilities can be used to retrain prebuilt models for use with other templates.

It has helped improve our organization by reducing human tasks and errors.

Whenever data is extracted from a document using UiPath Document Understanding, we receive a confidence level rating. If the confidence level is low, we send the extracted information to the Action Center for human validation.

UiPath Document Understanding does the work of three full-time employees.

Using UiPath Document Understanding for documents without business or application exceptions reduces human error by 100 percent.

UiPath Document Understanding's image file extraction feature is the best in any OCR solution.

The signature comparison feature of UiPath Document Understanding could be improved.

To my understanding, we can only integrate UiPath Document Understanding with UiPath. I would like the ability to integrate with other solutions.

I have been using UiPath Document Understanding for two years.

UiPath Document Understanding is stable. 

We previously used an Excel automation tool but switched to UiPath Document Understanding because it is a better solution for repetitive tasks.

The initial setup is straightforward. The deployment was completed by two people including myself.

The implementation was completed in-house.

We received a 60-day free trial before having to purchase a license to continue using UiPath Document Understanding.

I would rate UiPath Document Understanding nine out of ten.

Data extraction accuracy depends on the document's quality and format. The maximum percentage of accurate data we can extract using UiPath Document Understanding is 90 percent.

We started to see the value right after implementing UiPath Document Understanding.

We use UiPath Document Understanding to extract data from invoices so that the data can be entered into SAP applications. We often receive multiple invoices in different formats. To use UiPath Document Understanding, we need to train the document. This means that we need to provide a sample template that the robot can use to learn how to read the invoices and extract the desired data. The labels in the fields are important, as they tell the robot what information to extract. 

For example, the invoice number, seller's address, quantity, and any other required information. The table of line items also needs to be extracted. We define the fields from which we need to extract data. We use the form-based extractor or machine learning extractor to extract the data. We export the extracted data to an Excel file. This allows us to collect all of the data from multiple invoices in a single location. We can also implement a validation step to ensure that the robot has extracted the data correctly. This can be done easily by using the human in the loop to manually review the extracted data before it is entered into SAP applications.

Our organization has many invoices of varying formats. To simplify the process, we implemented UiPath Document Understanding to extract the required data from all the unstructured invoices and import it into a single, structured Excel sheet.

Using the different endpoints and machine learning, we can extract data in different formats including handwriting and signatures.

UiPath Document Understanding's machine-learning capabilities are good. We use it to extract the information we need from documents of any format, and then align it with the corresponding table.

We easily integrated UiPath Document Understanding with UiPath Studio by connecting the data flow from the different applications to extract the necessary records.

We have so many invoices that UiPath Document Understanding helps us classify them. The document is first classified into a type of document, such as an invoice or a resume. This segregation of data allows us to send the invoice templates to our folder and extract the data and all the details without having to read them one by one.

With UiPath Document Understanding, less and less human validation is required over time. Each time we run the process, we can select from an option for attended or unattended automation. The other option is to use the confidence score to determine whether human validation is required.

The handling time before automation for one PDF document was five minutes and now with automation, it is one to two minutes.

UiPath Document Understanding helps to reduce human error by removing the fatigue factor and by continuing to run after hours without breaks.

There are many features that can be added to the action center to keep humans in the loop to evaluate the accuracy of the extracted data. We can also set a confidence score threshold, such that if the confidence score is greater than 80 percent, we can take a certain action. Otherwise, we need to manually correct the problem in the action center.

UiPath Document Understanding could be more user-friendly. There are so many endpoints, and entering the API is also a manual task. Currently, it is a long and complicated process with many steps. If we remove all of those steps and use the ChatGPT or OpenAI library, we can start using the solution with fewer steps.

I have been using UiPath Document Understanding for six months.

UiPath Document Understanding is stable.

UiPath Document Understanding can be scaled for multiple invoices.

The deployment was straightforward and required a few days.

I would rate UiPath Document Understanding eight out of ten.

We are processing around 12 documents using UiPath Document Understanding. The documents are in PDF format.

We have four members using the solution.

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.

Data entry is the most common use for UiPath Document Understanding.

In Italy, a common document format for simplified sales invoices is the BBT, which lists the total cost of the entire merchandise unit.

Since our clients are primarily small and medium-sized businesses, UiPath Document Understanding processes around 10,000 documents annually.

The documents contain a header and a large table where data is extracted.

Around 30 percent of the documents are fully completed by UiPath Document Understanding.

AI and machine learning do a great job sorting and identifying fields and documentation orientation. Managing different layouts is the most valuable attribute of AI.

Companies that use the UiPath platform can easily integrate UiPath Document Understanding using a few modules.

Human validation is required for 20 to 30 percent of cases and it takes less than one minute to complete.

UiPath Document Understanding helps reduce human error by 70 percent.

UiPath Document Understanding has helped free up around 70 percent of people's time to work on other projects.

For most of our clients, the time to value is usually six months.

The prebuilt algorithm for extracting foreign invoices is the most valuable feature because it eliminates the need for us to build anything from scratch.

The signature and handwriting are a pain point for the OCR and have room for improvement.

The extraction logic portion of the UI is not as user-friendly as the rest of the platform and has room for improvement.

I would like to have generative AI integration added to a future release.

I have been using UiPath Document Understanding for two years.

The stability of UiPath Document Understanding is good. The higher the stability the less maintenance is required.

The scalability can be improved with the help of generative AI. It is difficult to build an algorithm and move to another project without making important changes to it.

The technical support is good.

Positive

The initial deployment process is not user-friendly. It requires a lot of steps, although depending on the size of the deployment, one person can usually manage it.

The average deployment takes around one month to complete. 

We implement the solution for our clients.

The price for UiPath Document Understanding is a bit expensive.

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

The number of people required for maintenance depends on the project. It can go from one person up to seven.

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.

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.

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.

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.

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

I have not experienced it crashing or lagging.

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

We have not contacted their technical support very much.

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.

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.

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

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.

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.

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.

The extraction and classification process should be simplified.

I have been using UiPath Document Understanding for six months.

UiPath Document Understanding is stable.

UiPath Document Understanding is scalable.

The technical support is good.

Positive

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

I implemented the UiPath Document Understanding myself.

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.

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.  

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. 

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. 

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. 

We have used UiPath Document Understanding for nearly two years.

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. 

Positive

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. 

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

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.

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.

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.

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

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.

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.

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.

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.

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

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

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.

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

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.

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. 

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.

I have been using the solution for two months.

The solution is stable.

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

The initial setup is straightforward and easy to understand.

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.