Robot thinking

Comparing ABBYY FlexiCapture with FineReader Server: Similarities and Differences

Summary: ABBYY FlexiCapture has many functions in common with ABBYY FineReader Server (formerly branded as Recognition Server). However, each product is designed with unique functions in mind which companies must consider when evaluating solutions to their document capture and OCR requirements. A comparison of the functions between FlexiCapture and FineReader Server is most easily done

Summer Is Here Sale

Summer Is Here Sale: Save 10% On ABBYY Software

Take advantage of our “Summer Is Here” sale going on throughout the month of June! Save 10% on select ABBYY FlexiCapture and ABBYY Recognition Server software! Let this software revitalize your company – saving time and money! Contact us to learn more about this special offer! Offer expires June 30, 2016.    

Thumbnail for FlexiCapture for Invoices Invoice Training video

ABBYY FineReader Server Video – Email Capture

Watch this video on how to configure ABBYY FineReader Server (formerly Recognition Server) to capture documents from emails. You can even save the message body as part of the final output document.

Related Content:

Thumbnail for FlexiCapture for Invoices Invoice Training video

ABBYY FineReader Server Video – SharePoint Online Integration

Watch this video on how to configure ABBYY FineReader Server (formerly Recognition Server) to submit documents to SharePoint Online. The process is simple, efficient, and flexible!

Hello, in this video I am going to show you how ABBY recognition server integrates with SharePoint online. Now this is a very neat integration. It’s very quick and it obtains high quality OCR results for us. What you see on the left here is what we call an input folder, or a hot folder. This is where we’re gonna simply drag and drop folders that we want to be OCRed, and then it put, here on the right, into SharePoint online. Now the cool part that I’m going to show you, is that I’m going to be dragging and dropping what we call TIF Image files, into the hot folder. In the process of OCRing them, we will also convert them to a searchable PDF. And that document will be stored in SharePoint as a PDF, also searchable, so that we can find the content at a later time.

So all I’m going to do is copy and paste some files into the input folder. They will not stay there long. You can see now they are already gone. What the software is doing right now, is converting those two pdf files, and once again making them searchable for us. So, if we go over here and we refresh our SharePoint Online site, you can see that I now have three PDF files. In fact, if I maximize this here, you will see I have those files right here, and I can simply click on them. And if I zoom in here just a little bit, you can see that I can highlight the text. Meaning that we do have searchable content and that SharehPoint will be able to crawl and index that content for us.

So, it’s really that simple. All I did is drag and drop into a hot folder and now they are there in SharePoint. Now I wanna show you a little bit behind the scenes because I want you to understand how easy this is. This is what we call the administration council and recognition server. And what I did is, I just completed this document to workflow and you can see here, I’ll just run through the steps very quickly. On the first input, we just tell the system what are the files that we’re going to capture. Where are they located and which ones do we want to process. For this one, that you just saw, we’re just saying. “Hey, we want every file in there.” We can tell the OCR results how well we want them to be captured. Do we want high quality results, or do we want high speed, or do we want somewhere in the middle.

And also we can target the language on the software here as well. If we have barcodes and things like that, we would also process them here. We can tell the software how we want to separate the jobs, and for this one we just said, “Hey, for every file going into that hot folder, we want you to create a job, or a file in the output.” Now we can look at quality control, so for example if we wanted staff to be involved before it ended up in SharePoint, we have the ability to stop and require what we call verification in the software. And we can do that based on the criteria that you see here, whether it’s on all documents, or if it’s just based on a certain arrange there of low confidence characters.

We can also handle exception and things, just different ways in what you want to control it there. If we wanna index the document, for example I have invoice documents that we process. Maybe I wanna index them by invoice number or even invoice date or vendor. We have the ability to allow a user to do that. In this case we did not, we bypassed indexes, but we can stop the process and require an AP clerk or another clerk, just randomly processing other documents to provide the index and information. And then you can see here, we have our output. The output here simple as saying, “Look, I want a PDF document.” and if I HIT edit, you’ll see a little bit of this information showing up here for us. You can say, I want a PDF document. You can say, I wanna save this in the SharePoint library. And then we simply provide the URL of where we’re going to have the documents live.

What library, what folder and those kind of things. We also have full control over down here, of the name you [inaudible 00:03:54] of the documents. So we can even use index information that we captured, to process those for us. And it’s really that simple, this is how easy it is. Honestly, probably setting up SharePoint Online, OCR process. This simple is probably no more than a 15 minute process, and that includes installing the software. So, a very simple and easy to use interface here from a administration perspective. And the cool part is then, we have all of our searchable content, and SharePoint Online in the cloud, so it’s accessible by any staff distributively, so. And that’s ABBY recognition server, I hope you enjoyed it. I hope you understand it. Such a neat and easy to use, and easy to implement product. And please contact us today to learn more.

Related Content:

FlexiCapture for Invoices Invoice Training

ABBYY FineReader Server Video – Processing Unstructured Docs

Watch this video to see how your enterprise may process both structured and unstructured documents quickly and cost effectively using award winning ABBYY FineReader Server (formerly Recognition Server).

Good afternoon, this is Jim Hill from UFC. This afternoon I’m going to show you ABBYY Recognition Server processing some unstructured documents. These types of documents will include things like letters, contracts, and we will also process some structured documents including invoices. Let me introduce ABBYY Recognition Server, talk about some of the features, the advantages and disadvantages of using recognition server to process unstructured documents.

This is one alternative. There are many different alternatives for processing unstructured documents. Let’s look at the demo. What’s I’m going to show you is the ABBYY Recognition Server. I’m just going to show you the quick … This is what the server looks like. This is where you set up your workflows. Let me just quick show you the workflow. From left to right, the name of the workflow, where the documents are coming from, in this case a shared folder, what you want done to the documents, what the language is, the level of OCR you want for example, would you like to optimize for quality or speed, here I have it set in the middle, how are you going to separate the documents many times. It’s simply one document per file. It you’re processing a PDF file, that can be how it can be done. If you’re scanning documents, most frequently we’d use a barcode separator sheet, which we would provide to you when you want to scan documents.

Quality control talks about if you want to verify the data coming off, which is verifying that the OCR engine produced the correct data. Indexing, now here’s where you set up the different document types. I’ve got three document types set up, different index values for each. There is a contract. We have an agreement number and we have a data for the contract. It takes a couple minutes to set those up. What do you want to do with the output file, that’s the last tab. We have the output data going to Microsoft Word. There’s a variety of options. We can set it to XML files, which I also have selected here. We can save the original images. We will show you that as we run some sample batches.

What I’m going to do right now is I’m going to show you some samples. Here’s the folder that is being watched. As I move in some sample documents, I have these sample documents here in this other folder. Let me just show you what one of those documents looks like. Here’s a contract. We’re going to extract the agreement number off of this contract. And some other forms, an invoice, there is a letter. These are all going to be processed together in one big blob as we would expect in an unstructured document processing system. I’m just going to select these documents, copy them over to the watched folder. You notice they disappeared quickly. ABBYY has already processed those documents.

Now what’s happened is we go to our verify, or actually our document indexing station. Since I did not select, tell the system to do any verify functions. What I’m doing here is just entering in index information. This index information will be put into an XML file. It will also be carried in variables that can be used for programming purposes. I’m also putting that index information into the file name. What I have set here, I have these documents set to go to Microsoft SharePoint so that you can have access to these documents anywhere that you have access to your SharePoint server. In this particular case, it’s Office 365 SharePoint, but any SharePoint system will work.

I can clearly see that this is an invoice document. It’s just asking me now what is the invoice, what’s the vendor. I’m just going to say it’s JL Smith, obviously that’s the vendor, and the date, so I’m going to find the invoice date. A caution on the date, it says month, month, day, day, year, year. You need to be careful that this was set correctly. In this case what I can do is just click and keyed the date, and then just move it around a little bit, accept the document. That’s pretty quick.

Now it moves on and it’s going to recognize another document’s pending, a sales agreement. I know that’s the sales agreement. I’m just going to go ahead now and select that field for the agreement number. There’s the agreement number. Okay, contract seller signature date. I’m going to jump to the last page, obviously that’s where the signature is going to be. Now again, I grabbed a little extra data and that format needs to be in month, month, day, day, year, so there’s a little manual intervention required here. What will happen is we can program this to strip out characters once they’re processed. I’m just going to go ahead and put it into that correct format, accept the document. Now the system is not learning how to process these documents. Each and every time I process these documents this is how I’m going to have to do it. You can see that this is a letter, and it’s looking for the sender. Well I’m going to have to go to the last page to find out who sent it. There’s sender. Who’s the addressee, we can see there’s the addressee and there’s the letter date again with our format correct 12/09/2006, accept the document. Then that is it for the batch.

Now what we will do is go to our SharePoint folder where we expect the document results to come up, and there’s the document results. We see a contract, a letter, and an invoice. Let’s just pull up one of those documents. Here’s the contract document showing the exported data coming out of the contract. You see what it did, it just grabbed all the text of the document. If I need to manipulate this data into another system, I can copy paste the system. Now of course we could program the system to put this data somewhere. It will require a little bit of custom programming in the system. Scripting is built into the system. Also, the index data that we entered here is written into the file name. ABC123 was the sales agreement number, and the data of execution was 3/15/2006 as you see that. Similarly for the invoice, you’re going to get the invoice data. It does a very good job of extracting the detail of the invoice, and same thing for the letter.

Well that concludes the ABBYY recognition server demo. I just want to say that there are many different alternatives that we can offer. This is one cost effective way to process unstructured data. We will also show ABBYY FlexiCapture, which is a much more powerful system, but does require more complex setup and is much more expensive. Please get back with me if you have any questions, but we wanted to show this so that you would be aware of the unstructured processing capabilities in ABBYY Recognition Server. Thank you very much.

Related Content:Save

FlexiCapture for Invoices Invoice Training

ABBYY FineReader Server Video – Introduction

Watch this video from ABBYY USA to learn how ABBYY FineReader Server (formerly Recognition Server) provides network enabled, high-volume capture and OCR processing of images. This document capture solution processes images through high quality OCR while providing flexibility for export of images and metadata. See more at

Related Content: