Tax practice management software: what it is and what it solves

What the category covers

Tax practice management software runs the firm's work around its clients. It holds who the client is, what work the firm owes, who is doing it, what the work costs to deliver and where the client's documents sit. Four functions sit at the center: a client record (CRM), workflow and deadlines, time and billing, and document management with a client portal. Most vendors bundle all four, so test each function on its own.

Tax preparation software is a different category. It computes and prepares the return, including the individual return on Form 1040, the business returns, the state forms and the e-file transmission. Practice management software does not prepare the return. The boundary is easy to apply. If the product produces a return, it is tax preparation software. If it tells you that a client's W-9 is missing or that a return is waiting on the reviewer, it is practice management.

CRM: the client record everything else hangs on

The CRM function stores one record per client entity, not one per contact. For a tax firm that means the legal name exactly as it appears on the return, the EIN or SSN masked in every view, the entity type, the states where the client files, the responsible preparer and reviewer, and the signed Form 2848 when the firm represents the client. Form 2848 authorizes an individual to represent you before the IRS, so the record should name the representative and show where the signed form is filed.

The usual failure is duplication. The same S corporation exists three times, once for bookkeeping, once for payroll and once for the return, under three spellings. The fix is one entity ID with the EIN as the match key, and a rule that new engagements attach to an existing entity instead of creating a new one. Run the duplicate report before the season opens, not after the first wrong form goes out.

Workflow: stages, recurring work and deadlines

Workflow answers one question: what is this client waiting on today? A tax return workflow should have stages a client can see and the firm can count, such as organizer sent, documents received, preparation, review, client signature, Form 8879 signed, e-filed and delivered. Form 8879 is the declaration document and signature authorization for an e-filed individual income tax return. Each stage needs an owner and a date.

Recurring work is where workflow pays off, and the annual 1099 cycle is the clearest example. Form 1099-NEC must be furnished to payees and filed with the IRS by January 31. The workflow should create a vendor-list task in November, a W-9 chase in December and a filing task in January for each entity that paid a contractor. Set these tasks from the calendar rule, not from memory, and attach the due date to the entity, not to the engagement.

Decision rule: if an entity paid $2,000 or more to a non-employee for services in 2026, the workflow shows a Form 1099-NEC task for that entity. If every payee was under $2,000, the task closes with a note that lists the totals.

Billing: time, fees and work in progress

Billing turns delivered work into collected cash. Test three things. First, whether time entries attach to a task code and an engagement, so a bookkeeping hour and a return hour land in different lines. Second, whether fixed-fee engagements can be invoiced by milestone, such as the return, the state return and the extension, without a time sheet. Third, whether unbilled work in progress shows by client and by month.

Worked example. A firm bills a partnership return as a fixed fee and bills the same client's monthly bookkeeping by the hour. The software should put the fixed fee on the return milestone and the hours on the monthly close, under one client, with no duplicate line for the same work. If the bookkeeping hours land on the return invoice, the client sees a return fee that was never agreed, and the firm spends the next month explaining it.

Decision rule: when one client has a fixed-fee return and hourly monthly work, bill the return on its milestone and the hours on the month-end close. Use two invoice line labels, “Tax return preparation, fixed fee” and “Monthly bookkeeping, hourly.” Never bill the same hour on both.

Document management and the client portal

Document management covers three jobs: the request that asks the client for a file, the storage where the file lives under the right entity and year, and the access rules that decide who can open it. Each file should carry the entity, the tax year and the document type, so a 2026 bank statement cannot be mistaken for a 2025 one. Ask the vendor to show one entity's folders across two tax years.

Security is part of this function, not an add-on. The IRS tax professionals page says “Protecting client data also is the law” and points firms to Publication 4557, “Safeguarding Taxpayer Data: A Guide for Your Business.” The same page says the IRS and the Security Summit remind tax pros that they must have a Written Information Security Plan, and it lists Publication 5709, “How to Create a Written Information Security Plan for Data Safety.” The FTC Safeguards Rule lists tax preparation firms as covered entities. It requires encryption of customer information on your system and when it is in transit, and multi-factor authentication for anyone accessing customer information on your system.

The rule also requires notice to the FTC if a notification event involves the unauthorized acquisition of unencrypted information for at least 500 consumers. The notice is due no later than 30 days after discovery.

Client consent under Section 7216

Section 7216 is the line that practice management vendors often blur. The IRS Section 7216 FAQ says: “A taxpayer must provide written consent before a tax return preparer discloses the taxpayer's tax return information.” The IRS information center notes that final Treasury Regulations on consent requirements relating to the disclosure or use of tax return information by tax return preparers became effective Dec. 28, 2012.

Decision rule: before you connect a tool that sends tax return data outside the firm, such as a vendor analytics service or an outside mailing tool, ask two questions. Does the data leave the firm? Does the client's written consent cover that disclosure? If the answer to either is unclear, keep that data inside the firm's system for that step. A common failure is a CRM sync that pushes tax return amounts into a marketing list. The fix is to sync contact fields only.

Testing a vendor in a demo

Run the demo on your own work, not the vendor's sample data. Give the vendor one entity with a missing W-9, one client with a document that arrived late, one return that needs Form 8879 and one client that owns a second entity. Score each vendor on the same four cases, and time how long each takes.

Ask these questions and write down the answers. “Show me the Form 2848 attached to this entity and who it names.” “Show me where this client's signed Form 8879 is stored and who can open it.” “Show me the unbilled work for last month by client, and where a fixed-fee invoice is created.” “Show me the access log for the last time someone opened this client's SSN.” “What happens to our data if we cancel, and in what format do we get it back?” Get the answer in writing.

Where Usual fits

Usual covers the document side of this category. It sends client requests with due dates and automated reminders, gives clients a portal to upload files and answer questions, keeps a secure document library organized by client, and keeps a light client record. It does not do time billing, and it does not prepare or e-file returns. A firm that needs billing and return preparation still needs a practice management system or tax preparation software alongside it.

A request item can read: “Upload the 2026 statement for each bank account, one PDF per account per month.” Usual sends that item with its due date and follows up with reminders until the file arrives.