An accounting firm should evaluate the security of its tax preparation software across six areas: data protection, user access, vendor security, hosting and infrastructure, backup and recovery, and ongoing support.

For a 5 to 25 employee accounting firm, tax preparation software is one of the most business-critical applications in the office. It may contain Social Security numbers, financial records, tax returns, and other sensitive client information. A product with strong features and a familiar interface is not necessarily the right choice if the firm cannot determine how client information is protected or how operations will continue when something goes wrong.

A practical evaluation follows six steps: Protect Data → Control Access → Evaluate the Vendor → Review Hosting → Verify Recovery → Confirm Support

Step 1: How Does the Software Protect Client Tax Information?

Start by understanding where client information is stored, how it moves between systems, and who can access it. Tax preparation software may store information locally, on an office server, in a vendor-hosted cloud environment, or across multiple locations. The firm should ask:

  • Is sensitive client information encrypted while being transmitted?
  • Is stored client information encrypted?
  • Where is the data hosted, and who operates that environment?
  • Can employees securely exchange information with clients?
  • Are access and activity logs available?
  • What happens to the firm's information if it stops using the software?

Encryption is important, but it is not a complete security strategy. Accounting firms also need appropriate access controls, endpoint protection, secure file-sharing practices, and procedures for handling sensitive information. The firm should understand which security responsibilities belong to the software vendor and which remain with the accounting firm and its IT provider.

The key question is not simply whether the software is secure. It is whether the entire process of storing, accessing, and exchanging client tax information is adequately protected.

Step 2: Can the Firm Control Who Has Access?

Tax preparation software should allow the firm to control access based on employee responsibilities. For example, a seasonal preparer may not need the same administrative privileges as a managing partner or designated system administrator. The firm should evaluate:

  • Whether multifactor authentication (MFA) is supported and can be required
  • Whether individual employee accounts are used instead of shared logins
  • Whether permissions can be assigned by role
  • Whether administrator access can be restricted
  • Whether accounts can be disabled promptly when employees leave
  • Whether the software records important user activity

If the software supports single sign-on or integration with an identity platform, the firm should understand how those features are configured and managed. A secure application can still expose sensitive information when user permissions are poorly managed. Strong password management and identity security practices help accounting firms reduce that risk by controlling how employees authenticate and which systems they can access. The firm should also review access before tax season, after staffing changes, and whenever employees change responsibilities.

Step 3: What Evidence Can the Software Vendor Provide About Security?

A vendor's claim that its software is secure should be the beginning of the conversation, not the end. Accounting firms should request information about the vendor's security practices and how the vendor handles potential incidents. Useful questions include:

  • Does the vendor provide current independent security assessments or audit reports, such as SOC 2, when applicable?
  • How frequently does the vendor release security updates?
  • How are vulnerabilities identified and addressed?
  • How does the vendor notify customers about security incidents?
  • Can the vendor explain its data retention and deletion practices?
  • Which subcontractors or hosting providers may handle customer information?
  • What security responsibilities remain with the accounting firm?

A SOC 2 report or another independent assessment can provide useful evidence, but it is not a guarantee that a product is secure. The firm should understand the scope of the assessment, whether it covers the services being purchased, and whether significant exceptions were identified.

Accounting firms should also consider how the vendor's practices fit into their own written information security plans and applicable data protection obligations. If a vendor cannot provide reasonable answers about how it protects sensitive client information, that uncertainty should be considered part of the purchasing decision. A broader software evaluation should also consider application compatibility, licensing, support requirements, and the total operational impact before the firm commits to a new product.

Step 4: Where Will the Software Run, and Who Is Responsible for the Infrastructure?

Tax preparation software may be installed on individual computers, hosted on an office server, delivered through a cloud platform, or operated in a managed hosting environment. Each model creates different operational and security responsibilities. For example:

Locally installed software may require the accounting firm and its IT provider to manage endpoint security, updates, local data storage, and backups.

Office-server applications may require ongoing server maintenance, access controls, operating system updates, backup management, and recovery planning.

Vendor-hosted applications shift some infrastructure responsibilities to the vendor, but the accounting firm may still be responsible for employee accounts, endpoint security, access permissions, and secure data handling.

Managed hosting environments may provide additional operational management, depending on the services included and the responsibilities established in the agreement.

The firm should ask:

  • Who installs and maintains application updates?
  • Who manages the operating system and supporting infrastructure?
  • Who monitors the environment for operational or security issues?
  • How is remote access secured?
  • Who is responsible when the application becomes unavailable?
  • How are responsibilities divided between the software vendor, hosting provider, and IT provider?

Moving an application to the cloud does not automatically eliminate security risks or operational responsibilities. Accounting firms considering a cloud migration should evaluate security, application compatibility, performance, ongoing costs, and vendor responsibilities before deciding whether the cloud is the right fit. The objective is to select an environment that supports the firm's security, availability, and business requirements.

Step 5: Can the Firm Recover Its Data and Resume Work After an Incident?

Backup and recovery capabilities deserve particular attention because tax preparation software may contain substantial amounts of work that would be difficult to recreate. The firm should determine:

  • What application data is backed up
  • Whether backups include configuration information and supporting files
  • How frequently backups occur
  • Whether backup copies are protected against unauthorized modification or deletion
  • Who is responsible for monitoring backup failures
  • Whether restoration procedures have been tested
  • How long recovery might take after a significant failure

Two useful recovery measures are:

Recovery Point Objective (RPO): The maximum amount of data loss the firm is prepared to tolerate, measured in time.

Recovery Time Objective (RTO): The target amount of time within which the firm aims to restore an affected system or service.

For example, a firm might establish a target RPO of four hours and a target RTO of eight hours for a particular application. These are illustrative planning targets, not universal standards or vendor guarantees. The appropriate targets depend on the firm's operations, available recovery capabilities, costs, and tolerance for disruption. A backup is only useful if the firm can restore the information it needs. Regular backup and disaster recovery testing helps verify that recovery procedures work and that the firm's expectations for restoring critical tax preparation systems are realistic. The firm should understand how its tax preparation environment will be recovered before an outage occurs, not during one.

Step 6: Who Provides Support When the Application Fails?

Even a well-secured application can create operational problems if responsibility for troubleshooting is unclear. Tax preparation software may depend on workstations, servers, network connectivity, authentication services, databases, and vendor-operated infrastructure. When something fails, the accounting firm needs to know who is responsible for investigating the problem. Questions to ask include:

  • Does the software vendor provide direct technical support?
  • What support hours are available during tax season?
  • Does the IT provider support the application's operating environment?
  • Who coordinates troubleshooting when multiple vendors are involved?
  • Is there an escalation process for business-critical outages?
  • How are urgent security issues communicated?
  • Who verifies that the application is working after updates or maintenance?

The firm should also confirm that its IT provider understands the application's system requirements and any vendor restrictions on hosting or support. The best support arrangement is one in which responsibilities are documented, and vendors can coordinate effectively when problems occur. When a server or critical application fails, the accounting firm needs a clear process for identifying the problem, coordinating the appropriate vendors, and restoring service. That process should be established before tax season, when an extended interruption may affect multiple employees and client deadlines.

Example: A 20-Person Accounting Firm Evaluates a Cloud Tax Platform

Consider a hypothetical 20-person accounting firm evaluating a move from locally hosted tax preparation software to a vendor-hosted platform. The proposed application offers remote access and eliminates the need for the firm to operate its existing application server. At first, the move appears to simplify IT management. However, the firm's evaluation identifies several questions:

  • Can the firm require MFA for every employee?
  • Will existing user permissions transfer correctly?
  • Does the vendor provide sufficient security documentation?
  • How frequently is application data backed up?
  • Can the firm obtain usable copies of its data if it changes vendors?
  • Who handles an outage that prevents employees from accessing returns?
  • Will the firm's existing client document workflows continue to work securely?

The firm asks the software vendor and its IT provider to document their respective responsibilities before proceeding. It also tests the application with a small group of employees before moving the entire practice. The result is a more informed decision based on security, operational readiness, and support requirements rather than convenience alone. This is a hypothetical example, not a claim about a specific client engagement.

A Practical Tax Software Security Evaluation Checklist

Before purchasing, renewing, or migrating tax preparation software, an accounting firm should be able to answer these six questions:

  1. Data protection: Do we know how sensitive client information is stored, transmitted, and protected?
  2. User access: Can we enforce MFA, individual accounts, and appropriate permissions?
  3. Vendor security: Has the vendor provided credible information about its security practices?
  4. Hosting: Do we understand where the application runs and who manages the infrastructure?
  5. Recovery: Are backup responsibilities, recovery procedures, and recovery targets documented?
  6. Support: Do we know who is responsible when the application experiences a security issue or operational failure?

If the firm cannot answer one or more of these questions, it should resolve those gaps before making a significant software or hosting decision.

How Everleap IT Helps Accounting Firms Evaluate Business-Critical Software

Selecting tax preparation software involves more than comparing features and subscription prices. Accounting firms need to understand how the application fits into their overall technology environment, how client information is protected, and how the business will continue operating when technical problems occur.

Everleap IT helps accounting firms evaluate business-critical applications from an operational perspective, including security controls, infrastructure, access management, vendor coordination, and business continuity.

That approach is informed by more than 20 years of production hosting experience. Operating production environments requires attention to availability, system maintenance, security controls, monitoring, recovery, and clearly defined responsibilities.

Everleap IT brings that experience to its Production Ready IT approach, helping accounting firms make technology decisions that support reliable daily operations.

Everleap IT provides managed IT services for accounting firms throughout Southern California, including California's Inland Empire communities of Rancho Cucamonga, Upland, Ontario, Chino, Claremont, and nearby areas.

If your accounting firm is evaluating new tax preparation software, considering a hosting change, or reviewing the security of an existing application, contact Everleap IT to discuss your technology environment.

Not ready for a conversation? Download our IT Buyer's Guide to learn what to look for when evaluating an IT provider.