Asking what the best accounting software for CPA firms is means asking about five different systems at once. The ledger your clients keep, the tax suite you file from, the workflow tracker that says whose desk a return sits on, the document store and the portal your clients upload to each answer a different question, and three of them come with rules that narrow the field before any feature does. Once your firm reasonably expects to file 11 or more individual, trust or estate income tax returns in a calendar year, the IRS e-file mandate decides part of the tax layer for you, and if your firm does attest work, the AICPA's hosting services interpretation decides part of the document and portal layers. Everything else is fit, and fit runs off your client mix rather than off a feature grid.
Best Accounting Software for CPA Firms Means Five Different Systems
Name the layer before you name a product, because products in different layers are not alternatives to each other.
A general ledger holds one set of books: the chart of accounts, the journal entries and the trial balance a financial statement comes off. Tax compliance software is where returns are prepared, reviewed and transmitted. Practice management tracks the job rather than the numbers, telling you whose desk a return sits on, what stage it has reached and what is due next week, usually with time and billing attached.
Document management is where workpapers, source documents and finished returns live, with version history and a retention rule. A client portal is the exchange layer, the way an engagement letter goes out and a client's paperwork comes back.
Those five fail in different ways, and the failure tells you which one you are shopping for.
| Layer | The question it answers | Where the buy goes wrong |
|---|---|---|
| General ledger | Whose books, kept in whose subscription | Buying a firm ledger to fix a client-books problem |
| Tax compliance | What your firm can prepare and transmit | Choosing on the interface before checking forms and states |
| Practice management | Whose desk the work is sitting on | Buying workflow before the workflow is written down |
| Document management | Where the file lives, and for how long | Treating retention as a storage setting |
| Client portal | How files and signatures move | Letting the exchange point become the archive |
Write down the symptom from last season in one sentence before any demo. A firm that could not tell a partner where a return had stalled has a practice management problem, and no tax suite on the market fixes it.
Your Client Mix Decides the Ledger Question
The ledger question splits in two, and only one half is yours to decide.
Your clients' books sit in whatever their bookkeeper already chose, so a compliance-heavy tax practice visits those systems rather than buying one. Your firm's own books are a separate and much smaller purchase. Mixing the two up is what sends a partner shopping for a general ledger when the thing that actually broke was document management.
The picture changes if you run write-up or client accounting work, where the books are the product rather than an input. Standardizing a client base onto one ledger is a genuine strategy there, and its price is the clients who will not move and the ones whose industry software will not feed the standard you picked. What that practice takes on beyond the software is worked through in what a client accounting services practice actually runs on.
The Tax Layer Has a Legal Floor, Not Just a Feature List
One rule decides whether electronic filing is optional for your firm, and it is counted at firm level rather than per preparer.
A specified tax return preparer is a preparer of covered returns who reasonably expects to file 11 or more covered returns in a calendar year, and a covered return is a return of income tax imposed by subtitle A of the Internal Revenue Code on individuals, trusts, or estates. The count belongs to the firm. The rules require firms to compute the number of covered returns, in the aggregate, they reasonably expect to file as a firm, and if that number is 11 or more in a calendar year then all members of the firm must e-file the returns they prepare and file. That stays true even where a member individually files fewer than the threshold (IRS, e-file requirements for specified tax return preparers).
The credential you e-file under is a firm-level asset too. Electronic Filing Identification Numbers, or EFINs, are currently issued on a firm basis, and all preparers in the firm are covered by one EFIN (IRS, e-file requirements for specified tax return preparers).
Read those together and the tax layer's first question is not how the return screen looks. It is which forms and which state returns the product transmits for the season you are actually buying, and what it does with a return it cannot transmit. Ask about prior-year files in the same breath, because a suite that cannot open last season's work turns a migration into re-keying. Coverage, conversion loss and the licensing shapes that decide what a tax suite costs at your return count are worked through in how to pick a tax preparation suite for your client mix.
What a Migration Actually Costs
The switching cost that matters is not the setup fee. It is whether you can still produce your own records once you stop paying.
Treasury puts that duty on the preparer rather than on the software. A signing tax return preparer, meaning the individual tax return preparer who has the primary responsibility for the overall substantive accuracy of the return or claim for refund (eCFR, section 301.7701-15), must retain a completed copy of the return or claim for refund, or retain a record by list, card file or otherwise carrying the name, taxpayer identification number and taxable year of the taxpayer and the type of return prepared, and must make that copy or record available for inspection on request by the Commissioner (eCFR, section 1.6107-1).
Where an organization employs a signing tax return preparer for compensation, or compensates one as a partner or member to prepare the return, the organization is treated as the sole signing tax return preparer (eCFR, section 1.6107-1). The retention duty therefore lands on the firm, separate from how long a client keeps their books.
The clock is longer than it first reads, because it does not run off the tax year. The material has to be kept available for inspection for the 3-year period following the close of the return period in which the return was presented to the taxpayer for signature, and where the return becomes due in a later return period, the clock runs from the close of that later one (eCFR, section 1.6107-1). The retention rule takes its definition of a return period from section 6060, and the regulation under that section defines it as the 12-month period beginning on July 1 of each year (eCFR, section 1.6060-1).
So the honest migration question is whether you can open what you filed after the subscription lapses, in a form that survives an inspection request, for as long as the rule runs. Ask what comes out before you ask what goes in: the export format, whether attachments and workpaper links travel with it, whether the archive downloads in bulk, and what read-only access costs after the contract ends. Handing back the records a client needs to meet their own federal tax obligations, when the client asks for them, is a separate duty that Treasury's rules of practice place on the practitioner, and it is covered in what to settle before switching providers.
The Document Layer Comes With an Independence Rule
If your firm performs attest work, where a client's file physically lives is an independence question rather than an IT preference. An attest client here means one your firm audits, reviews or performs another attestation engagement for, and a nonattest service is anything else you do for that same client. The question is what your own firm holds for that client, not what a vendor holds for you.
The AICPA Code treats hosting as a nonattest service. Under interpretation 1.295.143, hosting services involve a member accepting responsibility for acting as the sole host of a financial or non-financial information system of an attest client, for taking custody of or storing an attest client's data or records where those records are available to the client only from the member and are otherwise incomplete, or for providing electronic security or back-up services for an attest client's data or records (AICPA Code of Professional Conduct, interpretation 1.295.143).
The consequence is absolute rather than graded. When a member provides hosting services the member is maintaining the attest client's internal control over its data or records, so the management participation threat is not at an acceptable level, cannot be reduced to one by safeguards, and independence is impaired (AICPA Code of Professional Conduct, interpretation 1.295.143).
What stays allowed is the useful part, because it reads as a specification for how you configure the software. Using general ledger software to deliver bookkeeping is not hosting where the member and the attest client maintain separate instances on their respective servers and the member sends updated financial information to the client, or where the client contracts with a third-party provider for its cloud software and grants the member access to perform the work. Keeping a copy of a work product you prepared, such as a tax return, is not hosting. Holding a client's original records to perform a nonattest service is not hosting either, provided the records go back at the end of the engagement, or at least annually in a multi-year engagement (AICPA Code of Professional Conduct, interpretation 1.295.143).
A portal is treated as a channel and not a store. Exchanging data, records and work product with an attest client through a portal is not hosting, and to avoid providing hosting services members should terminate the attest client's access to the data or records in the portal within a reasonable period of time after the engagement concludes (AICPA Code of Professional Conduct, interpretation 1.295.143).
That gives the document and portal decision a shape you can shortlist against. Your system can be a copy and a channel. It cannot be the client's only copy, the place the client's own system runs, or the service that backs the client's records up. Per-client purge rules, dated access expiry and a clean export are requirements for an attest practice, not niceties, and a product that cannot expire access without deleting your own working papers has failed the test.
Five Questions That Separate Two Products on a Demo
Ask these live, while somebody from the vendor is still on the call.
- Export a real file now, not a sample. Watch what comes out, in what format, and whether attachments, workpaper links and prior-year comparatives survive the trip. A description of an export is not an export.
- What happens the day your firm stops paying? Ask how long read-only access lasts, what it costs, whether the archive downloads in bulk and who holds the copy after that. This is the answer that decides the real switching cost.
- Which forms and which state returns does it transmit this season? For the tax layer, ask for the current list rather than a marketing page, and ask what the product does with a return it cannot transmit.
- Which layer does this replace, and which does it only talk to? Make the vendor name the single layer the product is built for, then treat everything else on the feature list as an integration and price it that way.
- Who administers access, and can it produce a list of who opened what? That log belongs in your security program anyway, because the FTC Safeguards Rule makes monitoring and logging the activity of authorized users an element of the program in its own right, separate from the duty to evaluate the outside applications you use to handle customer information, and both are set out element by element in what the security rules require of a CPA firm.
Write the answers down during the call. A vendor who cannot answer the first two in a demo will not answer them faster once you have signed.
When the Software Is Not the Problem
Sometimes the tool is fine and the constraint is people. The tell is a firm that changed products and then watched the same weeks break the same way.
Software moves work, and it does not review work. If returns are stacked behind one reviewer in March, a faster preparation screen adds to the stack instead of clearing it, which is why a capacity plan starts at the review queue rather than at the software line in the budget (building a capacity plan that holds).
Two other cases are worth naming plainly. If the process lives only in one partner's head, a workflow product will ask you to write it down first, and that writing is the actual project. If the constraint is client mix or pricing, better software only makes unprofitable work faster to produce.
Questions CPA Firms Ask About Software
What Software Do Most CPAs Use?
The question is under-specified, which is why the answers conflict. A firm runs something in every one of the five layers, and the product that dominates one layer says nothing about another. Answer it for your own firm by naming the layer and the constraint first, then shortlisting inside that layer only.
Do CPA Firms Use QuickBooks?
Yes, whenever a client keeps its books there. The answer splits by whose books you mean. A firm works inside whatever ledger each client already keeps, so which ledgers it touches is decided by the client list rather than by the firm. The firm's own stack is a separate purchase, covering the tax suite, the workflow tracker, the document store and the portal.
Why Does a Client Ledger Frustrate a Firm?
Check whether the complaint is about the ledger or about work that belongs to another layer. A ledger keeps one set of books. When it is asked to track whose desk a return sits on, hold the workpapers, or move signed documents, it is being judged on three jobs it was never the layer for. Name the job that is failing, then look for it in the layer that owns it.
What Software Do Big 4 Accounting Firms Use?
What a global network builds and licenses for itself solves a different problem than a small or mid-size practice has, so it is a poor guide to a shortlist. Sorting by layer is the more useful comparison, because it starts from the question you are trying to answer rather than from the size of the buyer.
Name the Layer, Then Buy One Thing
Pick the layer that actually failed last season and write the symptom down in one sentence. Take that sentence to two products inside that layer, ask the export question and the stop-paying question before anything else, and hold the rest of the demo to the layer you came for. The other four can wait for next year, because buying all five at the same time means learning all five at the same time, in the season you had least room for it.
If what failed was review capacity rather than any product, that is a staffing problem wearing a software costume. Accountably places trained offshore accountants and tax preparers inside US CPA and EA firms, ramped on the firm's own software and SOPs in about 3 to 4 weeks, and the signature, the opinion and the final judgment stay with your firm. Since 2022 we have worked with 20+ US firms across 30+ placements. Don't trust us. Test us. The Free 40-Hour Proof Pilot runs a fixed block of your own representative work through full multi-layer review, so your reviewer grades real output before a client file depends on it.