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.

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.

We use ABBYY FlexiCapture to extract data from invoices and purchase orders.

It is saving a lot of time, especially for the users who are doing the same tasks on a regular basis. Previously, they were manually copy-pasting from the PDF files to the legacy systems. By using FlexiCapture's integration with UiPath, we are able to automate a lot of complex processes and save time.

We are able to extract details from a PDF and put them into a CSV. It is able to extract the details that we are looking for. We have the Machine Learning feature to extract the data with respect to the position of the field.

Most of the features are already included in ABBYY FlexiCapture. It is 95% good. It only needs an improvement of 5%. 

Occasionally, we found the Machine Learning feature to be not working as per our expectations. Sometimes, it also failed to extract details from a PDF. It would be great if training batches work with 100% accuracy. I don't see any other major concerns with ABBYY FlexiCapture.

In the future release, in the admin console, they can include information about the number of pages that we have consumed and the number of pages that are remaining. Currently, we are not able to see how many pages we have consumed. We haven't received any feedback from ABBYY on how many pages we've consumed for each template or the whole process. If they can include that in the future release, it would be great because we don't know how many pages we may require on a yearly basis.

It is expensive.

We have been using this solution for about two years.

We haven't seen many crashing issues so far.

The scaling process is of medium complexity. My company is a sales-based company, and we get millions of purchase orders from different vendors. So, we use ABBYY FlexiCapture a lot. We have plans to increase its usage in different departments.

Once in a while, when we have any questions, we reach out to ABBYY. They were okay, and they were able to help me.

We haven't used any other tools. We started with ABBYY FlexiCapture.

Its deployment process is of medium complexity. Currently, only one person from the India team or the Austria team is deploying the packages for ABBYY FlexiCapture. I have been deploying UiPath packages for a very long time, and the process for ABBYY FlexiCapture is a little bit different as compared to UiPath. ABBYY FlexiCapture is a little bit more complex than UiPath.

It takes 15 to 20 minutes for one template.

We have definitely seen an ROI. It might increase in the future.

It is expensive as compared to UiPath. We pay for the licensing and the page count.

We didn't explore any other OCR tools as of now. We are good with ABBYY FlexiCapture, and I don't think we are going to explore any other tools in the future.

I would strongly recommend using ABBYY FlexiCapture if you have a high number of invoices, purchase orders, or any manual checks, and you want to extract details.

I would rate ABBYY FlexiCapture a nine out of 10.

One use case was known as Manual Order and it was a type of invoice processing. When a customer had or was going to receive invoices from different distribution centers, which all could be accessed in different formats. For example, they could be different templates, be digital, and scanned. There could a wide range of variations. The purpose or the aim of FlexiCapture is to extract the information out of those invoices, such as a certain number of fields, which we need to extract from the invoice and that sent on into the SAP. For the SAP we were using Pega. There is integration between ABBYY FlexiCapture and Pega to solve the whole use case.

The second use case was for claims. For example, if a customer was supported to get a claim from the distribution center but some of the quantity was not being sent to them correctly or the price was not good, they would send those for correction. One claim could have multiple claims in between them that could have a price difference or quantity difference. It is more complex than device processing because it has more variations in the template. It has more business complex routes. On the FlexiCapture, we are extracting the data out of this document. We implemented some of the business tools and we are using Pega to revalidate the data in the SAP to correct it.

Additionally, we have four or five business processes that are already running in production with Blue Prism and ABBYY FlexiCapture.

While using ABBYY FlexiCapture we did not use the generic models that they do have for invoice and purchase orders. For one of the use-cases, the document was exactly the purchase order, but we are not using that generic model. We are creating the model from Scratch. However, if I was to compare ABBYY FlexiCapture with other IA tools, the machine learning and how the extraction is done is far better than competitors. This allows a lot less effort for the development.

The generic models have a lot of areas to improve. In our experience, we are not able to get good results in the generic models. From a developer's point of view, there could be more improvement if the source code is available on a broader scope. It is a low code platform but it requires implementing more complex code to be able to accomplish certain tasks. We are not able to tune the model on a programming level because we do not have the source code to do it. From a business point of view, ABBYY FlexiCapture is one of the best platforms for machine learning. The solution does not have anything related to RPA or robotics, but we can integrate it easily with a Pega or Blue Prism for these features.

ABBYY FlexiCapture has a lot of functionality but it does not have options to implement more machine learning business rules. It does not have the option to write the logic to implement other options according to the business. Most people do not like to choose ABBYY because of the lack of those functions, such as reading email or saving them to excel, they use other tools for these activities. If ABBYY had these functionalities more people would use it and it would be more useful.

I have been using the solution for approximately a year and a half.

The solution is stable. However, new versions come out frequently and our customers do not have a choice whether they are going to update since it is on the cloud. They still have to make sure it does not have any negative effect on their exciting solution in a bad way. 

There are times it takes a lot of time when we submit a document to FlexiCapture in between getting the results When this happens we raise a ticket to the ABBYY team and it gets released very quickly.

We have approximately four people in my organization using the solution. It is not the majority of the teams. We had five customers for which we were working with this solution, we had a trial contract with another tool, but due to some reason, the customer wanted to use FlexiCapture. I am one of those four people who have this experience in the ABBYY FlexiCapture.

We have plans to increase the usage of the solution.

My experience with customer service has been really good. I have not contacted them directly, but they do have forums. When we initially started, I had posted some technical questions and I did get a response from them.

ABBYY FlexiCapture is not very old which causes a limited knowledge base for assistance, this is possible because there are not a lot of people using it. There is documentation from the ABBYY FlexiCapture which is okay. However, if you start working with the solution, the practical knowledge is better than what you will find in the documentation.

Before using FlexiCapture we were previously using WorkFusion. It is an RPA or IA tool that has both the RPA plus machine learning. PNG decided to reconstruct those use cases and some others with the ABBYY FlexiCapture.

We did the installation for our own company, it is not very difficult because the customer service is good and are you will be given a particular team who will be responsible for the deployment.

We used the deployment team from ABBYY FlexiCapture for the implementation. The time it took was approximately two months including all customization and licensing.

Most of our customers have purchased an annual license and if you have multiple developers from other companies, you can assign the license on a monthly basis to developers. 

We have licenses for ABBYY FlexiCapture for our company.

We did evaluate other options with our customers before choosing ABBYY FlexiCapture.

My advice when doing the implementation is to do the practice mode rather than only going through the certification and documentation. It is better to implement the model, instead of using the generic model.

I would recommend this solution to others.

I rate ABBYY FlexiCapture an eight out of ten.

We are a logistics company, and, due to the fact that a lot of documents get generated on a daily basis, documents need to be processed and data extracted. That's our primary use case for this solution. We use it for a lot of data extraction.

The fact that IBM Datacap uses ABBYY's core engine for OCR, is quite useful for us. It makes them one of the key players as far as OCR extraction is concerned. 

The fact that they've packaged it very well in the sense that you have these field extraction batches which enable you to auto claim the documents, and you have these templates which are structurally laid out, which enables you to mark a specific zone from which data can be extracted. 

It saves us a lot of manual work.

The automation on offer is good.

Technical support, for the most part, is helpful.

A lot of things could be improved, especially if you look at the number of support tickets that we have created. Looking at those would indicate the things that can be improved. 

For example, more often than not, we are forced to rely on template creation in order to bring the accuracy of extraction to 100%. 

Even though the training works, it's not as good as it is made out to be. In our case, we've got thousands of suppliers and it is just not humanly possible for us to keep creating templates for each one of these suppliers. What we would need is an out-of-the-box extraction to be even more accurate, or for the training to improve in such a way that just the training should be able to give us a reasonable amount of accuracy. I know that 100% is too high a limit to aim at, however, even if we get close to 85% to 90% margin, it would be much better. Something that could do that out of the box would solve most of the problems.

ABBYY introduced a reporting data warehouse last December, however, that reporting data warehouse has its own fair share of problems. Something like accuracy and completeness of out-of-the-box recognition is something that should be available as part of your default reports in the tool itself. Right now, that is missing. 

ABBYY provides a document definition for an invoice, however, that invoice is a supplier invoice. In our organization, we deal with commercial invoices most of the time. The problem there is that supplier invoices. If you put them into the system, it gives you around 80% to 85% accuracy out of the box. However, with commercial invoices, you only get around 60% accuracy out of the box.

Based on the input that we have provided, ABBYY is now working on including the commercial invoices as well as part of that default invoice document definition. They are working on that as well. There are a lot of minor things that have come up. For example, when you create a template, ABBYY claims that you can export the default template that is generated as part of the training, and then make changes to that and then import it back. What we found was that the concept applies only to certain things. The training of the line items cannot be exported as a template. They said it's to do with the way machine learning was being applied and all that. However, these are all things which kind of increase the development time.

I have a couple of years' experience with this solution. I've been working with it since about 2019.

The performance can improve. Even though we have tried out the solution's provider, ABBYY, in terms of having more processing stations, all still boils down to the fact of how your application is configured. For example, in our case, we have about five processing stations in production. When we started off, it took almost 60 seconds to process one page because of the complex nature of our application. We had around five document types, and each type has to be classified based on a set of keywords, and then you had to apply the document definitions on top of them. Then it goes through this concept of the generic layout and the additional layout and so forth. Almost every page used to take about 60 seconds on average. Then we made a lot of tweaks to the application and then we brought it down to around 22 seconds per page.

That said, even then, when you're talking about the space that we are in, the domain that we are working in, sometimes a 100-page document has to be processed within around 30 minutes. If you take a 100-page document, only for processing that itself, it takes almost close to an hour. Then, what happens is that additional stages like verification, et cetera, by the time the data is exported and uploaded into the target system, it's taken too long.

With the normal ABBYY support, you go to support.abby.com and you raise tickets. The support is almost immediate. There are constant responses that come to you. However, what I've also seen is that there are a lot of complex problems for which we have not gotten the solution we need. While the response has been great, if you asked me whether all the queries for the problems that we raised have been solved, the answer is no. On the other hand, we also have a chance to interact with the ABBYY professional services team directly due to the contract that has been established with our organization. They are a wonderful bunch of people and there's this personal rapport that we have with them. We get in touch with them on a weekly basis and our query is resolved.

In our organization, it is the IT team that takes care of the installation. I do not have much information about the process and I wasn't really a part of it. 

We're just a customer and an end-user.

I'd advise users that, when you start off with your first project on FlexiCapture, choose a project which has at least something which can accommodate a very high pattern. For example, if you're going to go for a use case wherein documents have to be processed within the next 30 minutes, you're going to face a lot of problems. ABBYY is a wonderful tool, however, it has got its own set of constraints. It's very important to understand the constraints of the tool.

The strength of the ABBYY FlexiCapture license is the OCR engine. However, if you're extracting it to process millions of documents within a very small amount of time, that is not going to happen. 

It's very, very important for the final operators who are going to use the tool to understand what OCR is all about. The problems that we face are not technical at all. It is about trying to convince people, people who have been doing operations manually to change their processes. If you have a situation where people are looking at documents, looking at the data, and entering it into a system, and then come and tell them that the solution will extract that information automatically and they just have to verify that information, they'll need to change their approach. 

It's very important to get the business team who will be doing the verification into a meeting, in order to help them understand what OCR is, and also its limitations. 

You will need to specify the stock field and the zones. OCR is able to learn on its own and understand how to extract data from it. However, there are certain things that you will have to teach people. You have to tell them the fact that a page is converted into black and white, and that the gray areas either cannot be black or white as certain characters that are being recognized may turn out to be something else. OCR tells you the level of confidence based on what gets extracted. All this has to be translated to the business team so that they understand the tool and its limitations. If you do this, you can ensure the success of the project.

Therefore, while ABBYY, as a tool, is great, there is a lot of work that needs to be done before you start implementing it.

I'd rate the solution overall at a nine out of ten. We have had to initiate a lot of fixes, however, overall, it's quite good.

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.

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 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.

I work with document automation where we have to create settings to understand if all the documents are there to be processed or if there is something missing. I gather the data from these documents, making them available for any automation like UiPath.

I like that it has the capability of processing a high volume of documents with great accuracy, and also the possibility of creating layers with APIs and robotic process automation. We can use these layers to connect and create an automation for the data that are available from the paper source or document source.

They have a product called Mobile Web Capture that connects with ABBYY FlexiCapture and it is a separate feature. I think they should embed Mobile Web Capture as a standard feature.

I have been using ABBYY Flexi Capture for the past ten years.

ABBYY FlexiCapture is stable.

There is no other IDP solution able to scale as ABBYY FlexiCapture. They don't only have the OCR and the ability to contextualize it, but the ability to scale and process million of pages, I have not seen anything like it in the market.

When you reach technical support for some idea of writitng simple scripts, they want you to speak to professional services. There are two parts to technical support. One is the professional service team where you are charged every time you try to reach them. And the other is the support. The support should be able to give the most basic information to the customers like simple scripts. They are not allowed to provide simple funciotnalities scripts. You have to contact the professional sales team. Many of these small problems can be solved quickly by technical support. 

Professional Services know everything you need about the tool.

Positive

Setup is easy. There are some specific jobs that need some scripts to call the functionalities of this solution. You do not have a map to follow how-to read some specific functionalities. But most of our processes, ninety-five percent of them, we were able to process and create from the tool itself, the user interface, and by adding some simple scripts.

You can trust ABBYY FlexiCapture. It is a smart solution and has many functionalities. I can recommend instead other low-cost and no-cost solutions. 

You can not compare ABBYY FlexiCapture with anything else on the market. On a scale of one to ten, I rate ABBYY FlexiCapture a ten.