I am using the solution mostly for voice processing.
We have approximately 30 use cases in our company.
I am using the solution mostly for voice processing.
We have approximately 30 use cases in our company.
The most valuable feature of ABBYY Vantage is flexibility. You are able to edit at a granular level providing good control over the process. Additionally, the brochures and guides were helpful in learning the solution.
ABBYY Vantage could improve the processing of handwritten notes.
I have used ABBYY Vantage within the last 12 months.
In our region, we have a lot of Arabic text that is handwritten which the solution could improve.
I rate the stability of ABBYY Vantage an eight out of ten.
The scalability of the solution depends on the use case. However, if the solution is managed well it is scalable.
Our company is expanding and correctly we have approximately 16 users of the solution.
I have not used the support from the vendor.
There might be a need to complete a few courses to get used to the implementation of ABBYY Vantage.
We did the implementation of ABBYY Vantage in-house.
We were able to qualify for a reasonable price. The price is in the low to medium range compared to other solutions.
I rate the price of ABBYY Vantage an eight out of ten.
I evaluated IBM and AI builder prior to choosing ABBYY Vantage.
If you do the training it will be easy to use.
I rate ABBYY Vantage an eight out of ten.
It would be during the data extraction process. The ability to extract and insert data, then structuralize it into the actionable format, would be the most valuable.
I would have liked to see them make it easier for business users to implement themselves. This is what they have done with Vantage, which is essentially a low code/no code, slightly enhanced version of FlexiCapture that is already available.
I have been involved with ABBYY FlexiCapture off and on for approximately one year.
ABBYY FlexiCapture is a stable product. The stability is good.
The scalability of ABBYY FlexiCapture is good.
This solution is used on a daily basis throughout the organization.
My company has approximately 230,000 employees worldwide.
The technical support is good. They solve problems relatively quickly.
I am familiar with IBM Datacap.
The initial setup was relatively complex. The people who install it must be knowledgeable about what they are doing.
It took some time to get everything up and running properly.
The deployment was completed in-house.
We have seen a return on investment, but I'm not sure how much.
It would be far too difficult. Because we obviously deliver these types of solutions not only in-house but also for a large number of other companies. There's plenty of ROI that we have managed to deliver for our customers, in particular, but I can't give you figures.
I don't recall the pricing.
In terms of intelligent document processing, the company uses a variety of platforms, including IBM Datacap and ABBYYFlexiCapture, among others. We were constantly reviewing market products, and we were also doing things like Hyperscience. At the moment, I'm working on a review for Vantage, which is ABBYY's other recently released product, rather than FlexiCapture.
We are partners with ABBYY.
If you are going to implement it, I would recommend a combination of engaging with a delivery partner to accelerate your initial setup and scalability and then building your own internal capability, which requires accredited users, in parallel.
Because FlexiCapture requires a significant amount of domain knowledge or technical capability to implement. I am not sure if this is outside the scope of your research, but if a company is looking to implement ABBYY products in general and does not want to require a significant increase in internal capabilities, ABBYY Vantage may be a better option.
I would rate ABBYY FlexiCapture an eight out of ten.
I was using ABBYY FlexiCapture for invoices and purchase orders. We had invoices coming from a German client. From those invoices, we had to capture the invoice number, purchase order number, and invoice date. There were also line items, total quantity, and total sum. We had to take these things in an XML format or a CSV format. The outputs from these invoices were put into an application by an RPA project. So, we were basically using ABBYY FlexiCapture to capture all those details from invoices. In India, we have PAN Card and Aadhaar Card, and I was using ABBYY FlexiCapture to configure PAN Card and Aadhaar Card.
The client had around 400 to 500 vendors, and every day, the client was receiving thousands of invoices. It was a very hectic task for them to capture all those invoices into the application. It was not possible for them to capture all the fields by using any RPA tool because RPA can handle any structured data, but invoices are totally unstructured. So, we needed an intelligent OCR tool. That's when ABBY FlexiCapture came into the picture.
There are a lot of options in ABBYY FlexiCapture, and it is very vast. I have worked with multiple OCR tools, and I found ABBYY FlexiCapture to be the most accurate tool.
The key-value pair and relation were most valuable. Because the invoices were coming from different vendors, it was possible that they would come in different formats. The idea was to capture data from all formats. There were key-value pairs and nearest to the X coordinate or Y coordinate, and with a lot of hits and trials, I was able to get the exact fields configured for every invoice.
There are very few resources of knowledge. Whenever I got any doubt, I have to raise a ticket into their support forum. I can't find anything in Google or on YouTube. There is no training material, so it was very hard to learn in the initial days. The information about other tools is available on YouTube and other platforms, but ABBYY FlexiCapture is nowhere available to learn for free. They have documentation on their website, but it is very basic. It is not adequate for working on any live project.
ABBYY FlexiCapture has given a basic kind of project for capturing data from invoices, but I feel it is not sufficient for Indian invoices. A lot of times, some of the fields were not getting captured for new invoices. For such kinds of invoices, there is a training field. So, we can train it for the fields that it is not capturing so that when the same kind of invoice comes next time, ABBYY FlexiCapture will pick up these fields from those particular areas.
Another pain area was that clients were not giving proper invoices. We had clearly mentioned the proper DP for these invoices, but few invoices were not readable from ABBYY.
In IRISXtract, we can have master data, and we can set the master data. There are more options for taking any data and comparing it with master data. For a project, they have a dump from SAP for validation. This feature is there in ABBYY, but it is not extensive like IRISXtract. ABBYY is capturing the data, but there are not a lot of options to validate the captured data. It would be helpful if there are more options for validating the captured data in ABBYY FlexiCapture.
I last used it six months ago.
It takes time to get it stable. If a client has a lot of customers, and a lot of invoices from different vendors are coming, then all those invoices will not work in ABBYY FlexiCapture until and unless we configure each and every one of them.
It is scalable. There is no other tool in the market that is as creative, as vast, and as accurate as ABBYY FlexiCapture. If you have proper and complete knowledge and all the training for ABBYY FlexiCapture, then you can make it scalable in the organization. You need proper training.
I am not sure about the number of users in the whole organization, but in my team, there were four people who were using it. There were also two people from the RPA side. They all were RPA consultants and developers. There was also a team for Power BI for putting information about the number of invoices processed on a dashboard.
After that project was live, I was moved to a different project. Other people came into the picture for the support role. I was put in a purely RPA-based project. I'm working in Blue Prism for the last six to seven months.
If I send a query, they do reply. If it is a proper query with screenshots, they give you a solution very quickly. If you have a licensed version of ABBYY, they provide proper support.
I've worked with IRISXtract, and I've worked with OCR tools of RPA solutions such as UiPath, which has its own document visualization tool. I find ABBYY FlexiCapture to be most perfect for configuring any type of unstructured data.
IRISXtract is not a good tool. I struggled a lot with that tool. ABBYY FlexiCapture is much better than IRISXtract. ABBYY FlexiCapture is using the ABBYY OCR engine, and IRISXtract is using the Google Tesseract OCR engine. ABBYY's OCR engine is more accurate.
ABBYY FlexiCapture and ABBYY FineReader are licensed, and we can't get them for free, whereas Google Tesseract is a free OCR. In terms of capturing a full invoice from start to end, at least ABBYY's OCR engine is giving line breaks and other things, whereas Google Tesseract OCR, as well as Microsoft OCR, are not giving it in a proper manner. They give everything as a single string without any spaces or a new line. So, ABBYY has more intelligence.
IRISXtract provides more options for taking any data and comparing it with master data.
I initially worked on a PoC. I got a lot of doubts initially, and ABBYY's forum was very helpful. Whenever I posted any queries, they replied in minutes. The deployment was straightforward. We did the whole project in six months, which includes RPA and hosting into SAP application.
Before starting any project in ABBYY FlexiCapture, it would be better to have a few sessions with their product team or technical team to clarify all the doubts. If you have started a project and in the middle, you ask for their advice, it becomes hectic because they might ask you to change your approach. So, getting any support from them initially is always helpful.
The biggest lesson that I have learned from using ABBYY FlexiCapture is that only by trying more, you can get to the exact solution. If you are working on an invoices project, you should try multiple types of invoices. The line item is a typical area because different types of invoices have different headers and columns. You need to make sure that you have proper knowledge before configuring any line items details.
I would rate ABBYY FlexiCapture a nine out of 10.
Our primary use case of this solution is for our invoice project. We wanted to capture the sales and use tax data from our invoices. I'm a senior manager and we are currently customers of ABBYY, hoping to become resellers in the future.
I think the machine learning capability of ABBYY is pretty good. You can create your small frame model and then the software works well, applying that training to extract the data out of other invoices.
I think that the tool is really complex. It works well, but in terms of rolling it out to a large audience that is not very tech savvy, this tool might be a little too much for them to handle. I think there needs to be some sort of simplification for that kind of user. ABBYY has the FlexiLayout Studio tool which is used for creating layouts for semi-structured and unstructured documents. It's pretty complex and we'd like to see some simplification there.
I've been using this solution for four months.
I think that once it is installed, the solution is stable. There are no issues that come up.
When it comes to scalability, you might need to install multiple instances of these stations. It comes in two pieces, one is a server and one is the stations. The stations can be scaled up, and can connect to the centralized server and work well, but I think that if you wanted to have it scaled for a large number of users you might have to think about creating some wrappers around it.
We have a user base of around 50 to 100 people but we are gradually rolling it out, so I think right now we only have 20 users who are actively using it, but down the road we expect that to come close to 100.
In general, the ABBYY support is pretty good. They are very responsive and try to resolve any issues.
I think installation is pretty straightforward, except that if you are using a distributed version, then there are some prerequisites in terms of IAS that need to be installed beforehand. That makes it a little challenging, but I think if you have the right support from ABBYY you can manage that easily.
The ABBYY license is calculated by pages and it all depends on how you negotiate the licensing with them. If you have a pretty large use case, you might get some discounts, but if you have a pretty small use case, they might be firm on the price.
We did our due diligence on a number of solutions and we found ABBYY to be more widely known and they've received pretty good reviews. That's why we chose them along with the fact that their licensing is decent enough. The other solutions we looked at were not as good as ABBYY and were more expensive.
I think each company needs to make a judgment as to whether you can handle a technically challenging solution, because ABBYY is challenging. If you need to have your people trained ahead of time to get some support built into your organization, you should do that. If your organization is not very tech savvy, this solution might not work for you very well.
We still need to carry out more evaluations. For example, the out of the box, SDK support. I'd like to know how much free SDK support we would get if we try to build a wrapper around ABBYY. I think those are the things that we need to evaluate on our end, but overall I think we are pretty happy with this tool.
I think this is a good solution and would rate it an eight out of 10.
Our primary use case of this solution is for document processing. Whenever I receive an email from a vendor or business it gets processed to the ABBYY server. I've created a layout in FlexiCapture that recognizes the template, extracts the field and puts it into the Excel format. I mainly work with purchase and invoice documents and ABBYY checks the validation conditions of an invoice. I'm the manager RPA developer and we are customers of ABBYY FlexiCapture.
The advantage of the solution is being able to identify and extract the element you need from a document. The template can be customized for this. We can create our own rules to validate some values before exporting the results.
I would like to see consistency improved. If the same document is uploaded twice, I might get a different outcome the second time. Machine learning needs to be improved. We have some issues with scanned documents that may have a quality less than 300 dpi and the quality isn't high enough for ABBYY to accurately read it, and it therefore requires manual intervention. There is scope for improvement which could include AI modelling and training. If AI is there then it will identify it in a better way. There is a field training option that already has an ML algorithm for it, but it's not much use. Hand-written documents have less than 50% accuracy.
I've been using this solution for a year and a half.
We haven't had any issues with stability, I think it's better than other solutions.
I don't know about scalability because I'm the only user in the company. We deployed in the AWS server and we have a team who control everything. We currently have eight projects related to OCR which are in the pipeline. I have already trained two other guys.
There is a forum for support but not many people are active. We have a license with them so we will usually receive a response within 48 hours.
The initial setup was okay, the difficulties came later with the poor quality of documents we received.
We pay an annual license fee, our management team that deals with that.
I did a POC on all the different OCR tools in terms of the level of accuracy I get from each document. ABBYY and Amazon Textract did quite well, whereas Kofax did not provide as good a result. Textract reads the entire document data and provides raw data output in the string format. With ABBYY, I can add a field into the template and then extract it but in Textract adding a customized field is not possible.
Anyone using this needs to know they won't get 100% accuracy. Human intervention is required depending on the quality of the document. Clearly, if the quality is good, the results will be better. ABBYY has been on the market for over 20 years so they're well supported including all other RPA tools. Competitively, I think ABBYY is better than other OCR tools.
It's good to test the solution with multiple samples. Once you create a layout, test it with multiple documents and see what you're able to achieve. If I see that 30 out of 100 documents are not processed 100%, I'll retrain it to improve the accuracy level for when the same document comes in next time.
I rate this solution a six out of 10.
We use ABBYY FlexiCapture to recognize pictures or PDF files and transfer them to Word or Excel.
It's easy to use.
The integration with UiPath is not good.
I would like to see more documentation and guides to help gain more in-depth knowledge of how to use ABBYY FlexiCapture.
I've been working with this solution for about three or four months.
I have had no issues with stability so far.
I chose ABBYY because it had more solutions for intelligence automation, and it looked like I could combine it with other automation solutions. We currently have 20 to 30 users.
I recommend ABBYY FlexiCapture, and on a scale from one to ten with ten being the best, I would rate it at eight.
ABBYY Vantage is used for reading documents that require OCR or document intelligence, such as sales invoices.
The UI is user-friendly and ABBYY Vantage supports over 100 languages.
The handwritten recognition has room for improvement.
ABBYY Vantage is mainly available on the public cloud but for clients that use a private cloud, it is complicated to set up the solution.
I have been using ABBYY Vantage for two years.
I give the stability of ABBYY Vantage an eight out of ten.
I give the scalability of ABBYY Vantage a nine out of ten. The solution can handle millions of documents.
I give the initial setup an eight out of ten. There are two ways to utilize the solution. An individual can use the web-based user interface, which is easy to set up. If we intend to use the solution for bulk sorting, we'll need to use the API, which is also straightforward to set up. The full deployment can take a couple of days.
We implement the solution for our customers.
The price for ABBYY Vantage is at par with its competitors. I give the price a six out of ten.
I give ABBYY Vantage an eight out of ten.
We have over 1,000 people using the solution.
ABBYY Vantage offers better language support compared to its competitors, and it also demonstrates good connectivity and accuracy.
ABBYY Vantage is primarily designed as an enterprise-level solution that effectively fulfills OCR requirements. However, I do not suggest this solution for small companies or individuals.
We are using ABBYY FlexiCapture for invoices.
The most valuable feature of ABBYY FlexiCapture is the accuracy of the general extractions.
ABBYY FlexiCapture could improve in the maintenance, and there are some issues. You have to make efforts to do corrections. Additionally, it could be more user-friendly in terms of connecting between different solutions.
I have been using ABBYY FlexiCapture for approximately one year.
ABBYY FlexiCapture is highly stable. The processing time is very fast.
We have two people using ABBYY FlexiCapture in my company.
I have tested Vantage, and it is more user-friendly than the ABBYY FlexiCapture.
The initial setup of ABBYY FlexiCapture was not easy, mainly because you have to configure a lot of things. It depends on the installation itself if it's going to be on the server or on the same system, but either way, it is not simple.
I rate ABBYY FlexiCapture a nine out of ten.