ABBYY Vantage Reviews

We use Vantage for invoices and purchase orders. We have around eight members using it. It's good for the document types we use. I don't think we use many of the available skills. We use the invoices and purchase orders because that's what we need for our in-house product. We might use it in the future for remittances, 

The key fields that must be captured from a particular financial document are validated. This usually gives us 80-85 percent accuracy, which is good compared to other OCR tools. 

They're constantly adding patches that fix all those issues. They make improvements on the back end. ABBYY has made many enhancements recently. The address-conversion features are critical. It automatically converts the city and state name into the ZIP code.  That's a crucial feature we wanted that they've implemented.

Integration is very easy. There are lots of connectors. 

I would like better language support for Hebrew and Arabic. They're still working on that, and we might get an update by the end of this year. There is currently no support for those two languages because they write from the right to the left side. It would be great if they could add this as soon as possible because we have customers from the Middle East and Israel. 

We might need more machine learning or cluster things for ABBYY to learn from that and improve accuracy. There's a difference when you go into the invoices. If you have one template, we need one sample to clean it, but a purchase order may need a minimum of five samples. That's something I've noticed, but they might need to improve the machine learning. Generally, ABBYY's accuracy is better than other tools.

I've been working with ABBYY Vantage for nearly four years.

Vantage performs much faster than other OCR tools.

Vantage is scalable. We can integrate it with AI, ChatGPT, and RP tools. They have connectors. 

I rate ABBYY support nine out of 10. We reach out to them when we have issues that we cannot find solutions to on the community portal. They help us with the code and are always willing to hop on a call if needed.

Positive

Deploying Vantage is simple once we have access. To integrate it with our product, we only need to add the user IDs and passwords. We also need to write some code based on our requirements. It isn't very complicated. We previously used ABBYY FlexiCapture, but today, most of our clients use Vantage, so we use the latest cloud version of ABBYY Vantage.

ABBYY is continuously updating things, but we retain backups for 14 days in case anything happens, so it doesn't affect our end-to-end automation. Generally, it doesn't require much maintenance. 

I rate ABBYY Vantage eight out of 10. I would recommend it to others. We have some things we'd like to improve, but they will probably implement these improvements in the near future. 

ABBYY's machine learning requires a lot of training for some skills, but it's not much compared to other OCR tools. You can train a template using three or four samples, but with others, it has to go up to 10. The AI of other OCR tools is not good compared to ABBYY. However, they should add support for Arabic and Hebrew as soon as possible.

We are using the solution in our company for extracting details from invoice copies.

In our company, using the solution, we have seen that overall automation is quite easy. The output and time for developing the process are quite less.

It's worth noting that ABBYY Vantage employs both AI and machine learning techniques. Additionally, integrating with ABBYY Vantage is easy, with LinkedIn options available for use through the platform's built-in activities.

The customization can be done using ABBYY Vantage. But I don't have complete knowledge of its pricing.

Customization in the solution needs to be modified. In the future, I would like to see the product have better customization functionality.

I have been using the solution for a month. Also, I am using the solution's latest version. My company has a partnership with ABBYY Vantage.

Stability-wise, I can't rate the solution since it is still in the PoC phase. Once the products which we are developing go live, we can figure out the stability of the product. As of now, I rate the solution's stability an eight out of ten.

Scalability-wise, I rate the solution a seven to eight out of ten.

The technical support is helpful. I rate the technical support a seven out of ten.

Neutral

Previously, I used to use FlexiCapture. Still, we are using FlexiCapture in our company. ABBYY Vantage is user-friendly. Also, it has custom activities, and integrations are quite easy.

The deployment process can be done in a few minutes. So it can be done in less than 30 mins.

We were able to do the installation with the help of our in-house team. We already have a platform team who actually helped us with installation. So, I just started using the tool last month. I wasn't involved in the installation since I am a core developer who works on the design. Approximately 10-12 members are using the solution in its PoC phase. Later on, it may expand to thousands of users.

The cost is per page we use. So, the number of pages we use will be its cost.

I would definitely recommend the solution to those planning to use it. I am yet to explore the solution's load-balancing feature. I rate the overall product between seven to eight out of ten.

To be more concrete, I rate the overall product an eight out of ten.

Our company uses the solution for processing invoices that follow a particular template. We have some standard invoices on a monthly basis and use UiPath to download them from our suppliers. The downloads are extracted and exported to the solution.

We previously used the solution's on-premises version but it is no longer supported. We used the trial cloud version until we bought our license one month ago. 

We are in the development phase but once we go live, we will have many users for the verification station.

The solution has its own language that can be configured many ways and with higher accuracy than other products.

Programming interfaces should include intelligence or documentation. It is difficult to find documentation and implement without some information included in the backend scripting pages.

The support network is weak and needs improvement.

I have been using the solution for one year.

The solution is stable for documents that are standard format.

The solution is scalable.

The support is weak and it is difficult to find answers for day-to-day problems. There is no forum for answers and not many users are familiar with the solution to help with issues. The provider should have documentation for everything but it is not reaching end users.

Tickets are not responded to in a timely manner and it is difficult to get email responses or escalations. There is no standard format for support and they just respond whenever they like. In contrast, UiPath helped with anything needed.

I rate support a four out of ten.

Neutral

We used UiPath's Document Understanding but it had issues finding items that were marked in particular locations.

Accuracy is comparatively higher for the solution. You have the option to write rules in the backend which can be manually verified if a document does not satisfy conditions. Once verification is complete, the document feeds back and the solution picks up the rest of the processing. This flexibility was not available in UiPath.

UiPath also required too much user involvement at the time of our implementation, but I believe this has improved over time.

The cloud setup is straightforward and only requires configuring the development environment which includes flexi layout studio and product setup station. Any security concerns can be addressed through an SSO or AD integration.

The on-premises setup is a bit complex because it requires understanding connections.

We implemented the solution in-house.

Maintenance and updates for the cloud version are handled by ABBYY. We receive notification of updates in advance. Typically, an update requires some upgrade in the development environment to ensure there is no impact to users.

Our license is $6,000 and includes unlimited users for the verification station.

Licensing is a bit on the high side.

We looked at ABBYY's invoice processing but were not satisfied with the results so we moved to the solution.

The solution is the best for use cases with standard document templates. If your documents do not follow a particular format, then you cannot use the solution. 

The features for AI and processing lag behind so I rate AI a five out of ten.

Overall, for our purpose with standard document templates, I rate the solution a seven out of ten. 

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 mainly use ABBYY Vantage to process loan originations for cars.

ABBYY Vantage has reduced our data because it can classify and extract information from documents.

ABBYY Vantage's most valuable feature is auto-learning.

ABBYY Vantage's reporting could be improved - they don't have any out-of-the-box or detailed advanced reports.

I've been using ABBYY Vantage for about a year.

I would rate ABBYY Vantage's stability five out of ten.

I would rate ABBYY Vantage's scalability eight out of ten.

We've seen an ROI from ABBYY Vantage.

I'd give ABBYY Vantage's pricing a rating of seven out of ten.

I'd recommend ABBYY Vantage to other users and give it a rating of seven out of ten.

I use ABBYY Vantage in my company for extracting data from invoices, IDs, and contracts. I have also used ABBYY Vantage to extract data in English from different documents.

As my company operates in the Middle East, it is important for us to have a solution that accepts Arabic characters from documents. The most valuable feature of the solution is the extraction of data from passports and national IDs, a task that is generally difficult for most of the OCR engines to check data from such documents.

ABBYY Vantage is a product that does not include the Arabic language. From an improvement perspective, ABBYY Vantage should include the Arabic language.

I have been using ABBYY Vantage since 2018. My company has a partnership with ABBYY.

It is a very stable solution.

It is a scalable solution.

I work in a software company where there are more than 50 users of ABBYY Vantage.

The solution's technical support is very supportive.

In the past, my company used to use IQ Bot from Automation Anywhere. My company moved from IQ Bot to ABBYY Vantage to avail the latter product's features.

The product's initial setup is neither simple nor difficult.

If one uses ABBYY Vantage and is familiar with its components, I believe one can handle its setup phase. I think it is not a very basic solution.

The solution is deployed on an on-premises model. Depending on the projects undertaken by my company, I have also used the product on the cloud services by AWS.

ABBYY Vantage is a bit of an expensive tool. The payment model for ABBYY Vantage is such that a user needs to make payments for the number of pages consumed with the help of the tool.

I think my company chose ABBYY Vantage over other products in the market owing to the fact that it is a reliable product that offers stability, features, and capabilities to extract data from different documents. In our company, we tested ABBYY Vantage for many of our projects and saw that it delivers results.

I recommend ABBYY Vantage to those who plan to use it in the future, especially if you deal with complex, semi-structured, or unstructured documents since it is a dependable tool that provides high accuracy. Suppose a user wants to use a product to segregate financial documents and needs a tool that provides very high accuracy, then my company recommends ABBYY Vantage.

I rate the overall tool a nine out of ten.

We use the solution to extract the contents from documents like invoices and passports.

Verification Station is valuable. If the confidence level is lower than what we set, we can view it in Verification Station and correct it if there are any issues. For example, if the confidence value is 90%, and the confidence level of the extracted content is below 90, the documents will be pushed to Verification Station. We can check whether the document has been extracted correctly. If the values do not match, we can correct them.

It would be good if the product provided an AI-based prebuilt model that predicts and gives output. We can then verify and make changes if necessary.

I have been using the solution for almost three years.

I rate the solution’s stability a seven out of ten.

I rate the tool’s scalability a nine out of ten. Five to ten of our clients are using the solution. The number of users has reduced. There are other vendors who offer OCR solutions. Our clients are enterprise-level businesses.

Whenever we have issues, we raise a ticket, and we get a response from the support team.

Positive

The initial setup is not easy, but it is not complicated. It was pretty straightforward. I rate the ease of setup a five or six out of ten. The vendor provided all the documentation. We could raise a ticket if we had any doubts, and the team would help us.

Compared to most solutions, it is a good product. It has a lot of features. The extraction it provides is much better than any other vendor. Overall, I rate the tool a nine out of ten.

We had to extract some data from a commercial policy, which can run up to 300 pages, for a client. It was a challenge to look for the action data and extract it out of those 300 pages. With ABBYY FlexiCapture, we were able to do that easily by using its repeating group feature. It was helpful. For doing the same in Kofax, we would have had to heavily rely on scripting. There is no way of doing it with low code.

Its ease of use is valuable. It is easy to use and configure.

Its ICR is really good at handwriting recognition. The last version of ABBYY FlexiCapture that I used was better than other tools such as Captiva and Kofax. The base OCR engine of ABBYY is also very good. In fact, Kofax was using ABBYY's OCR engine in the last version, but they came up with their own engine.

One good thing about ABBYY is the training. All the training courses are available in ABBYY University. They were not free initially. They were instructor-led, but now, ABBYY has made them open for everyone to learn, whereas with Kofax, you have to purchase training courses, and then you can learn. With ABBYY, everything is there in their knowledge base.

I have not used it in the last six months, but at that time, there were some stability-related issues. These were known issues. They might have already fixed them, and it might have been improved by now. We had raised tickets, and they were working on various tickets. The known bugs included crashing of the application when there were more than 500 pages in the configuration window. It did not work in such cases.

There were also issues related to the classification by training. There is a feature in ABBYY where you can classify the type of a document, but it was not very effective when you trained it on a lot of variations. It worked fine for up to 10 or 15 variations but for anything beyond that, it was a mess. It wouldn’t work.

They can have more advanced workflows. They can have some custom status in their workflow. It was there, but they can introduce more cases such as triggering an email or interacting with other systems with APIs. They can be included as stages in their workflow rather than doing it all by scripting. 

They can also work more on connectors. The ABBYY connectors are there for SAP and SharePoint, but they can include more connectors. ABBYY's usage has increased. I have seen many companies using ABBYY in recent times, and it will help a great deal if there are more connectors to connect with the end systems.

I had worked with ABBYY FlexiCapture for around five years. Currently, I'm working with Kofax, and I have not worked with ABBYY for the last six months. The last version that I used was version 12.

I have not seen FlexiCapture environments with a lot of users. At the most, I have seen 20 users, which included five or six business users, five or six developers, and a few people from the admin and config team. That could be because at the time of implementing a project, not many people were required. When we handed over the project, more business users would have been created. It all depends on the phase of the project.

We did try to reach out to them for some of the challenges. They wanted us to take some proper services consulting, but we were able to manage on our own. We did not interact with the services consultant from ABBYY.

I used ABBYY FlexiCapture in my previous organization. Currently, I'm working with Kofax. Both of these organizations are service-based, and they provide services related to implementation, development, and other things. The tool that we use is decided by the client. When we approach a client, if they have already purchased a license of ABBYY or Kofax, we have to execute the use cases by using that tool. Otherwise, it will be a loss of a lot of money for them. 

If they don't have a tool, we do try to suggest what would be best for them, but it is up to them to decide which tool they want to go for. They can go for ABBYY, Kofax, TotalAgility, or any other tool.

I would recommend ABBYY FlexiCapture for those use cases where only OCR is needed, and there is no need for business processes. That's because not much branching is there in the workflow. It does not have a powerful workflow feature. If you are using it in association with any BPM or RPA tool, there is the ease of configuration, extraction, and classification. That's one thing that I like about ABBYY.

FlexiCapture is a good product. It can be used for any kind of use case that requires OCR. Except for the unstructured content part, which is there in Kofax, I cannot think of a use case that cannot be solved by using this solution. It caters to most needs of the projects. ABBYY is positioning this tool as only an OCR tool, not as a BPM tool. Kofax is an OCR and BPM tool. That's the difference, but I would not like ABBYY to change it because that's what makes ABBYY the simplest. There is a single component, which makes it easier to understand. When you add more features and modules, the complexity also increases from an understanding perspective. We can suggest more features, but it would be a trade-off.

It is a straightforward setup. If you have a cloud deployment, you just need your tenant. You simply start using it after installing a thin client on your machine. 

I have used ABBYY on the cloud. I had used ABBYY as a standalone installation on my machine. I have used ABBYY as a distributed solution within our VPN.

Deploying simple bug fixes in ABBYY doesn't take much time. It can be done within two minutes. When deploying the whole project from scratch, I have not seen it take more than 10 minutes. It can be done easily, and it is a straightforward process. To import from one environment, you just change the variables to cater to the needs of another environment. You just go there and import it. It is that simple.

You need to purchase user licenses, and you also need to purchase the license for the pages. User licenses are required for your developers to use the developer tools, and you also need to ensure that there is a pool of licenses for the business users so that they can log in and perform their activities.

It has a very simple GUI. When a person is using ABBYY FlexiCapture for the first time, I would suggest exploring all the features, especially the Flexilayout Language, because it is very easy to explore all the features. It provides you with a great level of flexibility to configure complex documents. ABBYY is no-code, but there are a lot of things that you can do by scripting in Flexilayout Language. So, I would recommend not restricting yourself to the GUI-based commands. You should go and try Flexilayout Language. It is a very powerful feature in ABBYY.

ABBYY is launching new products. It is not that they're not changing anything. They have launched Vantage 2.1, which is very good at cognitive capabilities.

While pitching their tool, every product's sales team tells clients about certain cognitive capabilities and other features, which might not be possible for specific use cases. So, client expectations should be set correctly. One of the clients was expecting us to use the cognitive capabilities of FlexiCapture, but FlexiCapture is not that cognitive. Vantage is cognitive, but FlexiCapture is not.

I would rate it a seven out of ten. There is ease of use and ease of configuration, but they need to include more features. They need to make the product more stable in dealing with more variants.