Your Payroll Provider Was Breached. What Should Your Texas Business Do?
When a payroll vendor reports a breach, learn what to ask, how to keep payday on track, and which Texas notice and cyber insurance questions to raise.

It’s Thursday morning, payroll is due Friday, and your payroll provider sends a notice: an unauthorized person may have obtained files containing employee information. The portal still opens. The notice doesn’t say whether your staff’s records were among those files. Now two people need answers: the employee who wants to know whether their Social Security number was exposed, and the bookkeeper who needs to know whether it’s safe to run payroll.
Those are separate questions. You may be able to verify Friday’s pay run before the vendor can tell you whose information was taken. At the same time, your business may have reporting or notification responsibilities even if nothing happened on your own network. Here’s how to handle both tracks without waiting for the vendor’s final report.
Verify the notice and protect the next pay run
Confirm the notice independently. Call the payroll provider using a number you already have, or open its portal from a saved bookmark. Don’t follow a button in an unexpected email or disclose login codes to an incoming caller who claims to be on the response team. Get a case number and a named contact. Tell the bookkeeper and whoever approves payroll how to verify any follow-up requests, including requests that sound like they come from the vendor or the owner.
Save the original message and start a timeline. Write down when it arrived, when you verified it, what the provider confirmed, and when you expect another update. Save the original message and relevant records in a restricted location. If your IT provider suspects your own accounts were involved, have it secure access and preserve records such as sign-in activity or payroll change history. Don’t delete messages or overwrite relevant logs in the course of cleaning up. The FTC’s breach response guide explains why preserving evidence and checking the service provider’s response matter.
Verify the pay file separately. Ask whether the incident affected the payroll processing system, an export of historical records, or both. Have an authorized employee compare the upcoming run with your last approved run and separately confirm any recent direct-deposit changes through a known contact. If a payment has already been redirected, contact the bank and payroll provider promptly. If the portal can’t be trusted or is unavailable, have your payroll lead work with the provider and bank on a secure fallback that still meets your pay obligations. An ordinary email thread full of account numbers is not a fallback.
Ask the vendor for facts specific to your account
A notice that says “some customer data may have been involved” is a reason to ask questions, not a basis for telling employees they were or weren’t affected. Send a short written request to your confirmed contact. Ask for:
- Your affected records and people. Which of our files, entities, and people are in scope? Does that include former employees, seasonal staff, or contractors? Can you provide a secure roster with the data fields involved for each person, without sending full Social Security or account numbers?
- What the evidence shows. Did someone obtain data, or is the vendor still determining whether that happened? What is confirmed, what is reasonably suspected, and what hasn’t been checked? If the files were encrypted, could the unauthorized party decrypt them?
- Dates and ongoing access. When did the activity occur? When did you discover it, and when did you determine our records were involved? Is there anything we should secure on our side, such as an integration or an administrator account?
- Notice plans and next update. Who is planning to contact affected people or regulators, on whose behalf, and when? What help will you provide with mailing, employee inquiries, or monitoring if appropriate? When will you update us even if some answers are still unknown?
Pull the service agreement and any data protection addendum. Check the notice contacts, cooperation obligations, and any provisions for who sends notices or pays for response costs. If the vendor says it will send a letter for you, ask counsel to review the draft, recipient list, and delivery plan. Get confirmation of what went out and when. A vendor’s promise to handle communications is not, by itself, confirmation that your obligations have been met.
Check who must be notified under Texas law
Texas Business & Commerce Code § 521.053 separates the duties of an organization that owns or licenses data from those of a provider that maintains it for someone else. The rule turns on the facts, including whether sensitive personal information was acquired, or is reasonably believed to have been acquired, by an unauthorized person. A file containing an employee’s full name and Social Security number in unencrypted form is one example of information the law protects. An outage alone doesn’t answer whether a breach requiring notice occurred.
- Provider to data owner or license holder. A provider that maintains but does not own the data generally must notify the owner or license holder immediately after discovering a breach if the acquisition or reasonable-belief standard is met.
- Data owner or license holder to affected individuals. A business operating in Texas that owns or licenses the computerized data generally must notify affected individuals without unreasonable delay and no later than the 60th day after it determines the breach occurred. The statute permits delays in specified circumstances, such as when law enforcement requests one because notice would impede a criminal investigation. Don’t treat the 60th day as a target.
- Separate report to the Texas Attorney General. A party required to give notice under the statute must also report to the Attorney General if the breach involves at least 250 Texas residents. The report is due as soon as practicable and no later than the 30th day after the party determines the breach occurred. The Attorney General’s electronic breach reporting form is separate from individual notices. Track the number of affected Texas residents and how many you’ve already notified; both counts are needed for the report.
For example, suppose a Friendswood contractor learns that names and Social Security numbers for 41 current and former employees were taken from its provider. The contractor’s headcount is not the right measure; the relevant people include former workers whose records were involved. If the contractor’s reportable breach involves only those 41 people, it’s below the 250-resident Texas Attorney General threshold, but the contractor still needs to address individual notices. The payroll provider’s incident may involve many more people across its clients. Its reporting analysis is not a substitute for the contractor’s. Ask privacy counsel to establish your company’s determination date and assess other states’ laws, industry rules, and contract deadlines as applicable. You may have people to notify outside Texas even if all your offices are here.
Call your cyber insurer while the vendor investigates
Pull your policy and use its reporting channel when you learn of a potentially covered incident. Don’t wait for a final list of affected people or an invoice before checking the reporting terms. For example, Travelers’ cyber claims guidance directs policyholders to report suspected as well as known incidents promptly. Your own policy tells you where to report, what information is needed, and which expenses require consent. Ask for a claim or incident reference and how to reach a breach coach, an attorney who helps coordinate the legal response.
Be ready to share the verified notice, timeline, and categories of data that may be involved. Use a secure channel for sensitive records. Before hiring a forensic firm, mailing vendor, or other outside provider, check whether the insurer requires approval or wants you to use firms from its approved list. If urgent containment is needed, don’t leave access open while waiting for an insurance callback; pursue both tracks at once and document your decisions.
Compare coverage for response costs, downtime, and stolen funds
The FTC’s cyber insurance guide distinguishes first-party coverage, which can address your own response costs, from third-party coverage, which can address claims made against your business. A payroll breach can raise both questions even if your network is intact. Ask your agent to show you where the actual policy answers these scenarios:
- A vendor loses employee data. Does the policy address data held by a payroll processor on your behalf? If the provider offers credit monitoring but won’t pay for your legal review, notices to former staff, or a help line, which expenses could be covered? If an employee brings a claim against you, look separately at privacy liability. Check limits, any smaller limits for specific costs, and your out-of-pocket amount.
- Payroll software goes offline. A New Braunfels restaurant may need to pay for an emergency processing service while its payroll provider recovers from ransomware. Ask if dependent cyber business interruption or extra expense coverage applies to that provider, what types of outages qualify, and whether a waiting period applies. A higher cost to run payroll isn’t the same as lost restaurant sales. Keep invoices and document why the expense was necessary.
- Pay is diverted or a client alleges an error. If someone impersonates an employee and redirects a deposit, ask about social engineering or funds-transfer fraud terms in both cyber and commercial crime coverage. Who initiated the transfer, whose money was lost, and what verification occurred can matter. If you’re a bookkeeping firm and a client instead alleges that your payroll services caused the loss, also review professional liability or errors and omissions (E&O) wording. Neither coverage question is answered simply by calling it a data breach.
Give employees a safe way to get updates
Choose a person in HR or management to handle questions and set a time for the next update. With counsel’s guidance, explain what you know, what you’re checking, and how workers can reach you through a channel they already recognize. Don’t tell everyone their information was stolen if that is still unconfirmed, or say no one was affected merely because pay arrived. An internal status update and a formal breach notice serve different purposes; one doesn’t automatically satisfy the other. If the provider is offering assistance, verify the enrollment instructions before sharing them and don’t ask employees to send sensitive information to a supervisor to check whether they qualify.
Test the plan before the next payday
Before the next renewal, run a short exercise: Can your backup payroll contact find the contract and the insurer’s reporting number? Can they get a secure copy of approved payroll records if the portal goes down? Ask the provider what multifactor authentication (MFA) is enforced for administrators, how historical files are retained, and how payroll can be restored or run during an outage. Document what the vendor controls and what you can verify yourself. If the insurer asks about MFA or backups, describe the actual setup rather than assuming the vendor’s safeguards match your own.
To compare cyber coverage for your Texas business, call BIG – Brock Insurance Group at (281) 482-4244 or request a quote below. We can help you compare coverage and value through our independent carrier network and review how the options fit the vendors and systems your business depends on.
Request a Quote