Continuous Monitoring
Monitors check every record of a period, such as every approval, payment and reconciliation, against a control's rules, from the records Muin already holds, instead of a sample.
A monitor tests a control against every record in a period, not a sample. It reads the records Muin already holds, so there is nothing to upload. Monitors show on the framework’s Tests tab under the Monitored view.
Sources
| Source | Records read |
|---|---|
| AP invoice approvals | Paid vendor bills of the period |
| Expense approvals | Finance expense documents and volunteer expenses approved in the period |
| Bank reconciliations | Reconciliations finished in the period and their review sign-off |
| Payroll runs | Payroll runs paid in the period and their approval |
| Grant spend | Grant disbursements and allowability decisions of the period |
What a monitor checks
- Approver differs from submitter. The person who entered a bill or expense must not approve it.
- Approved before paid. Approval must come before payment.
- The approval left an audit event. A missing audit event is an exception, never a pass.
- A reconciliation was signed off. A finished reconciliation with no sign-off recorded is an exception.
- A cost is allowable. A grant cost blocked or not yet assessed is an exception.
A volunteer expense approved automatically by policy has no approving person, so separation of duties is marked not applicable with that reason. It is not counted as a pass.
Runs and results
Each run records how many records it read, every exception, and the result. Click Run now to run a monitor for a period you choose, and Show exceptions to see each one with its reason.
| Result | Meaning |
|---|---|
| Pass | Every record met every rule |
| Fail | At least one exception |
| No data | The records could not be read; the run names the reason |
No data is never treated as a pass.
Alerts
The control owner is alerted when a monitor moves into a failed result, not on every failed night, so a control that stays broken does not page every day. Choose who is told and how from Alert settings (/compliance/alert-settings).
A monitor run can also be used as the population of a control test, so a failed monitor leads straight into a test and, if it fails, a deficiency.