There may be occasions where it is necessary to edit the completion and other status information in respect of an audit pack.

There may be occasions where it is necessary to edit the completion and other status information in respect of an audit pack.  For example, if a user has started to plan an audit and generated checklists based on the wrong master pack, you may wish to "undo" the action so that the master pack can be changed and the planning process restarted.

To change the pack status, select Amend pack completion status from the File menu of the Main window and the system will ask you to enter the code of the pack to be changed.  Enter the code, or select it from the pick list, and the Amend pack completion status dialog will be displayed. 

aa4.png
Amend pack completion dialog

This contains the following fields:

  1. Error flag.  If the pack is in error, e.g. power failed on a balance forward, the error flag will be set at a number other than 0.  You may edit the number to read 0 so that the pack may be used, but if you do this please look at all sections of the client to ensure that no corruption occurred as a result of the error condition.
  2. Mode.  The mode of the pack will either be Current or Backup.  Audit Automation keeps track of the current version of the client data when it is travelled out of the office using the [Transfer pack to or from office] button. This field is for information only and can not be updated by the user.
  3. Progress.  Audit Automation keeps track of the progress of the audit and will only allow access to certain options at times when they are relevant.  The contents of this field is the data that is used to track the current stage of the audit, and the number which appears has the following meaning:

        1  Balanced forward
        2  Planning completed
        3  Field work started
        4   Field work completed
        5   Senior signed off audit
        6   Manager signed off audit
        7   Partner signed off audit

Audit Automation will allow you to edit this field to move completion back in the audit cycle, but will not allow you to move it forward.

4. Programmes generated.  If this check box is checked it indicates that the audit programmes have been generated and the system will only allow you to update audit test exclusion.  Unchecking the box will cause the audit programs to be regenerated when you when you next access the client. Only uncheck this option if you wish to release the option and re-initialise the audit programmes.  By re-initialising the programmes you will delete any customisation that may have been carried out for the client.

5. Checklists generated.  If this check box is checked it indicates that the audit checklists have been generated and the system will only allow you to update checklist question exclusion.  Unchecking the box will cause the checklists to be re-initialised, forming a new set of questions for the client.  Only uncheck this option if you wish to release the option and re-initialise the checklists.  By re-initialising the checklists you will delete any answers that may have been entered in respect of the current year.

Once you have made the changes required click on [OK].  If you wish to close the dialog without saving any changes you have made, click on [Cancel].

Related documents

Inherent Risk Questions
This document outlines the process for assessing inherent risk in clients through a systematic approach of questions. The system can store up to 99 risk areas, each containing 99 questions, which are assigned point scores for "Yes" and "No" answers. It details steps for editing, adding, and deleting risk areas and questions, including interface navigation and confirmation prompts. Additionally, it emphasizes that once numbers are assigned to risk areas or questions, they cannot be changed. The document serves as a guide for managing inherent risk assessments effectively.
Audit Risks
This document details the functionality of CCH Audit Automation for recording Identified Audit Risks, also referred to as Significant Business Risks. It provides instructions for users to add, edit, and manage risks, including features for maintaining risks for future audits, assessing their significance, and linking them to assertions. The system includes tools for risk assessment, audit response, and documenting conclusions. Other functionalities encompass risk summarization, printing options, and risk linkage across multiple sources, enhancing the audit process's efficiency and accountability.
Default Specific Risk Questions
CCH Audit Automation allows users to define specific risk questions for audit areas, although it's not mandatory. If no specific questions are set, default questions will be used. Users can edit the default questions through the "Specific risk questions" option in the Risk Model section. Up to 99 default questions can be defined, similar to inherent risk questions. The system utilizes a lookup table that combines specific and inherent risks for audits, with editing instructions provided in the manual.
Risk/Sample Selection
This document outlines the concept of audit risk, defined as the likelihood of undetected material errors during an audit. It introduces a risk model used in Audit Automation that requires total audit risk to remain below acceptable levels across various audit areas. The risks are broken down into inherent risk, control risk, and detection risk, with further subdivisions for detection risk. It emphasizes the importance of understanding these concepts to design effective audit procedures and assess risk at different levels. Additionally, it discusses general and control environments, and the calculation of residual risk, alongside a risk scoring system.
Inherent Risks
The document outlines the procedure for addressing inherent risk questions in an audit context. Users can access a dedicated window to view up to 99 risk areas, answer questions, and modify responses as necessary. The system prompts users to validate changes to ensure proper risk assessments. It includes functionalities for viewing prior comments, copying text, and overriding calculated risk levels, emphasizing that auditor judgment is crucial. Comments on overrides must be provided to rationalize any adjustments made. The document serves as a guide for navigating and utilizing the auditing software effectively.