ABBYY Vantage Reviews

I specialize in RPA. So, I started learning FlexiCapture to include it in the automation process. Instead of users having to manually enter information into a database or something like that, they can just load their digital documents to a certain location for ABBYY to decipher them, and then the bot and the automation could just continue along with that.

For one of the projects, it was deployed on a public cloud. For the other project, it was on-premise.

The whole idea of designing your own templates is pretty much the bread and butter of the product, but that's really the best part because you can design flexible templates.

There is also the AI part. They have their machine learning models that are pre-setup for invoices and things like that, which is also very handy. It is a really good feature.

There is always room for improvement in any product. Some of the configurations for the machine learning models for invoice reading are fairly complicated. There is so much customization that is possible with that sort of thing, so it makes sense that there are a lot of options, but some of the more important ones can be a little better streamlined or more upfront. Currently, machine learning models are a little bit difficult to configure satisfactorily.

There are a lot of solutions for different things, and they are all kind of headed in the same direction where they all do everything. I know that ABBYY wants to try and do a little more RPA. Solutions like UiPath, for example, want to eat ABBYY's lunch too. They all are trying to make an all-in-one solution for all possible automation needs. In that sense, ABBYY as a standalone product could use some more automation features. They are not there yet.

Its integrations with strictly RPA products, such as UiPath, Blue Prism, and other solutions, work when they work, but when they don't, it is a kind of a pain. Those integrations could use a little bit more support.

I have run into issues with the connectors that they developed for UiPath. I had one issue with that. It didn't want to do what we wanted. We had to change how it worked a little bit as far as the automation goes. It wasn't a huge issue, but it would have been much more convenient if had worked the way it was designed to. Otherwise, in terms of the stability of the project itself, I've never seen it crash.

Its performance is usually dependent on the hardware it is installed upon. That's not really an issue with the software itself. Its accuracy is good. It is probably one of the better optical character recognition packages that I've seen, but it still is not perfect because none of them are. It is the nature of the software, but it is pretty good. As long as the clients can provide reasonably readable documents, then it has got no problems as far as I'm concerned.

It is actually relatively simple to increase the scale of the infrastructure that you install. When I was dealing with it, the licensing structure that they had was relatively affordable as compared to other solutions. The bigger the scale, the more affordable it is. These things change all the time, so I don't know if it is still current.

The projects I've been on were proof of concept and then we just rolled them into production on the first stage. It was pretty small scale, but they had plans to go large scale. One of the projects actually from my end was still just the small-scale stuff, but other departments in the company had already procured a rather large-scale ABBYY license, and it was in production. I had nothing to do with that section, but the company as a whole had a pretty large infrastructure for ABBYY itself. They were dealing with millions of pages per month or so.

For proof of concept, there were probably about four or five test users. For the second one that I worked on, it was planned to go to production from the get-go. It started out on small scale again with probably four or five users. So far, the scale is 20.

I have used tech support, and they've been extremely helpful. There was a part of the solution I couldn't figure out myself. So, I enlisted their help, and they walked me through how to do what I needed to do. They set up a time within the next day or so, and they spent an hour with me. We figured it all out, and it was good. There is always room for improvement. Other instances haven't been as perfect as that, but that was certainly a shining example.

When we did the first project, which was just the proof of concept that I was part of, they had older software from 20 years ago. There wasn't support for it anymore or something like that. They were looking for something that could handle a larger scale. So, they switched. We suggested them ABBYY, and that's where they went.

For the clients for whom I worked with ABBYY, we would arrange for them to provide an environment. We would go into the environment and install ABBYY servers. If required, we'd also walk them through installing the clients on their machines, but generally, what we've been doing so far has been the support to an RPA project. They didn't really need to use ABBYY clients. It has all been pretty much backend stuff. We would install the infrastructure, set up the automation and its interactions with ABBYY, and then run tests in UAT. Once everything is ready to go, we do the final production deployment. After that, we have a week or two of maintenance before it gets off to a specialized maintenance team.

It takes about a week for the installation, but the development planning usually takes months or longer. At the time, I was pretty much doing it myself with support from a business analyst. The deployment of the infrastructure, the development of the automation and the ABBYY components, and then running the testing was usually just a one-man job with support from a couple of other people, such as a project manager.

Once we have developed the solution, there is a testing period where we just put it in their hands, and they throw all sorts of scenarios at it. We fix the bugs as it goes along. ABBYY does have a learning function where it can pick up on these changes when things arise, as long as the users are able and familiar with how to train it, which we show them how to do. So, maintainability is pretty good as far as I'm concerned. If there is something completely wrong and it is not reading anything right, then we have to go in and edit the templates, etc. Generally, if we set it up right and they learn how to teach it right, it is pretty stable.

The client got an ROI in reducing the number of hours that the users have to spend on a given task. Again, my solutions are not purely ABBYY, so it is hard to say how much of the benefit the ABBYY section alone was. Usually, ABBYY is involved because the users are spending a lot of time entering the information they see on a piece of paper into the system, whereas ABBYY can read it all in seconds. So, there is certainly great time savings. It then becomes a matter of comparing the cost of installation and the cost of developing the solution, licensing, and everything else with the costs and the time of those users. Even if it is pretty close to equal, they usually go for it because it is a much better environment for the users to work in and is less tedium. So, they have more employee satisfaction.

It is more on the reasonable side as compared to the competition that I am aware of. I'm not an expert on pricing schemes for all sorts of things, but when we offer them a solution, we like to say we're agnostic. So, we offer more than one solution when possible. Amongst the ones that we've offered, ABBYY usually is the more reasonable solution on a big scale. On a small scale, they're all pretty similar.

As far as I understand, you pay a license for a number of pages, and that's pretty much it. It has just the rate per page, and it decreases as you scale.

I've never done a strictly ABBYY solution. My solutions have all been ABBYY plus UiPath or something like that. After a solution has been deployed, there have always been bug fixes. Other than that, clients have always been extremely happy with this solution. They're excited they have to do less work.

If you have the right use case, it is definitely worth it. As a solution, I would rate ABBYY a nine out of 10. It is a solid solution, and support is there. It is good.

We use this solution for supplier invoice processing work. We started using it because we needed a solution for supplier invoice automation.

The solution is deployed on-premises.

There are about 20 end users.

It's easy to use.

I would like to see a machine learning model to make the solution more intelligent.

There are no issues with stability.

Initial setup is easy.

It costs 5,000 Euro per year for one license. There are almost 500,000 pages available, so I think the price is good for what we have. It's worth the money.

I would rate this solution as eight out of ten. 

There are some technical constraints, but if you can address those, then the solution is good to use.

There are competitors, so I would like the ability to explore more options.

Our primary use case is for processing documents and extracting data from them - using the OCR capabilities. Documents include invoices, purchase orders, things like that. I'm an IT solution manager and we are customers of ABBYY. 

We've had two main benefits from ABBYY. Screening documents is a time-consuming activity, which has no real added value by itself so the solution saves the company a lot of time. The second benefit relates to the energy involved in employees going through documents. It's tiring work and mistakes creep in. We now have an increased level of accuracy by using the solution. 

Clearly the OCR capability of ABBYY is the top feature in our context. We can rely on the ABBYY knowledge and experience to extract data and recognize texts in different situations and especially in different languages, particularly English and Chinese. 

The main thing they need to work on is simplification of the solution, particularly use of the search tool. Configuring is quite complex and it's not very user friendly, particularly the user interface if you're trying to figure it out by yourself and create some configurations for processing documents. I know they are working on it. We used the new ideas on page projects they recently released and that has been great for enabling non-IT proficient users to start configuring and using it.

The stability of the solution is good. 

It's quite easy to scale. We currently have around 10 users, mainly IT professionals but also other users. I'm responsible for managing and maintaining the solution with a support team, and we generally carry out an annual upgrade, rather than an upgrade whenever ABBYY releases a new version. We use it every day and hope to increase usage as it would help more and more people at the company. 

The technical support was good. 

The initial setup was quite simple, perhaps slightly more complicated because it's on premise so it includes taking care of the architecture. I managed the project and we built a platform in a few months. A consultant worked with me and another solution architect during the initial period. The total setup took between two to three months. 

We haven't measured ROI but definitely as mentioned, there are many time-saving benefits.

We are on-prem so we're just paying the license fee. They have a clear pricing model. You pay extra for the training content. 

The main difficulty, as I mentioned, is to get people started on it if they're not specifically trained on ABBYY or not an IT professional. It's initially quite difficult and more so now that the learning material is not freely accessible online. Other than that, it's just a matter of following the documentation and using it. 

I rate the solution nine out of 10. 

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.

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.

Our primary use case for this solution is invoice processing. We have many different invoices on different maps so we use it as a tool to classify those documents and get the information that we enter into the SAP systems.

ABBYY Vantage is easy to use and allows us to run through documents and extract information.

The overall integration could be better. For example, the modelling, classification and handwritten information are not great. From my perspective, Hyperscience does the handwritten processes a lot better than ABBYY Vantage. Additionally, the overall end-to-end processes experience can also be improved in terms of how information is fed to ABBYY. By having the overall process flow built with ABBYY Vantage, it can hold up as an independent tool.

We have been using this solution for approximately one year. We deploy this solution on cloud and are currently using the latest version.

The solution is stable.

The solution is scalable. We can add new users without any issues. However, we do not need to add users often because the primary point is to reduce the number of users. Additionally, we are consultants, so we build and deploy solutions for our clients. Currently, we have five people involved in this process who are using and leveraging this product.

We have not had to contact customer service and support yet.

The initial setup was straightforward, and deployment was very quick as we used the ABBYY cloud setup that was provided. We didn't have to separate the installation and setup process. It was primarily structured on passing on documents and getting the information back.

The ROI is visible when there is enough volume of documents available. For example, if there are two documents a week, there would not be a good ROI, but if we have many invoices from large companies, there will be a high ROI.

I cannot give a specific figure for pricing because it is unique to each client. We negotiate at different times for different clients, depending on the size of their organization. However, I believe the price is a bundled package.

ABBYY Vantage is a good tool. In this space that we work in, Hyperscience and ABBYY Vantage are two essential tools that we work with. Others include Bioscript and many more, but these two are the primary tools because of their maturity and capability. Therefore, these are our tools of choice.

I rate this solution an eight out of ten. The solution is good and stable, but its overall integration could be improved. Our advice to customers will be to understand their business cases because it is attached to document processing, so there is a bundled cost with this product. It is necessary to understand the volumes and the documents being worked with. Understanding the volume and quality of documents that are being processed is necessary to ensure success.

Most of the use cases were invoice-related for sectors such as supply chain and finance. Sometimes, they were a little bit related to HR and payroll. We also had use cases for passports and IDs and documents related to HR and onboarding. 

I've also worked on a larger scale project for importing and exporting in Dubai. It had invoices, country of origin statements, and everything else that comes through with an import check event.

It was on-premise on all the projects I've worked on. I've never worked on it with the cloud. We would connect it to an RPA tool, such as UiPath or Automation Anywhere. So, it was a part of a larger solution.

Usually, it does the reading task for a document, such as an invoice, and that is a very mundane task for an employee when they have other stuff to do. It pretty much takes that off their plate. It gives them time to focus on bigger picture things or even look at the process as a whole.

It lessens the errors that can happen. An employee can be tired and read a number wrong, but if it is a computer-generated invoice, it is going to be of the best quality. If it is computer-generated, it will come out with zero error every time, and it will do it a lot faster than a person. It will extract the information and continue doing whatever you need to.

Verification station is a really good feature. It allows part-owners to be able to take a look at what comes out of the tool after a document, such as an invoice, is run through ABBYY. It also allows them to update it if there are any mistakes. So, it kind of gives them a little more control over what goes through the system and lessens the errors.

They say that they have invoice training or document training where if you put in a certain number of documents of the same type and you fix it once, twice, or a few times, it'll automatically be able to read the same document perfectly without you having to create a layout for it to follow. That has never worked properly for any project, so I just stopped recommending it completely. We spent time trying to test and getting a bunch of invoices to test it with, and in the end, it just didn't do what it needed to. If they fix that or if they can improve on that, that would be great. It will save a lot of time for a lot of people, and it will allow people with less experience with ABBYY to be able to use it.

The way FlexiLayout Studio and Project Station read a document, such as an invoice, is a little bit different. So, if you set it up in FlexiLayout Studio and create a template, it will read it just fine, but when you import it into Project Studio, sometimes, it will not read it the same way. The way both of them read is a little bit different. So, you have to go back, and you have to change it again, and it is trial and error until you get it right.

Its price should be a little lower. It is a lot higher than the competition.

The last project I worked on was in February of this year.

It is pretty stable. If I remember correctly, it has only crashed once, and I don't think it was a system issue. It was just some weird, bizarre glitch that happened at the time. Once the projects were live and running on the client system, we've never had any issues that I can think of.

Its scalability is good, but it also depends on how you're working on a project from the beginning. I like to put everything together, and I usually do think of it in a way that if we were going to add invoices in the future, it won't be a hassle. It is pretty scalable. I can have many different invoices on the same project. I can have a project going on the client-side for years and then just add to it if needed.

Usually, we have some type of business analyst whose main role is doing something that we call an OCR study. The business analyst would be reading the invoices and just telling us what the client wants to extract from them. On their end, they also make sure that the quality of the invoices is good for ABBYY. It can't be something that is written over and damaged or put in someone's pocket for a day and then in the scanner. It won't give us perfect results.

There would also be a developer who would take a look at the OCR study fed by the analyst and then think of how to develop each template. If you don't understand how you're going to design the whole project, you might need someone. Because we're putting it into another automation tool as well, after we've sort of developed everything, depending on the scale of the project, we may have somebody dedicated to just testing the submission before sending it over to the client.

We have plans to use it, and of course, it is a good product, but we work with what the client wants. So, if a client doesn't want it, then they're not going to be using it. It is not like a solution for every case in my line of work. It depends on if the client actually has a bunch of invoices or a bunch of documents that they need to read quickly. If that's the case, then we definitely recommend it every time. We recommend it over any other OCR solution on the market. ABBYY in itself isn't a perfect tool, but ABBYY is pretty good. It is not the best on the market at the moment.

I've been in contact with several people from ABBYY and their support staff. They're very helpful.

We were using the default OCR tool that came with the UiPath software. It is integrated with Google OCR and Microsoft OCR, which are okay for smaller, simpler documents, but they're not going to give you the control that you can have with ABBYY. The engine itself isn't as good.

ABBYY is definitely more mature. It's all-around better. If I pass through an invoice PDF, the percentage of getting everything right with ABBYY is higher than it is with the others. It is definitely a lot more expensive, but I can tailor what I need to each document, and I have multi-lingual support. I can pretty much just get behind what ABBYY is trying to read and make sure it is reading everything correctly, whereas, with Google OCR or Microsoft OCR, I just worked with whatever came out, and I had no control over it.

It depends. There are two types of installations. There is the standalone installation, and there is the server installation. The standalone one is very simple. It is just a normal install. You just push the license through the command prompt, and that's pretty much it. The other one is just going to take a little while longer depending on how you're going to deploy the solution for FlexiCapture on the system. From my experience, if someone is going to install it for the first time, they might need just a bit of help, but it is not that complex.

The duration depends on the solution. It depends on what a customer wants and how many invoices you're going to be preparing in ABBYY, but usually, we say that a good rule of thumb is about one to two hours for a normal invoice. If it has a complex table, then it may take three to four hours for an invoice. So, the time taken would depend on what the client actually wants. If we have five invoices for which the customer wants to use ABBYY, they can be created in a day or two days. We'll give half a day for installation, which also depends on how many servers we're going to be using. We'll give like another half a day for testing and pushing the project. So, maybe two days for five invoices is fair.

In terms of the implementation strategy, first, I would pretty much gather all the invoices the customer needs, and usually, if they are in the same sector and in the same business, they'll be very similar. If we have 50 invoices, I would rather waste an hour or two figuring out the similar invoices and then creating just 10 templates instead of 50. After that, I'd start with identifying the means of the values that I want to extract and figure those out in all of those 50 invoices, especially the ones that are going to be in the same template. Then, I'd get to work on those templates. Once I finish those, I'd push them to the project so that I can test them there, and if everything is working fine in the project, then I'd just give the solution to the customer.

We have definitely seen an ROI. Most of the ROI is related to time because it'll take a while for a human to go through a full process. If we assume that we have a process that takes a human or an employee an hour, that would be eight hours in a day. OCR would really cut that time by a lot. I'm also talking about adding automation to it, so I'm pretty much a little biased here. We can cut that time down by a lot, and once we do that, then we just have the whole process automated. It is not being done by an employee anymore, so that employee is free to do something else. So, you're saving time, money, and brainpower.

Its price should be a little lower. It is a lot higher than the competition, and if they just break the gap a little, then more people might jump onto their product. Their price is definitely a deterrent in the few cases that I remember.

They have monthly and yearly options, and if you want, they also have per project and per page options. We partnered with them for a few projects, and they provided us with a trial license that we use on our end for using the system, employing it, and developing the solution. On the client's end, they will charge them for the license because that's ongoing. They also get support and everything else.

They do charge extra for different types of installation. They have the standalone, which is pretty straightforward and a lot cheaper than the server installation. Server installation gives you a lot more, and it gives you control over the environment. They have a web management studio for the whole thing. You can create users and give people different permissions and track the progress of everything, so that's going to be a lot more expensive. I remember that one client was complaining about having to pay extra for having the Arabic language added to the system. I think they made all the languages free after that, but I'm not 100% sure.

I would advise first looking at what you're trying to extract from the documents that you have. If they are simple enough and are being extracted properly through a cheaper or a free OCR tool, then just use that. It is not going to be worth the price. If you have lots of invoices and some of them get very complex, and you'd rather have the control over making sure everything is fine, and you have no room for error, then it would be better to invest in ABBYY.

The biggest lesson that I have learned from using this solution is that when creating templates with different documents, make sure that you're using different identifiers for those documents. That's because, in the beginning, you might think that it would automatically know the difference between, let's say, an Amazon invoice and a Walmart invoice, but it won't unless you tell it. So, you have to make sure that those files are unique. You also have to make sure that what you've created fits perfectly for that invoice. If you leave a little bit of leeway, it is possible that something else will be picked up that you don't want, and then it will just ruin the rest of the process. It is no fault of the OCR. You just didn't restrict it properly.

I would rate ABBYY FlexiCapture an eight out of 10. It is not perfect, but it is the best I've used.

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.