How do I use the Management Letters in Agile?
As required by ASA 265 and ASA 260, the auditor is required to communicate significant deficiencies and specific information to those charged with governance.
In Agile Audit, there two draft letters that have been prepared for you to use to assist with your communication to those charged with governance:
4-605 Management Letter
4-606 Governance Letter
Summary of Detailed Findings
Included within each of the above letters is an automated Summary of Detailed Findings table. This area includes a summary of detailed items that are linked directly to Risks, Controls or Issues, at which the auditor has identified as a significant deficiency or specific information that should be communicated to those charged with governance.
The Summary of Detailed Findings is made up of:
Risks
Controls
Issues
Risks table
The risks that appear in this table have been selected as Include in summary of communication to management risks.
The table will display the risk name, description, risk type and risk level. The icons displayed will also be consistent with the Risk & Controls screen.
Controls table
The controls that appear in this table have been selected as Report to Those Charged with Governance (TCWG) controls.
This table will display the control name, description, whether it is a key control and the impact of the control. The icons displayed will also be consistent with the Risk & Controls screen.
Issues table
The Issues that appear in this table have been created as Letter issues.
This table will display the description of the issue and the status of the issue.
Do we have to use the default Management Letters?
The Management Letters in Agile Audit are not compulsory. You are able to determine if you wish to utilise the default Agile letters or not via the OPT Optimiser.
Related Articles
Agile Audit Process Map
The Agile Audit process map attached in this FAQ below illustrate the best methodology to use our CaseWare Agile Audit for an audit engagement. To go alongside the process map, a series of FAQs are below to provide details on parts of the process ...Enabling Agile Audit for staff
After Agile Audit ANZ has been enabled on your firm’s CaseWare Cloud site, a Cloud administrator will need to assign the app to the relevant staff to access and use. This is done one of two ways: Both options below can only be performed by a Cloud ...Agile Audit mapping structure
Based on recent questions we have received from Agile Audit customers, we have developed this explanatory FAQ on the use of the current mapping structure in Agile Audit. Background: The Mapping structure included in version 1 was designed to be ...Expectations with Agile November 2022 update
Introduction Prior to running the Carry forward with the Agile November 2022 template, it is important you are familiar with the following post-carry-forward impacts that will require your intervention. The post-carry-forward steps that need to be ...How to use the Agile Risk Library?
What is the Agile Risk Library? The Risk Library is a repository of risks that you can import into any Agile engagement file. How many risks are in the Agile Risk Library? Currently there are 20 risks contained in the Agile Risk Library. This number ...