Appearance
Add a control
Also known as
- new control
- edit control
- control design
- control objective
- evidence requirements
- test frequency
- key control
- manual control
- automated control
- IT-dependent
Use this form to add a control to the library or change its design: objective, type, test frequency, owner and the evidence a tester needs.
Add a control
- Open ComplianceControls and select New control.
- Under Control, enter the Name, the Process, the Owner, the Objective and a Description.
- Under Design, choose the Type, Nature and Test frequency, describe the Evidence requirements and set when the first test is due.
- Turn on Key control if a failure of this control would be material.
- Leave Activate now on to make the control active at once, or turn it off to keep it as a draft.
- Select Add control.
The control gets the next number (CTL-0026 …) and opens on its detail page.
Edit a control
- Open the control and select Edit.
- Change the fields and select Save control. Activate now is not shown when you edit; use Activate on the detail page.
Fields
| Field | What to enter | Required |
|---|---|---|
| Name | What the control does, such as "Three-way match before vendor payment". Up to 200 characters. | Yes |
| Process | The business process, for example Procure to pay or Record to report. | No |
| Owner | The person who performs or answers for the control. | No |
| Objective | The risk the control addresses and what it achieves. | No |
| Description | How the control is performed. | No |
| Type | Preventive (stops errors), Detective (finds them) or Corrective (fixes them). | Yes (default Preventive) |
| Nature | Manual, Automated or IT-dependent. | Yes (default Manual) |
| Test frequency | Daily, Weekly, Monthly, Quarterly, Semi-annual, Annual or Ad hoc. After each test the next test is due one period later. | Yes (default Quarterly) |
| Evidence requirements | What a tester must collect, such as "signed reconciliation and bank statement". | No |
| Next test due | The date of the first or next test. | No |
| Key control | On for key controls. An ineffective test of a key control raises a Material weakness. | Default off |
| Activate now | New controls only. On: the control is active and scheduled for testing. Off: it stays a draft. | Default on |
If you leave a required field empty, you see "This field is required".
Differences by role
- You need Permission:
compliance.control.manageto add and edit controls.
