Coming October 25: PeerSpot Awards will be announced! Learn more
Buyer's Guide
Intelligent Document Processing (IDP)
September 2022
Get our free report covering ABBYY, Kofax, IBM, and other competitors of OpenText Intelligent Capture. Updated: September 2022.
634,325 professionals have used our research since 2012.

Read reviews of OpenText Intelligent Capture alternatives and competitors

Technical Consultant
Reseller
Top 20
Offers several use cases, has knowledge-based learning, and great technical support
Pros and Cons
  • "Kofax TotalAgility is a single package. They provide you with OCR capabilities, BPM capabilities, and case manager features."
  • "It’s not truly low code yet, as every two or three projects, you will have a situation where you have to go behind the essential things. You will definitely still need to customize."

What is our primary use case?

It is an OCR software that can be used to extract the data from PDFs, add input channels, or PDFs that came from email. You have scans configured so that you can extract the data from the scanned image and fax. There are several input channels. It's all different according to your business and how you will extract that data from your input channel.

What is most valuable?

There are several use cases, from simple to complex workflows, as per the customer requirement. If you are talking about the BPM capabilities, Kofax is clearly a winner in that area. Other software tools have basic OCR. However, if you want to use some complex business processes, then Kofax is excellent as compared to other tools.

Kofax TotalAgility is a single package. They provide you with OCR capabilities, BPM capabilities, and case manager features. Apart from that, now they have RPA and some other tools, which are very clearly integrated with other solutions. They have a very good ecosystem.

If you need invoice processing, it suits account payable systems. Or in medical trial tasks, it can also be used there for the insurance sector and banking. There are several use cases where you can apply Kofax TotalAgility to different domains or areas.

It has knowledge-based learning. For example, if you have implemented accounts payable solutions for your company and you are getting different invoices, every organization has its own format of invoices. Therefore, invoice processing is quite complex. You have to deal with the end number of vendors; every vendor has their end number of templates defined for that invoice. It can process these easily.

We divided it into three categories. One invoice is very basic, and we can send it in a fixed form. Second, when you structure it, some data might be changed. However, it is still a fixed form. Then there is a third, unstructured, and you don't know where the data will appear. For the same supplier, sometimes you get the data from the top date, invoice number, or maybe on the bottom. However, in any case, this solution will handle the information quickly.

It has very good learning capabilities. It will learn from the user feedback. For example, if you have some documents which come to your system and are quite complex. Maybe the date format is slightly changed, or some amount is changed, and you cannot extract it. A typical user will manually learn via that data and enter it. It'll also ultimately learn. That way, the next time, it'll automatically extract the data, and that process will no longer require any manual intervention of the user.

What needs improvement?

When I'm talking about low-code development, they are consulting on a new product with low-code. This means that now you won't have to build that script. It's just a simple single centralized development tool where you can drag and drop things. You can just drag and create your form using drag and drop features, and you can implement your own business logic.

It’s not truly low code yet, as every two or three projects, you will have a situation where you have to go behind the essential things. You will definitely still need to customize. You cannot yet really rely on low-code development. If you have a complex business requirement, you must build that complex script.

Previously, it did not support all browsers. However, it’s my understanding that they have since changed that shortcoming.

They have to create a few different packages. For example, let's say we are in the insurance sector. The insurance sector will have a specific set of processes. If they could give us a framework where I don't have to be concerned about how to build the form, something already heard towards insurance, that would be ideal.

At least 80% of my time will be on implementing business cases rather than building software processes. I just want this to have some use case differences and some pre-built solutions based on industry. That way, a user can directly apply their business cases to that and it'll be like a ready-made solution - or at least 90% ready-made. The last 10% we can feed our inputs into more easily.

For how long have I used the solution?

I have around five years of experience using Kofax TotalAgility.

What do I think about the stability of the solution?

The solution is very stable.

They are the leaders of BPM. We get lots of fixes as needed and their support is very good. It’s reliable. The performance is great.

What do I think about the scalability of the solution?

Scalability, as compared to other software, is excellent. We have active cluster testing also involved in that project. Therefore, you have multiple instances of application servers in a very secure environment.

There are various different transitions, and we require that system to be very scalable. It's very good in terms of scalability. It can support the failover as well. You can configure it as per your requirements.

It requires some additional cost in terms of hardware. However, active clustering is also supported. If one node is down, it'll definitely pick up another server with only a few seconds of interruption.

How are customer service and support?

Technical support has been good, and we have been happy with their capabilities.

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

I had started my career as a technical consultant with another OCR tool, and initially, it was with Dell, now OpenText. Later I moved to the Kofax.

We have two pieces of software that we use. We are using accounts payable software, and we have OCR software. If you're talking about OCR, we are not only dealing with Kofax.

Some clients also have ABBYY. Somewhere we are using Captiva also, for a few of the government organizations, and now we have some small tool which is called Xtracta which we are using with some very small accounts, where we need invoices for maybe 50 invoices or 100 invoices per day.

How was the initial setup?

As compared to other software, and I'm not saying it's complex and easy, is that Kofax gives you the OCR capabilities plus business, including BPM capabilities, case management, and data management. Therefore, it has some additional components which we need to install on the server. It came with an applicant server and with a web server, and it has its own SQL database on the back end. It has its core designer, Transformation Designer. It definitely came with different components. In terms of the installation, I consider that the installation will be a little bit complex as compared to other software since we are dealing with more components here.

Deployment is very fast. Now they have this very centralized development tool. You can create a package. We have a list where you created the process, forms, and different scripts, so there are some processes that vary. You can create a package directly and just select whatever form you need.

What was our ROI?

We’ve seen an ROI. They're charging you more as compared to other options. However, they give you more features. There’s more value.

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

The price depends on how your relationship is with Kofax. Sometimes you get a discount. However, I’m not aware of what a standard price is.

Which other solutions did I evaluate?

The market is really competitive. ABBYY is also one of the leaders in the space. Apart from that, there’s IBM Datacap, then there are some small vendors which have their own tools.

What other advice do I have?

We are resellers.

We have some existing clients using it, and they are happy with Kofax. That said, currently, in the market, I'm seeing that it is very competitive now. There are some other very small vendors. That might beat it in terms of costs. These competitors are pretty cheap.

However, if you want different capabilities and other things, then definitely, Kofax is the very best tool.

I’d advise potential new users to consider the use cases and the kinds of documents you will be processed with your Kofax TotalAgility. Consider items such as the expected volume and number of users. Do you really require the BPM process? Are processes complex?

Kofax is very good for complex business processes. However, it may not be necessary if you don’t have complexity. With Kofax, it can support any end number of possibilities and end number of use cases if that sounds like what your company needs, then it is perfect.

I’d rate the solution nine 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/reseller
Flag as inappropriate
Shiwali Shukla - PeerSpot reviewer
IDP consultant at WNS
Real User
Top 10
An easy-to-use solution with good ICR and OCR capabilities, but needs more connectors and advanced workflows and better stability
Pros and Cons
  • "Its ease of use is valuable. It is easy to use and configure."
  • "They can have more advanced workflows. They can have some custom status in their workflow. It was there, but they can introduce more cases such as triggering an email or interacting with other systems with APIs. They can be included as stages in their workflow rather than doing it all by scripting."

How has it helped my organization?

We had to extract some data from a commercial policy, which can run up to 300 pages, for a client. It was a challenge to look for the action data and extract it out of those 300 pages. With ABBYY FlexiCapture, we were able to do that easily by using its repeating group feature. It was helpful. For doing the same in Kofax, we would have had to heavily rely on scripting. There is no way of doing it with low code.

What is most valuable?

Its ease of use is valuable. It is easy to use and configure.

Its ICR is really good at handwriting recognition. The last version of ABBYY FlexiCapture that I used was better than other tools such as Captiva and Kofax. The base OCR engine of ABBYY is also very good. In fact, Kofax was using ABBYY's OCR engine in the last version, but they came up with their own engine.

One good thing about ABBYY is the training. All the training courses are available in ABBYY University. They were not free initially. They were instructor-led, but now, ABBYY has made them open for everyone to learn, whereas with Kofax, you have to purchase training courses, and then you can learn. With ABBYY, everything is there in their knowledge base.

What needs improvement?

I have not used it in the last six months, but at that time, there were some stability-related issues. These were known issues. They might have already fixed them, and it might have been improved by now. We had raised tickets, and they were working on various tickets. The known bugs included crashing of the application when there were more than 500 pages in the configuration window. It did not work in such cases.

There were also issues related to the classification by training. There is a feature in ABBYY where you can classify the type of a document, but it was not very effective when you trained it on a lot of variations. It worked fine for up to 10 or 15 variations but for anything beyond that, it was a mess. It wouldn’t work.

They can have more advanced workflows. They can have some custom status in their workflow. It was there, but they can introduce more cases such as triggering an email or interacting with other systems with APIs. They can be included as stages in their workflow rather than doing it all by scripting. 

They can also work more on connectors. The ABBYY connectors are there for SAP and SharePoint, but they can include more connectors. ABBYY's usage has increased. I have seen many companies using ABBYY in recent times, and it will help a great deal if there are more connectors to connect with the end systems.

For how long have I used the solution?

I had worked with ABBYY FlexiCapture for around five years. Currently, I'm working with Kofax, and I have not worked with ABBYY for the last six months. The last version that I used was version 12.

What do I think about the scalability of the solution?

I have not seen FlexiCapture environments with a lot of users. At the most, I have seen 20 users, which included five or six business users, five or six developers, and a few people from the admin and config team. That could be because at the time of implementing a project, not many people were required. When we handed over the project, more business users would have been created. It all depends on the phase of the project.

How are customer service and support?

We did try to reach out to them for some of the challenges. They wanted us to take some proper services consulting, but we were able to manage on our own. We did not interact with the services consultant from ABBYY.

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

I used ABBYY FlexiCapture in my previous organization. Currently, I'm working with Kofax. Both of these organizations are service-based, and they provide services related to implementation, development, and other things. The tool that we use is decided by the client. When we approach a client, if they have already purchased a license of ABBYY or Kofax, we have to execute the use cases by using that tool. Otherwise, it will be a loss of a lot of money for them. 

If they don't have a tool, we do try to suggest what would be best for them, but it is up to them to decide which tool they want to go for. They can go for ABBYY, Kofax, TotalAgility, or any other tool.

I would recommend ABBYY FlexiCapture for those use cases where only OCR is needed, and there is no need for business processes. That's because not much branching is there in the workflow. It does not have a powerful workflow feature. If you are using it in association with any BPM or RPA tool, there is the ease of configuration, extraction, and classification. That's one thing that I like about ABBYY.

FlexiCapture is a good product. It can be used for any kind of use case that requires OCR. Except for the unstructured content part, which is there in Kofax, I cannot think of a use case that cannot be solved by using this solution. It caters to most needs of the projects. ABBYY is positioning this tool as only an OCR tool, not as a BPM tool. Kofax is an OCR and BPM tool. That's the difference, but I would not like ABBYY to change it because that's what makes ABBYY the simplest. There is a single component, which makes it easier to understand. When you add more features and modules, the complexity also increases from an understanding perspective. We can suggest more features, but it would be a trade-off.

How was the initial setup?

It is a straightforward setup. If you have a cloud deployment, you just need your tenant. You simply start using it after installing a thin client on your machine. 

I have used ABBYY on the cloud. I had used ABBYY as a standalone installation on my machine. I have used ABBYY as a distributed solution within our VPN.

Deploying simple bug fixes in ABBYY doesn't take much time. It can be done within two minutes. When deploying the whole project from scratch, I have not seen it take more than 10 minutes. It can be done easily, and it is a straightforward process. To import from one environment, you just change the variables to cater to the needs of another environment. You just go there and import it. It is that simple.

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

You need to purchase user licenses, and you also need to purchase the license for the pages. User licenses are required for your developers to use the developer tools, and you also need to ensure that there is a pool of licenses for the business users so that they can log in and perform their activities.

What other advice do I have?

It has a very simple GUI. When a person is using ABBYY FlexiCapture for the first time, I would suggest exploring all the features, especially the Flexilayout Language, because it is very easy to explore all the features. It provides you with a great level of flexibility to configure complex documents. ABBYY is no-code, but there are a lot of things that you can do by scripting in Flexilayout Language. So, I would recommend not restricting yourself to the GUI-based commands. You should go and try Flexilayout Language. It is a very powerful feature in ABBYY.

ABBYY is launching new products. It is not that they're not changing anything. They have launched Vantage 2.1, which is very good at cognitive capabilities.

While pitching their tool, every product's sales team tells clients about certain cognitive capabilities and other features, which might not be possible for specific use cases. So, client expectations should be set correctly. One of the clients was expecting us to use the cognitive capabilities of FlexiCapture, but FlexiCapture is not that cognitive. Vantage is cognitive, but FlexiCapture is not.

I would rate it a seven out of ten. There is ease of use and ease of configuration, but they need to include more features. They need to make the product more stable in dealing with more variants.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
ECP Architect at a computer software company with 10,001+ employees
Real User
Top 20
Captures and recognizes pages and documents
Pros and Cons
  • "The most valuable features of IBM Datacap is the capturing and recognizing of pages, documents as well as the scanner and barcodes."
  • "Currently, when you are entering invoices, you have to enter multiple rows. In Captiva the multiple rows will be dynamically added. This would be a beneficial feature for IBM to add."

What is most valuable?

The most valuable features of IBM Datacap is the capturing and recognizing of pages, documents as well as the scanner and barcodes. I also like the fingerprint recognition.

What needs improvement?

I would like IBM Datacap to add features similar to Captiva. Currently, when you are entering invoices, you have to enter multiple rows. In Captiva, the multiple rows will be dynamically added. This would be a beneficial feature for IBM to add.

Our users prefer TM's navigator more than  IBM's current navigator. It could just be a training issue, however, they like having more options like filter badges.  

In one case, our client needed to scan 5,000 pages in five minutes, or less, Datacap was not able to accommodate this task. 

For how long have I used the solution?

I have been using IBM Datacap for nine years.

How was the initial setup?

The initial setup of IBM Datacap is easy, with no issues.

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

Pricing of the solution is reasonable.

What other advice do I have?

I would rate this solution an 8 out of 10.

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
Buyer's Guide
Intelligent Document Processing (IDP)
September 2022
Get our free report covering ABBYY, Kofax, IBM, and other competitors of OpenText Intelligent Capture. Updated: September 2022.
634,325 professionals have used our research since 2012.