A full-population audit tests every transaction in a population, not a sample, and audit firms are now using AI agents to make that practical. For the company being audited, the change is simple to state and hard to absorb: every exception in your data will surface. Clean, consistent finance data, a disciplined ERP configuration and testable logs are no longer nice to have. They decide whether fieldwork is quick or painful.
Audit firms are replacing sampling with AI-assisted testing of entire populations. In an October 15, 2026 piece for CPA Practice Advisor, Tunde Adewole describes AI agents paired with deterministic code that check every transaction, for example every 401(k) deposit against payroll and every match against the plan formula. He argues that sampling was a constraint on testing time, not an ideal.
The largest firms are moving the same way. Accountancy Age reported in April 2026 that EY is deploying a multi-agent AI framework across 160,000 audit engagements, embedded in its EY Canvas platform, which processes 1.4 trillion lines of journal entry data per year. The same article says the industry is moving toward 100% population testing, and that EY aims to support all end-to-end audit activities with AI by 2028.
An audit still provides reasonable assurance, not absolute assurance. Adewole is explicit that testing everything strengthens evidence but cannot catch an incomplete population, a provision applied consistently but incorrectly, or something no dataset captures. A person still has to be accountable for every conclusion.
The standards have not been rewritten around the technique either. We are not aware of a PCAOB or AICPA standard written specifically for full-population testing. For public company audits, the most direct rules are the PCAOB's technology-assisted analysis amendments to AS 1105 and AS 2301, approved in June 2024 and effective for fiscal years beginning on or after December 15, 2025, as CPA Practice Advisor reported. They point auditors at the reliability of company information, including IT general controls and automated application controls, and require investigation of items a test flags to see whether they indicate misstatements or control deficiencies.
When your auditor tests every transaction, your data quality becomes your audit experience. Every miscoded entry, orphaned vendor and undocumented manual override becomes a question. The companies that will move fastest are the ones that run the same analytics on themselves first and arrive with the exceptions already explained.
Expect more questions, earlier, about data you may never have looked at in aggregate. Adewole notes that testing 100% of transactions surfaces more exceptions, which means more follow-up and more client conversations. Here is where that pressure lands.
Audit readiness fails most often at the handoff between IT and finance, so assign owners explicitly.
| Area | IT owns | Finance owns |
|---|---|---|
| Data extracts | Complete, repeatable exports of the GL and subledgers with control totals | Tying extracts to the trial balance and signing off on completeness |
| ERP configuration | Change management, test evidence and configuration history | Defining approval rules, tolerances and posting policies |
| Access and SoD | Provisioning, quarterly access reviews and conflict rules enforced in the system | Defining incompatible duties and approving exceptions |
| Journal entries | Logging of who posted, when and from where | Support, descriptions, approvals and review of manual entries |
| AI agents and automations | Scoped identities, immutable logs, change control and kill switch | Approval thresholds and review of agent output |
| Exceptions | Running analytics and routing results | Investigating, explaining and documenting resolution |
Start with the data, then the controls, then rehearse the audit on yourself.
Run the same population tests your auditor is likely to run, on a monthly cadence, and keep the investigation trail. Most of these tests are deterministic queries; AI helps by triaging results, drafting explanations from supporting documents and routing items to the right reviewer.
Keep a person accountable for each conclusion, as auditors do. An AI that explains exceptions is useful; an AI that closes them without review creates a new control gap. Running these tests monthly also shortens the close, which is the theme of our guide to an AI-assisted three-day financial close.
Our workflow automation team builds the extract pipelines and monthly analytics, custom AI agents handle exception triage with scoped identities and full logging, AI security covers access, SoD and log integrity, AI DevOps puts agents and ERP configuration under change control, and AI consulting helps controllers and IT leaders set the 90-day plan and ownership model.
A full-population audit tests every transaction in a population, such as every journal entry or every payroll deposit, instead of a statistical sample. Audit firms are using AI agents paired with deterministic code to make this practical at scale.
No. An audit still provides reasonable assurance, not absolute assurance. Testing every transaction strengthens evidence, but it cannot catch an incomplete population, a rule applied consistently but incorrectly, or something no dataset captures.
We are not aware of a PCAOB or AICPA standard written specifically for full-population testing. Existing evidence standards still apply, and the PCAOB's technology-assisted analysis amendments to AS 1105 and AS 2301, effective for fiscal years beginning on or after December 15, 2025, are the most direct rules for public company audits.
IT should own system access and segregation of duties enforcement, change management for ERP configuration, IT general controls, complete and exportable data extracts, and logging for any AI agents or automations that touch financial data. Finance owns the accounting judgments, reconciliations and exception explanations.
Yes. Run journal entry, duplicate payment, three-way match and access analytics on your full general ledger and subledgers each month, investigate what surfaces, and document the resolution. You will find most exceptions before fieldwork and arrive with explanations instead of surprises.
Infonaligy is based in Dallas–Fort Worth, serves the regions listed on our locations page, and delivers finance data readiness, accounting automation and AI governance programs remotely to clients nationwide.
Book a 30-minute assessment and we'll review your extracts, ERP configuration, access and AI agent logging, and outline a 90-day plan to run full-population analytics on your own books.