When applying the audit update to your engagement files it is important to note the following points:
- For rolled forward engagement files, we suggest applying the update immediately before any work has commenced on the file that could result in documents and procedures being signed off.
- For in progress engagements, please ensure that the 315 content is required for this engagement before updating as the changes are irreversible. Ensure you create a backup of the engagement file.
- For any engagement file that you are applying the Audit 24 update to, if there are any documents that are signed off or procedures within documents that are signed off, these will be skipped during the update to prevent your work being overwritten.
If you find that your engagement is still prompting for an update after you have already applied it, we suggest you follow these steps to identify the documents causing the prompt and to make sure that your file has in fact been updated.
Identifying that the update has been applied and your file is on Audit version 24
When the update bubble appears prompting for an update, click on it to review the recommendations.
When the update is first applied to the file, the recommendation will start by listing Content as the first part of the update and it will show the current version (23 in this screenshot) and the template version (24)
This is how you know that the update has not been applied to this file as it is still on version 23. Click the Yes button and select the relevant profile on the next screen and start the update.
Once the update has completed one of two things will happen depending on the original state of your engagement file.
- The file is updated and no updates are available when clicking the check for updates button
- The file has been updated to Audit 24 but there is still a prompt to apply updates
The second scenario is what we will focus on now.
Confirming the update has run and identifying the documents that were left out
After running the update and the update bubble still appears we need to point out a few things first to ensure the correct understanding.
When you click on the update bubble now it will likely be a shorter list of documents than before and WILL NOT SHOW "Content" as an option as seen in the previous screenshot
It is important to pause here to understand two things.
- The update has been applied successfully and your engagement file is on Audit 24 and you will be able to add in documents from the library. The update has not failed and your file is not broken.
- These documents have been skipped for a reason and it is either that they have been signed off on the document level, or there are procedures within these documents that are signed off
The reason we skip signed off documents and procedures is that we do not want to replace documents and procedures that are already completed with new ones from our library.
The list of documents in the check for updates dialog will list out all of the documents that were skipped so you know what to look at.
From here it is entirely your call as to if you update these documents or leave them as they are with signoffs intact.
If you choose to update these documents/procedures then you will need to remove the signoffs associated to the documents and procedures.
Once the signoffs are removed from the procedures and documents, click on the update bubble or the check for updates button and go through the update process again, it will be a faster process as it is just picking up these remaining documents.
When that update completes, assuming you removed all signoffs from documents and procedures then the documents will all have their content updated and you will see this message when checking for updates