How does the Audit Report in Agile Audit work?

How does the Audit Report in Agile Audit work?

The Audit Report (4-520) in Agile Audit has been designed to allow you to draft an auditor’s report in accordance with the relevant ASAs, efficiently. By answering questions in 4-500 ASA Requirements - Audit Opinion, the auditor’s report will be constructed based upon your responses.


Note: It is important to note that the generated Audit Report must be modified to suit your client’s particular situation. The generated Audit Report in Agile Audit will never be finalised by answering 4-500 alone and users are reminded to always modify the document accordingly as some circumstances may not be included based on the default document. 



What type of information is automated from 4-500?

Answering questions within 4-500 ASA Requirements - Audit Opinion will automate some of the following components of the Audit Report:

  1. Opinion

  2. Emphasis of Matter

  3. Key Audit Matters

  4. Other Matters

  5. Other Information


Note: Users are reminded that despite the automation of the above components, users need to be aware that default content may need to be adjusted based on a client’s unique situations. The content is not limited to what to what has been generated in the Agile audit report. 

What type of information is “not” automated from 4-500?

There are other contributing factors that may automate content in the 4-520 Audit Report, such as:

  1. OPT Optimiser

  2. Entity Information (i.e. Company, ACNC, Incorporated Association)

  3. Placeholders within the documentation, e.g. Select Date, Select Staff

Does the Audit Report information flow anywhere else?

Yes. The opinion selected in 4-500 ASA Requirements - Audit Opinion will flow through to the 4-520 Audit Report and the following workpapers:

  1. 4-605 Management Letter

  2. 4-606 Governance Letter



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

    • Consolidation in Agile Audit

      Although consolidation is a feature in Agile Audit, it is important to be aware of a few key rules/best practices: 1. Only Trial Balance and journal data will be consolidated - there is no consolidation of risks or documentation between entities ...

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