/
Audit Summary Report | What are the Standard logics used in the Audit Summary Report?

Audit Summary Report | What are the Standard logics used in the Audit Summary Report?

Owned by amani imtiyas (Unlicensed)
Last updated: May 27, 2022
2 min read

  1. Completed Actions – The logic applicable to identify recommendations as ‘Completed’ is as follows: 

  • The report must check for any recommendations for which the  ‘Action Status = ‘Completed’’ AND ‘Internal Audit Sign Off’ (Standard field: InternalAuditSignOff) is TRUE in order for those to be considered as ‘Completed’ 

2. In Progress Actions – These are the Audit Recommendations which are NOT past their due date and are yet to be completed. Therefore, in order to categorize a recommendation as ‘in progress’, 

  • First, the Due date (agreed implementation date) must be compared with the current system date. By default, 1st agreed implementation date will be considered as the due date. If ‘Use last agreed implementation date’ tick box is ticked, then it will consider the last agreed implementation date for the logic) 

  • Secondly, if this agreed implementation date is a date on or after the current system date, and the Recommendation is NOT completed according to the above-mentioned logics, then it must be considered as ‘in progress’ 

3. Overdue Actions – These are the Audit Recommendations which have passed their due date and are yet to be completed. 

  • Recommendations which are past their due date (agreed implementation date) and are NOT yet complete and Not Internally Signed Off would be considered as overdue recommendations. Therefore, in order to categorize a recommendation as ‘overdue’, 

  • Due date (agreed implementation date) must be compared with the current system date 

  • By default, 1st agreed implementation date will be considered as the due date. If ‘Use last agreed implementation date’ tick box is ticked, then it will consider the last agreed implementation date for the logic 

  • If the agreed implementation date is a date before the current system date and the Recommendation is NOT completed and also the recommendation has not yet got the Internal Audit Sign Off, then it is considered as ‘overdue’ 

4. Deferred actions - These will be the actions which has a status selected as ‘Deferred '  

Note: If the internal setting “Enable Synchronisation Of Progress Information For Risk Action And Audit Action” is assigned with Boolean value ‘True’ then the logics mentioned above should be applicable to the traffic light field. However, if the Boolean value is ‘False’ then the following logics should be applicable to the traffic light field. 

5. Off Track actions –  

  • The report must check for any recommendations for which the ‘Audit Action Status’ ≠ ‘Completed’ OR ‘Deferred’ AND Recommendation Completion Date < Current System Date then those to be considered as ‘Off-Track’ 

6. Monitor actions –  

  • The report must check for any recommendations for which the ‘Audit Action Status’ ≠ ‘Completed’ OR ‘Deferred’ AND Recommendation Completion Date > Current System Date then those to be considered as ‘Monitor’ 

7. On Track actions –  

  • The report must check for any recommendations for which the ‘Audit Action Status’ = ‘Completed’ OR ‘Deferred’ then those to be considered as ‘On-Track’ 

8. If the audit recommendation does not belong to either one of the logics mentioned above (5,6,7) it will pull audit action status into the traffic light column.  



Related content