Skip to main content

The internal audit process has four stages: planning, fieldwork, reporting and follow-up. In planning you set the objectives and scope, understand the business and schedule the work. In fieldwork you walk through the process, map its risks and controls in a risk and control matrix (RCM), and test the key controls with evidence. You then agree the findings, issue the report with management’s action plans, and later follow up to confirm the actions were taken. An audit of one department typically takes about two weeks of work.

Key points

  • Plan from the department’s own objectives: audit objectives, then scope, then risks and controls.
  • Spend time on planning and the walkthrough. Done well, they are half the audit.
  • The RCM is the backbone of fieldwork: it decides what you test and how.
  • Every conclusion needs evidence, and work not documented is work not done.
  • Discuss findings with the auditee as you go, so nothing in the report is a surprise.
  • An audit is not complete until the follow-up confirms the agreed actions were implemented.

The internal audit process at a glance

Stage Steps Main output
1. Planning Annual risk-based plan · scope and objectives · understand the business · plan and schedule · kick-off Audit plan, schedule, kick-off email, information request
2. Fieldwork Process walkthrough · risk and control matrix · gather information and evidence · sample and test · discuss queries Walkthrough notes, RCM with test results, working papers, agreed queries
3. Reporting Draft observations · exit meeting · management responses and action plans · issue the report Final internal audit report with action plans
4. Follow-up Track actions · obtain status · verify implementation · report the results Follow-up report; open items escalated

Stage 1: Planning the internal audit

Start from the annual audit plan

The internal audit function’s charter, approved by the audit committee, sets its mission, authority and scope as a whole. Each year the Chief Audit Executive prepares a risk-based annual plan: the list of auditable areas (the audit universe), rated by risk, with the higher-risk areas audited more often. Each individual audit, or engagement, then gets its own plan. In India, section 138 of the Companies Act 2013 requires certain companies to appoint an internal auditor, and the audit committee or board typically sets the scope and frequency of the work.

Define the objectives and scope

Start with what the department itself is trying to achieve, then align the audit objectives with it. For a procurement audit, the objectives might be:

  • compliance with procurement policies and procedures
  • effective supplier selection and evaluation
  • cost efficiency and timeliness of purchasing
  • identifying risks such as fraud, delays or weak supplier management.

The scope then states what will be examined (for example policies, vendor selection, contracts, purchase orders and payment terms), the period, the locations, the deliverables and anything excluded.

Understand the business before you audit

Study the organisation and ownership structure, the industry and regulations, applicable laws, products and services, key processes, financial performance and the control environment. Read the previous internal audit reports and working papers: the tests performed, the results, repeat issues and corrective actions. Collect key statistics such as revenue, inventory, and the number of customers, vendors and employees. Many teams record all this in a short “client understanding” document.

Plan and schedule the audit

List the areas to cover, set the time frame, allocate team members by expertise, and arrange access to the ERP and reports. Draft the initial risks and controls from the policies or the previous audit file. Communicate the scope, timeline and information needed to the department head, managers, finance and other process owners before fieldwork starts.

Open the audit: kick-off email and meeting

Send a kick-off email that states the start date and duration, the objectives and scope, the agenda for the opening meeting, the information needed and by when, and how observations will be discussed during the audit. Ask for a single coordinator on the auditee’s side, and ask the auditee to acknowledge the email: that confirms the timelines on both sides. Schedule the kick-off and walkthrough meetings four or five days ahead if you can, so the data is ready when fieldwork begins.

Worked example: a 10-day procurement audit plan

Days Work Meetings
1–3 Planning, document collection, data requests Kick-off meeting (day 1)
4–6 Process walkthrough; testing controls for design and operating effectiveness Walkthrough meeting (day 4)
7–9 Drafting findings; discussing them with the auditee Exit meeting (day 9)
10 Finalising the audit report

Work is split by area (for example, Auditor A: policy compliance and vendor selection; Auditor B: contracts, purchase orders and delivery; Auditor C: payments and reconciliation), but the team is jointly responsible for the whole audit and shares what it has found at the end of each day.

Stage 2: Fieldwork

Walk through the process

A walkthrough shows you how the department really works, where the key risks and controls are, and where the design is weak. Interview the process owners at each level, read the policies, study the main expense heads, and follow a transaction from start to finish. Ask about the purpose of each step, who does and approves it, exceptions, records and documents, systems, monitoring reports and compliance requirements. Write it up as a narrative or a flowchart, and confirm your understanding with the process owner.

Build the risk and control matrix (RCM)

The RCM is the backbone of the audit. For each objective it lists the risks, the controls that address them, and for each control its type (preventive or detective), method (manual or automated), frequency, whether it is a key control, and how you will test it. See our guide on how to build an internal audit checklist, with what to cover in 36 processes. For a worked example, row by row, see our RCM example for accounts payable.

Gather information and evidence

Track every information request, extract data from the ERP yourself where you can, and reconcile it to the books before you rely on it. Evidence must be:

  • reliable: from an independent or system source rather than a document the auditee could edit
  • relevant: it actually supports the conclusion you are drawing
  • sufficient: enough of it, spread across the period, for reasonable (not absolute) assurance.

Verbal explanations are not evidence. If no document exists, say in the report that the point is based on discussion only.

Sample and test

Test each key control for design (would it work?) and operating effectiveness (did it work, every time?). Choose samples with materiality and risk in mind, using random, systematic or stratified sampling, or test 100% of the population with data analytics where you can. Add analytical tests: ratios, trends, correlation, reconciliations and benchmarking, and data mining, for example invoice rates above the purchase order rate, or orders still open months later. Record each result in the RCM: the deviation rate, the control rating and the residual risk.

Discuss queries as you go

Send the auditee your queries with the evidence and analysis in advance, and discuss them in short, regular meetings rather than one long meeting at the end. Listen. If they show you missed something, correct your finding. If you still disagree, escalate. Every query should close with an agreed, achievable action.

Golden rules of fieldwork

  • Focus on internal controls and the areas of highest risk; when time is short, cover the high-risk areas and critical controls first, and record why.
  • Stay objective, even with senior or intimidating auditees.
  • Back every finding with evidence, and document processes as you go.
  • Watch for conflicts of interest, your own and the auditee’s.
  • Be flexible, but record any change of scope and get it approved.
  • Manage your time, and ask for extensions early, not on the due date.
  • Raise queries with confidence, and have your work reviewed before reporting.

Document everything in working papers

Work not documented is work not done. Working papers show the evidence for every conclusion, let your reviewer and the next auditor follow your work, and defend it if it is challenged. Keep base data untouched, and organise the file into planning; report and output; data from the system; data from the department; working sheets; and reference material. Document at once when you download a report, inspect something physically, receive a verbal response, change the plan, sample, test, or conclude on a finding.

Stage 3: Reporting

Draft observations during fieldwork, each with the criteria, condition, root cause, risk and recommendation. Hold an exit meeting to agree the findings, obtain management’s responses and action plans (with owners and target dates), and issue the report, with a one- or two-page executive summary, within a few weeks of fieldwork. Our guide to the internal audit report format covers this stage in detail, with a worked observation.

Stage 4: Follow-up

An audit is not complete until the agreed actions are implemented. For each follow-up review:

  1. Plan it from the action tracker: which actions are due.
  2. Obtain the status from the auditee, with evidence.
  3. Assess whether the action taken actually addresses the root cause.
  4. Verify implementation by testing enough samples, not by accepting a confirmation email.
  5. Report the results, and escalate overdue or ineffective actions to the audit committee.

You can support the auditee during implementation, for example by explaining what good looks like, but the auditee owns the fix. That keeps your independence intact.

How long does an internal audit take?

It depends on the size and risk of the area. As a guide, an audit of one function such as procurement takes about ten working days for a small team, as in the plan above, plus time for follow-up later. Larger or multi-location audits take several weeks. Whatever the length, a good share of the effort goes into planning and the walkthrough; if they are done well, the testing and reporting go much faster.

Adapting the process to the organisation

  • Size and complexity: larger organisations need a more formal plan, a bigger RCM and more sampling; a small business may combine steps, but should still plan, test with evidence, report and follow up.
  • Industry and regulation: banks, insurers and listed companies have specific regulatory requirements that shape the scope.
  • Risk profile: spend the time where the risk is highest. A risk-based plan means not every area is audited every year.
  • First audit of an area: with no previous file, derive the objectives, risks and controls from the policies and from good practice for that process, and have a senior review them.

📄 Get the template

Procurement: Risk and Control Matrix (Excel). 19 controls (11 key) for 10 objectives and 12 risks, each with walkthrough questions, evidence to ask for and test steps.

✅ Test yourself

Questions from our course quizzes. Click a question to see the answer.

When planning a procurement audit, where should the audit objectives come from?

From the procurement department’s own objectives. The audit objectives are aligned to them, then the scope, then the risks and controls.

During a walkthrough, the auditee explains a key step verbally but provides no documents. What should you do?

Ask for supporting documents. If none exist, state clearly in the report that the point is based on discussion only. Verbal information can be denied later.

Midway through the audit, management asks you to examine an extra area that is not in the scope. What should you do?

Record it, escalate to your seniors, and get formal approval for the change in scope and any extra days before the deadline.

Frequently asked questions

What are the steps of the internal audit process?

Planning (objectives, scope, understanding the business, scheduling and kick-off), fieldwork (walkthrough, risk and control matrix, evidence, sampling and testing, query discussion), reporting (observations, exit meeting, action plans, final report) and follow-up (verifying that actions were implemented).

How do you conduct an internal audit step by step?

Agree the scope and objectives, understand the process, send a kick-off email and data request, walk through the process, map its risks and controls in an RCM, test the key controls with samples and analytics, discuss findings as you go, issue the report with action plans, and follow up.

What is the difference between the audit plan and the audit charter?

The charter is approved by the audit committee and sets the mission, authority and scope of the internal audit function as a whole. The annual plan lists which areas will be audited in the year, and each engagement then has its own plan with objectives, scope and schedule.

How long does an internal audit take?

An audit of one function typically takes around two weeks of fieldwork and reporting for a small team, plus a later follow-up. Larger or multi-location audits take longer.

What documents does an internal audit produce?

The engagement plan and kick-off email, walkthrough notes or flowcharts, the risk and control matrix with test results, working papers with evidence, the audit report with management action plans, and the follow-up report.

Related reading: Internal audit checklist: build your own, plus 36 by process · Internal audit report: format, key parts and writing tips · Internal audit interview questions and answers

Zehra Maccawala

Author Zehra Maccawala

Zehra Maccawala (ACA, CIA) is a co-founder of Learn Internal Audit and a partner at ZMAS and Associates, a Chartered Accountancy firm specialising in internal audit. She has more than 20 years of experience evaluating business processes and conducting risk-focused operational and financial audits.

More posts by Zehra Maccawala

Leave a Reply