When Audit Findings Repeat but Accountability Never Changes

Repeat audit findings

Here’s a common scenario: an internal audit identifies overdue monthly reconciliations. Management agrees to introduce a checklist, provide refresher training, and monitor compliance. The actions are completed, supporting evidence is submitted, and the finding is closed. But only six months later, the same weakness appears in another internal audit. It can sometimes feel like a game of Whac-A-Mole.

Imagine that the reconciliations are being missed because the finance team faces reporting deadlines that leave insufficient time to complete them properly. The finance manager has raised the problem, but changing the timetable requires approval from senior management.

The checklist was implemented, and the training took place, yet neither changed the circumstances that caused the original failure.

For internal auditors, this example raises an uncomfortable possibility: the organization may have successfully completed its corrective actions without actually resolving the underlying problem.

Three Reasons an Audit Finding Keeps Coming Back

A repeated audit finding doesn’t automatically indicate that management has failed to take the original recommendation seriously. There are several possible explanations, and they call for different responses.

The simplest is that an agreed action was never implemented properly. A revised procedure may exist, but staff are not following it consistently. Additional testing, supervision, or training might resolve the issue.

Another possibility is that the action was implemented but was never capable of addressing the root cause. Management may have introduced an extra approval step when the real difficulty was an impractical workflow. The additional control creates work without preventing further failures.

The third possibility is more difficult. Management understands the problem, but resolving it requires a decision that has not been made.

In the reconciliation example, senior management may need to change reporting deadlines, redistribute responsibilities, or accept additional costs. Those choices may affect other business priorities, which helps explain why the original arrangements have survived. Sending the finance team another recommendation won’t change a timetable it has no power to set.

The Institute of Internal Auditors’ Global Internal Audit Standards address this issue. Standard 14.4 requires internal auditors to determine an appropriate approach to recommendations or action plans that addresses the root cause, among other objectives.

Revisit the Evidence Behind Closed Findings

Internal audit teams can learn a great deal from examining a handful of findings that were previously considered resolved, only to surface again.

Select three or four recurring findings from the past two audit cycles. Compare the original recommendations with the evidence used to close them and the control failures subsequently identified.

Suppose management agreed to introduce a monthly review. The closure evidence shows that a review template was developed and circulated. That establishes that the action was implemented, but it does not tell the whole story.

Did the reviews actually take place? Were exceptions identified and resolved? Was performance maintained after the initial period of increased scrutiny? The answers help establish whether implementation failed or whether the intervention itself was insufficient.

Standard 15.2 of the IIA’s Global Internal Audit Standards requires internal auditors to confirm implementation through an established methodology, including risk-based follow-up assessments. The extent of that work should reflect the significance of the finding.

The review should also examine what management knew when the action was agreed. If a department had already explained that the proposed solution was unlikely to work without additional resources, that information deserves attention. It may reveal that the audit action was agreed because it was achievable within the department’s existing authority, rather than because it offered a credible long-term solution.

The Action Owner May Not Be the Decision-Maker

Organizations often allocate audit actions to the manager responsible for the process where a weakness was found. Usually, that makes sense. The manager understands the work and is best placed to implement improvements.

Difficulties arise when responsibility for fixing a problem is separated from authority over the conditions causing it. A department head may be expected to improve compliance while having no control over staffing levels. An operations manager may be accountable for a failing process but unable to change the policy governing it. A senior executive may insist on tighter controls while retaining performance targets that make compliance difficult.

In some cases, managers are doing exactly what their roles allow. The problem is the gap between what they’re held responsible for and what they can actually change. A job description may name an accountable manager, but the real test is what happens when that manager needs another department to change course.

Internal auditors can examine the decisions made after a weakness was identified. Was a request for additional resources rejected? Did the issue reach the executive with authority to change the policy? Was a proposed solution postponed because of competing priorities? If so, who considered the consequences?

That record can show whether an action was assigned to someone without the power to deliver it, or whether an executive made a conscious decision to retain the risk. An action owner who cannot make the necessary decision is not the same as an action owner who refuses to act. Treating those situations alike can leave the original problem untouched while placing more pressure on the wrong person.

What Thematic Reporting Should Reveal

Recurring findings are often reviewed individually because they sit within different internal audit engagements, departments, or reporting periods. Looking across them can expose a problem that no single audit adequately captures.

Consider three hypothetical findings: departing employees retain system access longer than permitted, supplier checks are not consistently refreshed, and contract renewals occur without timely approval. Each could have its own corrective action, assigned manager, and completion deadline.

Further investigation might reveal that all three weaknesses arise when responsibility moves between teams. Nobody has clear authority to ensure that important handovers are completed, and each department assumes another team is responsible for initiating the necessary checks.

The audit committee needs to see that connection, not three separate updates marked “in progress.” Internal audit can explain the relationship between the findings, the evidence supporting it, and the organizational decision required.

The committee should also understand what remains unresolved. Has management agreed who will own the handover process? Are responsibilities formally delegated? Is there a mechanism for resolving disputes between departments?

Similar findings aren’t proof of a common cause, however. The connection needs evidence, not just matching descriptions in an audit report.

Give the Audit Committee a Decision to Scrutinize

If an audit committee has seen the same finding three times, another progress update adds very little. It needs to know who can remove the obstacle, what they have decided, and why the weakness remains unresolved. That might involve accepting additional expenditure, changing an established policy, or reallocating responsibilities between senior managers.

Internal audit should be able to explain the governance implications of those choices without taking responsibility for making them.

For example, a report could identify that a recurring control failure depends on a change to a centrally imposed reporting timetable. It could explain the operational impact of the current arrangement, document management’s response, and identify the executive responsible for deciding whether the timetable should change.

The audit committee can then challenge that decision and the reasoning behind it. It should not become responsible for redesigning the timetable itself. Internal audit provides independent assurance and insight; management owns the response to identified risks.

Where disagreement concerns the acceptance of significant risk, the IIA’s Standard 11.5 on communicating the acceptance of risks establishes an escalation process. If the chief audit executive (CAE) concludes that management has accepted risk exceeding the organization’s risk appetite or tolerance, the matter must be discussed with senior management and escalated to the board if it remains unresolved. That is an escalation route for serious unresolved risk, not a routine response to every repeated finding.

Before Agreeing on Another Action Plan

Some recurring findings are straightforward control failures. Others persist because an organization has not addressed the management arrangements surrounding those controls.

Before accepting another corrective action, one question is worth pursuing: Which management decision would have to change to prevent this finding from returning? If the answer sits with someone other than the assigned action owner, that is where the next conversation should begin.  Internal audit end slug


Glenn Oborne is a Director at Ingen Partners, a UK-based specialist governance recruitment and consultancy firm. His work focuses on governance leadership, organizational capability, succession and senior governance appointments.

Leave a Reply

Your email address will not be published. Required fields are marked *