Tax preparation tech stack and performance metrics for 2027

What to take away

This article covers tax-practice business operations, not individualized tax, legal, or representation advice. Requirements and deadlines depend on the tax year, the return, the jurisdiction, and the client's facts. Confirm current rules with the IRS, the state tax authority, or a licensed CPA or enrolled agent.

The six layers of a 2027 tax stack

Preparation software is where returns get built and computed. The 2027 field is crowded. The differences matter less than the fit. Consider these options:

The reviewed list of tax preparation software compares them on state coverage, pricing model, and support hours.

E-file transmission is a separate decision from preparation. Most desktop packages transmit through the IRS Modernized e-File system on your behalf. They charge per return or bundle it into the license. Confirm the transmission fee separately from the license fee before you sign. In most markets, per-return transmission fees run from $1 to $5. Some vendors bundle unlimited volume.

Client document collection is the layer practices most often leave to email. Purpose-built options include SafeSend, Liscio, and SmartVault. They give clients a portal, a checklist, and an audit trail. That trail shows what arrived and when. SafeSend often prices per return; Liscio and SmartVault commonly charge $20 to $60 per user per month.

Practice management covers engagement letters, deadlines, staff assignment, and time. Karbon, Canopy, TaxDome, and Jetpack Workflow all do this. They differ mainly in how much client-facing portal they include. Karbon and Canopy commonly run $50 to $100 per user per month; TaxDome and Jetpack Workflow often sit in the $40 to $70 range.

Bookkeeping and write-up software feeds the business returns and the practice's own books. QuickBooks Online plans commonly run $35 to $235 per month. Xero runs about $20 to $75 per month. Wave has a free starter tier and a paid tier near $16 per month.

Identity and access controls sit under all of it. The IRS and NIST both publish starting points for small firms.

Metrics that change a decision

A metric earns its place only if a bad number changes what you do next. Write the formula, the source, the exclusions, and the owner before you compare two periods. The 2027 targets below are planning ranges, not vendor claims.

Track these monthly through the season, not annually. A rework rate that climbs in the third week of February is a training problem you can still fix.

Where the compliance floor sits

PTIN renewal, Circular 230 duties, and e-file provider rules come from the IRS, not from your software. Anyone who prepares or substantially assists with a federal return for pay generally needs a current PTIN.

The IRS PTIN requirements page states the current rule and the exceptions. Credentials and representation rights are separate questions, and a PTIN does not grant either.

Recordkeeping is the other floor. The IRS guidance on records a business should keep covers what supports income, expenses, payroll, and assets. Your software's retention settings should match that guidance, not replace it.

State e-file mandates vary. California and Illinois require electronic filing above certain preparer thresholds. New York City clients can face city and state deadlines that differ from the federal date. Check the state authority each season; do not carry last year's assumption forward.

Security controls the stack has to support

Client data is the practice's largest liability. The NIST small business quick-start guides give a plain starting point for risk management. CISA's small business guidance covers the common failures. Neither is tax-specific, which is the point: the controls are general and the exposure is not.

Four controls belong in every stack decision. Individual accounts, never a shared login. Least-necessary permissions inside the preparation software, so a seasonal preparer cannot see the whole client list. Multifactor authentication wherever the vendor offers it. Prompt removal of access when a seasonal hire leaves in April.

Name a data-security administrator. That person reviews stale accounts quarterly and keeps the record showing the review happened. A 2027 target is 100 percent of seasonal accounts removed within one business day. If the practice cannot produce that record, the control does not exist.

What to test before you sign

Run one full return through the candidate software in a sandbox. The steps are intake, preparation, review, e-file, and acceptance. Then check the client copy. Test the failure paths next.

The export test matters most. Ask for every client record, every return, and every attachment in a format you can read without the vendor's software. If the answer is a PDF bundle, the answer is no.

Implementation, training, and the first season

Budget implementation separately from subscription. Data migration, chart-of-accounts mapping, template setup, and staff training usually cost more hours than the license costs dollars. Put those hours in the project plan with a named owner.

Train by role, not by feature. A preparer needs intake, computation, and diagnostics. A reviewer needs the review trail and the override log. Client-service staff need the portal and the status view. The owner needs the dashboard and the billing export.

Start with a limited pilot: one service line or one preparer, one month, one written expected result. If the pilot fails, revise or stop. Expanding a bad configuration across the whole practice in January is the most expensive mistake in this article.

Common questions

Which software should a small practice start with?

Drake Tax and TaxSlayer Pro are common starting points for price-sensitive practices with straightforward individual returns. ProSeries and Lacerte suit practices that want Intuit's state coverage and support. The right answer depends on your return mix, your state list, and how many preparers need simultaneous access.

How many metrics should a practice track?

Six is enough for most practices. The first three are cycle time, rework rate, and extension rate. The next three are document collection time, rejection rate, and realization rate. Add a metric only when you can name the decision it would change. A dashboard nobody acts on is a cost, not a control.

What does the 2027 change actually mean for software?

Software vendors update forms and schemas each year, and the IRS publishes e-file schema changes on its own schedule. The practice's job is to confirm the vendor's update date, test one return after the update, and hold a fallback plan for the week the update lands. Do not assume last year's configuration survives.

Who owns compliance in a small firm?

The owner or a named principal owns it, even when a data-security administrator handles access and a reviewer handles accuracy. Circular 230 obligations and PTIN status belong to individuals, so the practice needs a list of who holds what and when each renewal falls due.

Questions about a specific situation go to the IRS Office of Professional Responsibility or a licensed attorney.