Try our new research platform with insights from 80,000+ expert users
reviewer2133033 - PeerSpot reviewer
Lead of ABBY Implementation Team at a tech services company with 201-500 employees
Real User
Top 20
Has a good accuracy rate compared to other tools
Pros and Cons
  • "Integration is very easy. There are lots of connectors."
  • "I would like better language support for Hebrew and Arabic. They're still working on that, and we might get an update by the end of this year. There is currently no support for those two languages because they write from the right to the left side. It would be great if they could add this as soon as possible because we have customers from the Middle East and Israel."

What is our primary use case?

We use Vantage for invoices and purchase orders. We have around eight members using it. It's good for the document types we use. I don't think we use many of the available skills. We use the invoices and purchase orders because that's what we need for our in-house product. We might use it in the future for remittances, 

What is most valuable?

The key fields that must be captured from a particular financial document are validated. This usually gives us 80-85 percent accuracy, which is good compared to other OCR tools. 

They're constantly adding patches that fix all those issues. They make improvements on the back end. ABBYY has made many enhancements recently. The address-conversion features are critical. It automatically converts the city and state name into the ZIP code.  That's a crucial feature we wanted that they've implemented.

Integration is very easy. There are lots of connectors. 

What needs improvement?

I would like better language support for Hebrew and Arabic. They're still working on that, and we might get an update by the end of this year. There is currently no support for those two languages because they write from the right to the left side. It would be great if they could add this as soon as possible because we have customers from the Middle East and Israel. 

We might need more machine learning or cluster things for ABBYY to learn from that and improve accuracy. There's a difference when you go into the invoices. If you have one template, we need one sample to clean it, but a purchase order may need a minimum of five samples. That's something I've noticed, but they might need to improve the machine learning. Generally, ABBYY's accuracy is better than other tools.

For how long have I used the solution?

I've been working with ABBYY Vantage for nearly four years.

Buyer's Guide
ABBYY Vantage
November 2024
Learn what your peers think about ABBYY Vantage. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.

What do I think about the stability of the solution?

Vantage performs much faster than other OCR tools.

What do I think about the scalability of the solution?

Vantage is scalable. We can integrate it with AI, ChatGPT, and RP tools. They have connectors. 

How are customer service and support?

I rate ABBYY support nine out of 10. We reach out to them when we have issues that we cannot find solutions to on the community portal. They help us with the code and are always willing to hop on a call if needed.

How would you rate customer service and support?

Positive

How was the initial setup?

Deploying Vantage is simple once we have access. To integrate it with our product, we only need to add the user IDs and passwords. We also need to write some code based on our requirements. It isn't very complicated. We previously used ABBYY FlexiCapture, but today, most of our clients use Vantage, so we use the latest cloud version of ABBYY Vantage.

ABBYY is continuously updating things, but we retain backups for 14 days in case anything happens, so it doesn't affect our end-to-end automation. Generally, it doesn't require much maintenance. 

What other advice do I have?

I rate ABBYY Vantage eight out of 10. I would recommend it to others. We have some things we'd like to improve, but they will probably implement these improvements in the near future. 

ABBYY's machine learning requires a lot of training for some skills, but it's not much compared to other OCR tools. You can train a template using three or four samples, but with others, it has to go up to 10. The AI of other OCR tools is not good compared to ABBYY. However, they should add support for Arabic and Hebrew as soon as possible.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
PeerSpot user
Senior Consultant at Inovoo GmbH
Consultant
Very scalable and easy to set up but has a slow response for technical support
Pros and Cons
  • "We have found the solution to be stable so far."
  • "The solution needs more web or cloud-based development."

What is our primary use case?

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.

How has it helped my organization?

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. 

What is most valuable?

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. 

What needs improvement?

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. 

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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. 

How are customer service and technical support?

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.

How was the initial setup?

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

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Buyer's Guide
ABBYY Vantage
November 2024
Learn what your peers think about ABBYY Vantage. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
reviewer1647012 - PeerSpot reviewer
Sr. RPA Applications Engineer at a tech services company with 10,001+ employees
Real User
Saves a lot of time and is suitable for processing a high number of documents and doing away with manual processes
Pros and Cons
  • "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."
  • "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."

What is our primary use case?

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

How has it helped my organization?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

We have been using this solution for about two years.

What do I think about the stability of the solution?

We haven't seen many crashing issues so far.

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

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

Which solution did I use previously and why did I switch?

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

How was the initial setup?

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.

What was our ROI?

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

What's my experience with pricing, setup cost, and licensing?

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

Which other solutions did I evaluate?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Senior Software Engineer at a tech services company with 10,001+ employees
Real User
Effective information extraction, good machine learning capabilities, and stable
Pros and Cons
  • "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"

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

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.

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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.

What about the implementation team?

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

What's my experience with pricing, setup cost, 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.

Which other solutions did I evaluate?

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Mauricio  Dias - PeerSpot reviewer
C Data and Documents For Automation at PRTi Digital
Reseller
Top 20
A powerful and independent platform with good ability to scale for big processes, good accuracy, and good stability
Pros and Cons
  • "The most valuable feature is the ability to scale for big processes. We are able to process 1 million pages a day. Its accuracy is also very nice. It is a good feature that they have. It is an independent platform, which is its biggest advantage as compared to other solutions. It is also very stable and powerful. It is 100% on time."
  • "They should improve the RESTful API side of this solution. Currently, fully RESTful API is not available in the on-prem version, which is really a problem, and we have to work around this limitation. The cloud version already has a fully RESTful API, but the on-prem version doesn't have a fully RESTful API, which is a big mistake. It is easy to solve, but they aren't solving it quicker. They are taking a long time. Nowadays, most people don't go to the interface. They like to use RESTful API."

What is our primary use case?

We use this solution mostly for processing Brazilian servicing invoices and personnel documents and contracts, such as personnel ID cards.

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

How has it helped my organization?

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

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

What is most valuable?

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

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

What needs improvement?

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

For how long have I used the solution?

I have been using this solution for about 20 years.

What do I think about the stability of the solution?

It is very stable and powerful. 

What do I think about the scalability of the solution?

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

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

How are customer service and technical support?

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

How was the initial setup?

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

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

Which other solutions did I evaluate?

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

What other advice do I have?

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

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

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Mauricio  Dias - PeerSpot reviewer
C Data and Documents For Automation at PRTi Digital
Reseller
Top 20
Great accuracy, trustworthy, with easy setup
Pros and Cons
  • "I like that it has the capability of processing a high volume of documents with great accuracy."
  • "I think that technical support should help instead of developing a solution from scratch every time you reach out to them."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

ABBYY FlexiCapture is stable.

What do I think about the scalability of the solution?

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.

How are customer service and support?

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.

How would you rate customer service and support?

Positive

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer:
PeerSpot user
reviewer1548834 - PeerSpot reviewer
Technical Project Manager at a computer software company with 10,001+ employees
Real User
A proven and scalable product, but there are better products in the market in terms of accuracy and ease of implementation
Pros and Cons
  • "The advantage of this tool is that it is a proven product. A lot of other products are quite new in the market."
  • "Initially, it was good, but now, in terms of ease of implementation and accuracy, there are better competitors in the market. What we are seeing in some of the other tools isn't there in ABBYY. They have to improve it to include such features. Otherwise, it will be difficult for them to compete in the market."

What is most valuable?

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

What needs improvement?

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

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

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

For how long have I used the solution?

It has been more than three years.

What do I think about the scalability of the solution?

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

How are customer service and support?

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

What other advice do I have?

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

I would rate it a six out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Jagadeesh J - PeerSpot reviewer
Product Lead at redBus
Reseller
Helpful documentation, good support, and performs well for document extraction tasks
Pros and Cons
  • "The initial setup is not difficult. The vendor provides technical documents to assist with deployment."
  • "The accuracy changes depending on the scenario so you need to test it before committing to this solution."

What is our primary use case?

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

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

What is most valuable?

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

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

What needs improvement?

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

What do I think about the stability of the solution?

The is a stable product.

What do I think about the scalability of the solution?

FlexiCapture is scalable. 

How are customer service and support?

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

Which solution did I use previously and why did I switch?

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

How was the initial setup?

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

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

What other advice do I have?

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

I would rate this solution a ten out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free ABBYY Vantage Report and get advice and tips from experienced pros sharing their opinions.
Updated: November 2024
Buyer's Guide
Download our free ABBYY Vantage Report and get advice and tips from experienced pros sharing their opinions.