How do I use the Management Letters in Agile?

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.


Note: If you select No to Management and Governance Letters, you have a choice to include a single workpaper that will disclose the Summary of Detailed Findings (4-601) in place of the Management and Governance letters. This can be exported and included as an appendix to your current letters.




    • 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 ...

    • What is the Management Reporting template

      The Management Reporting template can produce monthly, quarterly and other periodic reports based on current year, prior year, budget and forecast data. The template is an add-on which consists of two extra documents: Profit and Loss Statement. ...