Quick answer
CPA professional liability covers the tax preparation and advisory services your firm provides, whether software or an AI assistant prepared the first draft. The claim follows the signature on the return. What automation changes is volume: more returns move faster, so a systematic review gap reaches more clients before anyone catches it.
What automation does to the exposure
Automation does not create a new coverage line. It changes the shape of the claim:
- Systematic errors spread. A mapping mistake in an import template can hit every return in a batch, which turns a single error into a multi-client event.
- Review gets compressed. When preparation takes minutes, review is the only control left. Firms that cut review time to keep up with volume are the ones that miss items.
- Documentation thins out. Automated workflows generate less correspondence. After a claim, the file needs to show what the client provided, what the firm asked for, and what was verified.
Where the coverage questions sit
- Covered services. Tax preparation and representation must be scheduled on the application. A firm that added automated business return preparation without updating the application has a coverage question waiting.
- Aggregate limits. A multi-client error is multiple claims. A $1M per claim policy with a $1M aggregate is exhausted by the first one, which is why firms running high-volume automated work should look at a $2M or $3M aggregate.
- Defense treatment. Defense inside the limit erodes settlement capacity. With batch errors, defense is the larger number.
- Penalties and interest. Client penalties and interest are usually part of the damages claim; preparer penalties assessed against the firm are a different matter and often excluded.
AI disclosure in engagement letters
There is no single required disclosure form, and no statute dictates the exact language. What carriers and clients expect is clarity:
- Whether AI tools may be used in preparing the return or in research.
- That a licensed professional reviews the return before filing.
- What the client is responsible for providing and verifying.
- How the firm handles confidential data, including whether it enters third-party tools.
Put it in writing, keep it in the engagement file, and make sure it matches what the firm actually does.
Review controls that support the coverage position
1. Define a review standard and keep it. Who reviews, what they check, and what gets escalated.
2. Spot-check automated batches. Sample before filing, not after a notice arrives.
3. Keep the client document trail. What was received, what was requested, what was never provided.
4. Log software and template changes. A mapping change mid-season explains a cluster of errors.
5. Report circumstances early. If a batch problem surfaces, notify the carrier before the first client complaint becomes a claim.
Limits and aggregates for automated practices
High-volume automated preparation concentrates risk in a short window. A firm filing thousands of returns in ten weeks has more chances for a systematic error than a firm filing a few hundred over the year. The limit decision follows the concentration, not the revenue line.
Review the CPA professional liability overview or start an application with your automation workflow described.
General information about coverage structure, not a quote or a coverage opinion. Terms, exclusions, and claims handling are set by each carrier's policy form.
To compare options from A-rated carriers, start a quick quote.