OCR for bank statements

I need to be able to OCR bank statements, including getting all the numbers and description in a form that can be processed.  How did you cope with the fact that every bank any a different layout? ANSWER (from http://stackoverflow.com/questions/7362926/what-is-the-state-of-the-art-in-ocr-of-bank-statements-in-net) We have first hand experience, and I have done it in two different ways in the past. Full Page OCR First, you can take the approach of “full-page OCR” and then parse the information into your desired data format. There is a variety of Engines with .NET support, such as ABBYY Engine SDK, or even a completely free-to-start cloud-based on-demand OCR API (OCR Cloud 2.0, http://www.ocr-it.com/ocr-cloud-2-0-api). This is more of a classic approach I used for over past 10 years and up to a few years ago. OCR provides you with a complete text-based result, and you use algorithms to extract informaiton. This approach is quite static and requires heavy programming usually, especially if there are multiple variations. There are two potentially troublesome areas to look for in this approach: A. making sure that OCR provides consistent layout and text structure so it could be parsed reliably. If there is a table without gridlines, or if there is just tabular data that could be detected as a table, then OCR may work unpredictably from document to document, which essentially breaks your parsing down the road. B. making sure that your parsing logic can accommodate various formatting differences and multiple variations of data structures. This is pure programming that requires code changes for adjustments or updates. Dynamic Data Capture Second, use a modern dynamic data capture system that automates template identification and...