AI Policy Template Rules for Small Accounting Firms

Why does a small firm need an AI policy now?

A small firm needs an AI policy because staff may already be using AI before partners approve tools, data rules, or review standards.

The risk is practical. A preparer asks ChatGPT to rewrite a client email. A bookkeeper uses Copilot to summarize transaction notes. A CAS manager asks an AI tool to draft a payroll memo. Nobody thinks they are creating a governance issue. But if client names, payroll data, tax positions, bank details or workpaper evidence entered an unapproved system, the firm has a problem.

CPA.com/AICPA risk-control guidance is direct: entering data into a generative AI tool means sharing it with the tool owner. AI models also produce answers that sound usable but are still wrong — and in accounting, wrong answers that look professional are the expensive kind.

There is an external pressure too. The SEC now reviews AI claims in annual filings and investment adviser brochures. If your firm advises public company clients or investment advisers, a written AI policy is no longer just internal hygiene. It is part of what examiners check. See what the SEC actually looks for.

What should the policy say about approved AI tools?

The policy should list approved AI tools, approved users, allowed workflows, blocked workflows, and the partner responsible for review.

Do not start with a broad sentence like "employees may use AI responsibly." That is too vague to enforce. Start with a tool list. Here is what that looks like in practice: Microsoft Copilot inside firm-controlled accounts for internal drafting; ChatGPT Team for generic research and non-client templates; public free tools get no firm or client confidential information.

Set 100% of approved tools on firm-owned accounts, and set 0% tolerance for client data in personal or public accounts. That bright line is easier to enforce than a judgment call buried in a long policy.

The cost test is practical too: a $1,000 AI subscription is not worth a $5,000 remediation scramble if staff accidentally upload client payroll or tax data to the wrong system.

The policy should also explain how new tools get approved. A staff member should not be able to install a browser extension, upload trial-balance data, and call it a pilot. Require a short request: tool name, vendor, use case, data involved, reviewer, cost, and whether the tool can retain or train on firm data.

What client data should never go into public AI?

Public AI tools should not receive client names, tax IDs, payroll data, bank records, financial statements, contracts, or identifiable workpapers.

This is the center of the policy. Employees need concrete examples, not abstract warnings. "Do not paste confidential data" is easy to agree with and hard to apply under deadline pressure. Spell it out.

Prohibited inputs should include Social Security numbers, EINs, account numbers, payroll registers, W-2s, 1099 detail, bank statements, customer lists, vendor lists, financial statements, board materials, audit evidence, tax returns, engagement letters, and client email threads. Even if an employee removes the client name, a combination of location, transaction detail, and unusual facts may still identify the client.

How should staff review AI-generated work?

AI-generated work should be reviewed as a draft, with source checks, math checks, client-specific verification, and documented signoff when risk is high.

A small firm AI policy should say that AI output cannot be copied directly into client deliverables without review. That includes emails, memos, financial summaries, tax research summaries, advisory reports, spreadsheet formulas, and explanations sent through portals.

Use a tiered rule. Low-risk internal wording can be reviewed by the employee using it. Client-facing explanations need review by the engagement owner. Tax, audit, attestation, payroll compliance, and financial statement language need review by a qualified professional before delivery. If an AI output affects a client recommendation, the source support belongs in the file.

A practical firm rule can be this direct: "AI may help prepare the first draft, but the engagement owner remains responsible for the final work product." That sentence is easy to train, easy to remember, and hard to misinterpret during busy season.

Should clients be told when the firm uses AI?

Client disclosure depends on law, contract terms, professional duties, and firm judgment, but the policy should create a review process.

CPA.com/AICPA disclosure guidance tells firms to assess whether legal or ethical requirements apply and to consider the trust value of transparent disclosure. The policy does not need one universal answer for every engagement. It does need a decision path.

A firm might decide that generic AI-assisted drafting does not require disclosure, while tools that process client records or connect to client systems require engagement-letter language. That is a reasonable line. What is not reasonable is leaving each staff member to draw it alone under deadline pressure.

What incident rules belong in the policy?

The policy should tell employees exactly what to do if they paste client data into an unapproved tool or receive unsafe output.

Employees hide mistakes when the policy sounds punitive and vague. Make the escalation path boring and fast. If client data enters an unapproved tool, the employee should notify the partner or operations lead the same day, preserve the prompt and output if available, stop further use, and help determine what information was exposed.

The FTC's privacy and security guidance is a useful baseline for small businesses: collect only what you need, keep sensitive information safe, and honor privacy promises. A firm AI policy should turn that into day-to-day behavior.

How do you roll out the policy without slowing the firm?

Roll out the policy with a short document, employee acknowledgement, approved-tool list, examples, and a 30-minute training session.

The policy should fit the firm. A six-person bookkeeping shop does not need a 40-page AI governance manual. It needs clear defaults. Four pages works: one page of allowed and prohibited uses, one page of client data rules, one page of review and escalation rules, one signature page.

For a small accounting firm, accountability means a partner owns the tool list, engagement owners review client-facing work and employees know where the line is before busy season starts. Not after.