Fixed-Fee Engagement Letters for Tax Compliance Work

Fixed-fee pricing has become the default billing model in accounting, and the engagement letter that worked fine under hourly billing does not automatically work under a fixed fee. The mechanics of the two models differ enough that a letter built for one can quietly fail under the other, and that failure appears in scope disputes, unpaid work, and professional liability claims.

The numbers back up how fast this shift happened. Ignition's 2025 domestic Accounting and Tax Pricing Benchmark Report, which surveyed 219 U.S.-based accounting firms, found 54% now use fixed fees, up from 50% in 2024. Hourly billing, meanwhile, dropped to just under 4% of firms in 2025 from nearly 8% the year before. For tax preparation specifically, fixed fee is the leading model at 37% of firms in 2025 (up from 35%), with only 3% still billing tax prep by the hour. The survey sample skews toward firms already using modern billing automation, and the shift is real but uneven across the profession. Still, the direction is unmistakable, and it has outpaced how firms actually write their engagement letters. Hourly letters tracked time worked; fixed-fee letters have to define and defend scope. That's a different document, and most firms haven't rewritten theirs to match.

Why tax claims often arise without an engagement letter

CNA Risk Control Consulting Director Deb Rood, CPA, MST, reports that tax services accounted for 77% of claims asserted against CPA firms in the AICPA Professional Liability Insurance Program in 2024. Of those claims, an alarming 56% involved no engagement letter tied to the underlying service, according to the CNA Accountants Professional Liability Claim Database (Continental Casualty Co., 2025). This isn't a one-year blip. Looking at 2023 data, roughly 75% of claims stemmed from tax services, and more than half of those had no letter at all, according to The Tax Adviser.

Practitioners tend to get letters signed for routine, recurring compliance work, but skip them for anything that feels incidental. Responding to an IRS notice. Helping with an audit. A year-end planning call. A piece of research a client asked for over email. Those are exactly the engagements that generate claims, because nobody wrote down what was promised.

And even when a letter exists, it isn't necessarily doing anything. The Journal of Accountancy documented a case where a CPA used the engagement letter bundled into their tax software, and it didn't define scope, didn't detail responsibilities, didn't identify deliverables, didn't allocate risk, and didn't mention fees. It offered no protection at all, despite technically satisfying the box-checking requirement of "having a letter." If a generic letter like that was inadequate for hourly work, it's worse for fixed-fee work, where the entire fee is staked on a scope definition that the letter never actually wrote.

Requirements unique to fixed-fee letters

Hourly billing has a built-in referee: the clock. When work expands past what anyone expected, the meter runs longer, and the dispute, if there is one, is about the rate or the hours logged, not about what was promised. Fixed-fee billing removes that referee. The letter itself becomes the price-setting document, and by default, every service not explicitly excluded reads as included at the agreed price.

That changes what the letter has to accomplish. It has to define what's in scope, with enough precision that a court or an insurance adjuster could read it cold and know what the firm agreed to do. It has to name, specifically, what's out of scope: actual named categories of work the firm won't perform under this fee. And it needs a built-in mechanism for turning an out-of-scope request into a new, priced engagement before anyone touches the work.

None of this is invented by insurers out of caution. Treasury Circular 230, Section 10.33 (Best Practices for Tax Advisors) encourages practitioners, as an aspirational standard, to communicate clearly with clients about engagement terms, and a signed letter is the profession's accepted way of meeting that bar. The AICPA Tax Section, working with CNA (the endorsed underwriter of the AICPA Professional Liability Insurance Program), publishes annual, form-specific engagement letter templates every year. Those templates are a floor, not a ceiling. They're built for compliance work broadly, and firms running fixed-fee models have to adapt them specifically for price certainty and scope defense, which the base templates weren't written to provide.

Writing the scope clause: naming what the fixed fee covers

A scope clause must name the exact tax forms, the tax year, and the jurisdictions covered. "Preparation of 2025 federal and state personal income tax returns" does that. "Tax services for the 2025 year" does not, and that vagueness is precisely what gets exploited when a client later insists something extra was included.

The Wolf Group's published 2025 Individual Tax Return Engagement Letter is a useful model of what specificity actually looks like on the page. It names a domestic and state individual income tax returns for 2025. It includes nonresident state or local returns where taxable income exists there, unless the client says in advance they don't want those filed. It covers FBAR (FinCEN Form 114) preparation if the firm determines a filing requirement exists, with a stated opt-out. It covers Forms 3520 and 3520-A when a filing requirement is identified. And it addresses dependent tax filings, noting when a separate engagement letter may be required.

That level of detail is what makes a fixed fee legally defensible. Business returns need even more of it: the letter should name the entity type and the specific form, and account for the preliminary steps that have to happen before return preparation can even start. The AICPA Tax Section's Annual Tax Compliance Kit reflects this by breaking templates out by return type: a 2025 Individual Tax Return Engagement Letter (Form 1040), a 2025 Partnership Engagement Letter (Form 1065), and a 2025 Private Foundation Engagement Letter (Form 990-PF), each built around the scope questions unique to that return.

Writing the exclusions clause: naming what the fixed fee does not cover

Insurers and regulators alike have landed on the same fix for scope ambiguity: an explicit "anti-scope" clause. The letter has to state, in named terms, what's excluded, not just what's included.

The Wolf Group letter again offers a concrete example. Gift tax returns (Form 709) are excluded, with the client responsible for flagging any transfers of value, and a separate letter required if preparation becomes necessary. Tax planning is excluded, the firm might mention a strategy in passing while preparing a return, but has no obligation to, and any planning work needs its own engagement. Prior-year returns get a limited review when provided for context, with no guarantee that review catches every error, and amendments require a separate engagement. Post-filing work such as IRS correspondence, audit defense, and notice response is best named explicitly as excluded rather than left implied.

The phrase "unless covered under a separate engagement letter" does real work here. It automatically converts any client request for extra service into a new, priced engagement, rather than leaving the firm arguing after the fact that the work was never part of the deal. Some client situations call for an even narrower scope definition, with any post-filing agency communication set up as its own separate engagement from the start.

The most common mistake here is writing exclusions too generically, something like "additional services not listed above," instead of naming the specific things clients actually ask for. A vague exclusion is much harder to enforce when a client disputes it later, because there's nothing concrete to point to.

Writing the fee clause and the change-order mechanism: where fixed-fee letters earn their protection

The fee clause needs to say that the client won't be billed for anything not authorized, and that fees won't exceed what's stated in the letter unless both sides agree in writing. That second part is the whole point of a fixed fee, and it only holds if the letter backs it up.

When a return turns out to be more complicated than expected, best practice is to stop the work, put together a written change order with a fixed price for the additional piece, and get the client's approval before going further, not to finish the work and present a bigger bill afterward. Common triggers for this in tax compliance work include an unanticipated schedule (a rental property sale, a K-1 from a new partnership), an additional jurisdiction nobody scoped for, records that arrive so disorganized they need bookkeeping cleanup before the return can even start, or the discovery of a filing requirement, an FBAR, a Form 3520, that never came up at intake.

Each of those triggers needs a named process in the letter itself: the firm identifies it, notifies the client in writing, and issues a written amendment or a new letter before proceeding. Payment mechanics reinforce all of this. A deposit taken at signing, held rather than applied to current work until the engagement wraps up or ends, is standard practice according to Intuit's Tax Pro Center guidance. Balances due before the firm releases or e-files the return give the firm its real leverage, since withholding delivery is often the only practical enforcement mechanism available. Payment terms should be stated in short, explicit windows. And if cash payments cross $10,000 in a single transaction or a series of related ones, the letter should note the firm's obligation to file Form 8300.

Client responsibility, reliance on client data, and liability limitation language

Every fixed-fee letter needs to spell out what the client is on the hook for: providing accurate and complete information, keeping adequate internal controls, reviewing deliverables and flagging errors within a set window, making the actual financial decisions since the firm only advises, and staying compliant with any filing obligation that falls outside the defined scope.

Tied directly to that is the reliance clause, language stating that the firm's work rests entirely on the information the client supplies, and that the firm isn't liable for errors caused by inaccurate or incomplete client data. This connects straight back to pricing: the fixed fee was set based on the complexity the client disclosed at intake. Complexity that appears later and wasn't disclosed at intake is a scope problem and a liability problem at the same time, not one or the other.

Liability limitation clauses need a dose of realism. They don't grant blanket immunity, courts routinely decline to enforce the more extreme versions of these clauses, and no state law lets a CPA escape liability for gross negligence or willful misconduct. A common approach caps liability at a multiple of fees charged, with an explicit carve-out for gross negligence or willful misconduct. Treat these clauses as risk reduction.

The AICPA Tax Section's Terms and Conditions Addendum, also developed with CNA, handles a lot of this surrounding material: billing and payment terms, professional termination and withdrawal, proprietary information, conflicts of interest, records management, and dispute resolution. Pairing that addendum with the main letter keeps these issues covered without turning the engagement letter itself into a document that tries to anticipate every possible contingency.

Clauses that belong in every fixed-fee letter but are routinely left out

Start with the engagement period. Every letter needs a stated start and end date, or at minimum a defined tax year, because that boundary determines the "discovery" window in any future claim and keeps a client from arguing the relationship was still active months or years later.

Communication expectations shape how a firm operates: preferred contact methods, expected response times, and how a thorny issue gets escalated and documented. Circular 230 Section 10.33 treats this as part of due diligence, not an afterthought. The letter should also say what happens if the client is late with information, whether the firm files an extension automatically, and whether that extension work is baked into the fixed fee or triggers a separate charge. E-filing should be stated as the firm's default, with exceptions spelled out, since most jurisdictions now require it anyway.

Examination and notice handling deserves its own explicit line: how IRS or state correspondence after filing gets handled, and that this work sits outside the original engagement with its own fee. This is one of the most common places scope quietly creeps, so naming it up front closes that door before it opens. Data privacy obligations should be addressed directly in the letter, and firms with clients subject to additional privacy regulations need to cover those requirements rather than assuming general language is sufficient.

Dispute resolution language, mandatory mediation before either side heads to litigation, is standard advice from insurers, and skipping it leaves a firm exposed to exactly the kind of costly litigation the clause exists to prevent. E-signatures are widely accepted for engagement letters, and for IRS-related work, knowledge-based authentication solutions address the identity verification question that comes with signing remotely. Finally, engagement closure deserves formal treatment: the AICPA Tax Section's 2025 Engagement Closure Letter, released November 10, 2025, exists specifically to mark when a professional relationship ends, which matters enormously for liability purposes since an engagement with no defined end can be argued to still be running.

The billing shift's workflow problem, unsolved by the letter alone

Fixed-fee pricing shifts risk. Under hourly billing, the client absorbed the risk of an unpredictable bill. Under fixed-fee billing, the firm absorbs the risk of scope creep it doesn't get paid for. The engagement letter draws the legal boundary line, but whether that line actually holds depends on the firm's intake process and day-to-day workflow, not on the letter alone.

The most common breakdown happens quietly: a preparer works through a return, hits something extra, such as an added schedule or a follow-up question that opens into a bigger issue, and just handles it, because in the moment it doesn't register as out-of-scope work. The letter defined the boundary perfectly well. Nobody was watching for it at the point where the boundary actually got crossed. A well-written fixed-fee letter sets the terms of the deal, but enforcing those terms in real time is a workflow discipline the letter itself can't provide.