What auditors ask about AI-generated code

By the AgentReceipt team · Updated 16 November 2026

If your company is audited, for example against a security framework such as SOC 2, expect questions about AI coding tools. This guide lists the questions that tend to come up and how records from AI sessions can help answer them. It is not legal or compliance advice, and no tool makes you compliant by itself.

What do auditors usually want to know?

The questions are old ones applied to a new author. For any change, an auditor wants to see who made it, who approved it, and that it went through your normal process.

  • Which AI tools are people allowed to use, and who decided that?
  • For a given change, who asked the AI to write it, and what did they ask?
  • Did a human review the change before it was merged?
  • How do you stop secrets and customer data from reaching the AI tool or the repository?
  • How long do you keep records, and who can read them?

Which of those can session records help with?

A per-session record helps with the second and fifth questions most directly: the prompt, the files changed and the flags are written down for each session, and a retention period is fixed. It supports the fourth by replacing secret-like values before anything is stored. It does not answer the first or the third, which are policy and review questions.

What should you write down before the audit?

Auditors read policies before they read logs. A short written policy that matches what you really do is worth more than a long one that does not.

  • The AI tools that are approved, and how they are configured
  • That every change still goes through pull request review
  • What is recorded for each AI session, where it is stored and for how long
  • What must never be put in a prompt

What can a self-reported record not show?

Receipts are written on the developer’s own machine. A missing receipt does not prove how code was written, and a local file can be edited by someone with access. Say this plainly to the auditor. It is better to explain the limit than to have it discovered.

To make records harder to change quietly, attach each one to its commit as a git note and review for missing ones. Your own process, not the record alone, is what an auditor tests.

How do the manager and employee views fit?

In AgentReceipt’s dashboard the manager sees every employee’s receipts grouped by person, and each employee sees only their own and cannot download them. After seven days the manager is emailed one PDF report per employee and the receipts are deleted from the dashboard, so the copy you keep is the one you store yourself.

Sources and further reading