Most of what internal auditors learn about your area, they learn by asking you. The planning interview shapes the scope, the walkthrough decides what gets tested, the follow-up questions decide which exceptions become findings, and the closing meeting decides how the findings read. For the person being interviewed, those conversations can feel like an examination with unknown rules. They are not. The questions are predictable, each one is aimed at something specific, and the answers that serve you best are the same ones that serve the audit: accurate, specific, and honest about what you do not know.
This guide explains the five kinds of conversation you may have with internal audit, sixteen common questions and what each is really testing, how to prepare in an hour, how to answer, an annotated walkthrough, what happens to what you say, how an investigation interview differs from an audit interview, and what to do if you know something is wrong. It is written for managers and for the people who do the work, who are the ones auditors most want to talk to. The whole engagement, from notification to follow-up, is covered in the site’s guide to what to expect during an internal audit.
In this guide
- Five kinds of conversation with internal audit
- Who gets asked what
- What auditors ask, and what they are really asking
- Preparing in an hour
- The planning interview, in detail
- How to answer
- A walkthrough, annotated
- The closing meeting: handling the conversation
- Questions you can ask the auditors
- Awkward situations, and how to handle them
- What happens to what you say
- When it is not a routine audit
- If you know something is wrong
- Remote interviews
- After the interview
- Questions people ask before being interviewed
- Related guides
Five kinds of conversation with internal audit
Knowing which conversation you are in tells you what the auditors want from it. The first four are part of any routine audit. The fifth is different in kind, and the section on investigations below explains how to recognize it.
| Conversation | Who usually attends | What the auditors want | Typical length | How to prepare |
|---|---|---|---|---|
| Planning or scoping interview | The manager of the area, sometimes their executive | How the process works, what has changed, what worries you, where the data lives | 60 to 90 minutes | A one-page description of the process as it runs today, recent changes, status of prior findings |
| Walkthrough | The person who performs the work, at their desk | To follow one real transaction end to end and find the steps that are not in the procedure | 30 to 90 minutes per process | The system open, access working, and the performer briefed that honest answers are expected |
| Fieldwork follow-up | Whoever knows the answer | An explanation of an exception or an anomaly before it becomes a finding | Minutes, often by email | The records for the specific item; an answer only when you know it |
| Closing meeting | The manager, their executive, the audit lead and manager | To confirm the facts behind each finding and discuss cause, rating and actions | One to two hours | Every fact checked against your records; evidence for any correction |
| Investigation interview | An individual, with investigators and often legal or HR | Facts about specific transactions or conduct | Varies | Different rules apply; see the section on investigations |
The walkthrough is the conversation that most unsettles people who do the work, and it is worth understanding why it is built the way it is. The auditor picks the transaction, not you, and will politely decline the clean example you offer. The auditor wants the performer, not the manager, because the aim is to find the steps that exist only in practice: the workaround when the system rejects an entry, the colleague who covers during leave, the spreadsheet between two systems. A workaround found in a walkthrough is usually a design observation that can be fixed; the same workaround found later in a failed sample is a finding. The auditors’ side of the exercise is in the site’s guide to process walkthroughs.
Who gets asked what
Auditors choose whom to interview by what each person can tell them. The manager knows why the process is designed as it is; the performer knows how it actually runs; the executive knows what the business is trying to achieve and what worries it; the system owner knows what the technology enforces and what it merely allows. Expect different questions depending on which of those you are, and prepare accordingly.
| Role | What the auditors mostly ask about | What to have ready |
|---|---|---|
| Executive sponsor | Objectives, strategic changes, the risks that concern leadership, how performance is measured | The two or three things you would most want assurance on |
| Manager of the area | Process design, changes, staffing, known problems, prior findings, how you monitor the process | A process overview, a list of changes, the status of open actions, the reports you review |
| Performer | The steps as done, exceptions and workarounds, backups, what the system does and does not check | The system open and a live transaction; nothing else |
| Reviewer or approver | What you look at, your thresholds, what you do when something looks wrong, how you record the review | Examples of reviews where you questioned something, and what happened |
| System owner or IT contact | Configuration, access, changes, interfaces, reports and their logic | Configuration screens, the access list, the change log for the period |
Reviewers are the group most often caught out. A reviewer who says “I look over it and sign” has described a signature, not a review, and the auditors will then test whether the review could have caught anything. A reviewer who can say “I compare it to last month, investigate anything over five percent, and here is the query I raised in March” has described a control, and the conversation moves on.
What auditors ask, and what they are really asking
Audit questions sound open and casual. Each one is aimed at a specific kind of risk or control, and knowing the target lets you answer the real question instead of the literal one. The sixteen below cover most of what you will hear in planning interviews and walkthroughs.
| The question | What it is testing | A good answer includes |
|---|---|---|
| “Walk me through what happens when a new one comes in.” | The process as it actually runs, compared with the procedure | Every step, including the ones you do by habit and the ones not written down |
| “What happens if the system rejects it?” | Workarounds and manual overrides | What you actually do, who approves it and where it is recorded |
| “Who covers when you are out?” | Key-person dependency and segregation of duties | The named backup, and whether they have the same access |
| “How do you know it’s right?” | Whether a review or detective control exists | The check, who performs it, how often and what evidence it leaves |
| “Can you show me?” | Evidence, as opposed to description | The screen, the record or the document, not a restatement |
| “What’s changed in the last year?” | Risks introduced by new systems, people or volumes | A plain list, including changes that went badly |
| “What keeps you up at night?” | Risks management already knows about | Your honest top two or three; a risk you name is one the audit can help with |
| “Has anything gone wrong recently?” | Incidents, near misses, customer complaints | What happened, what you did and what changed afterwards |
| “Who else can approve this?” | The delegation of authority and whether it is followed | The approval matrix as it really works, including informal delegates |
| “What reports do you use to do this?” | Reliance on information produced by systems | The report names, where they come from and whether anyone checks them |
| “Where is that kept?” | Evidence retention | The actual location, even if it is someone’s inbox |
| “Why is it done this way?” | Whether a step has a purpose or is a relic | The reason, or “I don’t know, it was like this when I started” |
| “What would happen if this step were skipped?” | Whether the step is a key control | What would go wrong and whether anything later would catch it |
| “Do you ever feel pressure to process things faster?” | Behavioral risk: targets and pressure that bend controls | An honest answer; the auditors are looking at the design of targets, not at you |
| “Is there anything we should know that we haven’t asked?” | Your chance to disclose | Anything you know is wrong, with what is being done about it |
| “Who else should we talk to?” | Where knowledge sits in the team | The people who actually know, not the most senior ones |
Preparing in an hour
Interviews go best when the person being interviewed has spent an hour getting ready, and worst when they have spent a week rehearsing. Preparation is about having the facts to hand, not about having answers scripted. For a planning interview or a walkthrough, the hour looks like this.
| Minutes | What to do |
|---|---|
| 10 | Read the audit’s objective and scope from the notification, so you know what the conversation is for |
| 15 | Walk through your own process mentally, step by step, and note where it differs from the written procedure |
| 10 | List what has changed in the last year: systems, people, volumes, vendors, policies |
| 10 | Check the status of any actions from the last audit, with dates |
| 10 | Gather the documents and reports you use, and make sure you can open the systems the auditor may want to see |
| 5 | Note what you do not know and who does, so you can say so and point to the right person |
The planning interview, in detail
The planning interview is the conversation with the most influence over the audit and the one managers most often treat as a formality. The auditors arrive with a draft view of the risks and leave with a scope; what you say in between shapes where fieldwork concentrates. A typical planning interview covers the ground below, usually in this order.
| Part of the interview | What the auditors are trying to learn | How to use it |
|---|---|---|
| Objectives of the area | What the process exists to achieve and how success is measured | State the objectives plainly; the audit will assess controls against them |
| Process overview | The main steps, systems, teams and volumes | Walk it end to end, including the parts done outside the main system |
| Changes | New systems, people, products, vendors, volumes since the last audit | Be complete; changes are where risk concentrates, and a change you mention is not a surprise later |
| Known problems and concerns | What management already knows is weak | Disclose what you know and what you are doing about it |
| Prior findings | The status of actions from earlier audits | Have the dates and the evidence ready |
| Data and reports | What populations exist and how to extract them | Name the reports and the people who can run them |
| Timing and contacts | When fieldwork can happen and who to talk to | Flag month-end, peak season and planned leave now, not in week three |
Before the interview ends, ask the auditors two questions: why the area is in this year’s plan, and what they are most concerned about. A good audit lead will answer both, and the answers tell you where the fieldwork will concentrate. The site’s guide to how audit plans choose what gets audited explains the scoring behind the first answer.
How to answer
Eight habits cover almost every situation, and they are the same habits that make you credible in any conversation where facts matter.
- Answer the question asked, then add the context. A direct answer followed by the explanation is clearer than a history of the department that arrives at the answer eventually.
- Separate fact from opinion. “The review happens monthly” is a fact the auditor will test; “I think it works well” is an opinion, and should be labeled as one.
- Say “I don’t know” when you don’t. Then say who does, or that you will find out. A guess that turns out wrong is remembered longer than an honest gap.
- Show rather than tell. If the answer is on a screen or in a file, open it. Evidence ends a line of questioning; description prolongs it.
- Describe what actually happens, not what should happen. The auditor will find the difference anyway, and hearing it from you makes it a design question rather than a surprise.
- Correct yourself afterwards if you got something wrong. A short email the same day is normal and appreciated.
- Speak for yourself. Describe your own work and what you have seen; do not guess at colleagues’ motives or speak for another team.
- Disagree plainly if you disagree. “I don’t think that’s right, and here’s why” is a professional answer. Silence in the room followed by an escalation afterwards is not.
A walkthrough, annotated
Here is part of a typical walkthrough in accounts payable, a composite rather than a transcript, with a note on what each exchange is doing. Notice how ordinary it is. Nothing in it is a trick; the auditor is building a picture of the process as it really runs, and the clerk’s plain answers, including one “I’m not sure”, are exactly what a good walkthrough needs.
| Auditor | Accounts payable clerk | What is happening |
|---|---|---|
| “Could you pick up the next invoice in your queue and process it as you normally would?” | “Sure. This one’s from our packaging supplier.” | A live item chosen from the queue, not a clean example chosen for the auditor |
| “Where did it come from?” | “The shared invoices inbox. I scan it in.” | The entry channel: who can put documents into the process |
| “What does the system check when you enter it?” | “It matches it to the purchase order and the goods receipt. If they agree within tolerance, it releases it for payment.” | An automated control; the auditor will later ask IT for the tolerance setting |
| “And if they don’t match?” | “It goes to an exception queue. If the difference is small, under five hundred, I can override it and add a note.” | An override path, and the performer approving their own override: a potential design issue, found openly |
| “Does anyone review the overrides?” | “I’m not sure. My supervisor might get a report. I’d have to check.” | An honest “I don’t know”, with a pointer to who does; the auditor will ask for the override report |
| “What about invoices with no purchase order?” | “Utilities and a few others. Those go to the department head by email and I attach the approval.” | A second process path, with approval evidence held in email |
| “Could you show me last week’s utility invoice and its approval?” | Opens the record and the attached email | Evidence shown rather than described; the question ends there |
| “Who covers for you when you’re away?” | “A colleague on the team. Same access as me.” | Backup arrangements and whether access is appropriate |
| “If you could change one thing about this process, what would it be?” | “The override limit feels high for what we buy.” | The performer’s risk insight, which auditors take seriously |
The walkthrough produced three things for the auditors to follow up: the tolerance setting, the override review, and approvals held in email. None of them was a finding yet, and the clerk’s candor about the override made it easier, not harder, for the audit to reach a fair conclusion about it.
The closing meeting: handling the conversation
The closing meeting is the one conversation where you are expected to push back, and the one where pushing back badly costs the most. The auditors present each potential finding: what they found, the criteria, the cause, the likely consequence and the proposed action. Your job is to confirm or correct each element with evidence. Sort anything you disagree with into one of three categories before you walk in, because each is argued differently: the facts are wrong (show the document), the cause is wrong (explain the real cause, with evidence), or the rating is too high (argue from the function’s written rating definitions). Mixing them, which is what happens when a finding is called “unfair”, produces a meeting in which nothing is resolved.
Two phrases do most of the work in a good closing meeting: “that fact isn’t right, and here is the record” and “we agree with the finding; the cause is slightly different, and it matters for the fix.” Two phrases do the most damage: “everyone does it that way” (which is true, and is the finding) and “we’ll take this up with your boss”. The guides to disagreeing with a finding and to writing the management response cover what comes next.
Questions you can ask the auditors
Interviews run both ways, and auditees who ask good questions get better audits. None of these is impertinent; a competent audit lead will answer all of them, and the Standards require the auditors to communicate the engagement’s objectives, scope and timing to management in any case.
- Why is this area in this year’s plan?
- What are you most concerned about?
- What will you test, and over what period?
- What will you need from us, and by when?
- How are findings and the overall report rated, and can we see the definitions?
- When will we see potential findings, so we can check the facts?
- How do we raise a disagreement if we have one?
- Who will receive the report, and in what form?
- How will actions be followed up and validated?
- Is there anything from other audits or other areas we should know about?
Awkward situations, and how to handle them
Some interviews come with complications that nobody prepares you for. The table covers the ones that come up most often, with the answer that serves both you and the audit.
| Situation | What to do |
|---|---|
| You are new in the role and the period being audited was before your time | Say so at the start, describe what you have seen since you arrived, and point the auditors to whoever ran the process before; you are not expected to explain decisions you did not make |
| Your account differs from your manager’s | Describe what you do and what you have seen, plainly; the auditors will reconcile the accounts with evidence, and they expect differences between how a process is described and how it is done |
| You are asked about a colleague’s work | Describe what you have observed and what you know, and say where your knowledge ends; do not speculate about reasons or motives |
| You made a mistake that the auditors are asking about | Acknowledge it, explain the circumstances, and say what has changed since; a mistake explained is a process issue, while a mistake concealed is a conduct issue |
| The question is in a language you are less comfortable in | Ask for the question to be rephrased, take your time, and ask for key points to be confirmed in writing; accuracy matters more than speed |
| You feel the conversation has turned into an accusation | Ask plainly what the conversation is for and whether it is still part of the audit; if it has become an investigation, the rules in the section on investigations below apply |
What happens to what you say
What you tell an auditor is inquiry evidence, the weakest kind on its own, so the auditors will corroborate it: inspect the record, observe the step, re-perform the check. That is not a sign they doubt you; it is how audit evidence works, and the site’s guide to audit evidence sets out the hierarchy. Interview notes are kept in the engagement workpapers, which is required documentation under the Global Internal Audit Standards. The auditors are also bound by the Standards’ confidentiality rules. Standard 5.2 requires them to respect the confidentiality and privacy of the information they gather and not to disclose it to unauthorized parties unless there is a legal or professional duty to do so.
Reports describe processes, roles and conditions, not who said what, and a finding does not usually quote an individual. If an interview produced a fact the auditors intend to rely on in a finding, you should hear about it before the report: Standard 14.3 requires auditors to work with management when they evaluate potential findings, on the causes, the effects and the significance. If something you said is being used, it is reasonable to ask to see how it has been summarized.
When it is not a routine audit
Everything above is about routine audits, which are the overwhelming majority. An investigation is different, and the signs are usually clear: the interview is unannounced, it is about specific transactions or specific people rather than a process, you are asked not to discuss it, and someone from legal, HR or an investigations team is present. The purpose is to establish facts about particular conduct, and different rules apply.
In the United States, when the organization’s own lawyers interview employees they commonly begin with what is known as an Upjohn warning, after the Supreme Court’s decision in Upjohn Co. v. United States (1981): the lawyers represent the organization, not you, and while the conversation is privileged, the privilege belongs to the organization, which can decide to share what you say. Most organizations’ policies require employees to cooperate truthfully with internal investigations, and it is never acceptable to alter or destroy records once you know an investigation is under way. If you are unsure of your position, it is reasonable to ask whether you should have your own advice; the answer depends on your jurisdiction and circumstances, and this guide is not legal advice. The audit function’s side of how investigations begin is in the guide to the first 48 hours after internal audit finds fraud.
If you know something is wrong
Sometimes the person being interviewed knows about a problem the auditors have not found. Tell them. The question “is there anything we should know that we haven’t asked?” is a genuine invitation, and a problem disclosed by the people closest to it is treated very differently from one discovered later: in most audit functions it is reported as management-identified, rated with the disclosure taken into account, and discussed as a process issue. If you would rather not raise it in the room, use the organization’s speak-up or whistleblowing channel. Retaliation for good-faith reporting is prohibited by most organizations’ policies and, in many settings, by law; in the United States, Section 806 of the Sarbanes-Oxley Act protects employees of public companies who report certain kinds of fraud, and the EU Whistleblower Directive requires larger organizations to maintain protected reporting channels.
Remote interviews
Many interviews and walkthroughs now happen over video, and a few practical points make them run as well as in person.
| Do | Why |
|---|---|
| Test screen sharing and system access before the call | A walkthrough is mostly screen sharing; a failed login wastes half the slot |
| Share the live system, not a slide or a screenshot | The auditor needs to see the process as it runs |
| Have the documents you expect to discuss open in another window | “Can you show me?” comes quickly |
| Keep your camera on and take the call somewhere quiet | Interviews are conversations, and they go better when both sides can see each other |
| Ask the auditor to confirm any document requests by email at the end | Requests made verbally on a call are the ones most often lost |
After the interview
Send anything you promised the same day or the next, correct anything you got wrong in a short email, and pass on the names of the people you suggested the auditors talk to. If a potential issue came up, ask what the auditors will need to evaluate it and send it, rather than waiting to see whether it becomes a finding. Answers given within a day are the difference between an exception explained during fieldwork and one that reaches the closing meeting. The guide to handling request lists covers how to keep the follow-ups organized.
Questions people ask before being interviewed
Can my manager sit in on my walkthrough?
Usually auditors prefer to see the performer alone, because managers tend to answer for their staff and the steps that only exist in practice go unmentioned. Managers are expected at the planning interview and the closing meeting. If you would feel more comfortable with someone present, ask the auditor; for a routine walkthrough a colleague who knows the process is rarely a problem.
Can I record the interview?
Ask first. Many jurisdictions require every party’s consent to record a conversation, and most organizations’ policies prohibit recording internal meetings without permission. If you want a record, ask the auditors to confirm the key points and any requests in writing afterwards.
Will the report say who said what?
Usually not. Findings describe processes, roles and conditions. The auditors are bound by confidentiality rules in the Standards, and a finding that depends on something you said will be discussed with management to confirm the facts before the report is issued.
Can I refuse to answer?
In a routine audit, internal audit’s access to personnel comes from its charter, approved by the board, and a refusal becomes a scope limitation the auditors report. If a question seems outside the audit’s scope, say so and ask what it is for; if it seems to be about your own conduct, it is reasonable to ask whether the conversation has become an investigation.
Related guides
- Being audited? — every guide for auditees and management, by stage of the audit.
- What to expect during an internal audit — the whole engagement from the auditee’s side.
- The PBC survival guide — the requests that run alongside the interviews.
- What not to say to your internal auditor — phrases that backfire, and what to say instead.
- Audit anxiety — coping when your work is being audited.
- When you disagree with a finding — what to do in the closing meeting.
- What internal audit can and cannot do — the authority behind the questions.
- Process walkthroughs — the auditor’s side of the walkthrough.
- How to Walk an Auditor Through Your Process — the walkthrough from the process owner’s chair: the two-hour prep, the one-page flow and the questions decoded.
- Walkthrough vs test of controls — what a walkthrough proves.
- Audit evidence — why auditors corroborate what you tell them.
- When internal audit finds fraud — how investigations begin.
- When Internal Audit Suspects Fraud in Your Area — what changes when an audit becomes an investigation, what to preserve, and what never to do.
- Audit interview techniques — the same interview from the auditor’s side of the table
- 60 Questions Internal Auditors Ask Process Owners — the questions by area, what each is testing, and what a good answer contains.
- The audit opening meeting — what the first meeting with the audit team covers
- Briefing Your Team Before an Audit — what to say, what not to script, and the three-minute talk.

Leave a Reply