Where Interim Fieldwork Time Actually Goes
The interim substantive-testing phase for revenue and receivables involves several steps that look analytical but are largely procedural: extracting the transaction population from the client's ERP, applying sampling criteria under PCAOB AS 2315, issuing and tracking positive confirmations, and documenting the results in workpapers before the substantive memo is finalized. Each of those steps requires coordination — with the client, with the confirmation provider, with the engagement team — and the coordination overhead compounds when any step runs late. Audit Managers in this position routinely find that the work takes longer than the underlying complexity warrants.
How an AI Agent Handles the Substantive Testing Workflow
An AI Labor Company agent mines prior audit-team PBC request emails and revenue-testing workpaper review notes to reconstruct the interim substantive-testing workflow your engagement has established. A managed agent then extracts the revenue-transaction population from the client's ERP, applies PCAOB AS 2315 sampling criteria, issues positive-confirmation requests through Confirmations.com, and routes exception items to the Audit Manager for resolution before the substantive memo is finalized. The Audit Manager reviews exceptions and approves the memo — the agent handles the execution steps. Typically live in 8 weeks.
The Case for Compressing Fieldwork Time
Interim substantive testing is a cost center for the engagement and a schedule constraint for the close. Illustratively, 55–75% of the hours currently absorbed by mechanical testing steps shift to the agent — which translates directly to reduced fieldwork time and, in most engagements, faster substantive memo finalization. For an Audit Manager running multiple engagements, the compounding effect on bandwidth is significant. There's also a quality argument: an agent applies sampling criteria consistently across the full population, with full documentation, which reduces the risk of AS 2315 review findings.
How does the agent connect to the client's ERP?
The agent works through data extracts provided by the client — the same population files your team would request via PBC anyway. No direct ERP integration is required on the client side.
Is the agent's sampling methodology defensible under PCAOB standards?
The sampling logic is configured to apply PCAOB AS 2315 criteria as specified during onboarding. The Audit Manager reviews and approves the sampling parameters before the agent runs them. Documentation of the methodology is generated as part of the workpaper output.