ABBYY Vantage Reviews

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.

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.

Our company uses the solution to develop structures for automatically reading customer documents. We produce the document definition for each layup and send data to customers. We have 40-50 developers using the solution in various departments. 

In the future, we will use the solution for automatic classifications of documents. 

The solution responds well to automatic document classifications with a 90% success rate. 

There are sometimes issues with calculations or integrations with the server when running multiple products with different languages. This causes data to not display properly in data fields. 

The system does not always train itself to recognize data properly from system leads. 

A more comprehensive training program should be available because free training books do not provide the level of detail needed. Sometimes, we encounter issues with an automatization but cannot resolve it even though we completed the associated training module. Training for particular scenarios need to be included in modules because integrations can be tricky or complex without these details. 

I have been using the solution for one year. 

The solution is stable. 

The solution is very scalable. 

We had one issue with speed where we could not achieve the minimum time for processing which should have been seconds. Otherwise, the solution is really fast with basic or fixed processing. 

Support does not answer tickets in a timely manner but eventually closes questions. 

For example, I have a few tickets for assistance with DVP, data pages, and working with multiple languages but support has not yet responded adequately to the email inquiries. I would like detailed information and an explanation for whether a shadow case can be used. I cannot authenticate, determine if available onloads would fix captures, or integrate without proper answers. 

Support should respond quickly to production issues. Time zones are an issue in getting responses because support works on Russian time. 

Support should have access to prior tickets to get a cumulative picture of issues a user has experienced. Generally, they do not have details from prior tickets to inform solutions so they base their answers on only the current ticket. Having cumulative knowledge will allow support to better understand a customer's situation and use case. 

I rate support a six out of ten. 

Neutral

The setup can be complex because it takes time to learn all the menu options. Our setup took one or two months because we wanted to ensure it was done properly. We do not use many of the menu options as our use case is rather basic. 

The help page is not very comprehensive or detailed. It uses code that is formal and the world is now more informal so some options might confuse users.

I have not evaluated other options. 

The solution is a good product but there is always room for improvement. I rate the solution a seven out of ten. 

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.

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.

The most valuable feature of ABBYY FlexiCapture is the ability to create your own template on the fly. You can train and classify, you can work with those different templates without the need to do special programming for it or with minimum programming. Additionally, the solution is supporting the Arabic OCR, both of these combined features are the most important for us in the Egyptian market.

ABBYY FlexiCapture could improve the performance. We are looking for better performance because it can be a lengthy capture process and the accuracy needs to be enhanced when it comes to Arabic.

In the next upgrade, ABBYY FlexiCapture could add invoices for the Arabic or for the Middle East because it's based on European or American standards mainly.

I have been using ABBYY FlexiCapture for approximately four years.

ABBYY FlexiCapture is stable, we did not find any problems.

In our usage, ABBYY FlexiCapture has been scalable enough. We had a cluster-based operation.

I rate the support form ABBYY FlexiCapture a four out of five.

The support could be more responsive.

I have used OpenText previously and overall the solution might work better, but for our use case, ABBYY FlexiCapture has all the features we need that are important, such as Arabic OCR, and is priced well.

The initial setup of ABBYY FlexiCapture is easy.

The price of ABBYY FlexiCapture is better than some competitors, such as OpenText.

I recommend this solution to others.

I rate ABBYY FlexiCapture an eight out of ten.

The solution is used mostly for form extraction, fixed form extraction, text forms, data extraction, OCR, et cetera. We use it for digital document processing.

We run software that does basically business process automation. It's given us a form extraction utility to add. We're utilizing the ATR in the FlexiCapture engine, and in that way, we can use the FlexiCapture engine to process forms. Any forms that contain data, we can extract.

Without that, we would have to use pattern extraction, regular expressions, and things like that. This is a forms processing engine, which allows us to be able to set anchors and OCR values, et cetera. 

The form extractions engine and the FlexiCapture designer are really useful.

The solution is easy to set up.

We have found the solution to be stable so far. 

The product is extremely scalable. 

The UI is okay, however, I remember the scanning and the way that you actually get documents into the system. The FlexiCapture, what they call a process developer, could use some work.

The solution needs more web or cloud-based development. Cloud-based FlexiCapture development would be great.

The on-premise web version doesn't seem to be intuitive or easy to use or install. It's not user-friendly.

Technical support is slow to respond.

The pricing is a bit high and we are looking into other options. 

I've been using the solution for three years now. I've used it for a while. 

The stability is good. It's a reliable solution. There are no bugs or glitches. It doesn't crash or freeze. 

The solution scales very, very well. If a company needs to expand it, it can do so. 

We have about ten users on the solution right now. They are mostly developers and consultants. 

Technical support could be better. once you create a ticket, it takes some time for them to respond, from a partner perspective. You send a ticket to an email address. There's no phone number. You can send it to support@abbyy.com and you have to wait. 

They do have a fairly thorough knowledge base. There are also available videos on YouTube. However, if you're having complex problems, it can take sometimes days for them to respond. If you're running a professional system, that's not going to cut it.

I don't know if they have level levels of support, and we have maybe just a really poor version of the support system. I can imagine that, if you pay for a really high level of support, then, of course, they're available. That said, from our perspective, being a partner developer, we've had problems with the support, for sure. If you pay for Professional Services hours, it would be my assumption that they would respond right away, however.

The initial setup was straightforward and easy. It was not too complex or overly difficult. 

Licensing is paid on a yearly basis. I don't know the exact price of everything, however, I do know that it is expensive from the perspective of our management team. We've also been looking for other solutions.

We are a partner with ABBYY.

I'm using version 12. I believe it is the latest version. I haven't seen any updates as of recently. There could be a version 14 out, however, I'm not sure. We're using the desktop version. 

I would advise those considering the solution to watch the YouTube lessons and pay for Professional Services training and assistance. 

At this point, I would rate the solution at a seven 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.