What four invented businesses reveal about real accounting software needs

"Which package should I use" has no answer without knowing what the business does, because the requirement is set almost entirely by transaction shape. Two businesses of identical size can need completely different things.

Below are four invented businesses, each with the transactions that define its requirement and the specific capabilities those transactions demand. None of them is a recommendation and no product is named. Read the one closest to your own shape and take the reasoning rather than the conclusion.

What to take away

A one-person consultancy

Transactions: a handful of customer invoices a month on terms, a dozen supplier costs, a bank account, an occasional payment in a foreign currency, and the owner taking money out.

What it actually needs is small: invoicing with terms, a bank feed, and a clean separation between owner drawings and costs. That separation is the single distinction most often got wrong at this size.

When it fails, the profit and loss statement becomes meaningless.

Over-buying is the trap. A consultancy with twenty invoices a month does not need a stock module, job costing or an approval workflow, and paying for them buys complexity rather than capability.

The foreign currency payment is the awkward case. Check how the package records the difference between the rate on the invoice and the rate on the day it was paid, because doing that by hand every month is unpleasant.

A shop holding stock

Transactions: many small sales through a till or a card reader, settlements arriving net of fees, supplier deliveries, and stock sitting on shelves.

The first is decomposing a settlement: a deposit arriving net of fees and refunds splits into gross takings, the fee as a cost, and refunds against sales. Without that split, a business never sees what its payment costs are.

The second is stock: a valuation adjustable after a count, with the difference landing in cost of sales in the right period.

Everything else is secondary. A shop that gets those two right can run on a modest package. A shop that gets either wrong will have a gross margin that moves for reasons nobody can explain, and the reconciliation that catches it is the dull one of agreeing the stock figure to a physical count.

A trades business working in jobs

Transactions: quotes that become jobs, materials bought per job, subcontractors invoicing per job, staged customer invoices, and retentions held back until work is signed off. Whether a person working on a job is a subcontractor at all is a separate question with its own consequences, and the federal guidance on independent contractor or employee is where to settle it.

The defining requirement is a tracking dimension that reaches every transaction: purchase invoices, subcontractor costs, employee time and sales, all taggable to a job. Without it, job profitability is a spreadsheet exercise repeated forever.

Two specific tests. Can a single supplier invoice be split across three jobs and one overhead line, and does the total still have to agree. And can a deposit taken before work starts be held as a liability and applied to a staged invoice later, which is the treatment described in the revenue recording guide.

The reconciliation this business most often skips is the sum of job costs back to the ledger. Job reports and the ledger drifting apart is the standard failure, and it always comes from a cost coded to an overhead account because nobody knew the job.

A subscription business

Transactions: recurring billing, payments collected automatically, failed collections, upgrades and cancellations mid-period, and money taken in advance for a year.

The defining requirement is deferred income. Money billed for twelve months is a liability on receipt, releasing into revenue as the service is delivered. The release schedule must be visible and checkable, not buried in a billing platform.

The statutory requirement, that a method of accounting clearly reflect income, is at 26 U.S. Code section 446. How it applies to advance payments is a question for your accountant.

The second requirement is the failed collection list. These do not appear as aged invoices, so the ordinary aged report is not the control here; the exception list in the billing system is, and it needs an owner. The measurement habits in the accounts receivable guide still apply, but the report they apply to is a different one.

Where the billing system is separate from the ledger, the joint between them is the thing to design first: what posts across, how often, and which balance is agreed to which.

The four side by side

The right hand column is the more useful one. Each of these businesses can be run adequately on a modest package and none of them can be run on any package without the reconciliation beside it.

What all four have in common

The same monthly joints: bank, receivables, payables, and whatever is held on behalf of an authority. The same requirement for a period that can be closed and not silently changed. The same need for an account structure that means something, which is a chart of accounts decision rather than a software one.

And the same order of work: settle the structure, then test the awkward transactions, then choose. That sequence is set out in the guide to accounting software, and it applies whichever of these four you resemble.

Common questions