Audit Findings, Reporting, and Follow-up on Recommendations
This domain tests how raw exceptions become structured findings and how recommendations are reported and tracked to implementation.
Finding structure
- Condition: what is.
- Criteria: what should be, drawn from law, contract, standard, or program passport.
- Cause: why it happened.
- Effect: money, service impact, or risk.
- Recommendation: addresses the cause, is specific, measurable, assigned, and time-bound.
Reporting and follow-up
- Report structure: objective, scope, methodology, findings, conclusions, recommendations, and management responses.
- Materiality determines what enters the report; significant noncompliance is reported even when small in amount.
- Follow-up tracks implementation and escalates non-implementation.
Worked example
Finding: 12 contracts for office furniture, each 9 million tenge, awarded to the same supplier within one month. The criterion is the procurement law’s prohibition on artificial splitting. The cause is lack of annual procurement plan control. The effect is reduced competition and possible overpayment of 8 million. The recommendation is to consolidate annual demand, reconcile plan against contracts, and investigate the 8 million. Follow-up after six months checks whether the reconciliation control operates, not merely whether a memo was written.
Traps
- Writing “must comply” without fixing the cause.
- Mixing the audit opinion with findings.
- Closing a recommendation on receipt of a response rather than evidence of implementation.