This year's PTIN application asks a question that takes a second to answer. Line 11 of Form W-12 asks you to confirm that you know paid preparers are "required by law to create and maintain a written information security plan." Yes or no.
Line 11 is an acknowledgment of awareness, not a certificate. It does not ask whether you have a plan, and the IRS has not said what happens if you tick No. But the form is signed under penalties of perjury, and the law it points to is real: the FTC Safeguards Rule, which treats tax preparers as financial institutions.
If you have a WISP, there is a fair chance it started from the IRS sample in Publication 5708. That sample is a sensible base. It was last revised in August 2024, though, and it says nothing specific about outsourced or offshore work. That gap matters, because the people outside your office are the one part of the rule that the small-firm exemption does not touch.
I should say where I stand. My firm is one of those outside providers: CPA firms use us for bookkeeping and month-end close, so I see these questions from the receiving end. I have kept to what the rules say and linked every source at the end.
Who has to have a WISP?
The FTC Safeguards Rule (16 CFR Part 314) says that "an accountant or other tax preparation service that is in the business of completing income tax returns is a financial institution." Every covered firm must keep a written information security program with safeguards "appropriate to your size and complexity." The IRS puts it more bluntly in Publication 5708: tax and accounting professionals are covered "regardless of size."
Two details are easy to miss. The rule's example covers firms that complete income tax returns. If your firm only keeps books for businesses, whether the federal rule reaches you is less clear, so ask counsel (state data-security laws may apply either way). And contractors are not let off. The Tax Adviser's August 2026 ethics Q&A notes that when an independent contractor works for a firm, "both the independent contractor and the firm are required to have a WISP."
What does the Safeguards Rule require for service providers?
The requirement is short. Section 314.4(f) says you must oversee service providers by:
- "Taking reasonable steps to select and retain service providers that are capable of maintaining appropriate safeguards for the customer information at issue;"
- "Requiring your service providers by contract to implement and maintain such safeguards; and"
- "Periodically assessing your service providers based on the risk they present and the continued adequacy of their safeguards."
The IRS and its Security Summit partners repeated the same point in their August 2026 reminder about WISPs: select providers that can maintain appropriate safeguards, and make sure their contracts require compliance.
A service provider is anyone that "receives, maintains, processes, or otherwise is permitted access to customer information" through its services to your firm. Read that against your own office. It covers the IT consultant with remote access, the cloud storage or client portal provider, the payroll processor, any AI tool that receives client data, and any outsourced bookkeeping or preparation firm, onshore or offshore.
Individual contractors are covered twice over. The rule defines an "authorized user" as any "employee, contractor, agent, customer, or other person" with access to your systems. So the access limits, multi-factor authentication and activity logging that apply to your staff apply to them as well. The multi-factor rule, for instance, covers "any individual accessing any information system."
How much checking is enough? When it finalized the current rule in 2021, the FTC said periodic assessment "need not include extensive investigation of a service provider's systems." Where a large company hands a vendor sensitive information, "certifications, reports, or even third-party audits may be appropriate," but the Commission declined to prescribe "a one-size-fits all approach." Its business guide gives the practical version: "Your contracts must spell out your security expectations, build in ways to monitor your service provider's work, and provide for periodic reassessments of their suitability for the job." And if you hire someone to run the program for you, "the buck still stops with you."
Does the small-firm exemption get you off the hook?
Partly. If your firm maintains customer information on fewer than 5,000 consumers, four requirements fall away. Everything else stays, including oversight of service providers:
| Requirement under 16 CFR Part 314 | Fewer than 5,000 consumers |
|---|---|
| Written information security program (314.3) | Required |
| A Qualified Individual in charge of the program (314.4(a)) | Required |
| Written risk assessment (314.4(b)(1)) | Exempt |
| Access controls, encryption, multi-factor authentication, secure disposal, activity logging (314.4(c)) | Required |
| Continuous monitoring, or an annual penetration test and vulnerability scans every six months (314.4(d)(2)) | Exempt |
| Security awareness training (314.4(e)) | Required |
| Oversight of service providers (314.4(f)) | Required |
| Written incident response plan (314.4(h)) | Exempt |
| Annual written report to the board or a senior officer (314.4(i)) | Exempt |
| Notice to the FTC of a breach affecting 500 or more consumers (314.4(j)) | Required |
Count carefully. The FTC has said the 5,000 figure counts "all individual consumers about which a financial institution maintains customer information, including both current and former customers." A firm with 900 clients this year and ten years of files may be well past it.
The Qualified Individual, the person responsible for the program, can work for a service provider. If you take that route, the rule says you still "retain responsibility for compliance," must name a senior member of your own staff to oversee that person, and must require the provider to maintain a program that protects you.
What changes when the help is offshore?
The Safeguards Rule has no location test. Search Part 314 for "foreign," "offshore" or "United States" and you will find nothing. The location rules come from other places:
- Section 7216. A US preparer needs the taxpayer's written consent before disclosing tax return information to a preparer outside the United States. That includes your own offshore staff, and a contractor abroad who only views data held on a US server. For Form 1040 clients, the Social Security number must be masked before it leaves the country, unless both preparers maintain an "adequate data protection safeguard" and the consent says so. Revenue Procedure 2013-14 sets the mandatory consent wording. A knowing or reckless improper disclosure is a misdemeanor under section 7216, and section 6713 adds a civil penalty of $250 per disclosure or use, up to $10,000 a year. Our article on section 7216 and offshore client data covers the consent in detail.
- The AICPA Code. Before disclosing confidential client information to a third-party service provider, a member "should inform the client, preferably in writing" (ET 1.150.040). Administrative support such as record storage, software hosting and e-file transmittal is carved out. ET 1.700.040 then requires either a confidentiality contract plus reasonable assurance about the provider's procedures, or the client's specific consent. A 2024 Journal of Accountancy article from the professional liability insurer CNA recommends doing both. ET 1.300.040 adds that you must "adequately plan and supervise" the provider's work.
- State law. Several states require written contract terms with service providers that handle residents' personal information. Massachusetts (201 CMR 17.03) applies to anyone holding a Massachusetts resident's personal information, wherever the firm is based. Rhode Island, Maryland and Nevada have similar contract requirements, and New York and Oregon include them in their safe-harbor provisions. New York treats a business that complies with the federal GLBA rules as compliant with its own.
What should the service-provider section of your WISP say?
Three things: who has access, what they have agreed to, and when you last checked. A one-page register does most of the work. For each provider, record:
| What to record | Example: an outsourced bookkeeping firm |
|---|---|
| Provider and service | Monthly bookkeeping and close for 40 business clients |
| Data they can reach | General ledgers, bank and card statements, vendor files. No SSNs. |
| How they get in | Named user accounts in your accounting software, with multi-factor authentication |
| Where the data is viewed | Outside the US, so section 7216 consent is checked for any tax return information |
| Contract terms in place | Confidentiality, safeguards, MFA, no subcontracting, 24-hour incident notice, deletion at exit |
| Last assessment | Questionnaire and call in June; next review due next June |
When I read a firm's contract with a provider, these are the clauses I look for. As a provider, they are also the ones I expect to be asked to sign:
- Safeguards that match your WISP. The IRS sample says any third party that needs access "must be compliant with the standards contained in this WISP at a minimum."
- Access limited to the job. The rule requires you to limit users to "customer information that they need to perform their duties and functions."
- Multi-factor authentication and encryption for customer information in transit and at rest.
- Named people, vetted and trained. Background checks, signed acknowledgments (Publication 5708 has a template in Attachment D) and inclusion in your annual training, which the IRS sample extends to "independent contractors, including temporary and contract employees."
- No subcontracting without your written consent.
- Incident notice within a fixed number of hours. No rule sets the provider's deadline, but yours are short. The FTC wants notice no later than 30 days after discovery of an event affecting 500 or more consumers, and e-file providers must tell the IRS by the next business day. The rule also treats knowledge held by your "employee, officer, or other agent" as yours, so depending on the relationship, a provider sitting on bad news may start your clock without you knowing.
- Return or deletion at the end, with written confirmation. Your own duty is to dispose of customer information no later than two years after its last use, unless you have a legitimate reason or a legal requirement to keep it.
- A right to assess: an annual questionnaire, a call, and evidence such as a SOC 2 report where the provider has one.
Why does a provider's breach become your problem?
The cautionary tale I keep coming back to is a small one. In October 2025, New York's attorney general announced a $60,000 settlement with Wojeski & Company, an accounting firm, over two data incidents. The second happened in May 2024, when "an employee from a firm hired to help with the investigation improperly accessed customer data located in the files that Wojeski had sent for review." The outside firm brought in to deal with the first incident caused the second.
Size is no protection either. In 2026, EY told US clients that a third-party IT service management platform had been accessed and that documents attached to tax support tickets were taken, according to TechRadar. And the IRS said that in the first half of 2025 nearly 300 data breaches were reported, affecting as many as 250,000 clients.
A word on penalties, because the subject attracts a lot of scare stories. The FTC has said it cannot obtain civil penalties for a first violation of the Safeguards Rule. What it can do is investigate and put a firm under an order, and violating that order can cost up to $53,088 per violation (the FTC kept its 2025 penalty levels for 2026). For most firms the sharper risks sit elsewhere: penalties under sections 7216 and 6713, state attorneys general, the terms of your malpractice policy, and, for willful failures, discipline under Circular 230. The IRS Office of Professional Responsibility made that last point in July 2026, warning that a missing WISP could expose a practitioner to liability under the Safeguards Rule and the terms of their malpractice coverage, and "in circumstances of willfulness, to discipline under Circular 230."
What should a provider be able to show you, including us?
Since I am asking you to hold providers to this standard, here is how my firm answers. A mutual NDA is signed before we see a record, and every team member who touches client work has also signed an individual confidentiality agreement. We work only inside the client firm's own systems, from work computers, with every login in a password manager and two-factor authentication switched on. Social Security numbers are masked by default. We report any suspected security incident to the firm within 24 hours of discovering it.
We do not have a SOC 2 report or ISO 27001 certification. Both are on our roadmap, and until an independent auditor signs one off, we say so plainly. If your policy requires an attestation, that is a perfectly good reason to choose someone else. The rest of the detail is on our security and confidentiality page.
A checklist before December 31
- Renew your PTIN. Current PTINs expire on December 31, 2026, the fee for 2027 is $18.75, and you need a valid 2027 PTIN before you prepare returns.
- List every person and firm outside your staff who can reach client data, including former contractors whose access was never switched off.
- Check each contract against the clauses above, and note what is missing.
- Confirm multi-factor authentication on every system, for every user, including remote contractors.
- Count consumers, current and former, to see whether the small-firm exemption applies.
- Check section 7216 consents for any client whose return information is seen outside the US, and confirm SSNs are masked where required.
- Update your client disclosure about third-party providers under the AICPA Code.
- Collect signed acknowledgments from contractors and update your list of who has access (Publication 5708, Attachments D and F).
- Write the date of each provider review into the WISP, and set the next one.
None of this needs a consultant. It needs an afternoon, a list and a few slightly awkward emails.
Frequently asked questions
Do I need a WISP to renew my PTIN?
Form W-12 asks you to confirm, yes or no, that you are aware paid preparers are required by law to create and maintain a written information security plan. It is an acknowledgment of awareness, not proof of a plan. The requirement itself comes from the FTC Safeguards Rule, which applies to firms in the business of preparing income tax returns.
Does the FTC Safeguards Rule apply to small tax firms?
Yes. Firms that maintain information on fewer than 5,000 consumers, counting former clients, are exempt from four specific requirements: the written risk assessment, continuous monitoring or penetration testing, the written incident response plan and the annual written report. Everything else, including oversight of service providers, still applies.
What must a WISP say about service providers?
The rule requires three things: take reasonable steps to choose providers capable of maintaining appropriate safeguards, require those safeguards by contract, and periodically assess each provider based on the risk it presents. A register listing each provider, its access, its contract terms and the date of its last review covers all three.
Can offshore staff access US client tax data?
The Safeguards Rule does not restrict location, but section 7216 requires the taxpayer's written consent before tax return information is disclosed to a preparer outside the United States, including viewing data held on a US server. For Form 1040 clients, the SSN must be masked unless both preparers maintain an adequate data protection safeguard and the consent says so.
How often should a WISP be updated?
There is no fixed annual deadline, but the rule requires you to evaluate and adjust the program in light of material changes to your operations or business arrangements. Taking on a new service provider is exactly that kind of change.
How much does it cost to renew a PTIN for 2027?
$18.75, the same as for 2026. Current PTINs expire on December 31, 2026, and anyone preparing federal returns for compensation needs a valid 2027 PTIN before preparing returns.
This article is general information about US federal rules, AICPA standards and selected state laws as of November 2026. It is not legal advice. State requirements vary, so check with counsel for your own firm's position.
Sources
- Form W-12 (Rev. October 2026) and its instructions (IRS)
- IR-2026-130: Tax professionals should renew their PTINs for 2027 (IRS, November 4, 2026)
- PTIN application and renewal FAQs (IRS)
- 16 CFR Part 314, Standards for Safeguarding Customer Information (eCFR)
- Safeguards Rule final rule and preamble, 86 FR 70272 (FTC, December 2021)
- FTC Safeguards Rule: What your business needs to know (FTC)
- Publication 5708, Creating a Written Information Security Plan (IRS, Rev. 8-2024)
- Publication 4557, Safeguarding Taxpayer Data (IRS)
- IR-2026-92: Tax pros need a written information security plan (IRS, August 2026)
- OPR Issue 2026-22: How to be a careful WISP(er) (IRS Office of Professional Responsibility, July 2026)
- Publication 1345, Handbook for Authorized IRS e-file Providers (IRS, Rev. 10-2026)
- 26 CFR 301.7216-3 (eCFR) and Revenue Procedure 2013-14 (IRS)
- AICPA Code of Professional Conduct, ET 1.150.040, 1.300.040 and 1.700.040 (edition updated through July 2026, hosted by the Minnesota Board of Accountancy)
- Outsourcing and professional liability (Journal of Accountancy, September 2024)
- Tax ethics and risk management: Common questions and answers, Part 1 (The Tax Adviser, August 2026)
- Settlement with Wojeski & Company (New York Attorney General, October 2025)
- Ernst & Young reveals data breach following hack on support system (TechRadar, July 2026)
- IR-2025-88: Security Summit summer series wraps up (IRS, August 2025)
- Prepared statement on data security (FTC, March 2019) and 2026 civil penalty notice (FTC, September 2026)
- 201 CMR 17.00 (Massachusetts) and General Business Law 899-bb (New York)
