CPA firms can start with approved AI use cases, a clear client-data boundary and a review record for any AI-assisted deliverable. Assign an owner for tool approval and a way to report mistaken output or data exposure.
Generative AI in a CPA firm: the risk is predictable (and manageable)
Define permitted GenAI uses, data that must stay out of the tool and how staff will record quality checks. Without those boundaries, staff may use it inconsistently.
The safest approach in practice (governance, privacy, disclosure and liability)
1) Governance: appoint an owner, define approved use cases, and publish a simple policy that staff can follow. Your policy should cover: allowed tools/models, prohibited data types, prompt logging expectations, human review requirements, and escalation when something looks wrong.
2) Data privacy: default to no client data in public GenAI tools unless your firm has verified contractual terms, security controls, and a clear data handling position. Where possible, route GenAI through enterprise controls (SSO, audit logs, model settings that prevent training on your inputs, and data retention limits).
3) Client disclosure: decide what you will disclose, when and how, considering material client work and administrative uses such as internal drafting. Professional review is a separate consideration from disclosure.
4) Liability: treat AI outputs as drafts that may contain errors. Have a qualified professional check assumptions, calculations, sources and final conclusions, and document the review.
Get an AI Risk & Efficiency Audit for your firm
A practical control checklist you can implement this quarter
- Use-case register: list permitted use cases (for example: summarising public guidance, drafting internal emails, drafting client-facing prose with full review) and banned use cases (for example: entering client identifiers into public tools, generating tax positions without verification).
- Data classification: define what counts as client confidential, personal data, special category data, and regulated data, and map each to approved tools.
- Tooling standards: prefer enterprise versions with admin controls, audit logs, and clear data retention terms. Disable optional features that increase leakage risk (plugins, browsing, automatic file syncing) unless explicitly required.
- Prompting guidance: teach staff how to ask for structure, assumptions, and citations, and how to avoid over-sharing. Include ‘safe prompt’ examples.
- Human review gates: require review by a qualified professional before AI-influenced content leaves the firm. For higher-risk work, add a second reviewer.
- Evidence: keep enough traceability to demonstrate that a human checked the work (for example: a short review note, version history, and the sources relied on). Avoid storing sensitive prompts in places that increase exposure.
- Incident playbook: define what to do if someone pastes client data into the wrong tool, or if a model output is discovered to be wrong after delivery.
What to say to clients (without overcomplicating it)
Client wording can address confidentiality and quality. Check that the statements below reflect your firm's actual practice:
- Confidentiality: ‘We do not place your confidential information into public AI tools. Where we use AI, it is within controlled systems and governed by policy.’
- Quality: ‘AI does not replace professional judgement. All work is reviewed and signed off by qualified staff.’
If you disclose AI use in engagement terms, describe its uses, exclusions and professional review.
Governance that actually works (without killing adoption)
Set consistent rules for GenAI use across the team.
The operating model below covers ownership, training, review and data handling:
- A named AI owner (risk/quality/compliance) and a small steering group
- Policy + training that fits on one page, plus detailed annexes for edge cases
- Quarterly review of tools, use cases, incidents, and client feedback
- Clear red lines on data handling and client deliverables
See our Managed AI Governance & Support (policy, controls and operating model)
Conclusion: make GenAI boring (in the best way)
Governance, data handling, disclosure decisions and human review form part of a CPA firm's approach to GenAI risk. Keep those controls in view as use expands.
Explore Implementation Projects (secure rollout + workflows)
Want to turn this into a practical AI plan?
For accountancy and audit teams, the next step is to identify where AI can reduce manual work without weakening review quality, client confidentiality or regulatory controls.