How to choose practice management software as your CPA firm grows
Updated 13th October 2026 | 13 min read Published 13th October 2026
TL;DR: As your CPA firm grows, choose practice management software based on the complexity you need to manage, not just headcount. Test whether a system can give partners a reliable, shared picture across offices, route work and approvals consistently, handle WIP and billing at scale, connect to the systems you already run, and migrate your data without losing operational context. This guide shows how to turn each of those into something you can test in a buying process rather than a claim you take on trust.
There's no set moment when practice management software stops fitting. A second office opens, a firm is acquired, a new service line takes off, and the setup that ran a single-office practice keeps going, held together by a little more manual effort each quarter. Often the mismatch only becomes visible when a partner needs a straight answer about a client and it takes a day and three spreadsheets to produce it.
This guide is for managing partners, COOs, firm administrators, and operations leads deciding whether to reconfigure, integrate, or replace what they have. It covers how to tell when your requirements have genuinely changed, what to ask vendors to demonstrate rather than assert, and how to plan a migration that keeps your operational context intact.
How do you know your practice management setup has stopped fitting?
Firms rarely outgrow a system all at once. Instead, a set of workarounds starts acting as the operating model, and the cost only shows up at month-end or when a new office comes online. It doesn’t mean that a particular tool is deficient, but just that your requirements have moved.
A few observable triggers are worth watching for:
- Partners can't see the same client, job, WIP, and receivables picture across offices
- Approval paths differ by service line with no consistent rule
- Month-end depends on spreadsheets stitched together by hand
- Billing exceptions are hard to trace back to a decision or an owner
- Standing up a new or acquired office means recreating setup from scratch
Treat these signals as questions to investigate, not universal defects. If several feel familiar, use the table to work out whether the problem is the tool, the configuration, or the process, and to decide what to ask a vendor to show you.
| Symptom | Question to ask | Evidence to request in a demo |
|---|---|---|
| Partners see different numbers for the same client across offices | Is there one source of truth, or reconciled copies? | Live firm-wide and by-office views of the same client, drawn from one dataset |
| Approval routes vary by service line with no clear rule | Can routing be standardized with controlled local exceptions? | An approval configured two ways, with the exception logged and visible |
| Month-end depends on spreadsheets stitched together by hand | Which numbers can't the system produce directly? | A consolidated close report generated in-session, with no export-and-rework |
| Billing exceptions are hard to trace to a decision or an owner | Can you follow an exception to its owner and reason? | An exception traced from invoice back to the originating decision |
| A new or acquired office means duplicate setup | How is a new office provisioned? | A new office stood up in the demo, inheriting existing templates and roles |
What should a growing CPA firm test before building a shortlist?
Demos tend to reward whoever tells the best story. To compare systems fairly, give every vendor the same tasks and watch them work. We've found these six criteria help narrow down what you actually need.
1. Implementation and migration. Request a sample migration plan covering client and job records, open WIP and A/R, history, and permissions, plus test conversions, training, and go-live support. How a vendor plans the move tells you as much as the product does.
2. Cross-office visibility. Ask to see client, job, staff, WIP, and A/R views by office and firm-wide, all from a single dataset. Then test the permission boundaries: have a role that should only see Office A confirm it can't reach Office B's records.
3. Workflow and capacity. Have the vendor demonstrate job assignment, recurring jobs, scheduling, and approval routing across two offices. Then run an exception, such as a reassignment or an out-of-sequence approval, and show how it’s handled and recorded.
4. Time, WIP, billing, and realization. Trace a single engagement end to end: time entry, review, invoice, write-off, collection, and the profitability or realization report that results. Watch for any step that requires leaving the system.
5. Reporting and controls. Ask whether a partner can drill from an aggregate KPI straight into the underlying record. Then test the audit trail and access controls: who changed what, when, and who is allowed to see it.
6. Integration and deployment fit. Map every system that must exchange data: accounting, tax, document management, CRM, payments, and BI. For each connection, verify direction, frequency, ownership, and whether custom work is required. A connection that only runs one way, or needs a nightly manual file, is not a live integration.
What changes for a Top 250 firm that is still growing?
Picture a firm adding a second or third office and a couple of new service lines over eighteen months. Nothing is broken, but partners increasingly ask for numbers that take a day to assemble.
For this firm, the selection team should weight a few tests heavily:
- Consolidated reporting that reflects all offices without manual merging
- Standardized workflows that still allow controlled local exceptions
- Capacity planning that spans offices rather than treating each as an island
- Clear ownership when a client is served from more than one location
- The practical effort of onboarding an acquired team, including their in-flight work and open balances
What changes for a Top 100 firm with complex multi-office workflows?
Now the firm shares clients across offices, runs multi-step billing approvals, needs job-level WIP visibility, enforces role-based access, and reports by both office and service line. Edge cases are the norm, not the exception.
Give each vendor a demo script and ask them to complete it live, using anonymized or synthetic data modeled on your production setup. Don’t hand over real client records. Here’s a script to start from:
A partner in Office A needs to see the current status, WIP balance, assigned approver, and any billing exception for a job staffed across Offices A and B. Then show the full audit trail for that exception.
Watch whether the answer comes from one place or whether the vendor has to jump between screens and reconcile. Ask them to repeat it with a restricted-access role so you can see the permission model working in the same flow. A system that handles this cleanly is demonstrating cross-office visibility, workflow, WIP, controls, and reporting all at once, which is the point.
How do you evaluate a move from your current system?
Focus on a repeatable transition method rather than a product name. A sound sequence might look like this:
- Inventory your workflows and integrations
- Separate must-have requirements from negotiable ones
- Export and clean your data
- Run a test conversion
- Validate opening balances and historical reports against the source
- Pilot with a single office or service line
- Train the people who will own each process
- Agree rollback and support plans before go-live
Then make a deliberate decision for each problem you’ve identified: keep, configure, integrate, or replace. Some pain points are solved by configuring what you already have, some by connecting a system you aren’t using fully, and some genuinely call for replacement. Framing the decision this way keeps the exercise honest. You’re evaluating fit against your requirements, not assuming your current system is inadequate.
How can IRIS help?
IRIS offers three practice management solutions for CPA firms:
- IRIS Firm Management offers configurable workflows, real-time reporting, and practice and document management for enterprise-level and growing firms.
- IRIS Star Practice Management provides multi-office visibility across clients, staff, jobs, WIP, and A/R, with configurable forms, fields, and reports.
- IRIS Practice Engine combines job and workflow tracking, scheduling, and staff and job budgets with client, job, and staff dashboards, and offers in-house or Azure hosting.
These are different products with different strengths, so evaluate each against your own criteria above rather than assuming they share every capability. As a starting point, we’ve mapped each solution to the six criteria so you can see at a glance which might fit best.
| Capability | IRIS Firm Management | IRIS Star Practice Management | IRIS Practice Engine |
|---|---|---|---|
| Cross-office visibility | Client and job information, dashboards, and reporting support a firm-wide view. | Multi-office visibility across clients, staff, jobs, WIP, and A/R. | Client, job, and staff dashboards and portfolios support operational visibility. |
| Workflow and capacity | Job templates, task assignment, availability views, scheduling conflicts, and budget-v-time views. | Scheduling can consider availability, skills, rank, location, and experience. Job budgets and approval processes can be configured. | Job and workflow tracking, scheduling, staff leave, and staff and job budgets. |
| Time, WIP, billing and realization | Time and expense capture, WIP tracking, billing workflows, client and job profitability, and configurable margin and realization calculations. | Time and expense capture, WIP allocation, billing goals, multi-step approvals, recurring invoices, and realization targets. | Posted and unposted WIP, transfers, provisions, job and group billing, recurring bills, and credit control. |
| Reporting and controls | Access controls, audit trails, period lockdown. Standard reports cover areas including WIP, A/R and staff analysis. Dashboards support drill-down. | Standard SSRS reports, optional dashboard views, configurable reports, and audit trails. Reporting by both current and historical client and job ownership. | Standard and scheduled reports, query builder, dashboards, granular security, and multi-factor authentication support. |
| Integration and deployment fit | Azure-hosted, time and billing APIs available. | Managed cloud option, links to iChannel, PowerBI and other APIs. | Browser access, in-house or Azure hosting, API connectivity. |
| Implementation and migration | Consulting-led implementation for complex firms. | Consulting, training, data conversion, and test conversions available. | Phased implementation, training, and conversion options available. |
| Best suited for | Enterprise-level and growing firms with complex, workflow-heavy requirements. | Multi-office firms that need shared visibility across clients, staff, jobs, WIP, and A/R. | Firms that want job, workflow, and budget tracking with flexible hosting options. |
Not sure which fits? Request a demo and ask us to run the multi-office scenario above on your own criteria.
Choosing practice management software FAQs
-
Test one hard, real workflow against anonymized production-like data: a job staffed across two offices, with status, WIP, approver, and any billing exception visible to the right partner, plus the full audit trail. Then confirm that role-based access holds inside that same flow. A system that passes this single test demonstrates cross-office visibility, workflow, WIP, controls, and reporting together.
-
Watch for observable triggers rather than headcount: inconsistent numbers across offices, spreadsheet-driven month-ends, untraceable billing exceptions, and duplicate setup for new offices. If several appear, test whether configuration fixes them before assuming you need a new system. For each signal, ask the vendor to show the fix live, using a consistent set of tasks for every vendor you evaluate.
-
Look for consolidated reporting without manual merging, standardized workflows with controlled local exceptions, capacity planning across offices, clear cross-office client ownership, and a credible onboarding path for acquired teams. Compare vendors using the same six tests: cross-office visibility, workflow and capacity, time/WIP/billing/realization, reporting and controls, integration fit, and implementation and migration.
-
Inventory your workflows and integrations, separate must-haves from negotiables, clean and export your data, and run a test conversion. Validate opening balances and historical reports against the source, pilot with one office, train process owners, and agree rollback plans before go-live. Then decide whether to keep, configure, integrate, or replace for each problem you found.
-
Validate client and job records, open WIP and A/R, historical transactions, and permission structures. Reconcile opening balances and a sample of historical reports against your source system during a test conversion, not on launch day. That is what protects operational context through the move.