ABBYY Vantage Reviews

Our company uses the solution to develop structures for automatically reading customer documents. We produce the document definition for each layup and send data to customers. We have 40-50 developers using the solution in various departments. 

In the future, we will use the solution for automatic classifications of documents. 

The solution responds well to automatic document classifications with a 90% success rate. 

There are sometimes issues with calculations or integrations with the server when running multiple products with different languages. This causes data to not display properly in data fields. 

The system does not always train itself to recognize data properly from system leads. 

A more comprehensive training program should be available because free training books do not provide the level of detail needed. Sometimes, we encounter issues with an automatization but cannot resolve it even though we completed the associated training module. Training for particular scenarios need to be included in modules because integrations can be tricky or complex without these details. 

I have been using the solution for one year. 

The solution is stable. 

The solution is very scalable. 

We had one issue with speed where we could not achieve the minimum time for processing which should have been seconds. Otherwise, the solution is really fast with basic or fixed processing. 

Support does not answer tickets in a timely manner but eventually closes questions. 

For example, I have a few tickets for assistance with DVP, data pages, and working with multiple languages but support has not yet responded adequately to the email inquiries. I would like detailed information and an explanation for whether a shadow case can be used. I cannot authenticate, determine if available onloads would fix captures, or integrate without proper answers. 

Support should respond quickly to production issues. Time zones are an issue in getting responses because support works on Russian time. 

Support should have access to prior tickets to get a cumulative picture of issues a user has experienced. Generally, they do not have details from prior tickets to inform solutions so they base their answers on only the current ticket. Having cumulative knowledge will allow support to better understand a customer's situation and use case. 

I rate support a six out of ten. 

Neutral

The setup can be complex because it takes time to learn all the menu options. Our setup took one or two months because we wanted to ensure it was done properly. We do not use many of the menu options as our use case is rather basic. 

The help page is not very comprehensive or detailed. It uses code that is formal and the world is now more informal so some options might confuse users.

I have not evaluated other options. 

The solution is a good product but there is always room for improvement. I rate the solution a seven out of ten. 

We use ABBYY FlexiCapture to recognize pictures or PDF files and transfer them to Word or Excel.

It's easy to use.

The integration with UiPath is not good.

I would like to see more documentation and guides to help gain more in-depth knowledge of how to use ABBYY FlexiCapture.

I've been working with this solution for about three or four months.

I have had no issues with stability so far.

I chose ABBYY because it had more solutions for intelligence automation, and it looked like I could combine it with other automation solutions. We currently have 20 to 30 users.

I recommend ABBYY FlexiCapture, and on a scale from one to ten with ten being the best, I would rate it at eight.

The most valuable feature of ABBYY FlexiCapture is the ability to create your own template on the fly. You can train and classify, you can work with those different templates without the need to do special programming for it or with minimum programming. Additionally, the solution is supporting the Arabic OCR, both of these combined features are the most important for us in the Egyptian market.

ABBYY FlexiCapture could improve the performance. We are looking for better performance because it can be a lengthy capture process and the accuracy needs to be enhanced when it comes to Arabic.

In the next upgrade, ABBYY FlexiCapture could add invoices for the Arabic or for the Middle East because it's based on European or American standards mainly.

I have been using ABBYY FlexiCapture for approximately four years.

ABBYY FlexiCapture is stable, we did not find any problems.

In our usage, ABBYY FlexiCapture has been scalable enough. We had a cluster-based operation.

I rate the support form ABBYY FlexiCapture a four out of five.

The support could be more responsive.

I have used OpenText previously and overall the solution might work better, but for our use case, ABBYY FlexiCapture has all the features we need that are important, such as Arabic OCR, and is priced well.

The initial setup of ABBYY FlexiCapture is easy.

The price of ABBYY FlexiCapture is better than some competitors, such as OpenText.

I recommend this solution to others.

I rate ABBYY FlexiCapture an eight out of ten.

The solution is used mostly for form extraction, fixed form extraction, text forms, data extraction, OCR, et cetera. We use it for digital document processing.

We run software that does basically business process automation. It's given us a form extraction utility to add. We're utilizing the ATR in the FlexiCapture engine, and in that way, we can use the FlexiCapture engine to process forms. Any forms that contain data, we can extract.

Without that, we would have to use pattern extraction, regular expressions, and things like that. This is a forms processing engine, which allows us to be able to set anchors and OCR values, et cetera. 

The form extractions engine and the FlexiCapture designer are really useful.

The solution is easy to set up.

We have found the solution to be stable so far. 

The product is extremely scalable. 

The UI is okay, however, I remember the scanning and the way that you actually get documents into the system. The FlexiCapture, what they call a process developer, could use some work.

The solution needs more web or cloud-based development. Cloud-based FlexiCapture development would be great.

The on-premise web version doesn't seem to be intuitive or easy to use or install. It's not user-friendly.

Technical support is slow to respond.

The pricing is a bit high and we are looking into other options. 

I've been using the solution for three years now. I've used it for a while. 

The stability is good. It's a reliable solution. There are no bugs or glitches. It doesn't crash or freeze. 

The solution scales very, very well. If a company needs to expand it, it can do so. 

We have about ten users on the solution right now. They are mostly developers and consultants. 

Technical support could be better. once you create a ticket, it takes some time for them to respond, from a partner perspective. You send a ticket to an email address. There's no phone number. You can send it to support@abbyy.com and you have to wait. 

They do have a fairly thorough knowledge base. There are also available videos on YouTube. However, if you're having complex problems, it can take sometimes days for them to respond. If you're running a professional system, that's not going to cut it.

I don't know if they have level levels of support, and we have maybe just a really poor version of the support system. I can imagine that, if you pay for a really high level of support, then, of course, they're available. That said, from our perspective, being a partner developer, we've had problems with the support, for sure. If you pay for Professional Services hours, it would be my assumption that they would respond right away, however.

The initial setup was straightforward and easy. It was not too complex or overly difficult. 

Licensing is paid on a yearly basis. I don't know the exact price of everything, however, I do know that it is expensive from the perspective of our management team. We've also been looking for other solutions.

We are a partner with ABBYY.

I'm using version 12. I believe it is the latest version. I haven't seen any updates as of recently. There could be a version 14 out, however, I'm not sure. We're using the desktop version. 

I would advise those considering the solution to watch the YouTube lessons and pay for Professional Services training and assistance. 

At this point, I would rate the solution at a seven out of ten.

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.

Our primary use case of this solution is for document processing. Whenever I receive an email from a vendor or business it gets processed to the ABBYY server. I've created a layout in FlexiCapture that recognizes the template, extracts the field and puts it into the Excel format. I mainly work with purchase and invoice documents and ABBYY checks the validation conditions of an invoice. I'm the manager RPA developer and we are customers of ABBYY FlexiCapture.

The advantage of the solution is being able to identify and extract the element you need from a document. The template can be customized for this. We can create our own rules to validate some values before exporting the results. 

I would like to see consistency improved. If the same document is uploaded twice, I might get a different outcome the second time. Machine learning needs to be improved. We have some issues with scanned documents that may have a quality less than 300 dpi and the quality isn't high enough for ABBYY to accurately read it, and it therefore requires manual intervention. There is scope for improvement which could include AI modelling and training. If AI is there then it will identify it in a better way. There is a field training option that already has an ML algorithm for it, but it's not much use. Hand-written documents have less than 50% accuracy. 

I've been using this solution for a year and a half. 

We haven't had any issues with stability, I think it's better than other solutions. 

I don't know about scalability because I'm the only user in the company. We deployed in the AWS server and we have a team who control everything. We currently have eight projects related to OCR which are in the pipeline. I have already trained two other guys.

There is a forum for support but not many people are active. We have a license with them so we will usually receive a response within 48 hours. 

The initial setup was okay, the difficulties came later with the poor quality of documents we received. 

We pay an annual license fee, our management team that deals with that. 

I did a POC on all the different OCR tools in terms of the level of accuracy I get from each document. ABBYY and Amazon Textract did quite well, whereas Kofax did not provide as good a result. Textract reads the entire document data and provides raw data output in the string format. With ABBYY, I can add a field into the template and then extract it but in Textract adding a customized field is not possible.

Anyone using this needs to know they won't get 100% accuracy. Human intervention is required depending on the quality of the document. Clearly, if the quality is good, the results will be better. ABBYY has been on the market for over 20 years so they're well supported including all other RPA tools. Competitively, I think ABBYY is better than other OCR tools. 

It's good to test the solution with multiple samples. Once you create a layout, test it with multiple documents and see what you're able to achieve. If I see that 30 out of 100 documents are not processed 100%, I'll retrain it to improve the accuracy level for when the same document comes in next time.

I rate this solution a six out of 10.