State tax preparer engagement letters: what to include

A state tax preparer engagement letter does one job: it records the work your practice has accepted for a client's state and local returns and what the client must do for that work to be finished. It does not register the preparer, satisfy a state posting rule, or authorize an electronic filing. This article gives the drafting items to include when the scope is state and local returns, then separates those contract terms from the state and city duties that sit outside the letter: California's registration regime, New York's posting law, New York City's consumer materials, and the filing authorization each return needs.

Separate the contract, the registration, and the filing authorization

An engagement letter is a written contract between the practice and the client. A registration requirement concerns the preparer's authority or eligibility to perform services. A posting requirement concerns information displayed at the place of business. A filing authorization concerns the transmission of one specific return. These documents can come out of the same intake process without being interchangeable: a signed letter does not prove that a required notice was delivered, and a registration certificate says nothing about the services the client bought.

Keep three questions apart as you review the package:

A fourth layer is private and is often mistaken for law. An insurer's preferred wording, a professional association's template, or a software vendor's default paragraph can help you draft, but none of them becomes a state requirement because it is widely used. Review professional liability insurance coverage as a question separate from the legal basis for a clause.

Where a state or city imposes something, it appears in that jurisdiction's own preparer provisions or licensing rule and has to be verified for that place, the credential involved, and the service being sold. Check the body that regulates your credential: a state board of accountancy for a CPA, a state bar for an attorney, the IRS for an enrolled agent or a PTIN holder.

The drafting checklist for a state-scope engagement letter

Build the letter around the actual assignment instead of a general promise to handle the client's taxes. Each item below should be answered clearly enough that another staff member could understand the file without asking the preparer.

1. Identify the client and the tax years

Name the person or entity receiving the services and list the tax years covered. For a business client, keep the entity's engagement separate from work for its owners or related businesses. Say whether the assignment covers an original return, an amended return, or another specified service, and avoid wording that pulls earlier years or later work into scope by accident.

2. Name every return and jurisdiction

List the federal, state, and local returns included in the assignment. Use the correct return names when the client's filing position is known: California Franchise Tax Board Form 540 is the resident individual income tax return, New York Form IT-201 is the resident individual income tax return, and New York Form IT-203 serves nonresident and part-year resident individual filers. If residency or the filing obligation is unresolved, mark the scope as needing confirmation instead of committing to a return the client used last year.

Record the filing date the client expects the practice to meet, and state plainly that the engagement letter neither sets nor extends a statutory due date. A letter signed late in the season changes the working arrangement; it does not change the date the return is due.

3. Describe what the client must supply

Identify the records the agreed work requires and how the client will deliver them securely. Include the client's duty to report changes that can affect a state filing obligation, such as a move, work in another state, or new business activity in another jurisdiction. Set a document-delivery target for your own office and label it an internal scheduling target: it is not a statutory deadline, and missing it does not mean an extension has been requested or filed.

4. Explain review and filing authorization

Describe how the completed return goes to the client for review, how corrections are reported, and who obtains the filing authorization and transmits or mails the return. Keep the engagement letter separate from return-specific authorization. IRS Form 8879 is the e-file signature authorization for individual income tax returns filed electronically with the IRS, and a signature on an engagement letter does not replace it when that form is required.

State authorization must be checked for the return and the filing method involved. Do not assume that a federal authorization covers every state return; confirm the state's own requirement by name before transmission, and keep the signed authorization with the return record.

5. Address extensions and payment

Say whether preparing an extension request is included, requires separate approval, or falls outside the assignment. An engagement letter is not an extension request. For individual federal returns the extension request is Form 4868, and a state extension is filed under that state's own procedure; the letter should say who prepares it. An extension of time to file generally does not extend the time to pay, so explain how payment information reaches the client and what action remains with the client.

6. Describe the charge and the exclusions

Explain how the agreed charge is communicated, what work it covers, and how additional work is approved. Avoid a vague reference to extra services without saying how the client learns about a changed scope and consents to it. List the exclusions that matter to this assignment — bookkeeping cleanup, amended returns, responses to notices, audit representation, and returns for other entities — unless those services are expressly included.

7. Set a change process

Explain what happens when information arriving during preparation reveals an additional state return or other work. Require a documented scope decision instead of letting the assignment grow through a hallway conversation. Record the revised work, the agreed charge arrangement, and the client's approval, and keep that record with the original engagement so the filing team can see which terms currently apply.

State and city requirements that stay outside the letter

Start with the authority responsible for the particular requirement. A state tax department, a preparer registration body, and a city consumer agency address different parts of the client relationship, and none of them collects your engagement letter.

California shows the registration layer. Registration for tax preparers who are not attorneys, certified public accountants, or enrolled agents runs through the California Tax Education Council under the California Business and Professions Code, section 22250 and following. That regime governs who may prepare returns for compensation; it does not supply your contract terms. Treat any CTEC disclosure or contract item as a separate requirement to verify against current CTEC materials rather than a clause to copy from a template.

New York shows the posting layer. The Department of Taxation and Finance explains that New York posting requirements under Tax Law § 32 require tax return preparers and facilitators to post certain items at their places of business. That is a posting rule, and it should not be relabeled as mandatory engagement-letter language.

New York City adds a city layer. The Department of Consumer and Worker Protection publishes tax preparer consumer rights material for filers. Review the city's instructions separately from the state posting rule and separately from the terms you negotiate with the client.

For each verified obligation, record the authority, the preparer or service it covers, the required action, and any delivery or display instruction. Preserve the official document rather than assuming a paragraph in the letter is an adequate substitute. On the federal side, Treasury Department Circular 230 (31 CFR Part 10) supplies the diligence and return-advising standards that apply to practitioners, and a PTIN or an EFIN is a credential record rather than a contract term. None of these belongs in the scope clause of a client letter.

Make the letter usable by the filing team

A letter can be clear to its author and still leave the rest of the office guessing. Put the accepted return scope, the client document target, the extension decision, and the filing responsibility into the client workflow as well as into the signed document, so a staff member preparing a state return can see what was sold without reading the whole engagement.

Use status labels that describe completed events. "Engagement accepted," "return reviewed," "authorization received," "transmitted," and "accepted by the taxing authority" are different points in the season, and one should not be used to imply another. Assign one person to confirm that the signed letter matches the returns actually being prepared; if a return is added or removed, update the scope record before the file reaches final review.

Keep the client's questions and your answers with the engagement record. An explanation that affects scope should stay visible to the reviewer instead of sitting in a staff member's inbox. Connect the letter to your tax preparation service standards so the document describes what the practice can actually deliver rather than a workflow that exists only in a template.

When a document is missing

When staff find a missing notice, an unsigned engagement letter, or an absent filing authorization, identify which document is missing before deciding what to do. These are not the same problem and should not receive the same automatic response.

Classify the gap as a legal obligation, a contractual agreement, or an internal control. Name the responsible person and the action needed before the related work proceeds, then close the gap in the record rather than in memory.

Do not backdate a signature or record a disclosure as delivered when it was not; preserve the actual sequence of events and seek qualified advice if the omission raises a legal or contractual question. Avoid assuming that every omission produces a fine, voids a limitation-of-liability clause, or blocks a registration renewal — those outcomes depend on the applicable rule and the facts. Use your complaint handling process when a client disputes what was promised or delivered, and keep the complaint record distinct from any corrective filing or disclosure.

Review the package before it goes out

Before intake staff send the engagement package, confirm that:

The finished package should make the assignment understandable and leave a usable record. Its purpose is not to make one letter stand in for every registration rule, consumer notice, filing authorization, or office procedure.