AI can challenge an audit finding. It cannot own the conclusion.

AI output should be reviewed like a claim, not treated like evidence

The Institute of Internal Auditors' October 13 discussion of AI's ethical dimension puts the obligation in familiar terms: due professional care and critical thinking still apply when an auditor uses AI. A model may accelerate search, comparison, and drafting. It cannot inspect the world, assume the engagement team's authority, or accept responsibility for a conclusion.

This distinction matters because internal-audit findings are linked judgments. The criterion must actually apply. The condition must be supported by a complete or appropriately sampled population. The proposed cause must be more than a plausible story. The effect or risk must be stated with calibrated scope. The significance and recommendation must follow the organization's methodology. A fluent model can make every link sound stronger than it is.

Current practitioner discussions on r/InternalAudit show the tension directly: auditors are experimenting with AI while asking whether critical thinking is being outsourced. These threads are qualitative signals, not representative surveys, but they identify a real operating risk. Junior staff may produce polished workpapers before learning why a test is designed; reviewers may accept a structured narrative that masks a broken population or missing counterevidence.

The Global Internal Audit Standards make the human ownership concrete. Requirements around evaluating findings, developing engagement conclusions, and engagement documentation are not satisfied by generating plausible prose. The accountable team must retain enough support for a knowledgeable auditor to understand and reperform the work, exercise professional skepticism, supervise the engagement, and communicate appropriately.

Freeze the assertion before asking AI to challenge it

A vague prompt such as “review this audit finding” invites the model to fill missing context. Instead, create a versioned assertion record containing the exact criterion, condition, population, period, scope, exception count, cause, effect, significance, recommendation, source IDs, and unresolved review notes. Hash the input set and record the AI tool, model, prompt, date, and user.

Separate statement types. An observed fact might be “17 of 214 sampled privileged accounts lacked current approval records.” An executed calculation is the exception rate for that tested sample. A management representation is an owner's explanation. An auditor inference connects the facts to a proposed cause. A human judgment determines whether the evidence is sufficient and how the finding should be framed. Mixing these types is a common path from data to overclaim.

Do not give the AI more data than the task requires. Use the organization-approved environment, minimize personal and sensitive data, and replace identifiers when exact identities are not needed. Audit records may include investigations, legal advice, credentials, security weaknesses, health or employee information, and commercial secrets. Public chatbot convenience is not authority to disclose them.

Build an assertion-to-evidence matrix and a counterevidence register

Break the draft finding into atomic propositions. For each one, identify the evidence record, provenance, date, custodian, relevance, reliability, calculation, contradiction, limitation, and reviewer. If one paragraph contains five claims but cites one interview, the matrix makes the gap visible.

Then reverse the search. Ask what evidence should exist if the assertion is false or narrower than stated. Look for compliant cases, compensating controls, later corrections, timing effects, excluded systems, denominator errors, alternate ownership, data-quality defects, and stakeholders whose evidence was not included. The AI can generate a search plan; an authorized person or approved read-only tool must execute it.

NIST's AI Risk Management Framework is useful here because it treats critical thinking, role clarity, validation, and documentation as governance work rather than a model feature. COSO's GenAI materials similarly frame generative output within existing internal-control responsibilities. Neither source turns the model into an auditor. They help teams design the conditions under which its output can be challenged.

Preserve contradictions instead of prompting the model to “resolve” them. A policy may require quarterly review while a system log shows monthly checks and an owner describes an annual process. Those are three records with different implications. The packet should route the conflict to a named reviewer, not average it into a smooth narrative.

Worked example: privileged-access review exceptions

Suppose a draft finding says: “Privileged access is not reviewed, causing unauthorized access risk.” The sentence combines at least four judgments. The criterion may require quarterly recertification. The condition may be that 17 approval artifacts were missing from a sample of 214 accounts. The cause may be workflow failure. The effect is stated as a risk, not a realized incident. Each needs different evidence.

Freeze the population query: source system, extraction time, account types, service-account treatment, terminated users, emergency access, date boundaries, join keys, exclusions, and totals. Reconcile the extracted population to system or owner control totals. Reperform the sample selection and exception rule. Check whether approvals exist in a second repository, occurred after the test date, or were performed through a compensating control.

Next, challenge the cause. Missing approval artifacts could reflect a failed review, failed retention, migration loss, an incorrect join, or a policy-to-system mismatch. Interview statements may suggest a workflow problem, but the finding should not label root cause until evidence discriminates among these possibilities. Similarly, unauthorized access “risk” should not be rewritten as unauthorized access “occurred” unless logs or incidents support it.

The decision options might be to retain the finding, narrow it to documentation failure, split operating-effectiveness and record-retention issues, revise the population, defer pending evidence, or remove the assertion. The AI should show the evidence consequences of each option and leave the decision blank. The supervisor then evaluates sufficiency, significance, wording, and whether further work is proportionate.

Reperform material checks outside the language model

Use deterministic tools for counts, joins, date tests, duplicates, financial totals, and exception logic. An AI can draft SQL or Python, but a qualified reviewer must inspect the code, run it in an approved environment, reconcile inputs and outputs, and retain the artifact. Never accept a number that appears only in model prose.

population = load_authoritative_export(digest=expected_digest)
assert population.row_count == control_total
assert population.keys_are_unique(["system", "account_id"])

in_scope = population.where(
    privileged == True
    and active_during(period)
    and not approved_exclusion
)
results = join(in_scope, approval_records, on=declared_keys)

exceptions = results.where(
    approval_missing
    or approval_after_deadline
    or reviewer_not_authorized
)
store(query, parameters, counts, totals, exceptions, environment, reviewer)

Test both hits and misses. Select known compliant accounts and known exceptions. Inspect nulls and unmatched joins. Vary date boundaries and verify time zones. Confirm that service accounts and emergency access follow the declared policy. Compare the exception population with management's evidence and preserve unexplained differences.

Reperformance also applies to ratings. Map likelihood, impact, scope, duration, control importance, and realized events to the approved rating model. If a factor is a human judgment, label it as such and record the owner. Do not let the model manufacture precision with an unsupported score.

Failure modes and controls

A second-order failure is skill erosion. If preparers stop designing tests and reviewers stop tracing evidence because AI makes workpapers look complete, the organization loses the competence needed to catch model error. Require staff to explain the assertion map and reperform at least one material check without relying on the generated narrative. Use AI to raise the quality of review questions, not to remove the apprenticeship embedded in audit work.

A 30-day bounded pilot

1. Select one completed, low-sensitivity engagement with a known final conclusion.
2. Obtain methodology, privacy, security, records, and audit-lead approval for the exact tool and data.
3. Sanitize a frozen draft finding and build the assertion-to-evidence matrix manually first.
4. Run the workflow pack and record all prompts, inputs, outputs, retrieval, time, and cost.
5. Have a different auditor execute the proposed counterevidence searches and deterministic checks.
6. Blind a supervisor to whether challenge points came from AI or a person; score relevance and materiality.
7. Measure unsupported claims caught, false alarms, missing issues, reviewer time, data-handling exceptions, and final wording changes.
8. Require the preparer to explain every retained conclusion and source without reading the AI summary.
9. Document residual risks, allowed tasks, prohibited data, supervision, retention, and stop conditions.
10. Expand only if the pilot improves challenge quality without weakening ownership, confidentiality, or documentation.

The desired result is not faster drafting alone. It is a more defensible conclusion with visible contrary evidence and fewer hidden judgment leaps. If the AI saves drafting time but increases verification work or creates privacy risk, the pilot has not cleared the gate.

Include a baseline review of the same frozen finding without AI. Compare not only minutes spent, but also material challenge points discovered, irrelevant questions raised, unsupported wording retained, data-handling incidents, reviewer rework, and the percentage of proposed checks that produced usable evidence. Record where the model missed organization-specific methodology or misunderstood a source. A pilot that merely moves effort from preparer to supervisor is not a productivity gain. A pilot that finds more relevant counterevidence while reducing total review effort may justify a carefully bounded next phase.

FAQ

Can AI decide whether evidence is sufficient and appropriate?

No. It can organize evidence and identify gaps, but qualified auditors exercise professional judgment under the charter, methodology, standards, engagement facts, and supervision requirements.

Should AI assign the finding rating?

No. It may map evidence to declared rating factors and expose missing inputs. The engagement team and authorized reviewers own the judgment and approval.

Can an AI-generated SQL query count as audit evidence?

Only after authorized people review and execute it against authoritative data, reconcile the population and outputs, test the logic, and retain the code, parameters, environment, and results. Generated text alone is not execution evidence.

What is the most useful AI role?

A structured challenger: atomize the assertion, ask what would disprove it, search for missing links, propose deterministic checks, and assemble a review packet that makes human judgment explicit.

May public practitioner posts define audit practice?

No. They are useful pain signals, not authority or representative evidence. The organization's charter and methodology, professional standards, laws, regulators, engagement records, and qualified judgment control the work.

Sources and further reading

• The IIA: AI's Ethical Dimension — due professional care, critical thinking, and human responsibility; Oct 13, 2026; accessed Oct 23, 2026.
• Global Internal Audit Standards — authoritative standards, including findings, conclusions, and documentation; accessed Oct 23, 2026.
• The IIA Artificial Intelligence Auditing Framework — governance, management, and control context; accessed Oct 23, 2026.
• NIST AI Risk Management Framework Core — role clarity, critical thinking, validation, and documentation; accessed Oct 23, 2026.
• COSO: Achieving Effective Internal Control Over Generative AI — GenAI within internal-control responsibilities; accessed Oct 23, 2026.
• The IIA: Governing AI Analytics — analytics governance and oversight; accessed Oct 23, 2026.
• r/InternalAudit: concern about outsourcing critical thinking — current practitioner signal, not survey evidence; Oct 22, 2026; accessed Oct 23, 2026.
• r/InternalAudit: AI and the profession — current practitioner discussion; Oct 17, 2026; accessed Oct 23, 2026.
• Public internal-audit skills repository — format reference only; source and license checked, no text copied; accessed Oct 23, 2026.
• Related: external-audit evidence workflow.
• Related: continuous control testing workflow.
• Related: accounting research evidence workflow.