Glossary · Audit & Assurance
Root Cause Analysis in Internal Audit
Definition
Root cause analysis in internal audit is the step of finding the underlying reason a control failed or a problem occurred, rather than stopping at the symptom. Its purpose is a recommendation that removes the cause, so the same finding does not come back next year.
At a glance
- Category
- Audit & Assurance
- Main provision
- Section 138, Companies Act 2013
- In this entry
- How it works in an audit Where the law or the standard sets it · A simple example
In detail
01 How it works in an audit
A symptom is what the auditor sees: unapproved payments, stock differences, late filings. The root cause is why it happened. Fixing a symptom, for example getting the missing approvals signed after the event, leaves the cause in place.
Common methods:
- Five whys: ask "why?" repeatedly until the answer is something the business can change.
- Cause categories: sort possible causes into people (skills, workload), process (unclear or missing steps), systems (no automated control), and governance (no ownership, wrong incentives).
- Pattern review: look across findings in several units; a cause that appears everywhere is usually a policy or system issue, not one person's error.
Good root cause analysis is done with the process owner, not about them. The goal is agreement on the cause, which makes the action plan easier to agree.
The provision
02 Where the law or the standard sets it
No law requires root cause analysis. Where internal audit is required under section 138 of the Companies Act 2013, read with Rule 13 of the Companies (Accounts) Rules 2014, its findings reach the audit committee or board, and root causes make those findings actionable. Rule 13 requires it for every listed company, and for unlisted public and private companies whose previous year's turnover was ₹200 crore or more or whose bank or public financial institution borrowings exceeded ₹100 crore at any point. An unlisted public company is also covered at paid-up capital of ₹50 crore or more or deposits of ₹25 crore or more. ICAI's Standards on Internal Audit, issued by its Internal Audit Standards Board, cover reporting of findings. As at November 2026 they are recommendatory: the ICAI Council has not notified a date from which they become mandatory.
Worked example
03 A simple example
An example, not advice on your facts.
Finding: 14 GST input credit claims were reversed in the year because supplier invoices did not match the government portal.
Why? The invoices were booked before the supplier had uploaded them.
Why? Accounts payable books invoices on receipt to meet payment terms.
Why? There is no step to check the portal before claiming credit.
Why? The month-end checklist was written before the matching requirement and was never updated.
Root cause: an outdated month-end procedure (process). Action: add a portal-matching step before credit is claimed, and assign an owner to review the checklist every year.
In detail
04 Why it matters to a company
Repeat findings are the clearest sign that root causes were not addressed. Asking "what caused this?" before agreeing a fix costs a little time in the audit and saves the same problem, and the same audit point, next year.
Need help with root cause analysis in internal audit? See our Internal Audit Service.
Review and sources
Sources: ICAI Compendium of Standards on Internal Audit (as on 1 Oct 2022), Preface.
