HomeBank

In this category, GnuCash asks you to learn double-entry, Beancount asks for the command line and Firefly III asks you to run a server. HomeBank is the option that asks you to learn nothing.

Its model is the one already in an ordinary person's head: a few accounts (salary card, credit card, cash, a payment app), each transaction belonging to a category, and monthly budgets per category. Enter the data and it produces a pie chart of where money went, trend lines across months, and budget progress. No debits and credits, no chart of accounts, no accounting equation.

Features that pull their weight:

• Statement import in CSV, OFX and QIF, which most banks can export. It detects duplicate transactions during import, so overlapping date ranges do not get recorded twice.
• Automatic assignment rules: "if the payee contains this keyword, file it under that category", so an import does not require clicking through every line.
• Scheduled transactions for rent, mortgage payments and subscriptions, which generate pending entries automatically when due.
• Multiple accounts and currencies, useful for anyone travelling or holding foreign currency.

Data stays entirely offline in a local file, with no account and no network. The interface is traditional GTK desktop styling — not fashionable, but clearly laid out, responsive, and untaxing on old hardware.

Its boundaries are equally clear:

• No investment portfolio tracking. Cost basis and returns on stocks and funds are not its strength; use GnuCash for that.
• No mobile app and no sync. It is single-machine desktop software.
• Not for business accounting. No invoices, receivables or formal financial statements.

Who it suits: households that want to understand where the money actually goes without learning accounting to find out. If you eventually outgrow it, migrating to GnuCash is straightforward — it exports CSV and QIF.