4 things to check in bookkeeping firm software

What to take away

This article is general business information for bookkeeping firm owners, not accounting, tax, legal or security advice for your clients. Requirements vary by jurisdiction and engagement, so confirm current rules with your state board of accountancy and a licensed CPA or attorney.

Four checks decide a software purchase: the ledger, the workflow, the document trail and the credentials. Everything else is a demo.

Check the ledger against your own client files

Load a real client into the trial. Set the accounting basis, build the chart of accounts, apply tracking classes, and add a second entity and a foreign currency if you serve them.

Post a bank feed, reconcile a month, make an adjusting entry, close the period, and print the statements. Export the file and open it in another program.

Then ask the question the sales call avoids: does the ledger support the controls you promise clients? Not every cloud product locks a closed period the same way, and some cannot restrict who posts to retained earnings.

If the trial file cannot survive a normal month, stop. The rest of the comparison is wasted effort.

Check how the firm runs a week

Put your recurring engagements into the system: weekly transaction coding, monthly reconciliation, quarterly payroll filings, annual 1099-NEC preparation. Give each one a due date and a reviewer.

Now run an ordinary week, then a week with a sick bookkeeper and a client who sends nothing until the 28th. Watch what breaks.

The test is whether the software tells you the work is late before the client does. A dashboard that only counts completed tasks tells you nothing about capacity.

If your team keeps a parallel spreadsheet to know what is due, the software has failed, whatever the feature list says. The routines that survive a real month are described in the operations and workflow guide.

Check the document and approval trail

A client sends a bank statement, a vendor changes its remittance account, and a bill gets paid. Trace all three through the system.

You want to see who uploaded the file, when it arrived, what version replaced it, and how long it is kept. On the payment side, you want the vendor change flagged, the approval recorded, and the audit trail uneditable.

OCR matters less than people expect. Test the limits anyway: how many pages, how many files a month, and what happens to a duplicate receipt.

Then map the roles. A staff bookkeeper should not be able to approve a payment or delete a reconciliation. A reviewer should be able to see everything and change nothing.

Write down who can do what, and check the software can enforce it. Roles you cannot restrict in the product become rules you police by hand.

Check credentials and client data

Every person gets their own login. No shared passwords, including the owner's.

Turn on multifactor authentication everywhere it exists. Give admin rights to as few people as possible, and review the list quarterly.

Back up the data, then prove the backup restores. Export a full client file and confirm you could hand it over if the client left tomorrow.

The Federal Trade Commission's Safeguards Rule guidance explains that coverage follows what a business does, not what it calls itself, and it names tax preparation firms among covered financial institutions. In-scope firms need a written information security program.

The IRS Protect Your Clients; Protect Yourself campaign points tax professionals to Publication 4557 and to a written security plan covering physical and digital client data.

Small firms can start with the NIST quick-start guides, which translate the Cybersecurity Framework into plain steps. Record keeping basics sit in IRS Publication 583.

Your written program is the firm's own duty, not something the software vendor carries for you. The compliance side is covered in the licensing and compliance guide.

Check integrations and the migration

Test each connection with a failure, not a success. Break the bank feed, duplicate a transaction, post a correction after the period closed, and see what the integration does.

Payroll, bill pay, point of sale, ecommerce and inventory all deserve the same treatment. A connection screen that says "connected" proves nothing.

Migration is its own project. Clean the chart, contacts, vendors, customers and opening balances before you convert anything, and leave obsolete access behind.

Convert one service group first. Compare opening balances and reports against approved records, then widen the cutover.

Write the cutover steps into your standard operating procedures so the next hire can repeat them without asking you.

Pick the numbers you will actually watch

Each metric needs a formula, a source, an owner and an action. Without all four it is decoration.

Track close cycle time, reconciliation completion, unresolved items and review findings. Add realization, utilization and onboarding time if you bill hourly.

For a flat-fee book, watch recurring revenue, client concentration and days to collect instead. Gross margin per client belongs on the list either way.

Review the set monthly while the process is new. Once the numbers and the responsibilities hold steady, move to a quarterly review.

Never accept a vendor dashboard label without checking the calculation behind it. Two products can both show "utilization" and mean different things.

Worked example: a four-week pilot

Week 1: run the current month in the new ledger for one client group. Record the hours it takes and the errors it produces.

Week 2: move that group's recurring work into the workflow module. Note every time someone reaches for the old spreadsheet.

Week 3: test documents, approvals and permissions with the same group. Fix the role settings before adding anyone.

Week 4: compare the hours, the errors and the missed deadlines against your starting numbers. Expand, revise or stop.

Common questions

Who should own the software decision?

The firm owner sponsors it and signs the contract. Daily ownership belongs to the person who runs the workflow, usually the operations lead or senior bookkeeper. Technical and compliance calls go to whoever holds that responsibility in your firm.

How long should a pilot run?

One full monthly close, at minimum. A four-week cycle covers the busy stretch, the review and the billing. Anything shorter tests the demo, not the software.

What does the software cost?

Pricing models vary: per client, per user, per module, or a flat monthly tier. Subscription cost lands in your fee model, which is set out in the pricing and profit guide. Compare the total against the hours the tool saves.

When should we switch again?

Reopen the decision when client count doubles, when you add a service line, when the vendor changes its pricing, or when the team stops using a module. Review the product-by-product comparison in best bookkeeping firm software for 2027 against your own list before you commit.