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 need to understand ABBYY Vantage to add some projects and push them to our customers.

I have worked on many different OCR extraction tools, like document understanding, which uses ML technology. Compared to other tools, ABBYY Vantage is better because it's very user-friendly. It has a wide variety where we can manipulate or code the document as per our specifications, like OCR or many more specifications.

Since we are using a trial version, we don't have administration access to create a tenant to integrate my OCR series with Postman. Right now, we are doing one POC, and to complete that POC, we need that access because it's a requirement.

I have been using ABBYY Vantage for a couple of months.

In my team, three to four people are using ABBYY Vantage.

Our experience with our FlexiCapture was good. In FlexiCapture, you have to create templates because it does not use ML or AI technology. We learned that ABBYY Vantage uses ML technology, and we want to explore it.

ABBYY Vantage's initial setup is very beautiful. We didn't face any hurdles during the setup.

The solution is deployed on ABBYY cloud in our organization.

Overall, I rate ABBYY Vantage an eight out of ten.

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.

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 use ABBYY Vantage for invoicing problems and for unstructured forms and documents.
ABBYY is an older tool that specializes in data extraction, OCR, ICR, and other recognitions. The company or the department just has to decide the use case. 

I like the flexibility of the layout. For example, for the documents that we're using, this is the main feature that is very useful and makes it flexible for extraction.

It could be more intuitive. It's huge and has many options, and that makes it difficult. You have to go to Google and search for documents and videos to try and understand how it works. Some tools or processes or some parts of the process should be intuitive to make it easier for the developers.

Many of these tools are divided into many parts. You have to buy different parts, and you have to know the difference between features. Sometimes it's difficult for the developer because you don't have the old information available in cleartext. These things need extra plugins to try and collect the different parts in different ways. 

It would also help if they improved the engine for ICR. I know that people improved this tool, but it's not expanded right now. We need to use an additional plugin to design or code some parts using a toolkit. It's not properly included in the standard package. 

I have been using ABBYY Vantage for about seven months.

ABBYY Vantage is very stable. I don't have any concerns about it.

I know that scalability is available, but I don't have a big project reference right now. We have about 50 people using it right now.

In the last three or four projects, we used ABBYY instead of IQ Bot. I know that IQ Bot probably works with a simple OCR extraction without complicated decisions or business rules. If we have more complexity when it comes to the business rules, for example, the quality of the images, or apply different filters over the images and do other things with ABBYY, we use ABBYY instead of the IQ Bot. But IQ Bot is more flexible.

It's not easy to set up this solution. But once the installation is done, you don't have to configure anything. The main part is related to the server and the infrastructure people handle that.

For simple types of documents, medium-sized projects with 25 types of unstructured documents, with seven or eight field sections, it probably takes one week to deploy. This includes bulk extractions where the information is put into the different outputs. We mainly use this in our Excel template.

On a scale from one to ten, I would give ABBYY Vantage an eight.

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.

We are using this solution for PDF reading capabilities for some invoices. We also utilize it to read DW4 forms.

There are many others to compare with such as Google and Microsoft, but we haven't seen any specific distinction that stood out with Abbyy.

They were the most used, which is the reason we chose them.

Abbyy is really good in terms of reading OCR.

There has always been a challenge with Word and PDF reading capabilities. This is an area that needs improvement.

There are certain controls like radio buttons and checkboxes that when reading PDFs, really doesn't go well with the RPA.

We work with Abbyy and UiPath. Abbyy provides its API to be utilized with UiPath, and that is how we use it.

We have been working with Abbyy for at least one year. We have one or two projects that we have worked on with Abbyy.

Abbyy is a stable solution.

It's not really scalable. When it comes to PDF reading, we are very specific to that particular document and that template with some of the verbiage.

I have not seen it to be more scalable with any OCR capabilities.

I have not contacted technical support.

Previously, we didn't try any other solutions. We have to have that screen gripping capabilities and OCR. UiPath with Abbyy was the right choice.

The initial setup is straightforward.

We did not go with the licensed version of this solution.

It's more trial and error, but Abbyy is still really good in terms of OCR. If you have a consistent use case, then I think that Abbyy is the right fit.

I would rate Abbyy Vantage an eight out of ten.

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.