What advice do you have for others considering UiPath Document Understanding?

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.

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.

Overall, I would give UiPath Document Understanding a nine because, despite pricing being a pain point, the solution is really great and yields good results.

They have introduced Agentic AI in the agent builder and AI features such as Autopilot. This is very useful for speeding up development and delivering projects faster. With Autopilot and Agentic AI, we can write prompts and build workflows. However, these workflows still need review, understanding, and possible modification. While AI integration has made development easier, there is a growing dependency on AI, which may lead to forgetting fundamental concepts and core knowledge. I can recommend UiPath Document Understanding to other users. I would rate UiPath Document Understanding a seven out of ten.

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.

I'd rate the solution eight out of ten.

I would rate UiPath Document Understanding nine out of ten. We have over a hundred users because we have various workstations in various branches. In every branch, we deploy five workstations. Any implementation challenges we encountered were due to the need to rapidly develop and execute our cyber training program. Given the increasing complexity of our programs and the critical importance of staying current with cybersecurity best practices, we prioritized upgrading our staff's knowledge. This new training likely contributed to our understanding of the platform's inner workings. UiPath Document Understanding requires maintenance just like any other product that has version upgrades. I recommend UiPath Document Understanding as the first choice due to its free trial, free training, and affordability. This platform will significantly enhance accuracy, leading to improved report generation, analytics, planning, and overall workflow productivity and growth.

I would rate UiPath Document Understanding nine out of ten. We have six people that use UiPath Document Understanding. I recommend UiPath Document Understanding to others.

I would rate UiPath Document Understanding nine out of ten.

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.

I would rate UiPath Document Understanding 8 out of 10. The integration of AI in UiPath Document Understanding will enhance its ability to read screenshots and handwriting within PDFs in the future. We're currently working with several internal clients across various industries, not just the financial sector. We're expanding our reach to assist them with both compliance and audit matters. By targeting a wider range of clients, we aim to help them implement effective tech ops practices. Currently, we are using UiPath Document Understanding in our client's finance department. We have a 4 person support team that monitors and maintains UiPath Document Understanding.

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.

I rate UiPath Document Understanding seven out of ten. It's an add-on for UiPath, so it isn't a standalone solution. If you already have a license for another third-party solution for RPA, you should consider whether it's beneficial to switch.

I would advise taking a step-by-step approach. If you miss any step, the bot will fail. For large document extractions, you need to follow the step-by-step instructions provided in the UiPath Academy. I have not used Forms AI, but I use AI Center. In AI Center, I am using some datasets. I am maintaining some data sets, and based on the business requirement, I use the data. Its integration should be good, but I have not tried any integration with other tools. I have integrated ABBYY and UiPath, but I have not integrated Document Understanding. I would rate it a ten out of ten. It is now a very mature tool.

I rate UiPath Document Understanding an eight out of ten.

I would rate UiPath Document Understanding nine out of ten. I was the only one using the solution in our organization. I recommend evaluating both the free and paid versions of UiPath Document Understanding.

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.

For those interested, I would recommend undergoing a POC to truly experience and be pleasantly surprised by the outcomes within a couple of days. In an overall comparison with other solutions in the local market, I would confidently rate this as a robust nine out of ten.

I would rate Document Understanding an eight out of ten.

I would recommend Document Understanding. I prefer Document Understanding over IQ Bot as they have multiple flavors of machine learning models. If a person is capable, they can also easily achieve the same thing with programming. I would rate Document Understanding an eight out of ten, but they can improve the costing part.

Overall, I would rate it nine out of ten.

I would rate UiPath Document Understanding seven out of ten. We have seen time to value with UiPath Document Understanding. UiPath Document Understanding requires constant maintenance because of the AI issues. One person can handle the maintenance. I recommend thoroughly testing UiPath Document Understanding to verify that the organization is genuinely deriving value from the tool and to assess whether the AI model can effectively handle the capabilities advertised by UiPath.

I would rate UiPath Document Understanding nine out of ten. Our clients experience time to value after approximately four months of usage because, initially, it takes some time to become familiar with the models and begin to see results. The number of people we have using the solution is specific to the AP team or data finance team. Currently, we have two teams working on the solution. Document Understanding requires ongoing maintenance in the form of model retraining. In the event of any encryptions, we may need to provide validation to the user. Additionally, we need to ensure that our models are regularly retrained. Organizations need to carefully evaluate the scope and requirements of their Document Understanding initiatives. While existing Document Understanding models have demonstrated capabilities in specific invoice formats, it is crucial to test their performance across a broader range of invoice types. I recommend conducting a pilot test using a sample of 20 diverse but similar invoices to assess the models' accuracy and applicability.

I'm a customer and end user. I work as a developer. I'd rate the solution nine out of ten overall.

Definitely talk first with a UiPath representative to get someone who will take care of you and the implementation. Do not waste your time reading through the documentation because it's very messy.

In terms of human validation for Document Understanding output, we have a limit of 75 percent correct scenarios. If it is below 75 percent, the user will be notified. The solution doesn't require any maintenance unless the client requires more fields to be extracted. Only then are there changes that I need to make. My advice is that if you are starting to learn about Document Understanding, you need to learn more about the taxonomy and what fields you are extracting. You need to have clarity on which position you are extracting, as it mostly depends on the position.

The document format is mostly PDF and can be structured or semi-structured documents. We have not dealt with handwritten documents. Our real-time use case is for structured documents like emails and invoices. Most of the client documents go through without any errors. However, there is a five percent failure rate that needs to be considered since the document may contain unexpected data. 90 percent of documents go through it. The solution handles signature-based documents. We are still working on that prototype. We faced issues with seals. It differs from department to department and state to state. The tool's AL and ML features work fine for us. We leverage these features for driving licenses. AL and ML keep a check on document generation. UiPath Document Understanding has come up with an API-based document understanding model which we will leverage soon. We implement human validation when we use anything new so that everything works as expected. I would rate UiPath Document Understanding an eight out of ten.

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.

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

I would recommend Document Understanding to other users and rate it eight out of ten.

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.

If you have the budget, this is a great option for building and deploying the IDB solution. It's not hard to develop, it's the issue of licensing costs. I rate this solution 10 out of 10.