The Internal Audit Lifecycle, Part 3: Communicating Value – Reporting Audit Findings Effectively.
- David Tyler
- Apr 22
- 6 min read
Welcome back to the ASD Consulting blog and our series exploring the internal audit lifecycle. In our previous post (Part 2), we delved into the fieldwork stage – the critical phase where our teams gather evidence, conduct testing, and identify observations. Now, we transition to the crucial step that translates that diligent work into tangible impact and valuable assurance: Reporting Audit Findings Effectively.
Think of reporting not as merely documenting what was found, but as the strategic communication channel through which internal audit delivers value. A well-executed audit can fall flat if its findings and recommendations are not clearly, concisely, and persuasively communicated to the right stakeholders. This post will explore the nuances of reporting, from the initial discussions with management to the formal presentations to the Audit Committee.
From Fieldwork to First Draft: The Internal Audit Report Takes Shape: Upon concluding fieldwork, the audit team shifts its focus to synthesising the gathered evidence and observations into a cohesive narrative – the draft audit report. This is where the findings are formally documented, supported by the work performed.
A typical internal audit report structure is designed for clarity and impact:
Executive Summary: A concise overview of the audit's purpose, scope, key findings (especially high-risk items), overall conclusion/assurance level, and the report's significance. This is often the only section some senior readers will review in detail, so it must be impactful.
Background and Objectives: Provides context for the audit, explaining why the area was selected and what the audit aimed to achieve.
Scope and Methodology: Clearly defines the boundaries of the audit, the period covered, and the approach taken. Transparency here builds confidence in the audit's conclusions.
Detailed Findings and Recommendations: This is the core of the report, detailing the specific observations, their implications, and proposed actions.
Management Responses and Action Plans: Documents management's agreement with the findings, their planned actions to address them, responsible parties, and anticipated completion dates.
Drafting requires objectivity, precision, and clarity. Findings must be directly supported by the evidence gathered during fieldwork. The language used should be professional, neutral, and focused on facts and observed conditions, rather than opinions.
The Crucial Conversation: Discussing the Draft with Auditees: One of the most vital steps in the reporting process is discussing the draft report and its findings with the management team responsible for the audited area (the 'auditee'). This meeting, sometimes referred to as the 'clearing' or 'vetting' meeting, serves multiple critical purposes:
Validate Accuracy: It provides management the opportunity to confirm the factual accuracy of the report's content and the completeness of the findings. Were all relevant details considered? Is the evidence correctly interpreted?
Ensure Understanding: It ensures management fully understands the findings, their root causes, and the potential risks or consequences.
Foster Collaboration: It transforms the process from an investigative exercise into a collaborative effort towards improvement. Internal Audit brings the independent perspective; management brings operational context and feasibility.
Solicit Management Responses: This is the platform for management to formally agree to the findings (or provide their perspective if there's disagreement, which is then documented) and develop practical action plans to address the identified issues.
A key principle here is the "no surprises" rule. While formal discussion happens with the draft report, effective auditors maintain open communication with auditee management throughout fieldwork, potentially discussing emerging observations informally as they arise. This builds trust and makes the formal discussion of the draft report a constructive conversation, not a confrontation.
The outcome of these discussions is the incorporation of management's formal responses and action plans into the report. This demonstrates management's commitment to addressing the findings and forms the basis for future follow-up.
Crafting Findings That Matter and Recommendations That Work: The heart of the report lies in its findings and recommendations. To be effective, findings should clearly articulate the issue, its context, and its significance. A common structure, often referred to as the "4 C's," is highly effective:
Criteria: What should be? (e.g., policy requirements, regulatory standards, best practices, management's own procedures).
Condition: What is? (e.g., the actual process observed, the control weakness identified, the deviation from criteria).
Cause: Why did it happen? (e.g., lack of training, unclear policy, insufficient resources, system error, control override). Identifying the root cause is crucial for developing effective recommendations.
Consequence (or Risk): What is the impact or potential impact? (e.g., financial loss, regulatory non-compliance, reputational damage, inefficient operations, increased fraud risk). This articulates the "so what?" and justifies the need for action.
Recommendations must directly address the root cause identified in the finding. Good recommendations are:
Actionable: Clearly state what needs to be done.
Practical: Feasible within the business's operational context, resources, and budget.
Specific: Avoid vague language; define the required outcome.
Prioritised: Clearly indicate the relative importance or risk level associated with the finding and recommendation. This helps management focus their efforts.
Recommendations should empower management to improve their processes and controls, not dictate prescriptive, rigid solutions. Internal Audit suggests the what; management, leveraging their operational expertise, determines the how.
The Formal Output: Issuing the Final Audit Report: Once management responses are incorporated and any factual differences are resolved (with differing views documented where necessary), the report is finalised. The final audit report is the formal, official record of the audit engagement. It is typically issued to the head of the audited function and copied to relevant senior management. This report serves as the formal communication of the audit's results and the agreed-upon actions. It also acts as the baseline document for the subsequent follow-up process, which we will discuss in our next post.
Reporting to the Apex: Communicating with Senior Leadership and the Audit Committee/Board: While the detailed report goes to the audited function's management, reporting to the Audit Committee and the Board of Directors requires a fundamentally different approach. This audience needs strategic insight, not operational detail.
Reporting to the Audit Committee typically involves:
Focus on Significant Risks: Highlighting findings related to high-risk areas, critical control weaknesses, or matters with significant potential impact on the organisation's objectives.
Aggregated and Thematic Reporting: Presenting results from multiple audits to identify patterns, recurring issues, or systemic weaknesses across different business units or processes. This provides a holistic view of the control environment.
Overall Assurance Levels: Providing an opinion or conclusion on the adequacy and effectiveness of controls within the audited areas or across the organisation (depending on the scope of the reporting).
Effectiveness of Risk Management and Governance: Commenting on the maturity and effectiveness of the organisation's risk management framework, governance processes, and internal control system based on audit observations.
Key Insights and Observations: Offering value-added insights that go beyond specific findings, perhaps highlighting emerging risks, industry trends impacting controls, or opportunities for significant process improvement.
Matters Requiring Committee Attention: Drawing attention to issues where Internal Audit believes the Audit Committee's oversight, guidance, or intervention is required (e.g., insufficient resources for remediation, resistance to implementing agreed actions, significant disagreements on findings).
Reporting at this level must be highly concise, forward-looking, and focused on supporting the Committee and Board in fulfilling their oversight responsibilities. It provides them with independent assurance and critical information for strategic decision-making regarding risk and control.
Hallmarks of Effective Audit Reporting
Regardless of the audience, effective internal audit reporting shares common characteristics:
Clarity: Easy to understand, free of jargon, logical flow.
Conciseness: To the point, avoiding unnecessary detail without sacrificing accuracy.
Timeliness: Issued promptly after fieldwork completion to ensure findings are relevant and action can be taken swiftly.
Accuracy: Factually correct and supported by evidence.
Objectivity: Unbiased, fair, and balanced presentation of findings and management's perspective.
Constructiveness: Focused on providing value and facilitating improvement, even when identifying difficult issues.
Impact: Clearly articulates the significance of findings and motivates stakeholders to act.
Conclusion: Reporting is Where Value Crystallises: Reporting is far more than just the final written output of an audit. It is the essential process through which internal audit's work gains meaning, drives necessary change, and provides vital assurance to management and the Board. Effective reporting builds credibility strengthens relationships with stakeholders and underscores internal audit's role as a valuable partner in enhancing the organisation's control environment and achieving its strategic objectives.
Having communicated our findings and agreed upon action plans, the internal audit lifecycle moves to its final, critical stage: following up to ensure agreed-upon actions are implemented effectively. Join us for the next post as we explore the importance of the follow-up process in closing the loop and ensuring sustained improvement.
Comments