Choosing accounting software isn’t about finding “the best program” — it’s about finding one that covers your workflows and survives growth. A mistake is expensive: migration takes weeks, and some history is almost always lost. Below are the three models — desktop, cloud, open-source — and how to compare them. All three appear in the business accounting category.

Start with a list of must-have workflows

Before comparing prices, write down what the system must do every month:

  • Invoices and closing documents. Do you handle VAT? Do you need statements, delivery documents, tax invoices, templates with your details? There’s a separate category for invoicing tools.
  • Bank reconciliation. How do payments get into your books: automatic bank import, or manual entry of each transaction?
  • Payroll. If you have employees — contributions, payslips, advances. The heaviest module, and not everyone needs it.
  • Reporting. What you file and where: declarations, balance sheets, statistics — and does the system file them itself or export for an accountant?

Such a list cuts half the market immediately. A solo founder doesn’t need payroll; a marketplace seller cares more about the platform integration than the bank one. The second filter is who keeps the books — you, an in-house accountant, or a remote contractor — which decides whether you need multi-user access and a web version.

Desktop software: offline control and a one-time price

The classic model: the program installs on your computer, the license is bought once. Strengths — data stays local, no internet required, total cost known upfront.

The downside: updates to reporting forms and reference dictionaries are bought separately or installed manually, and after 2–3 years those upgrades can cost as much as a new license. A second machine means file transfers or a network; a remote accountant means trading archives.

For a micro-business keeping books by hand, a heavyweight desktop system is often overkill. A solo founder without employees or bank autoloading gets by with a lightweight offline app: manual entry plus cash flow forecasting — future balances are visible in advance, and a cash gap is no longer a surprise.

Cloud services: bank integrations and a per-user subscription

Cloud accounting takes over the busywork: statements are pulled from your bank automatically, payments are recognized and offered for posting, documents are generated from templates, and reporting forms update themselves. Access is from a browser and a phone, and the accountant and the owner see the same data.

Pricing is the key difference: a subscription tied to users and transaction volume. A plan that suits a solo founder doubles once a second accountant joins. Calculate the cost over three years and budget for growth.

Before paying, check:

  • Is your bank and country supported? Automatic statement import is the main argument for the cloud — and the one that most often “doesn’t work” in your region.
  • If you cancel: in what format, and at what price, do you get your data archive?
  • What are the plan’s limits — transactions, documents, counterparties?

Open-source and open-core: self-hosting or paid support

Free systems with open code — for example, GnuCash — give you double-entry accounting, multi-currency support, and decent reports with no subscription fee. The price: everything beyond the core is on you. Country-specific reporting, backups, updates — your time or a specialist’s fee. The real cost of open-source is administration hours times their price.

Who self-hosting suits

Anyone with a person able to install and maintain the system: a sysadmin, an enthusiastic accountant, or a technically minded owner. Data stays on your server — for teams wary of sending financial data outside, that’s the deciding argument.

The open-core model

A middle ground: the core is free, while cloud hosting, support, and integrations are paid. A sensible compromise if you can self-host but don’t want to face the problems alone.

Multi-currency, branches, inventory: when simple accounting stops being enough

A simple system handles one account in one currency. The threshold:

  • Foreign-currency payments. Exchange rates on the transaction date, revaluation of balances, exchange differences — a basic tracker can’t do this.
  • Separate divisions. Separate cash registers, accounts, inter-branch settlements — that takes a multi-user system with access rights.
  • Inventory. Stock levels, write-off costs, batches — that’s inventory management; gluing it to accounting through Excel breeds discrepancies.

The sign it’s time to switch: your books run on “accounting program + spreadsheets + a notebook.” Every manual link is a future error at month-end close.

Data migration: what to check before moving

  • Balances as of the transition date. Minimal option — carry over balances and counterparty debts as of the first day of a quarter, keeping the old system as a read-only archive.
  • Reference data. Counterparties and product lists usually transfer by file without trouble; contracts and open orders — not necessarily.
  • Transaction history. A full transfer of past postings is rarely clean: test the import on a real export from your old program, not the vendor’s demo.
  • A parallel period. Run both systems for a month or two and compare trial balances — before filing reports, not after.

Last: judge the decision against your own workflow, not someone else’s success story. A financial apps directory with filters by platform, pricing model, and bank integrations narrows the field to a dozen candidates — then run each against your must-haves.