Agile Audit mapping structure

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.

The Mapping structure included in version 1 was designed to be condensed and to align with the common primary statement line items only.  As a result, we are aware that some firms have added in their own additional groups.

Interim measure:
Please be advised that we will be disabling the feature to add in custom groups in the coming weeks (we will advise you of an exact date when this is confirmed), based on feedback received from both customers and CaseWare International. 

There are  2 key limitations when adding in custom groups:
  1. Can’t delete groups once they are created
  2. Can’t have firm-created groups flow to Analysis areas in checklist

Future plan:
We are currently revising our mapping structure, with a focus on developing a consistent one that can be used across all CW ANZ Cloud-based apps (e.g. Agile Audit, Cloud Finanicials, AnalyticsAI, etc.)
This new structure will be far more detailed, and therefore, we expect it will address the reason firms have been customising the mapping structure.

Action required by firms:
To ensure that there is minimal or no impact to your existing files, we strongly recommend that firms stop adding custom groups, and wait for the release of our revised mapping structure in early 2021.

The review and amendment of the current Agile Audit mapping structure is a current project for us, and we expect to complete early in the New Year. We will be sending out an update email prior to the release of the new mapping structure, so we recommend you inform your firm’s primary contact to keep an eye out for such an email. 

If you have any questions or feedback that you want to share regarding the mapping structure, please share this with our customer support team via contact details below. 

Customer Service:
Ph: (03) 9660 4688

    • 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 ...
    • Efficiently Mapping Audit Only Files

      Audit System users who will not be using the Financials IFRS template, can use the mapping “audit” filter to simplify the list of mapping numbers required for audit, and to hide all the Financials IFRS specific mapping numbers. The remaining mapping ...
    • CloudBridge Getting Started 7: Enabling LeadSheet Mapping for CloudBridge

      In this video you will learn how to set CloudBridge up to transfer leadsheet mapping from your Caseware Working Papers file to your Cloud engagement file. Note: If you already have the leadsheet structure in your mapping database (e.g. files created ...
    • 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 ...