Keep QuickBooks and ProSeries Accessible When Accounting Staff Leave

When a staff accountant's personal phone holds your firm's QuickBooks 2FA, their departure becomes your access crisis — during the busiest season of the year. JoltSMS gives your firm a dedicated, firm-owned verification number so platform access stays with the practice, not with whoever configured it last.

  • Dedicated US number the firm owns — not tied to any individual staff accountant, bookkeeper, or seasonal hire
  • Shared inbox so authorized staff receive QuickBooks, Xero, Gusto, and ProSeries codes instantly without relaying through a personal phone
  • Team Access with Owner, Manager, and Viewer roles so partners control who sees what
  • Message history with timestamps documents your MFA implementation for FTC Safeguards Rule and WISP compliance reviews
JoltSMS shared inbox showing a CPA firm receiving a QuickBooks Online 2FA verification code in real time

Verification codes from QuickBooks, Xero, Gusto, and ProSeries arrive in a shared firm inbox — visible to the right people regardless of who is at their desk.

How accounting firms accidentally make phone verification a single point of failure

It starts with the firm's first QuickBooks Online account. The office manager registers 2FA on their personal iPhone. A staff accountant sets up ProSeries on their cell because it is the only phone they have at onboarding. The bookkeeper links their number to Gusto payroll. By the time the practice has been running for three years, access to eight critical platforms is scattered across six personal phones — and nobody has documented which number belongs to which portal. With 20% annual voluntary turnover at public accounting firms (AICPA data), this is not a theoretical risk. It is a recurring crisis that arrives every busy season: January brings new seasonal staff who configure personal phones on firm accounts, and May brings their departure — leaving behind 2FA registrations on phone numbers the firm no longer controls.

ProblemWhat it looks like for accounting firms & cpa practices
Staff departure account lockoutA junior CPA leaves mid-filing season. Their personal phone was registered as the 2FA for the firm's QuickBooks Online account. The firm is locked out of live client financials during active tax deadlines. QuickBooks support recovery can take 1-2 business days — days the firm does not have.
ProSeries single-phone catch-22ProSeries and Lacerte allow only one phone number for 2FA with no backup option. Intuit's own support has confirmed this limitation. If that phone belongs to a departed employee, the firm cannot log in to access client tax returns — and cannot update the registered number without first being able to log in.
Seasonal staff MFA sprawlTax season brings temporary hires who need platform access. They configure their personal phones on firm accounts as the fastest path to login. When they leave in April or May, their personal numbers remain registered as 2FA contacts on accounts the firm still actively uses.
FTC Safeguards Rule compliance gapThe FTC Safeguards Rule (16 CFR §314.4) requires all tax professionals — including solo practitioners — to implement MFA and document it in a Written Information Security Plan (WISP). When 2FA is distributed across personal phones, the firm cannot demonstrate firm-controlled, auditable MFA to IRS or FTC reviewers.
Code-relay productivity drainWhen QuickBooks is registered to a partner's phone and a staff accountant needs to log in, they must contact the partner, wait for the code relay, and then complete login. At $250/hour billing rates, 10 minutes of 2FA friction per login across multiple staff is thousands of dollars of wasted time over a 90-day tax season.

Turn verification from a personal phone problem into a firm-owned system

JoltSMS provides your firm with a dedicated, non-VoIP, real-SIM US number that belongs to the practice — not to any individual staff member or seasonal hire. Register it as the 2FA contact on QuickBooks, Xero, Gusto, ADP, ProSeries, Lacerte, and every other platform your firm uses. When staff join or leave, nothing changes — the number stays with the firm, and every platform account stays accessible.

  • Dedicated US real-SIM number accepted by QuickBooks Online, Xero, Gusto, ADP, and ProSeries — survives any personnel change without account recovery
  • Non-VoIP real SIM passes carrier verification checks on accounting and payroll platforms that block VoIP numbers
  • Shared inbox with role-based access — staff accountants and bookkeepers receive codes while partners control permissions
  • Complete message history for every received code — timestamped audit trail for FTC Safeguards Rule, WISP documentation, and cyber insurance reviews
  • Instant Slack, email, or webhook notifications so the right person receives the code the moment it arrives — even during client calls or remote working
JoltSMS numbers dashboard showing an accounting firm's dedicated verification number with active status and platform labels

One firm-owned number. Registered across your entire accounting software stack. Stable through any staff change.

Common ways accounting firms use JoltSMS

The Departing Staff Accountant Scenario

A junior CPA gives two weeks notice mid-March. With JoltSMS, the firm's QuickBooks Online and Gusto accounts are registered to the firm number — not the departing accountant's iPhone. The managing partner removes the employee's JoltSMS team access on their last day. Every platform account — QuickBooks, Xero, Gusto, ProSeries — remains fully accessible. No support tickets. No filing delays. No access crisis during the worst possible time of year.

FTC Safeguards Rule and WISP Compliance

The FTC Safeguards Rule requires every tax professional to implement MFA and document it in a Written Information Security Plan. A firm-owned JoltSMS number satisfies all three compliance gaps at once: the firm controls the authentication factor (not an individual employee's personal phone), message history provides a timestamped audit trail of authentication events, and role-based team access lets the firm demonstrate granular permission controls to IRS or FTC reviewers.

Seasonal Staff Onboarding and Offboarding

A 12-person firm brings on four temporary staff from January through April. With JoltSMS, all four are added as Viewers on the shared inbox — they can receive codes but cannot change firm settings. When tax season ends and they depart, the managing partner removes their JoltSMS access with one click. The firm number remains registered on QuickBooks, ADP, and ProSeries unchanged. No platform updates needed. No recovery calls.

How a CPA firm typically rolls out a firm-owned verification number

1

Provision a dedicated firm number

Sign up for JoltSMS and provision a dedicated US real-SIM number. This becomes the firm's permanent verification contact — not tied to any partner, manager, or seasonal hire.

2

Replace personal numbers on accounting platforms

Work through each platform — QuickBooks Online, Xero, Gusto, ADP, ProSeries, Lacerte, TaxDome, and IRS e-Services — and update the 2FA phone number from personal cell phones to the JoltSMS firm number. This one-time migration takes 30-60 minutes across a typical firm's platform stack.

3

Configure the shared inbox and team access

Invite partners, staff accountants, bookkeepers, and office managers with appropriate roles. Owners manage billing. Managers configure notification rules. Viewers receive codes in the shared inbox without touching firm settings.

4

Route codes to where your team already works

Configure notification rules to deliver incoming codes to Slack, email, or Microsoft Teams. A QuickBooks code during tax season reaches the staff accountant who needs it without anyone checking a separate dashboard.

5

Establish a staff offboarding protocol

When an employee or seasonal hire departs, remove their JoltSMS team access. The firm number remains registered on every platform — unchanged and accessible. Document this step in the firm's WISP for FTC Safeguards Rule compliance.

JoltSMS inbox showing a QuickBooks Online 2FA code arriving in an accounting firm's shared verification inbox

Role-based access that mirrors how CPA firms actually operate

Accounting firms have clear working hierarchies: partners set direction, managers supervise engagements, and staff handle day-to-day workflows. JoltSMS Team Access maps directly to that structure — partners keep control of billing and permissions while staff accountants and bookkeepers get the codes they need to do their jobs.

  • Owner role — Assigned to the managing partner or firm administrator. Controls billing, number provisioning, and full team access. Typically one or two people at the practice.
  • Manager role — Assigned to senior managers, engagement leads, or the office manager. Can configure notification rules and manage team members without touching billing or provisioning.
  • Viewer role — Assigned to staff accountants, bookkeepers, and seasonal hires. Read-only inbox access — they see and use codes but cannot change firm settings or team membership.
  • Invite team members by email with a 7-day expiry link. When a seasonal hire departs or a staff accountant leaves, one click removes their access — the firm number and all platform registrations remain untouched.
Learn more about Team Access
JoltSMS team access settings showing partner, manager, and staff roles configured for an accounting firm

Get verification codes where your firm already works

Accounting firms run on deadlines. JoltSMS delivers verification codes to the tools your team already uses — so a QuickBooks or Gusto 2FA code never sits unseen in a tab while a client is waiting for an answer.

  • Slack — Route QuickBooks, Xero, and ProSeries codes to a private firm Slack channel. The staff accountant handling the engagement gets the code without interrupting a partner's client call.
  • Email — Forward all incoming verification codes to a firm operations email address or a shared distribution list. Every code becomes a timestamped email record — directly useful as a WISP audit trail.
  • Discord — Smaller firms and modern practices using Discord for internal communication can receive codes in a private server channel, keeping the verification workflow inside existing tools.
  • Webhooks — For firms with practice management systems or custom intake workflows, codes can be HTTP-posted to any endpoint — enabling automated logging without manual dashboard access.
See all notification options
JoltSMS notification configuration panel showing email and Slack set up for an accounting firm's verification workflow

Accounting firm verification — common questions

If the QuickBooks 2FA is registered to that accountant's personal phone, your firm will lose SMS verification access when they leave — and recovery requires contacting QuickBooks support, which typically takes 1-2 business days. During tax season, that delay can directly affect client filings. The fix is to register your QuickBooks account to a JoltSMS number the firm owns outright. When a staff member departs, you simply remove their JoltSMS team access. The number — and your QuickBooks account access — remains exactly as it was.

Also see how law firms use JoltSMS to handle the same personnel departure problem — ABA Model Rule 1.6 compliance creates the same firm-owned MFA requirement that CPA firms face under the FTC Safeguards Rule.

Also relevant for insurance agencies managing GLBA Safeguards Rule MFA documentation — a shared regulatory framework with accounting firms.

Give your firm a verification number that survives any staff change

Stop routing QuickBooks, Xero, and ProSeries access through personal phones. One firm-owned JoltSMS number keeps every accounting platform tied to the practice — not to whoever happens to be the current staff accountant.