The AICPA’s October 28 announcement of proposed 2027 SOC 2 Trust Services Criteria puts artificial intelligence more explicitly into the language of third-party assurance. The proposal names AI governance, model monitoring, prompt manipulation, data poisoning and automated decision-making among its considerations. For finance leaders buying software or overseeing AI-enabled workflows, the immediate issue is evidence: what can a vendor demonstrate about the systems on which financial operations increasingly depend?
The judgment
Implication: AI risks are becoming part of mainstream assurance conversations rather than a separate innovation checklist. The proposal is not yet effective and should not be represented as a new compliance mandate.
What would change the conclusion: The final criteria may narrow or revise the AI-related points of focus, and adoption timing could change following public comment. The practical priority would also shift if assurance reports demonstrate that existing controls already address the relevant risks.
Management action: Inventory AI-enabled vendors and internal agents that touch finance processes, identify accountable owners, and ask what access, change-management, monitoring and human-review evidence already exists. Use the exposure draft as a discussion aid, not a certification checklist.
What the AICPA actually proposed
The AICPA describes targeted restructuring of its SOC 2 criteria: consolidating overlapping concepts, removing some criteria, refining wording and adding considerations for emerging technology. Its October 28 release specifically references AI governance, model monitoring, prompt manipulation, data poisoning, training-data management, output transparency and automated decisions. These are examples of proposed points of focus, not proof that every SOC 2 engagement must adopt a named AI control.
The AICPA is accepting comments through January 15, 2027. If the proposed criteria are approved, they would be effective for engagements beginning on or after December 31, 2027, with early adoption permitted. That future date matters. A company should not describe itself as noncompliant with criteria that have not been finalized.
Why finance should care about assurance scope
SOC 2 examinations assess controls relevant to security, availability, processing integrity, confidentiality or privacy of systems, depending on engagement scope. They are performed by independent licensed CPAs under AICPA attestation standards. A SOC 2 report is therefore useful evidence about specified controls over a defined system and period—not a blanket guarantee that a vendor’s product, its AI outputs or its financial conclusions are correct.
Consider a vendor that reads invoices, recommends coding, drafts journal entries or routes approvals. Finance’s exposure depends on more than the model’s accuracy. Which systems can the agent access? Can it change vendor master data? Who approves high-risk transactions? How are errors detected? Are exceptions logged, retained and independently reviewed? The answers determine the design of the organization’s own complementary controls, whether or not the vendor provides a SOC 2 report.
Points of focus are not a prescriptive AI checklist
A point of focus helps explain characteristics that management and an examiner may consider in determining whether a criterion is met. It is not, by itself, a required individual control. Treating each draft example as a mandatory line item would confuse the AICPA’s principles-based approach with a new rulebook.
That distinction should shape procurement. Rather than demanding a generic declaration of ‘2027 SOC 2 AI compliance,’ finance teams can ask vendors to identify relevant system boundaries, subservice organizations, access paths, material model changes, incident procedures and evidence retained. The questions can be tailored to the transaction and data risk. They also remain useful if the final exposure-draft wording changes.
Three controls to examine before the next vendor renewal
Access and authority. Document what the system or agent can read, recommend, approve and execute. A read-only summarizer poses a different financial-reporting risk from an agent that can create payments or change account mappings. Review service accounts and permissions as capabilities expand.
Change and monitoring. Establish who approves model, prompt, integration and data-source changes, how changes are tested, and how unexpected outputs are surfaced. Monitoring should be tied to actual workflow failure modes rather than an arbitrary model-quality number.
Evidence and override. Preserve a trail from input to recommendation to human decision for material financial processes. Clarify who can stop an automated workflow, correct erroneous entries and notify affected users. An assurance report can support these questions, but management still owns its internal-control environment.
A board-level distinction: assurance versus reliance
Boards and audit committees should distinguish three separate assertions. First, a vendor may have controls that were examined against defined criteria. Second, the organization’s own use of the service may be appropriately configured. Third, outputs may be sufficiently reliable for a particular financial decision. Evidence supporting the first does not automatically establish the second or third.
This is especially important for nonprofits and smaller finance teams, which may adopt AI-enabled tools without dedicated technology-risk staff. A concise inventory, accountable process owner and documented escalation route may deliver more practical protection than a lengthy policy without operational evidence.
What happens next
The AICPA’s public-comment period runs to January 15, 2027. Finance and procurement teams can read the clean and redlined exposure drafts, compare them with their current vendor review process and submit comments where proposed language would create ambiguity. Organizations should continue applying existing requirements and their own risk-based controls while the proposal remains under review.
Sources and related analysis
Primary sources: AICPA announcement, October 28, 2026; AICPA exposure draft and redline download page. Related Numbers & Judgment coverage: contract controls and accounting evidence and CFO control remediation. The exposure-draft materials are a free resource, although access to downloadable documents may require an AICPA account.
Leave a Reply