We accept policies, descriptions and queries that an AI assistant helped your team write, once a person has approved them and they match what you do. We do not accept evidence that an assistant generated, edited, summarized or recreated: we need the record as your system produced it. No AI is the auditor. A licensed CPA firm examines the evidence under SSAE 18 and forms the opinion.
Key takeaways
- An assistant may draft. A person at your company decides, approves and verifies.
- The record is what the system produced. A summary, a rewrite or a recreation is not the record.
- For every list from your systems, we obtain evidence that it is complete and accurate before we rely on it.
- A document shows design. It does not show that the control operated.
How does an auditor decide what evidence to accept?
A SOC 2 examination is performed under SSAE 18, AT-C sections 105 and 205. The standard requires us to obtain sufficient appropriate evidence before we form an opinion: enough of it, relevant to the control, and reliable given where it came from.
The standard has no separate rules for AI. An assistant makes it easy to produce something that looks like a record and is not one, so we ask how each artifact was made. See tests of controls, IPE and IUC.
We explain the criteria and send our evidence request list once engaged. Your management designs the controls, writes the policies and operates them; we do not draft, configure or choose anything. See the Zero-Platform SOC 2 audit and, for the preparation, SOC 2 with AI.
What are the auditor’s rules on completeness, accuracy, provenance and human review?
| Rule | What we need | Why |
|---|---|---|
| Completeness | Every item for the period is in the population: every leaver, every change, every account. | When we use information produced by your company, AT-C section 205 requires us to evaluate whether it is reliable enough for our purpose, including obtaining evidence about its accuracy and completeness. |
| Accuracy | Each item matches the system of record. | We trace selected items back to the system. A rewritten text may differ from the record, and we cannot tell without the original. |
| Provenance | The source system, who ran the export, the query or filter, the date and time, and the record count. | Reliability depends on the source of evidence and on how it was obtained. |
| Human review | A named person at your company reviewed the artifact before it was sent and can explain it. | Management is responsible for what it gives us and confirms this in written representations. An assistant cannot take that responsibility. |
Will an auditor accept a screenshot, an export or a document?
A document shows design, not operation. To conclude that a control operated, we need evidence of it being performed, such as tickets, approvals, logs and sign-offs. For a Type II report that evidence must cover the whole period.
A screenshot needs the system, the date and the full context: the hostname or URL, the signed-in user, the full date and time and the environment, in one uncropped capture. One screenshot shows one record, not a population.
An export needs the source, the query or filter, the date and the record count. Send the file as the system produced it, with the query beside it. See audit evidence management best practices.
Anything an assistant summarized, rewrote or recreated is not the record. Send the original.
What do auditors accept from work done with AI?
- A policy drafted with an assistant that management approved and that matches practice. We read it as your policy, then test whether practice follows it. See SOC 2 policies with AI.
- A query written by an assistant and run read-only, by a person or by an agent a named person supervises, with the output reviewed by that person. Send the query with the output. See evidence collection with AI agents.
- A system description drafted with an assistant and verified by management. We evaluate it against the description criteria (DC section 200). See the system description with AI.
AI-written policies and descriptions are acceptable only if they describe what your company actually does. The audit tests how controls operate, not how documents read.
What do auditors reject, and why?
| What we reject | Why |
|---|---|
| Generated or edited “evidence” | A file that an assistant produced or changed records what the assistant wrote, not the control being performed. |
| Recreated logs | A log rebuilt from memory or from other data is not the log the system wrote. |
| Screenshots without a date or a source | We cannot tell which system, environment or day the capture shows. |
| Populations filtered by a prompt, with no query shown | We cannot reperform the filter, so we cannot obtain evidence that the list is complete. |
| Policies that describe controls nobody operates | The document does not match practice. When we test the control there is no record to inspect, and we report an exception. |
The mismatches between policy and practice that most often lead to exceptions are in SOC 2 common findings and how to fix them.
What should we check on each artifact before we send it?
- It is the original file or export, not a copy that was retyped, reformatted or summarized.
- The source system is named. On a screenshot, the URL and the signed-in user are visible.
- The export date and time are shown, and the records cover the period requested.
- The query, filter or parameters are shown.
- The record count is stated and matches the file.
- Nothing was edited after export.
- A named person ran the export, and a named person reviewed it.
- A policy or description carries management’s approval and its date, and matches what you do today.
Prompt: review an evidence package index against the checklist
Review the index of an evidence package before I send it to our SOC 2 auditor. I will paste the index: one line per artifact, with file name, type (export, screenshot, document or summary), source system, export date and time, period covered, query or filter, record count, exporter and reviewer. Review only. Do not add, change or fill in any entry, and do not suggest values for missing fields. I will go back to the source system for anything missing. Ask me how each type of artifact is exported at our company today and who reviews it, before you start. For each line, tell me which of these is missing: source system; export date and time; period covered; query or filter; record count; exporter; reviewer; for a summary, the original it summarizes; for a document, who approved it and when. Return one row per artifact with the missing items and the question to take back to the exporter. Flag every assumption you make. List anything you assumed that I need to verify.
Is there such a thing as an AI auditor for SOC 2?
No. No AI is the auditor. A SOC 2 report contains an opinion, and a licensed CPA firm forms that opinion, signs the report and is responsible for it. Software does not form the opinion. See who can perform a SOC 2 audit.
This series describes AI-guided preparation, CPA-performed audit: the assistant is your team’s tool. Our own methods are on the audit methodology and Auditsuisse AI pages.
Who does what
| Task | Your team (with or without AI) | Your AI assistant | The auditor |
|---|---|---|---|
| Policies | Decides the content, approves it and follows it | Drafts text and lists its assumptions | Reads the approved policy and tests whether practice matches it |
| Queries and exports | Runs or supervises the read-only query and reviews the output | Helps write the query | Examines the export and tests that the population is complete and accurate |
| System description | Verifies every statement | Drafts sections from your facts | Evaluates it against the description criteria |
| Review before sending | Checks each artifact against the checklist | Reviews the index for missing fields | Requests what is missing and selects items from each population |
| The opinion | Provides management’s assertion and written representations | No role | Forms the opinion and issues the report |
Frequently asked questions
Do we have to tell the auditor that we used an AI assistant?
Tell us how each artifact was produced. If an assistant wrote a query, send the query.
Does a policy written with ChatGPT or Claude count against us?
No. Who typed the first draft does not matter. What matters is that management approved it, that your people follow it and that the records show it.
What if the original record no longer exists?
Tell us. We do not accept a recreated record in its place. We consider whether other evidence of the control exists; where it does not, we may report an exception. See qualified and unqualified opinions.
Sources & further reading
AICPA, 2017 Trust Services Criteria (with revised points of focus, 2022); SSAE No. 18, AT-C sections 105 and 205; AICPA, description criteria (DC section 200).
Related: Tests of controls, IPE and IUC, Audit evidence management.
Product names are trademarks of their owners. Auditsuisse is not affiliated with these vendors.
Work with a licensed CPA firm
Auditsuisse Assurance NA PC is a licensed US CPA firm, enrolled in the AICPA Peer Review Program and authorized to perform SOC 2 examinations and issue SOC 2 reports. You prepare; we examine your evidence. See the Zero-Platform SOC 2 audit or book a scoping call.