Golden Age CPAIT for Accounting FirmsSchedule a consultation
Home / For accounting firms / Tax season checklist
For CPA and tax firms

Tax season readiness checklist

The security and AI rules that apply to tax and accounting firms, in plain words, plus the everyday IT that keeps filing season calm. Work through it in the fall, before the season gets busy.

How to read this list

Required means a law or regulation asks for it. Expected by the IRS means IRS guidance on professional conduct calls for it. CPA ethics rule comes from the AICPA Code. Recommended is good practice from IRS security guides.

Section 1

Using AI safely with client data

There is no IRS rule written just for AI. The rules that already protect tax return information still apply when an AI tool touches it. Here is what that means in practice.

  • Keep taxpayer data out of public AI tools. Expected by the IRS

    Why it matters: Consumer AI chat tools can keep or learn from what you paste in, and they give you no confidentiality promise. In June 2026 the IRS told tax professionals to handle client data "using only secure, enterprise-approved AI" and to never upload sensitive data to unsecured or public systems.

    Source: IRS Office of Professional Responsibility, AI guidelines, June 2026

  • Have a short written AI policy and a list of approved tools. Expected by the IRS

    Why it matters: The IRS expects firm leaders to have written procedures, staff training, and vendor checks for AI under Circular 230 section 10.36. A list of approved tools also stops "shadow AI," where staff use tools nobody has checked.

    Source: IRS Office of Professional Responsibility, AI guidelines, June 2026

  • Check each AI vendor before client data goes in. Required

    Why it matters: The FTC Safeguards Rule requires you to oversee any service provider that handles client information, and to require safeguards by contract. Look for: no training on your data, data kept in the United States, confidentiality terms, and prompt breach notice.

    Source: FTC Safeguards Rule, 16 CFR 314.4; AICPA Code of Professional Conduct, 1.150.040 and 1.700.040

  • Know when a signed client consent is needed (Section 7216). Required when it applies

    Why it matters: Federal law (IRC 7216) makes it a crime to disclose or use tax return information for anything other than preparing the return without the client's signed, dated consent, unless an exception applies. US-based tax software and IT contractors working for you usually fit an exception. A signed consent is likely needed if the AI tool or its data is outside the United States, if the vendor uses your data for its own purposes, or if you use the data for anything beyond return preparation. The IRS sets the consent wording: its own page, at least 12-point type, signed before the data is shared. Civil penalties are $250 per disclosure.

    Source: Treas. Reg. 301.7216-3, taxpayer consent; Treas. Reg. 301.7216-2, uses allowed without consent; Rev. Proc. 2013-14, consent wording and format

  • Give IT and software contractors the written Section 7216 notice. Required

    Why it matters: You may share return information with contractors who maintain your systems or software, but only as much as they need, and only if every person who receives it gets a written notice explaining Sections 7216 and 6713 and their penalties. Many firms miss this step.

    Source: Treas. Reg. 301.7216-2, uses allowed without consent

  • Tell clients in writing that you use outside providers, including AI services. CPA ethics rule

    Why it matters: The AICPA Code says CPAs should tell clients, preferably in writing, before confidential client information goes to a third-party service provider, and should have a confidentiality contract with that provider or the client's specific consent. A short paragraph in your engagement letter usually covers it.

    Source: AICPA Code of Professional Conduct, 1.150.040 and 1.700.040

  • A person reviews every AI draft before it reaches a client or the IRS. Expected by the IRS

    Why it matters: AI tools can invent facts and citations. The IRS reads its due diligence and competence rules (Circular 230 sections 10.22 and 10.35) to mean you check AI facts, citations, and math yourself.

    Source: IRS Office of Professional Responsibility, AI guidelines, June 2026

Section 2

Your written security plan (WISP)

Every paid tax preparer is required by law to have a written information security plan, whatever the size of the firm. A sole practitioner's plan can be short. It does have to be real, current, and followed.

  • Your WISP is written, fits how your firm works today, and has been reviewed this year. Required

    Why it matters: The FTC treats tax preparers as financial institutions and requires a written security program. The IRS offers a sample plan in Publication 5708 that you can adapt.

    Source: FTC Safeguards Rule, 16 CFR 314.4; IRS Publication 5708, creating a WISP

  • One named person is in charge of the plan. Required

    Why it matters: The rule calls this person the Qualified Individual. It can be an outside provider, but your firm stays responsible and must name a senior person to oversee them.

    Source: FTC Safeguards Rule, 16 CFR 314.4

  • Every staff member has read the plan and signed an acknowledgment. Recommended

    Why it matters: A signed, dated acknowledgment shows the plan is in use, not just on file. The IRS suggests it in Publication 5708.

    Source: IRS Publication 5708, creating a WISP

  • You can honestly check the security plan box when you renew your PTIN. Required

    Why it matters: Form W-12 asks you to confirm, under penalty of perjury, that you know preparers are required to keep a written security plan. PTINs expire December 31 each year, so renewal is a good time to review the plan.

    Source: IRS Form W-12, PTIN application and renewal

  • A written risk assessment lists what could go wrong and what you do about it. Required at 5,000+ clients

    Why it matters: Firms with information on 5,000 or more clients must have one in writing. Smaller firms are exempt from that part, but a short risk list still makes the rest of the plan easier.

    Source: FTC Safeguards Rule, 16 CFR 314.4; 16 CFR 314.6, small firm exception

Section 3

FTC Safeguards Rule: the core protections

These are the controls the rule names for tax and accounting firms. Small firms are not exempt from any item marked Required here.

  • Two-step sign-in (MFA) is on for everything with client data. Required

    Why it matters: That means email, tax software, client portals, remote access, IRS e-Services, cloud storage, and banking. Each login is unique and kept in a business password manager. The rule requires MFA for anyone accessing any system with client information.

    Source: FTC Safeguards Rule, 16 CFR 314.4

  • Client data is encrypted on every computer, on backups, and when it is sent. Required

    Why it matters: A lost laptop with encryption turned on is an inconvenience. Without it, it may be a reportable breach. Lost or stolen devices should also be able to be locked or erased remotely.

    Source: FTC Safeguards Rule, 16 CFR 314.4

  • Each person can reach only what their job needs, and former and seasonal staff lose access the day they leave. Required

    Why it matters: The rule requires access controls that limit people to the client information they need. Leftover accounts from last season are a common way in for attackers.

    Source: FTC Safeguards Rule, 16 CFR 314.4

  • Staff have security training, including spotting fake "new client" emails. Required

    Why it matters: Tax season brings phishing emails posing as new clients with attached "tax documents." Training is required, and it should be refreshed as the risks change.

    Source: FTC Safeguards Rule, 16 CFR 314.4; IRS Publication 4557, safeguarding taxpayer data

  • Your systems are monitored, and tested on a schedule. Required at 5,000+ clients

    Why it matters: The rule asks for continuous monitoring, or a yearly penetration test plus vulnerability scans every 6 months. Firms with information on fewer than 5,000 clients are exempt from the test schedule, but monitoring is still good protection.

    Source: FTC Safeguards Rule, 16 CFR 314.4; 16 CFR 314.6, small firm exception

  • You follow a written policy for keeping and securely destroying old client data. Required

    Why it matters: Information you no longer need is risk you do not need. The rule calls for secure disposal within 2 years after you last use it, unless you need it for business or the law requires you to keep it.

    Source: FTC Safeguards Rule, 16 CFR 314.4

Section 4

Everyday IT before the season

The basics that keep filing season calm. None of these are new, and all of them still matter.

  • Every computer runs a supported, fully updated operating system and software. Recommended

    Why it matters: Most attacks use flaws that already have a fix. Unsupported systems stop getting fixes at all.

    Source: IRS Publication 4557, safeguarding taxpayer data

  • Security software is installed, current, and watched. Recommended

    Why it matters: The IRS recommends strong security software with regular scans. Someone should actually see the alerts.

    Source: IRS Publication 4557, safeguarding taxpayer data

  • Backups run on their own, include cloud apps, and one copy is kept where ransomware cannot reach it. Recommended

    Why it matters: Microsoft 365, Google Workspace, and portal data need their own backup. Do a test restore before the season starts, so you know it works.

  • Clients send documents through a secure portal, not plain email. Recommended

    Why it matters: Ordinary email is easy to intercept and easy to send to the wrong person. A portal also keeps records in one place.

  • Your email domain has SPF, DKIM, and DMARC set up. Recommended

    Why it matters: These settings make it much harder for criminals to send email that looks like it came from your firm.

  • The office network is current: firewall updated, default passwords changed, guest Wi-Fi kept separate. Recommended

    Why it matters: Printers and scanners count too. Remote staff connect through secure remote access, never an open connection.

  • Clients know they can get an IRS Identity Protection PIN. Recommended

    Why it matters: Any taxpayer can now get an IP PIN. It blocks someone else from filing a return with their Social Security number.

    Source: IRS, Identity Protection PIN

Section 5

If something goes wrong

Speed matters. If the IRS hears quickly, it can often block fraudulent returns using your clients' information. Keep this list printed, because your computers may be the thing that is down.

  • A written incident plan says who decides, who calls whom, and in what order. Required at 5,000+ clients

    Why it matters: Firms with information on 5,000 or more clients must have one in writing. For smaller firms, a one-page plan still saves hours on the worst day.

    Source: FTC Safeguards Rule, 16 CFR 314.4; 16 CFR 314.6, small firm exception

  • Report data theft to your local IRS Stakeholder Liaison right away. Required

    Why it matters: Authorized e-file providers must report a security incident no later than the next business day after it is confirmed. Firms that only file returns for clients report through their Stakeholder Liaison.

    Source: IRS Publication 1345, e-file provider rules; IRS, data theft information for tax professionals

  • Notify the FTC within 30 days if 500 or more people are affected. Required

    Why it matters: Since May 2024, the Safeguards Rule requires an online notice to the FTC within 30 days of discovery when unencrypted information on 500 or more people is taken.

    Source: FTC Safeguards Rule, 16 CFR 314.4

  • Notify affected Colorado residents within 30 days, and the Colorado Attorney General if 500 or more are affected. Required

    Why it matters: Colorado law requires notice within 30 days of determining a breach happened. More than 1,000 residents also means telling the national credit bureaus. Clients in other states may fall under those states' rules.

    Source: Colorado Attorney General, data protection laws

  • Know who else to call: state tax agencies, local police, the FBI, your insurance carrier, and your IT team. Recommended

    Why it matters: The IRS lists these steps for tax professionals. Check now whether your insurance covers a data breach.

    Source: IRS, data theft information for tax professionals

Watch list

Rules that are still changing

  • More IRS guidance on AI is expected. In November 2026 the head of the IRS Office of Professional Responsibility said more AI guidance is coming in the next few months.
  • Colorado's automated decision law starts January 1, 2027. It covers AI that helps make important decisions about people, such as hiring or lending. Using AI to draft emails or sort documents is unlikely to fall under it, but check before using AI to screen job applicants. Colorado Attorney General.

This checklist was last reviewed in November 2026.

How we help

You do the client work. We do the IT and security work behind it.

Most of this list is IT work, and the paperwork that goes with it. Our team handles it for your firm, so you can keep your attention on clients.

  • We set it up. Two-step sign-in, encryption, backups, secure client portals, email protection, and staff accounts.
  • We keep it current. Updates, monitoring, and a review of your written security plan when your office or the rules change.
  • We help with the paperwork. We work with you on your WISP, incident plan, AI policy, and vendor checks, and we keep the records together so they are ready when you need them.
  • We check AI tools for you. Before your team uses a new AI service, we review where the data goes and what the vendor's terms allow, and flag anything your advisor should look at.

Our Secure plan is built for tax and CPA firms: $219 per person, per month, 5-person minimum. It includes everything in Complete Care plus staff security training, written security plan updates, and a quarterly security review. See all prices.

Help desk hours are Monday to Friday, 9 AM to 5 PM. Complete Care and Secure plans add an after-hours emergency line.

Questions

Common questions about AI and client data

Does the IRS require us to tell clients we use AI?

There is no IRS rule that names AI or requires an AI disclosure on its own. But Section 7216 can require a signed client consent when tax return information goes to an outside party outside the allowed exceptions, and that includes some AI tools. CPAs also have an AICPA ethics rule about telling clients when outside providers are used. Many firms add a plain paragraph to the engagement letter and keep a 7216 consent form ready for uses that need one.

Can staff paste a client email into a chat AI to draft a reply?

Not into a public or personal AI account. The IRS has told tax professionals to use only secure, enterprise-approved AI with client data. A business AI tool your firm has checked and approved, with the right contract terms, is a different matter.

We are a small firm. Do these rules really apply to us?

Yes. The FTC treats tax preparers as financial institutions regardless of size. Firms with information on fewer than 5,000 clients skip a few written pieces, such as the formal risk assessment and test schedule, but still need the written security plan, two-step sign-in, encryption, training, vendor oversight, and breach notice.