If you prepare tax returns for pay, you handle some of the most sensitive information people have: Social Security numbers, bank accounts, income and family details. Federal rules expect you to protect it, and to write down how you do it. That written document is called a WISP, short for Written Information Security Plan.
Why tax preparers need one
Under the Gramm‑Leach‑Bliley Act, the FTC treats tax preparers and many accounting and bookkeeping firms as “financial institutions.” That puts them under the FTC Safeguards Rule, which requires a written information security program. Size doesn’t matter: a one‑person seasonal office is covered just like a large firm.
The IRS reinforces this. When you renew your PTIN, you’re asked to confirm that you understand your data security responsibilities, and the IRS and its Security Summit partners publish a sample plan (IRS Publication 5708) to help preparers create one.
In plain terms: a WISP is your office’s rulebook for keeping client data safe. It says who is in charge, what the risks are, what protections you use and what you’ll do if something goes wrong.
What a good WISP includes
- A responsible person. Someone named to oversee your security program.
- A risk assessment. Where client data lives, who can reach it and what could go wrong.
- Your actual safeguards. Passwords and multi‑factor authentication, encryption, secure software, locked file cabinets, backups and how you dispose of old records.
- Staff training. How employees learn to spot phishing and handle data properly.
- Vendor oversight. How you make sure your software providers and IT help protect data too.
- An incident response plan. Exactly who you contact and what you do if data is lost or stolen.
- Regular reviews. A schedule for updating the plan as your office changes.
The most common mistake: a generic template
Downloading a template is a fine start, but a WISP only helps if it describes what your office really does. A plan that mentions encryption you don’t use, or leaves out the laptop you take home, won’t protect you when it matters. Your WISP should name your actual software, devices, people and vendors.
Getting started
- List everywhere client data lives: software, computers, phones, email, cloud storage and paper files.
- Note who has access to each one.
- Write down the protections already in place, and the gaps.
- Decide what you’ll do about each gap, and by when.
- Put it in writing, have staff acknowledge it and set a date to review it each year.
A WISP isn’t just paperwork for the regulators. It protects your clients, your PTIN and the reputation you’ve built.
Need a WISP for your practice? See our WISP service for tax professionals or get started.
Keep reading
- The 9 elements of the FTC Safeguards Rule, in plain English
- Before tax season: a data security checklist for small tax offices
This article is for general education only and isn’t legal, tax, credit or investment advice. Rules vary by state and situation. Talk with a qualified professional about your specific circumstances.