- Plan an engagement with a documented risk assessment, objectives, scope and criteria
- Build a work program that meets Standard 13.6
- Evaluate and rate findings using root cause and significance
- Draft a final communication that meets Standard 15.1 and set up follow-up
Planning (Principle 13)
Communicate early. Standard 13.1 requires internal auditors to communicate the objectives, scope and timing to management and to tell management promptly about later changes.
Engagement risk assessment. Standard 13.2 requires an understanding of the activity under review: its strategies, objectives and risks, the organization’s risk tolerance if set, the risk assessment behind the plan, the governance, risk management and control processes, and the frameworks or criteria that apply. Then identify potentially significant risks, consider fraud risks specifically, and prioritize them. If a prior engagement already identified the risks, a review and update is enough.
Objectives and scope. Standard 13.3 requires documented objectives and a scope that names the activities, locations, processes, systems, time period and other elements covered. Scope limitations (for example, restricted access to data or people) must be discussed with management, and if unresolved, the CAE takes them to the board. The CAE approves the objectives and scope and any changes during the engagement.
Criteria. Standard 13.4 requires the most relevant criteria. If management’s criteria are adequate, use them; if not, identify appropriate criteria with the board or senior management. For a SOX-related engagement, the criteria are usually the control descriptions in the RCM and the COSO framework the company uses for its ICFR assessment.
Work program. Standard 13.6 requires a documented work program that identifies the criteria for each objective, the tasks, the methodologies including analytical procedures and tools, and the auditors assigned to each task. The CAE must review and approve the work program before it is used and approve later changes promptly.
Fieldwork (Principle 14)
Gather information that is relevant, reliable and sufficient, compare the condition to the criteria, and document potential findings. Standard 14.3 requires internal auditors to evaluate each potential finding for significance, to collaborate with management to identify root causes when possible, to determine potential effects, and to consider likelihood and impact. A significant risk exposure must be documented and communicated as a finding. Findings are prioritized using the CAE’s methodology.
Standard 14.6 requires documentation that would let an informed, prudent internal auditor repeat the work and reach the same results. Internal auditors and the engagement supervisor review it, and the CAE approves it.
Reporting (Principle 15)
Standard 15.1 requires a final communication for each engagement that includes objectives, scope, recommendations or action plans where applicable, and conclusions. For assurance engagements it must also include:
- the findings with their significance and prioritization;
- an explanation of any scope limitations;
- a conclusion on the effectiveness of the governance, risk management and control processes reviewed.
It must name the individuals responsible for addressing findings and the planned completion dates, acknowledge actions management already took, be reviewed and approved by the CAE before issue, and go to parties who can ensure the results get due consideration.
Follow-up
Standard 15.2 requires internal auditors to confirm implementation using an established method: inquire about progress, perform risk-based follow-up assessments, and update a tracking system. If management misses dates, internal auditors obtain and document an explanation and discuss it with the CAE, who decides whether senior management has accepted a risk beyond tolerance. Under Standard 11.5, unresolved unacceptable risk goes to senior management and then to the board.
A finding that holds up
Write each finding with the four elements reviewers expect:
- Criteria: what should happen (policy, control description, regulation).
- Condition: what you found, with numbers.
- Cause: the root cause agreed with management.
- Effect: the risk or impact, tied to significance.
Then the recommendation or management action plan, owner and date.
Vendor master data engagement at Elmstead Foods, Inc.
Objective: determine whether controls over changes to vendor bank details prevent unauthorized payments. Scope: all vendor master changes January 1 to June 30, 2026, in the ERP system, U.S. entities only. Criteria: the vendor maintenance policy requiring call-back verification to a known number and independent approval.
Risk assessment: the team rates payment diversion fraud as the top risk. The CAE approves a work program with four tasks: walkthrough, full-population data analysis of 1,240 vendor changes, inspection of call-back evidence for 40 bank detail changes, and a review of approver access.
Results: 6 of 40 bank changes had no call-back evidence; data analysis shows 3 changes approved by the same user who requested them.
Evaluation under Standard 14.3: root cause, agreed with the AP manager, is that the ERP workflow allows requester and approver to be the same user, and call-backs are logged in email only. Effect: a reasonable likelihood of diverted payments with high impact. Rating: high.
Final report: objectives, scope, the two findings with rating, the conclusion that controls over vendor bank changes are not effective, actions (configure workflow segregation by September 30, 2026, owner IT applications lead; add a call-back field, owner AP manager). The CAE approves and issues it to the CFO and audit committee chair. Follow-up testing is scheduled for November 2026.
Self-check
Answer each question before you open the answer.
Who must approve the engagement work program, and when?
Show answer
The chief audit executive, before it is implemented, and promptly when changes are made (Standard 13.6).
What three items must an assurance engagement’s final communication include in addition to objectives, scope, actions and conclusions?
Show answer
The findings with their significance and prioritization, an explanation of any scope limitations, and a conclusion on the effectiveness of the governance, risk management and control processes reviewed (Standard 15.1).
What documentation standard does Standard 14.6 set?
Show answer
Documentation that would let an informed, prudent internal auditor, or similarly competent person, repeat the work and reach the same results, reviewed by the supervisor and approved by the CAE.
Management misses an action plan date. What happens next?
Show answer
Internal auditors obtain and document an explanation and discuss it with the CAE, who determines whether senior management has accepted a risk that exceeds tolerance (Standard 15.2), escalating under Standard 11.5 if needed.
Use it on the file
- TemplateInternal Audit Program Template
- GuideWriting Internal Audit Findings: Criteria, Condition, Cause and Effect Under Standard 14.3
- GuideWhat an Internal Audit Final Report Must Contain Under Standard 15.1
- GuideInternal Audit Follow-Up: Confirming Action Plans Under Standard 15.2
Sources
- The IIA, Global Internal Audit Standards (condensed edition, issued January 9, 2024)
- The IIA, Global Internal Audit Standards (domains, principles and standards)
Standards are paraphrased from the primary sources listed above; read the source before relying on a requirement. This lesson is training material, not professional advice. Report an error