On the first Monday of March, a sole proprietor drops a folder on the desk of a four-person CPA firm: 12 checking statements, 12 Amex statements, no books. The return is due in six weeks.
A small CPA firm runs about eight kinds of software, one per job: tax preparation, client ledgers, statement conversion, receipt and bill capture, practice management, a client portal with e-signature, payroll, and workpapers. Most firms don't buy that stack on purpose. They inherit it, and each spring they replace whichever piece hurt the most.
I build tools for accountants, and I keep seeing the same mistake: people compare products before they've written down the jobs. So here is the stack as a list of jobs, with the March folder as the test case.
What does each piece of a CPA firm's stack actually do?
Tax preparation is the anchor. Drake Tax, UltraTax CS, Lacerte, ProSeries and CCH Axcess Tax are the names you hear most. Each client's prior year rolls forward inside it, which is why leaving one is painful.
The client ledger holds each client's transactions, reconciliations and financial statements. QuickBooks Online Accountant and Xero dominate, and AI ledgers are a newer option for clients whose books the firm keeps end to end.
Statement conversion turns PDF bank and card statements into Excel or CSV. It barely matters for eleven months and then decides how March goes.
Receipt and bill capture (Dext, Hubdoc and similar) reads documents so nobody types vendor names and amounts.
Practice management (Karbon, Canopy, TaxDome, Financial Cents) tracks deadlines, tasks, time and billing. Plenty of small firms run this on a shared calendar and a spreadsheet until the day it breaks.
The client portal and e-signature layer (TaxDome, SmartVault, ShareFile, Liscio, SafeSend) collects documents and signatures without email attachments.
Payroll (Gusto, ADP, Paychex) runs paychecks and files payroll taxes.
Workpapers means CaseWare for some firms and Excel for nearly all of them.
None of those lists is a ranking. Several vendors cover two or three rows in one suite.
Which tool should a small firm choose first?
Tax software. It is the hardest to move, so everything else should either export into it or sit comfortably beside it. Picking a ledger first and then discovering it doesn't fit your tax workflow is the expensive order.
For the ledger, follow the client. If a client already keeps their own books in QuickBooks Online, you work there. You only get a real choice for clients whose books you keep yourself, and that is where automation pays back fastest.
How does the March statement pile actually get handled?
Back to the folder. Here is the arithmetic, with figures that are illustrative, not measured:
| Retyping by hand | Converting with a balance check | |
|---|---|---|
| Statements | 24 | 24 |
| Transactions (assumed) | about 1,100 | about 1,100 |
| Time per transaction (assumed) | 20 seconds | none, reviewed by exception |
| Entry time | about 6 hours | minutes to upload and download |
| How you know nothing is missing | someone re-adds every month | each statement tied to its printed opening and closing balance |
Six hours hurts, but the transposed digit in July hurts more, because nobody finds it until the profit number looks strange in April.
So the workflow I'd recommend:
- Ask for actual statements through the portal, not screenshots and not exported activity. A download from online banking has no printed opening and closing balance, and those two numbers are your proof.
- Convert the full year in one pass and get one Excel file for the client, or one per account. Card statements with extra cardholders should come back with a cardholder column.
- Open only the statements that don't tie. If one month is off by $214.60, you look at that month, not all 24.
- Categorize in your workpaper and map to tax lines. Watch the card payment, which shows up on both the checking and card side and gets counted twice more often than you'd think.
- Decide whether this client should have real books next year. If yes, set them up as a client company in a ledger now, so next March starts from a finished profit and loss.
What's the most common mistake in building the stack?
Adding a tool to fix a problem another tool already half-solves. Every extra product is another login, another place a document can hide, and another vendor that holds client data.
That last point has a compliance side. Firms that prepare returns must keep a written information security plan under the FTC Safeguards Rule, and IRS Publication 5708 has a template sized for small practices. Each tool you add belongs in that plan.
A short checklist before you buy anything
- Write the jobs down first and mark which ones already have an owner.
- Confirm the new tool exports in a format your tax software or workpapers accept.
- For a converter, check that it proves each statement against its printed balances and splits by account and cardholder.
- Ask whether clients get logins, and whether you want them to.
- Add the tool to your written security plan the day you sign up.
- Drop one overlapping tool for every one you add.
Where does ZeraBooks fit?
Disclosure: I'm the founder of ZeraBooks, so weigh this paragraph accordingly. ZeraBooks covers two rows, statement conversion and the client ledger, for firms that keep client books themselves. It does not do tax prep, practice management, a client portal, e-signature or payroll. It has no bank feed and doesn't sync with QuickBooks or Xero; the converter gives you QuickBooks-ready and Xero-ready CSV to import yourself. If you want the full table by job, it's in our guide to CPA tools for a small firm, and the ledger side for multi-client work is on our page for accountants who keep client books.
Top comments (0)