ABBYY Vantage Reviews

My client uses ABBYY Vantage for a banking and insurance account and usually processes invoices and banking documents in paper format.

The advantage for ABBYY Vantage is in the visual tools to parameterize and set documents. Those are the stronger features.

It's important to incorporate image detection for signatures or other handwriting elements in the document.

I have been using ABBYY Vantage for the last year.

I rate the stability an eight out of ten.

For standard documents without complex rules to apply, scaling is easy. But when we need to apply complex rules, we need the skills to do so.

My client is a high enterprise.

I rate the scalability a seven out of ten.

Initial setup is easy. There are existing templates for several kinds of documents.

For most documents, it takes a few weeks or so to deploy. Deployment time depends on the rules one must apply to the documental process rather than the document complexity.

I rate the pricing a five out of ten.

I recommend ABBYY Vantage and rate it ten out of ten.

We use this solution for invoice processing.

The most valuable feature of this solution is its ability to extract content from documents. It is able to identify specific fields and special characters. We are able to train the tool to identify certain sets of fields based on specific definitions. This solution is also user-friendly. 

This solution could be improved by offering better integration with other platforms. They have released the connectors for all other RPA tools such as Blue Prism UiPath, but this integration is quite challenging to use. It's not very straightforward or easy to understand for a non-technical person. The integration should be configured in such a way that anyone can understand it and use it.

I have been using this solution for six to eight months.

ABBYY is a user-friendly and stable product. ABBYY is more flexible and stable compared to a solution like Kofax.

This is definitely a scalable solution. 

The customer support team are knowledgeable and responsive. Their response depends on the license that you hold with them. Their licenses come with predefined response and SLA times. If you are a golden license holder, you will receive a response within three to four hours. 

Positive

There are different sets of initial configurations and this depends on the use case. We have standalone and multi-server setups. Being a consultant, I configured ABBYY FlexiCapture myself. I could easily go through their documentation and figure out what needed to be done and how it needed to be done. The documentation is user-friendly.

They have a trial license that is limited to a certain number of pages. The paid license varies from six months to one year depending on the number of documents that need to be processed. We are a consulting firm and our license model depends on customer requirements. 

I would rate this solution a nine out of ten. 

We are using this solution for bank transfer orders.

The most valuable features have been the rate of recognition and the structured documents.

The recognition intelligence could improve by having more details in the documents. There are limitations with the forms, templates, and manuscripts. 

In an upcoming release, it would be a benefit to have Arabic documentation.

I have been using this solution for one year.

We contracted the technical support and everything was fine with their support.

I have previously used UiPath and I would recommend it over ABBYY FlexiCapture. UiPath is easier to use, has both intelligence and robotic processes, supports many OCR platforms, and the documents are updated frequently by the company.

The setup of this solution was a medium level of difficulty. The difficulty level depends on the model, the quality of documents, and the process.

The price of this ABBYY FlexiCapture is a bit expensive and the price is based on how many documents have been captured. For example, one or two million captures.

I rate ABBYY FlexiCapture an eight out of ten.

Our primary use for this solution is the automatic processing of invoices. We used the invoice module for capturing and processing the invoices.

We have this solution installed as if it were on-premises, but it is hosted on a virtual machine in the cloud.

The OCR is the best on the market. Even if you go for an open-source solution, it will never be as good as recognizing imagines as ABBYY. The is the main reason that we chose this product.

The automatic processing of invoices is not set up. We had to invent our own way of handling this. For example, if the invoice is not recognized successfully then it goes to a verification station for a person to verify whether everything is ok. But, there are no predefined solutions for this. They should have some basic types of different projects already in place, which would allow you to just take a template and customize it for your needs. We had to do all of this from scratch. It was a difficult job because ABBYY consultants are very expensive. You do not have any other consultants that really know the details, and then you have to figure that out all by yourself. It is tough. It's not just about having the product but having some examples on how to use it.

Thre is not much help available on Google or from ABBYY on how to use this solution, and it would be helpful if there were more examples available.

This solution should have better integration with RPA solutions such as Blue Prism.

Generally, this solution is stable. We have had production running for more than a year and a half, and it is fine. However, when we needed to migrate, it was not really stable.

We do not have any other environments for testing and development. We only have production, and it was a mistake that I wanted to migrate to a newer version than we had (from version 11 to version 12) because it broke my project. In retrospect, it should have been migrated in a test environment in order to ensure that it would work in production. After that, it could have been moved.

Since we did not have another environment, and it was broken, I needed to set up and fix it quickly. 

We only have one robot. It's going on and processing invoices every day.

We are now selling automation of invoicing to more of our clients.

Technical support for this solution is mixed. Not all of the consultants from ABBYY are good. For example, we have had very good experiences, but at the same time, one consultant we had really didn't help up too much and took up a lot of time. They have good ones and they have bad ones, but the price for all of them is the same. When you do not receive services for a very high price, it's disappointing.

The initial setup of this solution was difficult and complex because we needed to set up all of the rules. I needed to learn how to program inside of ABBYY. Without those clicks, our project would not work. At the same time, ABBYY sells you the license, but they do not tell you all of the pros and cons, or all of the obstacles that might come.

When we faced all of these obstacles without any help, it was really tough because we were right in the middle of the project. The solution was already sold to the customer, and we were left trying to set it up.

My advice to anybody who is considering this solution is to ask for case studies and examples in advance. Ask for real examples on how to set it up. One example might be for invoices, or for formulas that should be inside the product, and how to set them up quickly. We asked for automatic invoices and they said that they didn't do that yet.

We had to put a great deal of effort into this, and it took a lot of time and our money to invent our process together with ABBYY. If we would have had some examples then we would not have had to start from scratch.

I would rate this solution an eight out of ten.

We use it for document processing. We have PDF documents, and we need to extract tables from those documents. We use ABBYY FlexiCapture to extract tables.

We are able to extract tables from PDF files. Before ABBYY FlexiCapture, it was done manually. We had to manually input tables into our banking system. We could automate that with FlexiCapture. It is also integrated with RPA. So, FlexiCapture just extracts the information, and RPA takes that information and enters it into the banking system.

Its OCR Engine is very successful, and it is the leading OCR Engine. It also has NLP support. 

In FlexiLayout Studio, you can create your own variables. It works great for semi-structured documents.

Their tutorials are not enough. They can improve the tutorials and maybe add more examples in their tutorials. Currently, if you want to learn ABBYY technology, it is very difficult. There are just a few resources, such as YouTube channels and blogs. There are not many resources for learning ABBYY.

It would be great if they can make a community edition to use ABBYY. Currently, if you want to try ABBYY, you have to contact a salesperson and take a trial license, which is complicated. They should just give a community edition or a free edition with a few features.

Its licensing is very expensive and should be improved.

I have been using this solution since 2019.

We didn't encounter any crashing. It is stable, but it has some bugs. For example, the PDF quality is very good, and you can read the text easily, but sometimes, ABBYY FlexiCapture reads it incorrectly. It is not very frequent, but it can cause a problem for some of the documents.

For such bugs, we open tickets with ABBYY, and they try to solve the issue. If they are able to solve the issue, they send us the solution, and we apply that. Sometimes, they weren't able to solve it, so they took that ticket to their backlog, and after a new release, they notified us that they have solved a problem in the new release.

We don't have a problem with scalability. In the beginning, our volume of documents was small, but it has increased about 10 times. It works without any problems. If we want to increase its capacity, we put another machine, and it defines a processing station. So, we can increase its capacity easily.

Currently, I am the only one using it in my company. I do all the administration and create new templates. Its maintenance is also done by me.

We plan to increase its usage. At the moment, we are using ABBYY in just one project, but there are upcoming projects that require ABBYY.

Their tech support was successful. I would give them a nine or a 10 out of 10.

The deployment process was a little bit tricky for us. We didn't take professionals for the installation or deployment process. We learned how to deploy it from other sources such as YouTube or blogs, and we did it ourselves, but it took about a week to deploy. Now, if I want to deploy it, it will just take one or two days. At that time, we didn't have ABBYY expertise, so we learned how to do it and tried to deploy it. Three people were involved in its installation.

Its maintenance is done by me. It requires some manual effort. For example, for some templates, I do some updates, and there is some manual work. I go to document definitions and remove the other one. I then upload the new one and do some settings.

For an operational process, about 40 people were dedicated previously, but now, five people can do the same work by using ABBYY integrated with RPA. It is not just ABBYY; there is also the RPA part. ABBYY is used just for data extraction from PDF files.

Its price is a little bit high and can be lower. Its licensing is very expensive. I don't remember exactly, but for each page, it is about four or seven cents, which is too expensive.

Before using ABBYY, we considered many products. We considered Ephesoft and other document processing engines, but ABBYY was the most successful one. There may be other successful vendors, but they don't have very strong support in our region. ABBYY's support is very strong in our region. Other tools also do not provide on-prem installation. They are cloud-based, so we chose ABBYY.

Their sales team was great. They were very helpful, and their technology is great. 

If you are looking for an on-prem solution, ABBYY would be better, but if you are looking for a cloud solution, you can use other platforms. Google and Microsoft have great data extraction tools that are cloud-based.

I would rate ABBYY FlexiCapture an eight out of 10. Its licensing price is high, and there are no training materials that you can use easily. There should also be a trial or community version.

We are a solution provider and ABBEY FlexiCapture is one of the products that we implement for our clients. It is an OCR tool that we use as part of different automation solutions. 

It is flexible and easy to deploy into any environment, be it on-premises or in the cloud.

The handwriting recognition is very good, as it can recognize handwriting done with pen and paper with at least 70% accuracy.

The interface is very easy for a non-technical person to use. For example, the fields that have been correctly identified are color-coded green, whereas the exceptions are color-coded red. 

Our basic concern is that ABBYY does not allow you to use the product unless you are a trained professional. This has been a roadblock for some of our clients because they have been okay with the pricing, but because they are not an expert on ABBEY, they are not able to use it.

In the future, I would like to see integration with Google Sheets. That way, if somebody has data in another format then ABBEY can pull it out and work with it directly.

We have been using ABBYY FlexiCapture for more than two and a half years.

This is a pretty stable platform.

We have not found any issues with scalability.

The majority of our clients are small to medium-sized businesses with less than $500,000 USD annual revenue. We do have some enterprise-level clients that have a revenue of more than $1,000,000 USD per year.

The technical support is pretty good. The ABBYY support teams are very good and there is an open community, which is very supportive as well. We normally get a response within about six hours of creating a ticket.

It is very easy to set up. The deployment takes around 48 hours, end to end.

This is absolutely a solution that I would recommend. If you are having problems with handwritten text and the recognition of data then ABBYY is the place to go.

I would rate this solution a nine out of ten.

We primarily use this product for data capture.

The most valuable feature is the ability to capture data from documents with different formats.

IT team don't need to maintain multiple systems.

If you are not used for training layout feature, a lot of effort is required in order to upgrade to the latest version.  FlexiCapture get the better training layout feature in deep learning and NLP.

We have been using FlexiCapture for three years.

FlexiCapture is a stable product.

Scalability has not been a problem. 

I would say that the technical support is average. 

This is the first data capture product that we have used.

The initial setup and preparing for our first capture was no so easy. The application used to create the database was not easy to use.

We are the in-house team.

For us, the price is reasonable for semi-structure and unstructured forms.

We did not evaluate other options before implementing FlexiCapture.

My advice for anybody who is considering this product is that if they have many different types of documents that need to be captured, then this is a good option.

I would rate this solution an eight out of ten.

Our primary use case is for invoicing. We use it for product licenses and reports about insurance policies and invoices.

It's a very useful and user-friendly product.

The stability is very good. 

We use around 100% of data and the success rate is 90%.

We have around fifty users using this solution. The users are mostly engineers and developers. 

The initial setup was straightforward. 

I would rate this solution an eight out of ten. Not a ten because sometimes some documents have handwritten data. If this improved, I would rate it a ten out of ten.

The product is user-friendly. I would recommend it.