From pilot to production: how to implement AI tax preparation

Note

This is the second post in a two-part series that draws on real experience from deploying Accrual at existing clients. The first post covered how to structure and measure a pilot.

A successful pilot answers one question: can this technology produce accurate, review-ready tax returns with real client data? But strong pilot results are only the beginning.

The real challenge is operational: moving from a small number of returns in a test environment to hundreds of practitioners using the system across multiple offices.

This is where many enterprise AI initiatives stall, not because the technology fails, but because firms underestimate the work required to operationalize it.

This guide explains how leading accounting firms turn successful pilots into full deployments: how to scope the rollout, redesign workflows, train teams, and manage the organizational change required to deploy AI-powered tax preparation at scale.

Scoping the rollout: where to start

Start with a subset, not the entire firm

Top firms are national — start with a subset of your practice rather than a firm-wide launch. This is the pattern that works: constrain scope to manage risk, build organizational confidence through demonstrated results, then expand. One large firm selected five offices with high concentrations of 1040 work as controlled deployment environments.

Define complexity targets

Start with moderate complexity returns. This gives practitioners time to build confidence with the workflow before introducing highly complex scenarios.

One firm structured its rollout as:

• 85% simple and moderate returns (i.e. standard returns)
• 15% highly complex returns

Complexity expanded in later seasons as teams gained experience.

Decide what to exclude

Equally important as defining what's in scope is defining what's out. Accrual works with each firm to identify clients and sites that aren't a good fit for the initial deployment. This may include recently acquired offices or teams with very low technology adoption who would benefit from seeing peer success first.

This isn't a permanent exclusion — it's sequencing. The scope expands in subsequent cycles as capabilities grow and organizational readiness improves.

Mandate adoption where appropriate

One of the clearest findings from Accrual deployments: optional adoption produces inconsistent results. Firms that treat the rollout as a suggestion see fragmented usage and unreliable data. Firms that make it an operational decision see faster learning curves and cleaner feedback.

One Accrual customer mandated client selection centrally. This approach ensured meaningful volume without relying on opt-in enthusiasm and produced the data needed to evaluate performance at scale.

Data preparation: the work before the work

Client data cleanup

Every firm that deployed Accrual at scale reported the same lesson: data cleanup takes longer than expected. Start 4–6 weeks before the season. Key tasks include:

• Email validation: eliminate duplicates and outdated contact data
• CRM reconciliation: ensure CRM and tax system data match
• Life event updates: address changes in filing status, dependents, or household structure

Clean data dramatically improves client onboarding and portal adoption.

Permission and compliance configuration

For firms with offshore teams, Form 7216 consent requirements must be configured before staff can access client data. Accrual's group-based permissions system supports this directly: create Member Groups for each office or team (including offshore), create Client Groups for consented clients, and grant access at the group level.

A common configuration: a "7216 Consented" Client Group grants access to the offshore Member Group, while sensitive or high-profile clients are restricted to senior staff through a separate "VIP Clients" group.

Redesigning the workflow

The fundamental shift

The key operational implications:

• The preparer's role shifts from data entry to review and exception resolution. Preparers spend less time on manual entry, OCR verification, and document sorting. They spend more time investigating technical exceptions, providing instructions to the agent (via the Issues workflow), and communicating with clients about missing or ambiguous items.
• The admin role expands. Tax administrators handle client setup, engagement creation, role assignments, portal invitation management, and document upload for paper materials. Admins can also trigger return generation once sufficient documents are received, a function that previously required preparer involvement.
• Review starts at a higher level. Returns generated by Accrual consistently arrive at what firms describe as manager-review quality. The existing review hierarchy doesn't disappear, it gets elevated. Partners and managers review work that has already been through an AI-generated first pass with citations, preparer notes, and flagged issues, rather than starting from a junior preparer's initial draft.

Inverting the 75% rule

Traditional workflows follow an informal “75% rule”: wait until roughly three-quarters of a client’s documents have arrived before starting preparation, then send the package offshore or assign it to a preparer. In practice, that means complex returns sit idle for weeks while the last few K-1s trickle in.

Accrual inverts that rule. Firms generate a first draft as early as February, once W-2s and 1099s are available. That early pass lets the agent flag missing information and surface follow-up items months before the filing deadline. As K-1s arrive, each new document triggers a checkpoint showing only the incremental changes to the return. The same applies after an extension is filed: when the final documents land in the fall, the agent picks up where it left off rather than starting over.

Practitioners can review a return over the course of the season, looking only at what changed, rather than doing a single marathon review in April with everything stacked up.

Maintaining the tax engine

Accrual handles preparation and review; the tax engine handles calculation and filing. The two systems stay synchronized through bidirectional integration: one-click export from Accrual to the tax engine, and re-import capability when changes are made directly in the tax engine. Clear SOPs for this handoff are important — firms developed specific documentation for when and how data moves between systems, who is responsible for each step, and how to resolve conflicts if the systems diverge.

Training at scale

Structured training by role

The firms that achieved the highest adoption rates structured their training by role rather than delivering a single overview session. Different staff levels need different depth and different emphasis.

Case 1: A phased approach:

• Tax admin training: Focused on client setup, document management, engagement creation, and portal administration.
• Office-specific case studies: Hands-on sessions where practitioners worked through real client scenarios. These sessions proved critical for overcoming partner hesitancy — in one office, partners who were initially skeptical became advocates after experiencing the platform firsthand.
• Offshore team training: Separate sessions for international teams, with specialized scheduling and workflow guidance tailored to their role in the review process.
• All training sessions qualified for CPE credits with technical CPA review.

Case 2: A comprehensive program:

• Overview session: 50-minute CPE-qualified introduction covering platform positioning, change management context, and a client portal demonstration.
• Hands-on case study: Each attendee was assigned a specific synthetic test client and worked through the complete workflow — document upload, return generation, issue review, and export — with step-by-step guidance.
• Ongoing support structure: Twice-weekly office hours, a Microsoft Teams channel with 4–5 designated champions filtering questions, and highly responsive support in-app support.

The principles that drive adoption

Schedule training before busy season begins. Allow enough time between sessions for practitioners to absorb the material and form questions.

Interactive live sessions consistently outperform recordings. Q&A, screen sharing, and real-time troubleshooting build confidence in ways that pre-recorded walkthroughs cannot.

Designate a change manager. Assign a dedicated resource (0.5–1 FTE) for the first year, responsible for adoption oversight, internal messaging, and coordination between the firm and Accrual. This role proved essential for maintaining momentum through the inevitable friction of any new workflow.

Local champions are force multipliers. Identify 4–5 power users per office who can provide peer support, filter questions before they reach the vendor, and demonstrate the workflow to colleagues using real examples from their own clients.

Expanding from tax prep to end-to-end

A consistent pattern across deployments: firms that begin with Accrual for tax preparation quickly discover that extending to the client portal and document collection workflow produces compounding efficiencies. Rather than using separate tools for client communication, document collection, data extraction, and return preparation — each with its own integration challenges and product roadmap — the entire workflow lives in one system.

The practical benefit is that when Accrual ships a feature, it works across the entire platform. When a client uploads a document through the portal, it flows directly into the binder, gets classified, and is available to the agent for return preparation without anyone manually moving data between systems.

Managing the organizational change

Address billing and time tracking directly

AI-assisted preparation changes how practitioners spend their time. Firms should track this explicitly by creating new charge codes for:

• Agent-assisted preparation
• AI-assisted review

This helps firms measure productivity improvements and address staff concerns about billable hours.

Set realistic expectations

Preparers should expect to spend less time on data entry and more time on technical review. They should expect the agent to flag issues they'd otherwise catch manually, and occasionally miss things that require professional context. The system improves every season as it processes more of the firm's work and as Accrual incorporates feedback into the platform.

Overcome resistance through experience

The most consistent finding across every deployment: skepticism resolves through hands-on use, not through presentations or data. Partners who reviewed accuracy numbers from a distance remained cautious. Partners who sat down and worked through a return in the system became advocates.

This is why hands-on training, local champions, and mandated adoption for participating teams matter so much. The conversion from skeptic to advocate happens at the keyboard, not in the conference room.

The feedback loop

Rapid iteration as a feature

During tax season, firms maintain direct communication channels with the Accrual team. This creates a fast feedback loop:

• Practitioners report edge cases
• Workflows improve during the same season
• Product improvements ship quickly

Many firms report dozens of workflow improvements during the first deployment cycle.

Infrastructure for ongoing support

The support structure that works during tax season:

• Multiple channels: Teams/Slack for quick issues, email for case-specific questions with expected timelines, scheduled office hours for recurring topics.
• Champions as first-line triage: 4–5 designated power users per office filter and consolidate questions before they reach Accrual, preventing vendor overwhelm while ensuring nothing falls through.
• Weekly FAQ updates: A firm-specific FAQ document maintained and refreshed weekly throughout the season.
• Defined escalation paths: Clear routing for technical issues (Accrual engineering), tax questions (firm's internal experts), and client-facing concerns (firm's client service team).

Building for year two and beyond

The firms that approach Accrual as a workflow transformation rather than a one-time technology adoption see the strongest returns over time. Year one establishes the foundation: the integration is configured, the team has built working familiarity, the client portal is active, and baseline accuracy and time savings data has been collected.

Year two is where the compounding begins. Complexity scope expands to include return types and scenarios that were excluded in year one. The system itself improves as Accrual incorporates every season's feedback into the agent's capabilities, and the underlying AI models continue to advance. Practitioners who were cautious become efficient. The champion network deepens. And the operational data from year one provides the evidence base for expanding to additional offices and client segments.

Example implementation checklist

• 4–6 weeks before tax season

  • Complete client data cleanup (life events, emails, duplicate resolution)
  • Configure permissions and 7216 consent groups for offshore teams
  • Finalize rollout scope (offices, client segments, complexity tiers, exclusions)
  • Co-develop SOPs changes with your Accrual implementation team
  • Create new charge codes for automation-related work

• January (before busy season)

  • Conduct role-based training sessions (admin, preparer, reviewer, partner)
  • Establish communication channels and designate office champions
  • Send client portal invitations

• February through April

  • Maintain twice-weekly office hours and weekly FAQ updates
  • Monitor engagement metrics and escalate adoption issues through change manager
  • Collect and relay product feedback through direct Accrual channel
  • Track time allocation against new charge codes for year-over-year analysis
  • Begin return generation as clients complete their binders

• Post-season

  • Conduct executive review of accuracy, time savings, and practitioner experience
  • Identify scope expansion targets for year two
  • Document lessons learned and update SOPs

For firms ready to plan their deployment, contact us to discuss rollout scope and timeline.