Halo

  • Auditors are required to perform testing over journal entries as they are a common way that management can commit fraud. Most modern businesses post thousands, if not millions, of journal entries every year. Simply acquiring these massive data sets is a challenge for auditors and that’s before they even start to perform the required analytics to identify fraudulent accounting practices.

  • Halo was designed to streamline the process of Extract, Transform and Load; standardise the tests performed; and visualise the results for auditors and clients.

    • 10k+ audits in 60+ countries use Halo every year

    • 50k+ Halo apps generated every year

    • 1 billion+ records can be processed in each instance

    • Same day test results are now possible compared to turnaround times of several weeks

    • Anomalies clearly identified via data visualisations

'Audit Innovation of the Year'

2016 International Accounting Bulletin Awards.

“Halo is revolutionising the PwC audit and harnessing the power of data.”

STRATEGY

Using the Kano Model to help define the product strategy.

The mission was to develop a product that auditors could use themselves without the need for a data specialist so the tool needed to be able to handle large data sets and be easy for non-technical users to perform their tests and visualise the results.

The table shows the comparison vs the most common competitors (legacy solutions).

ITERATING

Prioritising User Needs

Users of v1 were invited to rate 8 proposed feature upgrades in terms of their importance (1-100) and current level of satisfaction (1-100) to help identify the highest priorities for v2 and beyond.

One user need clearly stood out as having high importance and low current levels of satisfaction.

As a Halo user

I need to add 3rd party fx rates to my client data

in order to calculate reporting currency values