A compliance framework includes conforming to requirements. In an organization it is achieved by taking into account applicable requirements (defined by laws, regulations, contracts, strategies and policies), assessing the state of compliance, costs and risks of non-compliance against the projected expenses to achieve compliance, and hence prioritize, fund and initiate any corrective actions deemed necessary.
Compliance data is defined as all data belonging or pertaining to enterprise or included in the law, which can be used for the purpose of implementing or validating compliance. It is the set of all data that is relevant to a governance officer.
The Compliance system contains the Compliance/accreditation requirements linked to the company policies, Standard Operating Procedures (SOPs) and appropriate checklists.
All the reporting is visible within the system and can be accessed as pre-defined reports which can be fed to the corporate level for monitoring and control of compliance.
The Dynamics 365 Compliance module provides the user with the ability to capture all the information required to manage the above. The flow is depicted below.
For a more formal approach the user can activate the “Internal audit focus” on the parameters form. Do this by adding a user group in the Internal audit field, Compliance bullet tab. This will then add a dedicated object – “Audit project”. See the Wiki page for Internal audits.
In order to create a Nonconformance, Quality management has to be enabled
Go to: GRC > Setup > Governance, Risk and Compliance parameters
The Item number and Problem type fields have to be populated
Go to: GRC > Internal audit > Setup for internal audit > Problem types
Users can select rules to be used when internal controls (such as ISO clauses) are audited and scored for effectiveness and conformance.
Go to: GRC > Setup > Governance, Risk and Compliance parameters
In the example above, the Top threshold for yellow indicator is set on 6 and the Bottom threshold for yellow indicator is be set on 4 because the Expected score is 10.
To enable Internal audit functionality, users will have to be a member of the selected user group.
Under the Scoring mechanism Fast tab, you can do the following:
1. Use the simple Yes/No tick box for compliance scores
2. Use Compliance dropdown
|
|
3. Choose to Use manual scores
This is useful for RAG (Red, Amber, Green) type scoring.
Users select email templates to use for sending email notifications.
From a compliance perspective, users will create and link an email template here for audit notifications, for example an engagement letter to be sent to a department to notify them of an upcoming audit.
Go to: Organisation administration > Setup > Organisation email templates
Remember to setup a Case category of type Audit to use when recording an audit issue.
Go to: GRC > Governance > Setup for governance > Case categories
By selecting roles for the Case category type security, only users with these roles assigned to them, will have the privilege to create a New contract request/Request for contract review.
Go to: Organisation administration > Setup > Cases > Case category type security
Ensure Dynamics 365 GRC module Base data or Lookup data are created as follows:
Please note that Dynamics 365 includes a Content Wizard that creates relevant static data and information for the user. This includes, amongst others, a generic list of Hazards.
Alternatively, users can manually create the base data.
Go to: GRC > Risk > Setup for risks > Control status and effectiveness
Users can define risk categories. One of these, Inherent risk, is used in the Compliance function setup.
The inherent risk ratings that are defined on this form will be used in the Compliance function form when the risk % is entered per clause line.
Further down the line, users can use these to filter and audit high risk clauses or controls.
Go to: GRC > Risk > Setup for risks > Risk configuration
Compliance groups, group individual Compliance functions together and carry rules for time-based audits, i.e. scheduling of future audits.
Go to: GRC > Compliance > Setup for compliance > Compliance group
Related functions to be audited will automatically be displayed in the bottom grid.
Users must define types of audits. This is imperative as the type of audit will guide D365 GRC to add or remove functionality. In specific internal audit functions differ from compliance type (ISO etc.) audits.
Go to: GRC > Compliance > Setup for compliance > Audit type
Evaluation | Compliance |
---|---|
Blank Major NC Minor NC Observation Strength |
Blank Full Partial Not applicable Zero |
- If a team is not selected here, individual compliance clause lines cannot be assigned to a Planned user to audit (See Step 4.3 below)
- If no scoring method is specified on the Audit type, the scoring method specified on the Parameters will be used
- These values default to the scope of the Area of compliance
Go to: GRC > Compliance > Setup for compliance > Audit findings category
The Audit findings category can be selected on the Non-conformances under the Findings menu item
Go to: GRC > Setup > GRC actions and questions
The Question text is the text that is displayed on the Declaration of interest dialogue on the Audit file.
A question must have an Answer type:
The response to the question is set by the Negative outcome setting:
The audit team, including specialists engaged to assist with the audit, is required to collectively possess the knowledge, skills, and experience necessary to carry out the audit effectively.
Selecting audit team members is an important part of the preparation stage.
Go to: HSE > Setup > Work force > Teams
Start with the lower level, referred to as Compliance functions and the related
Clauses (i.e., requirements placed on an organization)
Then go back to the top: Area of Compliance |
The Clauses Fast tab contains the requirements (things to be checked and scored during the audit). They form the lowest level of the Area of Compliance. When doing fieldwork, users will score and mark whether the requirements have effectively been met.
Users can add an Inherent risk percentage against each line.
Go to: GRC > Compliance > Compliance function
The two calculation options are explained:
The inherent risk rating which corresponds with the Risk register lines, is used for this calculation
The average of the risk in the Clause lines corresponding with the selected Compliance function, is displayed in the Risk rating% column when this calculation function is selected
Where a risk register does not exist, the inherent risk will be calculated by using the data in the Impact and Likelihood columns as factors
When a Compliance audit is selected on the Operational risk register lines, under the Associations Fast tab, the details are displayed under the Risk Fast tab
Go to: GRC > Compliance > Area of compliance
A responsibility assignment matrix describes the participation by various roles in completing tasks or deliverables for an audit.
An email can be sent to the selected workers under the RACI field group, if they have a Primary email address
The scope of a compliance audit is a statement that specifies the focus, extent, and boundary of a particular area. The scope can be specified by defining the physical location of the compliance audit, the organizational units that will be examined, the team and activities that will be included, as well as the budgeted time proposed to execute the audit.
In the Header view:
In the Lines view:
The user has to be a member of the Team selected as described above
If the functions have been setup with ISO section and ISO clause details, these lines will be copied into the grid above.
Also note that the displayed Requirements and scores are linked to the function that is selected in the Functions and standards Fast tab above
If changes have been made to the clauses on the Compliance function form, click on the Refresh button in the button strip to update the lines in the Requirements and scores Fast tab on the Area of compliance
The purpose of a compliance audit is to provide independent assurance that an organization’s risk management, governance and internal control processes are operating effectively.
Enterprises require scheduled audits (compliance scores) to be created based on user specific frequency rules, or users can create ad-hoc audits
Both these are supported in Dynamics 365 GRC
Go to: GRC > Compliance > Compliance function
The scheduling Period frequency will be displayed (it can be changed)
The last date when a schedule for this Area of compliance was run is displayed, as well as next date that a scheduled score has to be completed by.
Go to: GRC > Create schedules
The Site and Department must be the same site and department selected on the Area of compliance
Users can ALSO go to the Area of compliance and choose to EXCLUDE certain functions from an audit
Go to: GRC > Compliance > Area of compliance
On the Scheduling dialogue that opens:
If the Scheduling period on the Area of compliance is different to that on the Compliance function, a yellow line with a warning message will appear across the screen.
The system will use the scheduling period as set up on the Area of compliance.
Go to: GRC > Compliance > Schedules > All audit schedules
The status is important:
- A scheduled audit has to be Approved for it to become an audit
- Only Approved records can be used to create new audit files and allow users to enter audit fieldwork
- When the status is Approved, the Created, Scheduled and Approved buttons will be unavailable to the user
- When the status is Created, the schedule can be deleted
- Approved audits cannot be deleted
Details of a scheduled audit can be changed while the status is Created.
Go to: GRC > Compliance > All compliance audit files
On the new Audit file:
If the last two steps are not done, the Audit file cannot be selected for the posting of scores
- To send an email to users selected under Administration, click on the email icon next to the relevant name
- The selected worker must have a primary email address
It is advisable to create the Audit file before starting with the audit process, as the compliance scores and Findings will be posted into the Audit file
Go to: GRC > Compliance > All compliance audits
The following buttons will be disabled when the record is closed:
The Audit file has to have a status of Started before it can be selected for the posting of findings and scores
The capacity load of the selected audit can be calculated according to the budgeted hours
Go to: GRC > Compliance > Schedules > All audit schedules
The capacity load of the selected audit can be re-calculated by clicking on the Calculate button on the Action pane
Go to: GRC > Compliance > All compliance audits
- One audit will be created with schedule of type Manual
- The audit Status will be Approved
- An Audit file for the audit will be created
- One audit can have many audit files
Go to: GRC > Compliance > All compliance audits
To view all the Audit files for the selected compliance audit:
There is also a list page view of all the Compliance audit files
Go to: GRC > Compliance > All compliance audit files
A closed Audit file can be re-opened if:
- The user is a member of the Admin user group
- The Audit is open
Auditors must identify, analyze, evaluate and document sufficient information to achieve the audit engagement’s objectives. This includes assisting the organization in maintaining effective controls by evaluating their effectiveness and efficiency, and by promoting continuous improvement.
Engagement findings and recommendations emerge by a process of comparing what should be with what is. Whether or not there is a difference, the auditor has a foundation on which to build the report. When conditions meet the criteria, applicable test programs would have been marked as “Effective” and as such no findings will be raised. However, in cases where the conditions do not meet the criteria, audit findings will be raised, taking into consideration any issues to be reported verbally based on their materiality.
Audit findings will be raised as and when the individual test programs are completed and reviewed by the audit manager. This is done in two ways; Dynamics 365 can log a formal (more serious) non-conformance or just log an issue via the Issue register.
The results and scores of assessments being done are recorded inside GRC 365.
- Only Approved audits via its referenced Area of compliance can be selected.
- The same applies for Site and Department, only those that exist in an approved audit are selectable.
If these have not been specified on the approved audit, the fieldwork cannot be posted.
Go to: GRC > Compliance > Periodic > Compliance scoring
If the Compliance function is not selected, the scoring cannot be posted
The user can choose which columns to see in the left-hand side grid by clicking on the Show button in the Action pane and moving the relevant sliders to Yes
When doing the scoring, users can use the Inherent risk percentage to filter and focus on high-risk clauses
These values will be used when Activities are created
- The Department selected on the Scoring form header will be used on the Issue register
- If no scoring method is specified on the Audit type, the scoring method specified on the Parameters will be used
Findings are the results of an evaluation of the collected audit evidence against audit criteria. Findings can indicate conformity or nonconformity with audit criteria, or opportunities for improvement.
The Compliance function can be linked to external ISO standards and must have a unique name and a description. These Compliance functions form the basis for creating the Area of compliance.
Results (Compliance column and observations) can be posted to an Audit file
The lines from of the selected improvement plan will be displayed
When the fieldwork is posted, a pop-up will ask the user if a checklist should be created form the existing Improvement plan
When the Audit file is selected, the dialog will change adding a display of the Audit name, Audit type and the name of the Assessor (Responsible Worker on the audit)
If the logged in user is not the same as the assessor associated with the selected audit, a warning will prompt the logged in user to confirm that he/she still wants to continue with the scoring
Activity features allow you to create appointments, notes, and tasks.
If you want to send someone a reminder, you can create a task and assign it to anyone in the organization. The task will then show up on their activity list, and also pop up as a reminder in Outlook (if you have the synchronization enabled).
Go to: GRC > All planned Governance, Risk and Compliance actions
Go to: GRC > Compliance > All compliance audit files
To view the Activity that was created:
Go to: Common > Activities > All shreq activities
AND
Go to: GRC Workspace > All open actions
Go to: GRC > Compliance > All compliance audit files
Go to: GRC > Compliance > Reports and Inquiries > Completed compliance scores
If there is a tick next to a record in the Latest column, it means that the system has done a check on the following and has marked the latest record
- Company (legal entity)
- Audit name
- Area of compliance
- Function
- Site
- Department
The Compliance scores detail form will open, displaying the details of the selected record
Users can choose to record findings:
- Raise a non-conformance inside Dynamics or,
- Report an issue in the Compliance audit issue register if the outcome is less critical and of lesser significance
Note that these outcomes are counted and recorded as findings
To view the average score per Site, based on the Departments under the Site:
To view the corrections that were created for the non conformances when the scoring form was posted:
Go to: GRC > Compliance > Findings > Non conformances
To print the Audit correction report:
Go to: GRC > Compliance > Findings > Non conformances
The loop is closed in that the last posted score is sent back to the Area of complaince
Go to: GRC > Compliance > Area of compliance
Based on the threshold values specified under the GRC parameters and on the Audit type, Dynamics will fill in the Compliance indicator value
While the Audit team collects information and does its observations, they can choose to raise non-conformances or create less critical issues. These are collectively referred to as Audit findings.
Go to: GRC > Compliance > Reports and inquiries > Compliance audit findings
- A list of all Issues that have been created can be viewed: GRC > Compliance > Findings > Compliance audit issue register
- A list of all Non conformances can be viewed: GRC > Compliance > Findings > Non conformances
Go to: GRC > Compliance > Reports and inquiries > Audit RAG report
OR
Go to: GRC > Compliance > All compliance audits
Go to: GRC > Compliance > Reports and Inquiries > Audit findings per ISO standard report
Go to: GRC > Compliance > Reports and Inquiries > Audit findings per ISO standard graph
Go to: GRC > Compliance > Reports and Inquiries > ISO audit report
Go to: GRC > Compliance > Reports and Inquiries > Area of compliance report