The defaults are illustrative. Replace every example observation and treat the calculated rating as a draft before partner, CAE or audit committee review.
| Ref | Cycle | Observation title | Condition | Financial impact | Likelihood | Control weakness | Recurrence | Compliance | Pervasiveness | Score | Suggested | Override | Override rationale | Approved by | Approval date | Owner | Status | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 23/30 | High | |||||||||||||||||
| 20/30 | Medium | |||||||||||||||||
| 11/30 | Low |
IA-001: IA-001 is rated High on a score of 23/30. Main drivers: financial impact, likelihood, control weakness, pervasiveness.
IA-002: IA-002 is rated Medium on a score of 20/30. Main drivers: control weakness, recurrence.
IA-003: IA-003 is rated Low on a score of 11/30. No individual driver is scored 4 or 5.
Use this after the control gap register or sampling plan, then move final ratings into the observation report pack.
An issue rating matrix helps internal audit apply consistent severity logic across observations. It should consider impact, likelihood, control weakness, recurrence, compliance sensitivity and pervasiveness, not only the rupee value of an exception.
The suggested rating should remain reviewable. If the auditor overrides the score, the report file should retain why the rating changed and who approved the judgement.
This generator creates an editable scoring matrix, rating rationale sheet and audit committee summary. It is useful for P2P, O2C, R2R, H2R, treasury, inventory, compliance, ITGC and continuous monitoring observations.
A P2P review identifies that bank portal approvers are not matched to the ERP authority matrix. Financial impact, likelihood, control weakness and pervasiveness are all high enough to drive escalation.