Understanding of the IT environment
A description of the applications, infrastructure and IT processes that are relevant to the financial statements, with the risks that follow from them.
Service for accountancy firms
An IT auditor in your audit team, with work that fits your audit file.
Standard 315 requires you to understand your client's IT environment and to identify the risks in it. With a simple package you can do that yourself. With an ERP system, a webshop or outsourced IT you need an IT auditor. Our IT auditors and chartered accountants join your audit team and deliver findings you can rely on in your audit.
Or call 085 7609740
Since the revised Standard 315, which applies to financial years from 2022, you as the auditor must understand your client's information system, including the IT environment. You determine which applications are relevant to the financial statements, which risks arise from the use of IT and which general IT controls address those risks.
This is not a formality. Regulators keep finding the same shortcomings in audit files: the reliability of the information used has not been tested sufficiently, and a report from a standard package is wrongly assumed to be reliable.
Not for every client. The standard is scalable: in a simple environment with standard software, formal general IT controls are often not needed. An IT auditor adds value when:
Work that you can include directly in your audit file, written in the language of the audit.
A description of the applications, infrastructure and IT processes that are relevant to the financial statements, with the risks that follow from them.
Testing of access management, change management and IT operations for design, existence and, where needed, operating effectiveness.
Testing of the controls in the application that you want to rely on, so that you can limit substantive procedures.
Analyses of the full population, with substantiation of the reliability of the data used.
Assessment of ISAE 3402 and SOC reports from service organisations: scope, exceptions, period and what you still need to do yourself.
Points for the management letter in plain language, so that your client benefits too.
The professional body says so itself: involve the IT auditor in April, not in November. If you only discover at the interim audit that the general IT controls do not work, you have to overhaul the audit approach under time pressure.
That is why we already think along about the approach per client at the planning stage: where can you rely on IT, where can you not, and what does that mean for your procedures.
Involve the IT auditor in the planning, not only at the interim audit. Discuss the approach per client with us.
Most audit clients of the firms we work for are SMEs. An approach designed for a listed company does not fit there. We test what is relevant to the financial statements and explain why something is or is not needed.
We also know that practice from the other side. Our director has been teaching at the SRA for more than twenty years, including the course IT in the SME audit, and coaches auditors in practice on using the IT audit in the audit.
We fit in with your audit approach, your planning and your audit file.
Together we determine which clients need an IT auditor and what the scope will be per client.
We perform the work at your client, in coordination with your audit team.
You receive documentation with conclusions that fits your audit file, so that you can evaluate our work and rely on it.
We discuss the consequences for your audit approach and the points for the management letter.
No. Standard 315 does not prescribe an IT auditor. For more complex IT environments, however, the standard says that team members with specialised IT knowledge are likely to be needed.
To audits of financial years that began on or after 15 December 2021, so in practice from financial year 2022.
The processes the standard names: access management, change management and IT operations, such as backup and recovery. Which controls are relevant depends on the applications and the risks at your client.
Formal general IT controls are then often not needed. But a report from a standard package is not automatically reliable: you still have to substantiate why you rely on it.
Yes. We assess whether the report covers the right services and period, what the exceptions mean and which controls should be in place at your client itself.
We agree that with you in advance. For a client where we ourselves advise or provide assurance, we first discuss whether we can perform the IT audit.
In a short conversation we discuss your client portfolio, your planning and how we fit in with your audit approach.