UiPath IXP Reviews

We have been using UiPath IXP previously after utilizing UiPath's Document Understanding for one of our clients. We found that significant improvements have occurred with UiPath IXP, which is an intelligence extraction process that uses LLMs. The use case is for a manufacturing company, and we have used this for the extraction of POs and non-POs. It is a large workflow that we have automated. Incoming every month are around 1000 plus invoices. We extract the information and send it to SAP, and from SAP, other processes run. We have utilized UiPath IXP for this extraction.

There are different kinds of invoices we use for a supply chain process with ERP and vendors in the manufacturing company. Whenever they purchase something from the vendors for the manufacturing unit, diverse invoices will come. We have used those invoices with UiPath IXP, where we have mapped those fields. The model has categorized and classified all the invoice types and facilitated the mapping of the fields, taxonomy, and the mapping of the result confidence. After this extraction is completed, we take all those fields and inject them into SAP so that the next process, which is a large workflow, occurs smoothly. UiPath IXP has to identify a specific kind of invoice and needs to extract those fields with a sufficient level of confidence, which it successfully does before injecting to SAP.

The best features UiPath IXP offers include its model training capability, which we have been using previously in Document Understanding. We had invoice models available and would manually map the fields. We needed to run the model, run the pipeline, and then use that skill. With that skill, the classification and extraction occurred, requiring us to upload data sets, invoices, and more. When it comes to UiPath IXP, we just need to inject for the classification and extraction of the same set of invoices, and afterward, the mapping happens automatically. Due to the training imposed on the UiPath IXP model, once that mapping has happened, there is an opportunity for a human to check the fields, although usually, most of the fields are mapped correctly. User intervention is limited. Once the mapping is done, the model will be trained upon those things, taking significantly less time than in UiPath Document Understanding. All these things happen within a matter of time, which I would say is the best feature.

Both aspects are significant because regarding user intervention, if you want to map different sets of invoices and if you are mapping it every time, it takes too much effort that is unnecessary, which UiPath IXP is reducing. Additionally, whenever you map some fields and upload a data set to train or evaluate a pipeline, these manual steps become unnecessary for the developer. You just need to understand and map it. The training and everything happen with UiPath IXP in a notably shorter time because it is a pre-trained model that already knows everything. Both aspects hold equal importance.

UiPath IXP has positively impacted our organization by reducing the processing time while enhancing the model capabilities and the diversified nature of the model. We can inject anything without needing to find the kind of input we are feeding it, as it automatically identifies and classifies the type of invoice. Additionally, the extraction capability, speed of extraction, and ease of use have improved. When discussing models and pipelines, it involves less effort than before, making it easier to use.

We have seen a measurable difference in processing time with UiPath IXP. Previously, the processing of 1000 plus invoices would require six to seven FTEs working for 10 to 15 days. Now, we accomplish this in a couple of days with UiPath IXP due to the faster processing time. We utilized different machines, about three to four, giving queues for availability. Once the machine is available, the processing of the invoices with UiPath IXP occurs much better and faster.

When it comes to improvements in UiPath IXP, there is a challenge with different languages, particularly Arabic invoices or handwritten ones, where there is some mismatch or difference in extraction. This could be improved. For instance, if there is a "Z" available on the screen, it may be identified as "2." Improvements in these two areas from the extraction point of view are necessary, along with considerations regarding pricing levels.

In terms of support, UiPath is performing very well. Whenever we require assistance from UiPath, it has been positive. However, I would suggest that there is room for improvement in identifying complex different layout invoices, particularly for handwritten text, since there is potential for improvement in that area.

We have been using UiPath IXP for a significant amount of time.

UiPath IXP is stable.

UiPath IXP is pretty scalable and works effectively.

UiPath is performing very well in terms of support. Whenever we require assistance from UiPath, it has been positive. I would rate the customer support at 10 out of 10 because UiPath has maintained excellent customer support and community engagement for many years.

We previously used UiPath's Document Understanding for a different client. At that time, there was no model training, which has since scaled up and improved through UiPath. We moved from one stage to another but did not switch from a different provider.

Observing a return on investment is clear. UiPath IXP performs better for organizations with a high inflow of invoices, and when you couple UiPath IXP with automation, it significantly increases ROI. The UiPath IXP model charges a little higher, but when bundled with automation, it generates a good ROI. It is best suited for large-scale companies, handling around 1000 plus invoices in a month or even up to one lakh invoices.

My experience with pricing, setup cost, and licensing has been somewhat complex. I feel that the pricing structure is a bit high.

We have evaluated other options such as different OCRs, including Azure OCR.

My advice to others considering using UiPath IXP is that if you have a large set of invoices or any kind of documents needing extraction and if you are already using UiPath, it will be a better solution for OCR extraction, bringing significant ROI if you have a substantial number of documents incoming. If you couple this with some kind of process for automation, it will yield considerable ROI and ease in working. UiPath IXP is a pretty solid model that delivers good ROI to clients and reduces developer effort. Compared with Document Understanding, it is a better model. I rate this review a 9 out of 10.

By implementing UiPath Document Understanding, we wanted to extract data from the documents, specifically native PDF documents. 

In terms of integration, we have integrated it with SAP. 

We are processing 100 to 150 invoices of 20 to 30 pages, totaling around 1k pages in a month, and the document format is PDF. Our organization's documents are completely processed automatically if there is no change in the template, but if there is a slight change in the invoice template, then they aren't processed automatically.

Validation does not take much time because we have developed an application that allows us to validate by modifying the data in the database while viewing the PDF image and extracted text. Human validation is required for at least 2 out of 10 invoices. The human validation process may take approximately 10 minutes per document, but it depends on the number of pages.

Before automating our process with UiPath Document Understanding, the average processing time was in hours, but now, after validation, it takes just 5-6 minutes.

UiPath Document Understanding has helped reduce human errors to some extent. The extraction of data should be accurate to avoid manual validation. 

UiPath Document Understanding has helped to free up staff's time for other projects, but the cost is high. In India, costs are increasing, and we are looking for cost-effective solutions. We are trying Agentic AI solutions to reduce costs, as every year the license cost of UiPath Document Understanding increases. 

Regarding time savings, 1-2 hours are reduced to 5-6 minutes.

Pre-trained models are valuable, and they work well. UiPath Document Understanding has pre-defined sets of trained models. We are using those and training our invoice templates, so we are using the pre-trained templates, and we are able to extract data based on our needs.

We have to do manual validation for some of the things due to the OCR engine not being so accurate. For example, S is read as 5, 5 as S, 2 as Z, and Z as 2. In the case of currency, if one dot is missing, it gives a completely incorrect number.

These discrepancies should be fixed because if the OCR itself doesn't work properly, then AI doesn't help with that. When AI is used for training models, the AI Center works precisely, but if the data itself is wrong, we can't do anything. If the extraction of data is proper, it definitely helps. However, 20% errors could be reduced if the OCR engine were better. In future updates, I would like to see better handling of issues such as when a dot is missing in currency, for example, with dollars, it should handle that automatically.

It's very expensive. If the volume increases, we can't afford to use Document Understanding. We are thinking of moving to another solution because we are expecting 80,000 to 100,000  invoices.

My overall experience with UiPath Document Understanding is for more than 3 years.

It is stable.

UiPath Document Understanding is scalable. We are not planning to increase the usage of UiPath Document Understanding. We are trying to find alternative solutions as the volume is expected to increase, requiring more bots, which would increase costs.

In the initial days, we interacted with them, but we now find solutions ourselves. At the time, there was a delay in response. Our system is healthcare-related and needs to function 24/7, so we don't have the bandwidth to rely on the technical team's response times.

Neutral

The initial deployment was straightforward and took a few hours.

I was personally involved in the deployment process of the automation. Our implementation strategy involved deploying it in two environments: staging and production. We process invoices in the staging environment first, then confirm them before pushing to production. We use GitHub for code management. We create branches and push the updated code without impacting others.

For deployment, we didn't use any third-party integrators or consultants. We used GitHub and Jenkins schedulers, avoiding additional costs due to licensing expenses of those tools. For the process, a couple of resources are needed, specifically 16 developers are involved.

It definitely saves time. However, there are alternative solutions at lower costs.

We can use a simpler solution. We can use a Python script that converts PDF to text with 100% accuracy. There are other solutions that are free. We are planning to migrate to those.

It is expensive. The license cost for UiPath Studio has risen to around 3.5 lakhs last year, and I am uncertain how much the increase will be this year. They have also increased the bot prices. 

There are no additional costs; there is no extra cost aside from the standard licensing fee.

Before choosing UiPath Document Understanding, we evaluated other options like Automation Anywhere. We chose UiPath instead of Automation Anywhere because it is an on-prem solution suitable for governmental projects, like defense organizations.

My overall rating for UiPath Document Understanding is a four out of ten. It's good in technical aspects, but it's not cost-effective. 

The main use case is document automation. We have done everything from medical forms to supplier quotes, invoices, PO invoices, check requests, expedited invoices, utility invoices, expense reports, reimbursements, and things of that nature.

The documents we are processing are as low as 20,000 a year and as high as 2 million a year. They are as complex as you could humanly imagine.

What I appreciate most about UiPath Document Understanding is that it's a good introduction tool for customers to use, and it can be deployed quickly. UiPath Document Understanding, while good, is a very good IDP out of the box. You need to invest significant time to make it great, and you are probably better off integrating other tools with it to get to that level. The best thing about it is that it is decent out of the box. 

You can certainly configure it to help with human error. You can set up rules to do basic value checks and even route for human escalation.

The downsides are that it's wildly overpriced. The other players in the industry are catching up quickly, and if you really want it to be good, you probably need to augment its answers with those of another tool, whether that be Textract, Computer Vision, or another AI tool. It does not integrate smoothly with these solutions. I have to build custom integrations.

I have significant experience with UiPath Document Understanding.

We have used many different IDPs before. We've used Hyperscience, ABBYY, AWS Textract, and so forth.

UiPath is more expensive than ABBYY, and Hyperscience is more expensive than UiPath. In terms of what they try to do, their core value proposition is the same. ABBYY probably has slightly better, or at least did have slightly better, out-of-the-box capabilities for the price. Whether that remains true now, I'd have to study it. Hyperscience was supposed to have some automation with their tool. They overpromised and underdelivered. They were supposed to be what UiPath Document Understanding is, and I don't think they've achieved that, though maybe they have now.

We can deploy it quickly. UiPath is a very flexible platform that allows for customization.

We use agentic automation in this product. People are looking to automate more complex tasks, judgment-based tasks that are too complex for RPA to handle. This could be something as simple as generating a custom email for a potential client, doing outreach or quote follow-up, or as complex as setting up a remediation plan for reconciliation policy monitoring.

Regarding automatic document processing, invoices can have a 90% successful extraction rate, but with business rules, automatic processing reduces to 70%, which is intentional. The system can be configured to help with human error through basic value check catching and routing for human escalation.

Human validation requirements vary between 5% to 40% of the time, depending on how clients want to configure their tool.

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

UiPath Document Understanding is primarily used for invoice and document processing through optical character recognition (OCR). The team utilizes this technology to digitize quotes and orders from customers, extracting relevant details and updating our systems, including SAP.

UiPath Document Understanding cuts down a lot of order processing time and agents' time. They don't have to manually enter numbers into the system. This saves both human effort, which in turn translates to better cost efficiency.

It has many connectors and is considered an industry standard. Therefore, it works well with regular applications. For legacy systems, we utilize RPA and other solutions.

The accuracy of the solution is pretty good, and it offers flexibility in handling various types of documents. Most of the documents processed are in PDF format, but it also supports JPEG files. Overall, it does a decent job of highlighting and processing both PDFs and JPEGs.

UiPath Document Understanding provides capabilities for handwriting as well as PDFs and JPEGs. It does a decent job.

For UiPath Document Understanding, there is a possibility for improving accuracy with multilingual documents, especially handwritten ones. It doesn't have very great accuracy, particularly for handwritten documents and multiple European languages. They have to improve their accuracy of the models with UiPath Document Understanding.

They have to improve their accuracy of the models with UiPath Document Understanding. They are exploring agentic and other things, and they are keeping up with developments.

We have been using UiPath Document Understanding for the last three years.

It's pretty stable.

It's scalable.

Their technical support is very good.

Positive

It is easy to deploy.

We get around 60% to 65% accuracy with UiPath Document Understanding. The other 30% requires human validation. 

Approximately 60% of our company documents are completely processed automatically through straight-through processing (STP). 

Within six months of implementing, UiPath Document Understanding started yielding value and savings.

It can be cheaper, but for the work it does, it's decent. It's not a very affordable solution.

With a lot of LLMs and developments rapidly evolving, there are indeed some cheaper options. However, if you want an enterprise-grade, stable solution, then UiPath is definitely a choice.

I would rate this solution an eight out of ten.

We use it for broker closure, KYC, mortgage processing, and invoice processing as of now.

We have about 100,000 invoices a year, 50,000 KYC applications, and another 100,000 for broker closures.

It is a pretty scalable tool. It works well for big companies.

The challenge is more on handwriting and language-specific document extraction. There is some room for improvement when it comes to understanding handwriting. Document Understanding at the current stage is moving some of their technologies to Agentic using LLMs to increase the accuracy of their extraction, so I still find there's a lot of room for improvement. For example, extracting information from engineering drawings will be a challenge, so we'll have to use a lot of AI technology to make it happen.

From the technology point, they are already working in the agentic space and trying to deploy more agents. I believe that enhancing their orchestration engine with an API-driven approach would be a great starting point for further development.

I have been using UiPath Document Understanding for about five years.

My experience with technical support of both UiPath Document Understanding and Blue Prism has been good. They can improve in terms of the response time and resolution of the issues.

Positive

I have not used any other similar solution.

Both UiPath and Blue Prism are expensive.

Customers are trying to move to some other Agentic space because of high pricing, so the new initiatives are put on hold, and they're looking for alternatives as well.

I would recommend UiPath Document Understanding for big companies, not for small ones. A lot of coding is required to make handwriting decoding happen; it's not so easy as plug and play. It's all about putting in a lot of effort to make that work.

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

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.

Document Understanding processes handwritten and printed documents in PDF, PNG, and Excel format, with a monthly volume of around 9,000. We have an 80 percent success rate of automated processing.  Only about 20 percent of documents require human validation. It takes about 30 minutes per document to validate by hand. 

Before automating, we had 14 people completing the process from end to end 8 hours a day. The bots reduce that to 2 people. Our success rate is 90 percent. On some days we've had a nearly 99 percent success rate. We're satisfied with the quality.

We are working with 40,000 different vendor templates. Document Understanding can understand and process various formats without much manual effort to configure the templates. That wasn't the case when we were using Microsoft. 

UiPath can read handwritten signatures with a success rate of around 70 percent. We've even processed pay slips in German. The language translations are around 90 percent accurate. 

The AI/ML component offers great flexibility in creating custom models. Its built-in models are also highly mature. The integration is seamless. We have RPA talking between our ERP systems and sharing information on the UiPath cloud.

I want more flexibility in Document Understanding's validation center.

I have used Document Understanding for 2 years.

I rate Document Understanding 10 out of 10 for stability. 

I rate Document Understanding seven out of 10 for scalability. 

I rate UiPath support 8 out of 10. 

Positive

We used previously used Microsoft Power Automate. We switched because we weren't satisfied with the outcome. Microsoft is more labor-intensive, and the data we were getting was less accurate.  We needed to put a lot of effort into configuring the templates each time the vendor sent us new templates. The success rate was only 30 to 40 percent. 

Document Understanding was easy to deploy, and it only took a day. It's deployed on one server on the East Coast, and only one department uses it. The solution requires about five or six hours of maintenance monthly.

I rate UiPath Document Understanding 2 out of 10 for affordability. It's one of the more expensive solutions on the market. 

I rate UiPath Document Understanding 8 out of 10. I recommend Document Understanding based on the quality of its results. It can read your handwritten documents and translate them. The outcome and success rate is higher than what I've seen in the traditional OCRs.

The primary use case for UiPath Document Understanding is to identify and classify documents, extract metadata, and use this data in automation workflows. This can be particularly useful in HR processes where various documents need to be submitted during hiring, such as graduation certificates, IDs, etc. UiPath Document Understanding helps classify these documents and extract the necessary data to process internally or initiate workflows.

UiPath Document Understanding is a tool that assists with processing documents containing various formats, including tables, handwritten text, and checkboxes.

We leverage machine learning and artificial intelligence to train UiPath Document Understanding on various documents. This integrated capability significantly simplifies extracting and comprehending information from these documents within the platform.

We can incorporate human validation into the training process to ensure accurate data classification and extraction. This valuable step, while adding a few minutes to the process, allows for human oversight and correction, ultimately improving the reliability and quality of the results.

UiPath Document Understanding helps reduce human errors, especially in data entry functions. 

By automating processes, UiPath Document Understanding can save approximately 70 percent of the time.

Customers realize value quickly with UiPath Document Understanding, typically seeing results within a few weeks of implementation.

UiPath Document Understanding offers valuable features like Arabic language support, which is crucial for effective communication and automation in the Arabic-speaking world. Furthermore, its integration with advanced language models leverages AI to quickly understand and classify document data, improving efficiency and accuracy in processing information.

One area where UiPath could improve is by including pre-trained models for general-use documents specific to the Middle East. This would enhance the platform's utility in the region by allowing users to more effectively automate tasks involving documents in Arabic and other Middle Eastern languages.

I have been using UiPath Document Understanding for almost five years.

The premium support UiPath offers is speedy and satisfactory. However, basic support may be somewhat limited.

Positive

For cloud deployment, the initial setup is fast and straightforward. On-premises setup, however, can be complicated and requires more effort.

Deploying UiPath Document Understanding in the cloud takes only a few minutes, while on-premises deployment requires three to five days.

UiPath Document Understanding is considered a bit expensive compared to other options like Microsoft Azure, which can offer similar quality at a more affordable rate.

I would rate UiPath Document Understanding seven out of ten.

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

The solution allows us to continue with vendors whose information comes in correctly and to stop the automation for vendors with many items that are not clearly defined. The precision is not very high when there is a lot of text in the item table.

Sometimes, when the number of items is very large, the solution doesn't properly identify them. It's not 100% accurate, but it gives an 85% to 90% output. The solution doesn't work properly when too much data is on the table. Using 10 pages of data only for tables makes it difficult to collate the data.

We would like to have a better conversion of data, which is in tables and available on multiple pages. The same table is repeated with different items across multiple pages, which is challenging. We have to give similar keywords when indicating the second or third page. We should be able to use the same keyword for one document to identify the first page. From the second page onwards, the keyword should be done away with.

The repeated keywords on the second and third pages create problems because not many keywords are available on the second and third pages. It is a simple table-to-table repetition. The keywords, including the vendor's registration number, address, phone number, or email, are unavailable on the table pages.

Pages 2 to 10 are all just simple tables. The keywords are not available on those pages, and that's where the system gets more complicated.

I have been using UiPath Document Understanding for 3 years.

A person who knows the system can deploy it very easily and quickly without any difficulty or complication.

We take about 2 to 3 days to set up UiPath and install the UiPath Document Understanding programs we have developed. It takes time to create the vendor data and train the bot for each vendor. We spend about 40 minutes training the bot for each vendor.

The solution is a good investment. The investment of one year's license fees and development costs could be recovered in four to five months' time.

The product is not very costly in itself. It is part of the normal license. The solution’s cost increases for machine learning or artificial intelligence because we have to go for UiPath Orchestrator. UiPath Orchestrator's cost is very high, around $10,000 per year.

If somebody has a lot of vendors and about 100 invoices per day, we have to train the bot for various formats. We convert data from scanned PDF into a standard Excel table, including invoice numbers, purchasing order numbers, dates, and vendor names. The solution uses typed or printed data, not handwritten. It's difficult to capture handwritten data because different types of handwriting increase the errors in capturing the data.

About 80% of our organization’s documents are completely processed automatically. Sometimes, we don't have good data capture when the PDF is not of good quality. You need to have good-quality scans. Using the artificial intelligence or machine learning capabilities of UiPath Document Understanding is costly.

Integrating the solution with other ERP systems and applications is very easy. There are a lot of commands specifically for SAP. Initially, almost every document was verified by human beings. After gaining confidence and segregating the vendors who were giving out correct results, we stopped human intervention and started running on the bot completely.

When there were about 200 invoices per day, we employed about 5people to process the invoices manually in the ERP. When we introduced the UiPath Document Understanding bot, it could process faster and reduce the number of people required from 5 to 2. The solution helped reduce human errors and made processing in time possible, thereby avoiding delays.

Users should take the solution as an opportunity to reduce costs and not expect 100% results. Expecting 100% results would make it a failure from day 1 because it will not give 100% results. It will give you 80% accurate and 20% jumbled details because of the various complications arising from lengthy or unclear documents. If your expectation is reasonable, your success rate will be high.

Overall, I rate the solution an 8 out of 10.

We use UiPath Document Understanding to extract insurance document data related to vehicle accidents in a pilot project to better understand who is at fault. We open the documents, connect with the insurance companies, and obtain the police reports describing the scene of the accident. We extract the information into a single spreadsheet to charge the third party.

Before implementing UiPath Document Understanding, humans required around 15 minutes to extract the required information per document. Now, using Document Understanding, we can process 11 documents per minute with 98 percent accuracy, saving a significant amount of time and money.

The data we extract using Document Understanding relates to vehicle accidents. The insurance company uses this data to charge third parties involved and recover most of their money with minimal human intervention.

We are extracting information from 50 insurance documents to prove the concept of showing coverage for those involved in the accident.

The information from the insurance company is in PDF format and is structured so that we can easily extract information from it. The other public policy documents vary in quality depending on the state and district in Brazil. We have 27 states, and these documents are unstructured, making it difficult to extract data from them. Sometimes they are in image format, and other times they are in PDF format.

The 50 structured PDF documents from the insurance company are all 100 percent automated using UiPath Document Understanding.

We are impressed with the machine learning and AI capabilities of Document Understanding. We can use APIs to identify whenever a vehicle accident is reported, which helps our business.

Using the AI we can access vehicle accident reports and train the machine learning to understand the majority of the documents we extract information from to help improve our business processes.

We use the UiPath platform orchestrator with an API to integrate with OpenAI.

UiPath Document Understanding has helped our organization demonstrate to potential customers how the solution, together with AI and machine learning, can benefit their businesses.

Before Document Understanding our process took 15 minutes per document and now it takes under one minute.

Document Understanding has helped free up our staff's time to work on other projects.

UiPath Document Understanding is easy to configure and user-friendly.

It is easy to insert a human into the loop.

Explaining the UiPath Document Understanding process to my customers is easy for them to understand.

UiPath Document Understanding produces a high accuracy rate of 98 percent.

The interface has room for improvement.

I have been using UiPath Document Understanding for ten months.

UiPath Document Understanding is stable.

We can easily scale UiPath Document Understanding by adding licenses.

We have only used the UiPath User Community site for support on issues or questions related to Document Understanding.

Positive

We previously used Microsoft solutions and switched to UiPath Document Understanding because it is the best. 

We can demonstrate a return on investment for our customers with the huge amount of time saved using UiPath Document Understanding.

UiPath Document Understanding is expensive, with the basic annual package including 6,000 documents and the next package including one million documents, a huge price difference.

We evaluated Automation Hero and a Microsoft platform. We chose UiPath Document Understanding because we are a UiPath partner in Brazil, and as a global leader, UiPath can support us on all of our projects.

I would rate UiPath Document Understanding nine out of ten.

We are currently conducting a proof-of-concept using UiPath Document Understanding, so we must use human validation for all processes to demonstrate the accuracy of the bots to the customer. Human validation takes five minutes per document.

Three professionals are required for the maintenance.

We primarily use it for invoice processing as well as receipt processing or expense processing.

It has advanced capabilities compared to other competitors, whether Blue Prism or Automation Anywhere. We can select the ML models based on the type of process that we are automating. 

It has helped process around two thousand documents per month, in formats including PDF, text, image, and even handwritten documents. This solution has played a significant role in drastically reducing human errors by ensuring that 95% to 98% of tasks are done through the system.

They can include some features in utilizing the product of assessment understanding, or more specifically, a better efficient handling of the ML skill, which right now is not that efficient. The integration could also be simplified as it's somewhat complex at present.

I have used the UiPath Document Understanding for one year.

They often ask us to go through the documentation first instead of directly explaining or addressing the root cause of issues.

Neutral

We did not use any previous solutions for document undertsnading. This is the first one we have used.

The initial setup is not straightforward. One needs to have knowledge to set it up.

The implementation team involved an architect, senior developers, and another architect.

Return on investment could be high if you are using the product for multiple processes. The more automation you achieve, the more ROI you will see.

It is expensive/ It's not easy to accommodate in the budget.

We didn't evaluate other options since we didn't have time to explore that much.

I would rate UiPath Document Understanding a seven out of ten, although the platform doesn't accommodate half ratings.