Accounting Automation · Audit Readiness

When Your Auditor Tests Every Transaction: Getting Finance Data Ready for AI-Driven, Full-Population Audits

By Infonaligy · Updated November 12, 2026 · 8 min read

EVERY TRANSACTION // TESTED // READY

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.

What is changing in the audit?

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.

What full-population testing does not change

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.

The headline

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.

What changes for the company being audited?

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.

  • Every exception surfaces. A sample might miss the one invoice paid twice or the entry posted on a Sunday by a terminated user. A full-population test will not.
  • Data completeness matters more. If the extract you hand over is missing a subledger, a legal entity or a month, every conclusion built on it is weaker. Completeness is the first thing to prove.
  • ERP configuration becomes evidence. Approval workflows, posting rules, tolerance settings and three-way match configuration are what make an automated control reliable. Undocumented changes to them invite questions.
  • Journal entry hygiene is exposed. Manual entries, round-dollar amounts, entries posted after close, entries by unusual users and vague descriptions are classic analytics targets.
  • Access and segregation of duties get tested at scale. Analytics can compare every posting against who held which role at the time. Conflicts that were tolerated quietly become findings.
  • Your own AI agents are in scope. If an agent drafts entries, matches invoices or proposes reconciliations, auditors will want logs showing what it did, under which identity, and who approved it.

Who owns what: IT or finance?

Audit readiness fails most often at the handoff between IT and finance, so assign owners explicitly.

AreaIT ownsFinance owns
Data extractsComplete, repeatable exports of the GL and subledgers with control totalsTying extracts to the trial balance and signing off on completeness
ERP configurationChange management, test evidence and configuration historyDefining approval rules, tolerances and posting policies
Access and SoDProvisioning, quarterly access reviews and conflict rules enforced in the systemDefining incompatible duties and approving exceptions
Journal entriesLogging of who posted, when and from whereSupport, descriptions, approvals and review of manual entries
AI agents and automationsScoped identities, immutable logs, change control and kill switchApproval thresholds and review of agent output
ExceptionsRunning analytics and routing resultsInvestigating, explaining and documenting resolution

A 30/60/90-day readiness plan

Start with the data, then the controls, then rehearse the audit on yourself.

Days 1 to 30: inventory and extract

  • List every system that produces financial transactions: ERP, payroll, billing, expense, banking and any AI agents or bots.
  • Build repeatable extracts of the full general ledger and key subledgers, with record counts and control totals that tie to the trial balance.
  • Pull the ERP change log and user access listing for the audit period, and note any gaps.
  • Agree on a data dictionary for account, entity, vendor and user fields so every extract means the same thing.

Days 31 to 60: clean up and harden controls

  • Fix master data problems: duplicate vendors, inactive users with active access, unmapped accounts.
  • Document configuration for automated controls such as three-way match, approval limits and posting restrictions, with evidence that each was tested after its last change.
  • Enforce segregation of duties in the system rather than by policy. Our guide to AI agent segregation of duties covers how to apply this to agents as well as people.
  • Give every AI agent its own identity, and log prompts, tool calls, outputs and approvals. See AI agent audit evidence logging for what a testable log contains.

Days 61 to 90: pre-run the audit

  • Run full-population analytics on your own data, using the tests described below.
  • Investigate every flagged item and record the explanation, the evidence and who reviewed it.
  • Fix root causes, not just individual entries, and rerun the tests to confirm.
  • Share the results package with your auditor before fieldwork so the conversation starts from explained exceptions.

How do you pre-run the auditor's analytics with your own AI?

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.

  • Journal entry tests: manual entries, entries posted after period close, weekend or holiday postings, round amounts, entries by users outside finance, and entries with missing or generic descriptions.
  • Payables tests: duplicate invoices and payments, invoices without matching purchase orders or receipts, vendor bank changes followed by payment, and vendors sharing addresses or accounts with employees.
  • Access tests: every posting compared with the user's role at that moment, and every SoD conflict that was actually exercised.
  • Reconciliation tests: unreconciled balances, aged reconciling items and reconciliations completed by the same person who posted the entries. Our post on AI reconciliation automation shows how to automate the matching itself.

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.

Where to get help

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.

Frequently asked questions

What is a full-population audit?

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.

Does full-population testing mean the audit is guaranteed to be right?

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.

Is there an audit standard specifically for full-population testing?

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.

What should IT own in audit readiness?

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.

Can we run the same analytics before the auditor does?

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.

Sources

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.

Audit-ready finance data

Find your exceptions before your auditor does.

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.

DFW · remote nationwide · governed by default · 800-985-1365