7 January 2013

First client

31 December 2019

Last software update

< 2 hours

Support response

StatementReader is used by forensic accountants, bookkeepers, insolvency investigators, solicitors, auditors and business review professionals to stop wasting time and talent converting bank statements into Excel

This website uses cookies to enhance the user experience.  Click here for our cookie statement and here for our privacy policy.

All Rights Reserved 2012-2020 Suave Software Limited. London, England, United Kingdom. Email Us

  • LinkedIn Social Icon
  • Twitter Social Icon

Automated bank statement corrections

Once a scanned document has been converted to Excel, StatementReader can check and correct date and amount errors that may have been introduced during the character recognition process. There are two types of corrections that can be selected, safe or unsafe, each of which can be applied to either the dates or amounts.

Errors that are identified and corrected in the dates and amounts will be highlighted in Excel. Orange cell shading signifies error, green means a correction has been made. To get started, right-click on a completed job.

Safe corrections

When a date is in an incorrect format but the date before and after are the same (say 1 January 2015), StatementReader can safely assume that the incorrect date should also equal 1 January 2015.

When a balance figure is displayed on consecutive lines, StatementReader can use multiple lines to calculate whether an error lies in the receipt, payment or balance column, and make the appropriate correction. This is a safe assumption.

Unsafe corrections

Other date corrections can also be completed, for example assuming that the previous correct date should be used for any subsequent incorrect dates. This is fast but slightly unsafe and so requires the user to select this option.

Unsafe amount checks assume that the balance column is always correct, and the receipt or payment column should be corrected.

#Features #All