We’ve been testing a financial application that does account reconciliation for several years now. The financial software we test conforms to SAS70 (Statement on Auditing Standards No. 70), so all of the data and workflows are designed according SAS70.

Although we aren’t accountants, certainly testing this type of software needs a more careful eye than ordinary UI testing, so I thought I’d share some of the best practices developed by our team over the last few years.

This isn't accounting. Can your financial software testing handle market fluctuations and currency conversions?

Going beyond accounting and traditional interface testing, does your financial software testing cover market fluctuations and currency conversions?

What to look out for?

Firstly, SAS70 defines the standards an auditor must employ in order to assess internal controls. This is especially important for public companies that have numerous regulations and it’s important to understand SAS70 as it impacts data and business work flows, as well as roles and privileges of those that have access.

Financial Software Testing – Best Practices Learned on the Job

  1. Testing input fields needs to be comprehensive. It should include legitimate data and illegal data. Negative testing is a must. For example, when testing an input box, if the requirement is a number, it is necessary to enter a number to test, but you also need to enter letters, spaces and other characters. This is certainly not new for testing, but very important for testing financial applications. For example, the amount and percent field should not allow non-numeric values.