Control Testing
Test your key controls the way an auditor does: load the population, draw a seeded sample, record each attribute, and sign off with a reviewer who is not the preparer.
A control test checks whether one key control worked during a period. You load every record the control should have acted on (the population), draw a sample, record a result for each attribute of each sample, and send the test to a reviewer. Control testing is part of Compliance Pro.
Where tests live
| Place | What you do there |
|---|---|
Tests tab on a framework (/compliance/frameworks/:id?tab=tests) |
Plan, run and sign off tests of that framework’s key controls. Filter the list by All tests, Planned or Monitored. |
Control Tests (/compliance/control-tests) |
Every test across your frameworks, with framework and status filters. |
Test workspace (/compliance/control-tests/:id) |
One test: objective, population, sample, results and sign-off. |
Click New test, pick a key control, set the period start and end, the test type (Operating effectiveness or Design) and a reviewer. You prepare the test, so the reviewer must be someone else.
Objective, procedure and conclusion
Every test carries three written parts:
- Objective: what the test checks.
- Procedure: how you tested. Put each attribute on its own line. The sample table tests each line as an attribute.
- Conclusion: what the sample showed.
Editing any of them on a returned test moves it back to draft.
Population
The population is every record the control should have acted on during the period. Two sources:
- Upload CSV: a
.csvup to 5 MB. Therecord_refcolumn is required;amountandoccurred_atare optional. Rows that cannot be read are listed with the row number and the reason; the rest load. - From Muin: load records Muin already holds, such as AP invoice approvals, expense approvals, bank reconciliations, payroll runs and grant expenditures.
Sample
Pick the method: Random, Haphazard, Top N by amount or Judgmental. A random draw is seeded. The workspace shows the seed, and drawing again with the same seed gives the same sample, so your reviewer and your auditor can reproduce it.
For a judgmental sample, list one record ref per line; the count must equal the sample size. A record flagged on the Insights Spend flags tab can be sent to a draft test with Use in a control test.
Default sample sizes
The default comes from the control’s frequency. The higher-risk column applies when a risk linked to the control scores 15 or more.
| Frequency | Normal | Higher risk |
|---|---|---|
| Annual | 1 | 1 |
| Quarterly | 2 | 2 |
| Monthly | 2 | 3 |
| Weekly | 5 | 10 |
| Daily | 25 | 40 |
| Many times a day | 25 | 60 |
A compliance manager can change these in Settings > Compliance > Sample sizes (/settings/compliance). Each size is a whole number from 1 to 500, and the higher-risk size cannot be below the normal size. A preparer can test fewer items than the default only with a written reason.
Recording results
The sample table shows one row per sampled record and one column per attribute. Mark each cell Pass or Fail. A failed cell needs a note that says what was wrong. Automated checks and audit events Muin found for the record show in the Checks column.
Sign-off
Click Submit for review when every part is in place. Muin refuses a submit that is missing the objective, procedure, conclusion, result, a sample (for operating effectiveness tests) or a result for any sample, and names what is missing.
Each step signs in order. The preparer’s submit is the attestation; the reviewer then approves or returns the test with a note. If your workspace has an approval rule for control tests, its steps follow the reviewer.
| Rule | What happens |
|---|---|
| The preparer cannot review | “You prepared this test; another reviewer must sign” |
| An agent cannot sign | “An agent drafts tests; a person signs them” |
| A returned test | Goes back to the preparer with the reviewer’s note |
| A signed-off test | Locked. Signed-off tests cannot be changed. |
A test signed off with a failed result creates a deficiency. See Deficiencies.
Control Test Agent
On a draft test with a population loaded, Run Control Test Agent pre-fills attribute results with cited evidence. Cells it filled show Draft from agent and link the evidence. Anything it could not decide is listed with the reason. The agent never submits and never signs: a person reviews every cell and submits the test.
What your external auditor sees
An auditor invited through the auditor portal sees only signed-off tests of the framework they were invited to, with the sample and attribute results, and can download them as a PDF. Draft, submitted and returned tests are never listed.
Related
- Risk-control matrix: processes, risks and key controls
- Deficiencies: what a failed test leaves behind
- Continuous monitoring: test every record instead of a sample
- Evidence requests: ask control owners for evidence