Choosing accounting software for a client means matching the ledger to five things: how many transactions they have, what their industry needs, who on their side will log in, how bank statements will reach the books, and whether your practice can support it. Score two or three candidates against those, and pick the one that fails nowhere important.
Who should choose a client's accounting software?
The client should make the final choice of accounting software, with the bookkeeper leading the recommendation. The client pays for it, owns the data and may keep it after you part ways. The bookkeeper knows what the books need and will spend the most hours inside it. Both views belong in the decision.
In practice, the decision falls into one of three situations:
- A new business with no books. You have the most freedom. Recommend what fits them and your practice.
- A client already on a ledger. The bar for switching is high. Stay unless the current system is causing real problems.
- A client on spreadsheets or nothing. Often this is a catch-up job first. Choose the ledger before entering a year of history, so the work is done once.
The third case is common enough to plan for. Getting a client from a pile of statements into a working ledger is its own project, and the post on software for catch-up bookkeeping covers the tools for that stage.
Write the recommendation down with the reasons. If the client later asks why they are paying for a particular plan, you can point to the needs it met.
Matching accounting software to client size and transaction volume
Client size, for this choice, is mostly about transaction volume and complexity rather than revenue. A business with a few hundred bank lines a month and one account needs a simple ledger. One with several accounts, inventory and staff needs more. Buy for the next two years of growth, not the next five.
Count before you choose. Look at three recent months of the client's bank and card statements and note:
- The number of transactions per month across all accounts.
- The number of bank, card and loan accounts.
- Whether they hold inventory.
- Whether they pay employees, and how many.
- Whether they invoice customers or are paid at the point of sale.
A client with forty lines a month and no staff can run on an entry-level plan. A client with two thousand lines and stock needs inventory features and probably a higher tier. Many ledgers price by feature tier, so the count tells you which tier to start on.
Industry needs that narrow the accounting software choice
Industry needs narrow the choice when a client's business requires features most ledgers lack or price highly. Job costing for contractors, inventory for retailers, fund tracking for nonprofits and class or location tracking for multi-site businesses are the usual ones. Check these first, because they rule options out faster than anything else.
Questions to ask by industry:
- Trades and repair businesses. Do they need to track parts and labour per job? Do they hold parts stock?
- Retail and restaurants. Does the point-of-sale system connect to this ledger, and how are card deposits net of fees recorded?
- Professional services. Do they bill by time? Does the ledger connect to their time or practice software?
- Property. Do they need to track income and costs per property?
Also check whether the client runs other software the ledger must talk to, such as a shop management system or a point-of-sale terminal. An unsupported connection means manual entry every month, which often costs more than a higher ledger tier.
Users, access and the client's own team in the software
Users are the people who will log into the accounting software: the owner, an office manager, the bookkeeper and perhaps a tax preparer. Each needs a login with the right access. Plans often limit the number of users, and some charge per seat, so count them before you pick a plan.
Think through each role:
- Owner. Usually wants reports and perhaps invoicing, but rarely entry rights to the bank accounts.
- Office staff. May enter bills or invoices, but should not edit closed months or change the chart of accounts.
- Bookkeeper. Needs full access to the books.
- Tax preparer. Needs read access at year end, often through an accountant user that does not count against the plan.
Restricting rights matters because the most damaging errors in a client's books are often made by well-meaning staff editing past months. Ask whether the ledger can lock a closed period and who can unlock it.
Access planning belongs in client onboarding too, alongside getting statements and logins. The post on client onboarding software for bookkeepers covers tools for that step.
How will statements get into the accounting software?
Statements get into accounting software in one of three ways: a live bank feed from the bank, an import of a file converted from the statement, or manual entry. Check which of these the candidate ledger supports for each of the client's banks.
A ledger with no working feed for a key account and no import option will cost you hours every month.
Bank feeds are convenient but not always complete. They can start only from the date they were connected, skip older history, or stop for a while when a bank changes its connection. For catch-up work and for accounts without a feed, you will need to import transactions from the statements themselves.
That is where a statement converter fits. AutoBankConvert turns a batch of PDF statements into files ready for QuickBooks or Xero, with each client's transactions categorized and each statement balance-checked before export. If the client's chosen ledger is one of those two, the import path is covered even when feeds are patchy.
For any other ledger, check what import file format it accepts and whether your tools produce it. Do this before the client signs up, not after the first month.
Accounting software choices that fit your practice too
An accounting software choice should fit your practice as well as the client, because you will work in it every month. A ledger you have never used costs learning time on every close. Where two options serve the client equally, pick the one your team already knows and your other tools connect to.
Benefits of keeping clients on a small number of ledgers:
- Your team learns one or two systems deeply.
- Your SOPs and checklists apply across clients.
- Statement imports, reports and other tools connect the same way for each client.
- Accountant programs offered by some ledger vendors give you one login across clients.
Do not force a client onto the wrong ledger to match your preference, though. A contractor who needs job costing should not be on a ledger that lacks it because your other clients use that one. The overview of bookkeeping software for accountants shows how firms organize their stack around the ledgers their clients use.
A worked example: an auto repair shop
The example below scores two unnamed ledgers for an example auto repair shop client. The shop has about 600 bank and card lines a month, holds parts inventory, has four staff and uses a shop management system for repair orders. Scores run from 0 to 5, and every figure is illustrative.
| Criterion | Example weight | Ledger A | Ledger A weighted | Ledger B | Ledger B weighted |
|---|---|---|---|---|---|
| Handles 600 lines a month | 3 | 4 | 12 | 5 | 15 |
| Parts inventory | 5 | 4 | 20 | 2 | 10 |
| Connects to shop system | 4 | 3 | 12 | 4 | 16 |
| Staff roles and locked periods | 3 | 4 | 12 | 3 | 9 |
| Statement import route | 4 | 5 | 20 | 3 | 12 |
| Your team knows it | 2 | 5 | 10 | 2 | 4 |
| Total | 86 | 66 |
Ledger B connects better to the shop system and copes slightly better with volume. Ledger A wins because inventory and statement imports carry the most weight for this client, and Ledger B is weak on both. The post on auto repair shop bookkeeping covers the parts, labour and card deposit questions that sit behind those weights.
Switching a client's accounting software midyear
Switching a client's accounting software midyear is possible but usually worth avoiding. Moving in the middle of a fiscal year splits the year's records across two systems, complicates year-end reports and means rebuilding opening balances at an odd date. Unless the current system is failing, wait for the start of the next year.
Reasons that justify a midyear move:
- The current ledger is losing data or cannot be backed up reliably.
- The client has grown into needs the ledger cannot meet, such as inventory or payroll.
- The current subscription is ending and cannot be renewed.
If you must switch, choose a month end and do it cleanly:
- Close and reconcile the old ledger to the switch date.
- Export the trial balance and open items, such as unpaid bills and invoices.
- Set up the new ledger with the same chart of accounts where possible.
- Enter opening balances at the switch date from the trial balance.
- Import transactions from the switch date forward, from statements or a feed.
- Keep read access to the old ledger for the rest of the year and for later questions.
A move at a fiscal year start follows the same steps, with less to carry across. Either way, keep the old ledger's final reports in the client's file, because questions about past years will come back to them.