ABBYY Vantage Reviews

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.

It is used for reading the invoice and working between customer ERP to implement RPA service, the robotic process automation. We've read the data from MD.

The OTR (Optical Text Recognition) is the most valuable feature of this solution. 

There is an area of improvement. For example, when we read the data from the OCR,  the accuracy is not good.

In future releases, I would like to see Thailand English integration in this solution. There is not a lot of Thai language integration, which is pre-dominantly an issue in Thailand.

It's been in use for the past year. We use the latest version of the solution. 

I would rate the stability a six out of ten. 

It is pretty low in terms of scalability. I would rate the solution a two out of ten. 

In Thailand, we've had to be the technical support,  especially as resellers. So there's not really a lot of technical support available in the Thai language.

Neutral

The initial setup is of medium complexity. I would rate my experience with the initial setup a six out of ten, where one is difficult, and ten is easy.

We have deployed it both on-premises and on the cloud.  

Overall, I would rate the solution a five out of ten. Specifically in Thailand, ABBYY Vantage does not have proper Thai language integration. So, when you're trying to read or analyze data that implements Thai language, it proves quite problematic.

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.

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 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 use this solution mostly for processing Brazilian servicing invoices and personnel documents and contracts, such as personnel ID cards.

I am a strategic partner of ABBYY here in Brazil. I deploy this solution for the customers. We mostly deploy it on a customer's cloud infrastructure. It is not the cloud side from ABBYY. It is like on-premises, but it is in the cloud of the customers.

Most of our customers work with RPA. On the cognition side, you have to look at the document and also create some intelligent rules to validate the data from the document. We give the bots the ability to put documents to be processed, and then the bots give back the results to move on to the next task in the process. In the process on which bots are working, there are two high-value workflows that require finding things and using judgment. Both are conditional logic.

When talking about documents, RPA can read the full text of the document, but it cannot understand the rules of a document as a human does. This is something ABBYY can do very easily. You put some rules in the ABBYY task, and ABBYY will say, "Okay, so this invoice is $20, and 10% tax is $2." If the tax is $3, ABBYY will say, "Look! There is a mistake here with this tax amount." ABBYY is able to understand the content and the context of the document and give it back to the RPA to go on with the task.

The most valuable feature is the ability to scale for big processes. We are able to process 1 million pages a day. Its accuracy is also very nice. It is a good feature that they have. 

It is an independent platform, which is its biggest advantage as compared to other solutions. It is also very stable and powerful. It is 100% on time.

They should improve the RESTful API side of this solution. Currently, fully RESTful API is not available in the on-prem version, which is really a problem, and we have to work around this limitation. The cloud version already has a fully RESTful API, but the on-prem version doesn't have a fully RESTful API, which is a big mistake. It is easy to solve, but they aren't solving it quicker. They are taking a long time. Nowadays, most people don't go to the interface. They like to use RESTful API.

I have been using this solution for about 20 years.

It is very stable and powerful. 

It is easily scalable. It is for all kinds of customers. Our customers are small, medium, and large businesses. RPAs are used in all kinds of organizations nowadays, and documents are always involved. RPAs are used even for testing and learning, and documents are always a problem.

Our clients do plan to increase the usage of this solution in the future. FlexiCapture is able to scale or spread in the department without having the need for any other RPA tool or AI tool.

They are very good and fast. If you find any vulnerability or there is an issue in scaling this solution, they are very fast in fixing the issue.

It is very easy to deploy but only after we have handled the security side of the customer. It is not complex, but, like any other server-based solution, things have to be clarified with the security team and the IT team. The biggest friction is not involving all the teams from the customer side, especially the security teams.

Our implementation strategy is to involve everyone two or three months before. This is because the businesses that purchase the solution sometimes don't have a good relationship with the IT team. We go to a workshop with them and try to understand their concerns, which takes two or three days. Its installation takes one or two days.

Our clients evaluate Kofax, UiPath, Brainware, and Nuance. The competition is big here. FlexiCapture is the most independent solution. It is an independent platform, which is its biggest advantage. You are not dependent on other solutions. In UiPath, you depend on scaling the RPA to spread OCR.

I would highly recommend this solution. My advice is to engage with a professional services provider at the beginning for installation, deployment, and training. Don't try to do it on your own because it is a very powerful and big solution. You'll have to learn it before you try to use it. Don't do it yourself. 

I would rate ABBYY FlexiCapture a nine out of ten. It is missing only RESTful API.

The advantage of this tool is that it is a proven product. A lot of other products are quite new in the market.

Initially, it was good, but now, in terms of ease of implementation and accuracy, there are better competitors in the market. What we are seeing in some of the other tools isn't there in ABBYY. They have to improve it to include such features. Otherwise, it will be difficult for them to compete in the market.

There is more ease of implementation in new products. The time taken to extract the information is less in new products. We should be able to have a very light implementation. I have seen other products where you don't have to install anything, and everything works on the cloud as a service.

Similarly, there are difficulties with some of the documents, but there are some for which it works out. ABBYY should be definitely looking into that.

It has been more than three years.

Based on the implementation experience we have, it is scalable, and there is no doubt about it.

I don't have much experience with them. I only contacted their support team for something related to their training.

There is no doubt that it is a good tool, but you need to think about what is your goal and what you want to use it for in the long term. When we started, this was the only intelligent document-processing company available, but now, there are a number of players in the market. We came to know very recently that they have a higher success rate than this one. So, you have to evaluate according to your needs. 

I would rate it a six out of ten.

We are an implementor and we create solutions for our clients. One of the products that we use is ABBYY FlexiCapture.

We are currently implementing a use case for capturing bank statements. Using ABBYY FlexiCapture, we are working to capture the check statements with different fonts that include the value, payee name, and date of birth.

This product makes intelligent automatic documentation predictions, and for our use case and what we are targeting, the accuracy is 90%.

The most valuable feature is the accuracy of document extraction. If you compare it to other applications, such as IQ Bot, or products on AWS, FlexiCapture is much better.

The accuracy changes depending on the scenario so you need to test it before committing to this solution.

The is a stable product.

FlexiCapture is scalable. 

I would rate the technical support a nine out of ten.

I also use IQ Bot and UiPath. ABBYY is easier to use than these other products.

The initial setup is not difficult. The vendor provides technical documents to assist with deployment. It normally takes a few days to deploy but if there are a lot of configurations, for example with all of the network-related stuff, it takes more time.

For the deployment, between three and five people are enough. The maintenance can be handled by two people.

My advice for anybody who is considering this product is to start with a PoC. They need to see whether it's feasible and can handle the documents that they want to capture. Before entering into an agreement to purchase the product, try different samples and different scenarios because the accuracy is different.

I would rate this solution a ten out of ten.