Population coverage changes the audit queue; it does not transfer the opinion to AI.
AI value · Population coverage
Company-reported
Approximately 480 billion general-ledger lines loaded into the US analyzer in FY2025
Operator-reported coverage, not causal audit-quality evidence.
Before
Defines the risk population and selects transactions for testing under EY's sample-first baseline. → Examines selected transactions and follows anomalies through client evidence.
After
Loads general-ledger and subledger data and runs full-population analyses across ERP systems. → Uses patterns and outliers to target follow-up questions and additional audit procedures.
Human boundary
Audit partner and auditors retain all assurance conclusions; AI prioritizes evidence.
Why it matters
Audit risk assessment can begin with population-wide analytics instead of statistical samples alone.
This case is company-reported. Use it for the operating-model shift; do not treat the numbers as independently measured.
How the work changed
Before
How the work ran before the change.
Step 1 of 2
Engagement audit team
Defines the risk population and selects transactions for testing under EY's sample-first baseline.
ControlAuditing standards and engagement methodology; EY does not publish a baseline cycle time.
Step 2 of 2
Auditor
Examines selected transactions and follows anomalies through client evidence.
ControlProfessional skepticism and partner review; the source does not quantify sample size.
What changed
Audit risk assessment can begin with population-wide analytics instead of statistical samples alone.
Decision rightAI handles the default; humans own exceptions
After
How the same work runs now.
Step 1 of 2
Client data and EY Helix
Loads general-ledger and subledger data and runs full-population analyses across ERP systems.
ControlData provenance, quality, lineage, and analyzer configuration are explicit controls.
Step 2 of 2
Engagement auditor
Uses patterns and outliers to target follow-up questions and additional audit procedures.
ControlAuditors retain evidence evaluation and the audit opinion; no anomaly is an autonomous finding.
Process model built from the published workflow evidence for EY. Every step, actor, and control appears in full below.Every step, actor, and control
Exception path
Unreliable provenance or data quality requires conventional or expanded testing.
Decision authority
Audit partner and auditors retain all assurance conclusions; AI prioritizes evidence.
Before
#
Actor
Action
Control
01
Engagement audit team
Defines the risk population and selects transactions for testing under EY's sample-first baseline.
Auditing standards and engagement methodology; EY does not publish a baseline cycle time.
02
Auditor
Examines selected transactions and follows anomalies through client evidence.
Professional skepticism and partner review; the source does not quantify sample size.
After
#
Actor
Action
Control
01
Client data and EY Helix
Loads general-ledger and subledger data and runs full-population analyses across ERP systems.
Data provenance, quality, lineage, and analyzer configuration are explicit controls.
02
Engagement auditor
Uses patterns and outliers to target follow-up questions and additional audit procedures.
Auditors retain evidence evaluation and the audit opinion; no anomaly is an autonomous finding.
Work that left the path
Sample-first population screening as the only initial method
Human role before
Engagement auditors selected transaction samples, examined supporting evidence, and escalated anomalies through audit review to the partner under the engagement methodology.
Human role after
Auditors validate data, investigate exceptions and retain the audit opinion.
AI role
Screens complete ERP populations and surfaces patterns and outliers.
Outcomes
Population coverage
Company-reported
Statistical samples→Approximately 480 billion general-ledger lines loaded into the US analyzer in FY2025
Fiscal 2025 · US audit clients; global platform
Operator-reported coverage, not causal audit-quality evidence.
What leaders can reuse
Anti-pattern
Do not equate population screening with substantive audit of every transaction.
Questions
01Where is the operating threshold set and who can override it?
02What measured result would trigger rollback or retraining?
03Which residual decisions must remain human-owned?
Portability conditions
Reliable ledger extraction
Auditor override
Documented lineage
Reputation risk
low
Evidence and authority
What the public record supports.
Current · updated
2 primary; publication outcomes are reported.
Bundle 1.0.0 · reviewed 2026-09-06 · stable ID 60af9a4866ff31fc