How do I choose small-business accounting software?

Choose accounting software by testing your actual bookkeeping workflow, the records you need to keep and how you will retrieve them if you leave. Compare the complete cost of setup, paid work, subscriptions and exit. A longer feature list is useful only when the features solve the jobs your business actually has.

I would bring a small set of representative transactions to the decision before watching a polished demonstration. The demonstration shows what the presenter prepared. Your own awkward invoice, partial payment or correction shows what you need to understand.

Start with the records and the people

List how the business creates an invoice, records a receipt, approves an expense, pays a bill and corrects an error. Add stock, projects, payroll, tax reporting or multiple currencies only where they genuinely belong. Identify which tasks must be handled inside the proposed software and which will stay in a separate supported process.

Include the people who do the work and the accountant or other qualified adviser who uses the records. The owner may love a dashboard while the person reconciling receipts cannot find the underlying transaction. Both experiences matter.

The IRS's recordkeeping guidance allows a system suited to the business that clearly shows income and expenses, while noting that business type affects the records needed for federal tax purposes. That is a reason to establish your record requirements, not a federal endorsement of a particular product.

Separate “must do” from “would be convenient.” A required export format or supported tax process is different from a preferred screen color. A weighted score cannot make a missing essential function acceptable merely because the product has attractive extras.

Turn broad requirements into tasks

“Handles invoices” is too vague. Can the business issue its actual kind of invoice, allocate a partial receipt, enter an authorized correction and show the remaining customer balance? Can an authorized person trace the result to the original records?

Write the required outcome, who performs it, who approves it and what evidence would demonstrate it. Keep permissions specific. A colleague who can create an invoice does not automatically need the ability to change the business's payment settings or every user's access.

Also ask what happens when the usual person is absent. The founder-absence guide examines whether information and authority remain usable beyond one person. A tool that only the owner can access may automate the work while concentrating the dependency.

Before comparing prices, determine which subscription level includes the required number of users, relevant functions and usable records. A low headline price is not the complete quote if every necessary task requires a separate upgrade.

Use a small acceptance fixture with known answers

The following is an original fictional fixture for a simple service business. It is a test specification, not a report of software the author has used or results obtained from any actual product. Use appropriate synthetic or authorized test records rather than placing live confidential data into an unapproved trial.

Start with $2,000 in a fictional bank account and no customer or supplier balances. Enter invoice I101 for $900. Allocate a $400 customer receipt to it. Enter an authorized $100 credit against the invoice, then allocate a further $400 receipt. Separately, record a $120 supplier bill and a $60 payment against it. There are no other entries.

Expected records for this defined fixture

Scroll across to follow the expected outputs. Use the arrow keys when the table area is focused.

Now present the existing $400 receipt as a matching bank-feed item. The expected outcome is a supported match to the receipt already recorded, not another $400 of sales or cash. Ask the person doing the trial to show the path, not simply point to a final total.

This fixture does not determine your business's accounting or tax treatment. It defines simple entries and expected balances so a workflow can be examined. Add the cases your business actually needs, with expected treatment agreed with the appropriate adviser.

The bank-reconciliation guide explains the separate month-end process. Software selection should establish whether the necessary evidence is accessible; a matching screen does not establish that every real payment was authorized.

Inspect corrections, exports and the exit route

Ask how an authorized person corrects a mistake while preserving a usable history. A system should not make it easy to hide a change merely to achieve a desired total. Establish what logs, supporting documents and approval records are available for your required process.

Then investigate export. Which transactions, balances, attachments, customer records and history can you retrieve? In what format? Does exporting require a particular plan, support request or additional fee? What access remains after canceling the subscription?

A summary spreadsheet may be useful without being enough to reconstruct the books. An export of current invoices may omit attachments or earlier corrections. List the needed records and have the supplier show the actual scope, rather than accepting “your data is portable” as the answer.

For a trial, confirm that an appropriate authorized person can open and interpret the proposed export in the intended destination. Do this in a safe test process. A downloaded file that nobody can use has not demonstrated a workable exit.

Compare complete costs over the same period

Consider two wholly fictional offers, A and B, for the same simple business. Neither represents a real provider, current market price or tested product. The quoted features appear to meet the required workflow, but the owner has not yet verified them through the acceptance tasks.

Both comparisons cover twelve months. Required bookkeeping work is paid at $45 an hour. Staff time includes all setup, test, migration, training and routine work stated below, without unpaid owner effort or double counting. These are the complete tool-and-work costs for this limited comparison, before tax and financing; no other business costs are being compared.

• Offer A: $35 a month; eight paid migration hours, four implementation-and-testing hours and four training hours. Routine work requires three paid hours a month.
• Offer B: $65 a month; four paid migration hours, four implementation-and-testing hours and two training hours. Routine work requires two paid hours a month.

The hours are fictional planning assumptions to verify. They are not evidence that one actual product is faster. If the trial reveals more work or a missing integration, change the estimate rather than preserving the preferred answer.

A's initial sixteen hours cost $720. Twelve subscriptions cost $420 and thirty-six routine hours cost $1,620. The twelve-month total is $2,760.

B's initial ten hours cost $450. Twelve subscriptions cost $780 and twenty-four routine hours cost $1,080. Its total is $2,310. Under these assumptions, B costs $450 less despite the higher monthly subscription.

The company has $3,000 separately available for the complete year's modeled tool-and-work costs. Both totals fit. It also chooses a $650 limit for initial work plus the first month's subscription and routine work. A needs $890, exceeding that limit by $240. B needs $605, leaving $45 within it.

This opening limit is the owner's chosen constraint, not an industry standard. The full year's remaining money is already assigned; no speculative customer receipt is needed to fund the comparison. Timing still matters when accepting an actual subscription or service arrangement.

Let a failed requirement outweigh the price result

The arithmetic makes B an attractive candidate, conditional on its requirements being satisfied. It does not make B the winner before the workflow and records are checked.

Suppose B cannot supply a required history in a usable export. That missing requirement is not repaired by the $450 saving. Establish whether there is a supported, acceptable process with a complete additional cost. If not, hold B rather than labeling the limitation a minor inconvenience.

Likewise, if A's extra routine hour was based on an incorrect assumption, recalculate the comparison. Removing twelve paid hours would reduce A's cost by $540, to $2,220. A would then be $90 cheaper than B on the revised annual inputs, although its separate opening-cost issue would remain.

That sensitivity is useful because it identifies a worthwhile trial question. It does not prove either estimate. Ask the person doing the actual work what created the extra hour and whether the same task has been counted in both offers.

Plan migration as a controlled change

Choose a cutoff, preserve the old records and identify who may change each system during the transition. Agree which opening balances and outstanding transactions must transfer. An invoice already paid before the cutoff should not reappear as collectible merely because an import succeeded.

Reconcile the relevant balances and a sample of supporting records before declaring the new process ready. Document omissions, failed imports and corrections. If critical records remain unresolved, keep the limitation visible and decide whether the change can proceed safely.

Do not cancel the old access simply because a migration file was uploaded. Establish the retention and retrieval arrangement for the records you actually need. The applicable retention period depends on the record and requirement; a software cancellation date does not settle that question.

Finish with a selection record someone can revisit

1. Required work: the actual transactions, records, roles and outputs the business needs.
2. Acceptance evidence: which tasks were demonstrated, by whom, in what version and with which unresolved gaps.
3. Complete cost: subscriptions, paid work, integrations, migration and exit across the same period.
4. Control and access: authorized roles, recovery routes, records availability and responsibility if a colleague leaves.
5. Transition decision: the cutoff, reconciliation, remaining exceptions and conditions for retiring the old process.

A good choice makes the books easier to maintain and understand. It should not require the business to forget how an important number was produced.