GnuCash 5.9

Original Article ↗ Hacker News Discussion ↗

Overall impressions & use cases

  • Many praise GnuCash as solid, free software with long-term stability; some have 15–20+ years of continuous data.
  • Used for personal finance, freelancers, small businesses, cafés, and hackerspaces; strong for balance sheet / P&L reporting and planning cash flow months ahead.
  • Others bounced off it, finding it too complex or “accountant‑oriented” for simple personal budgeting.

Data formats & scripting

  • Data backends: XML, SQLite, and SQL databases. XML is appreciated for being human‑readable and version‑controllable, but considered cumbersome to edit and fragile by some.
  • SQLite is seen as more robust and easier to script against, though the schema is non‑trivial.
  • Users mention Python bindings, a REST API, and Guile-based extensions, but documentation and user-facing scripting “engine” are considered weak.
  • CSV import is widely criticized; bulk corrections after imperfect imports are painful.

Plain‑text vs database/GUI tools

  • Several switched to plain‑text accounting (Beancount, HLedger, Ledger) for easy bulk edits, git history, and custom reporting.
  • Counterpoint: plain text is harder to parse reliably; structured XML/SQL is seen as better for robust tooling.
  • Some run scripts to convert GnuCash XML to Ledger/Beancount formats to get the best of both worlds.

UI/UX and usability

  • UI described as “mid‑90s”, enduring but clunky; good that it doesn’t change constantly, bad for discoverability and productivity.
  • Learning curve is steep; documentation does teach accounting basics but scripting/reporting tutorials are lacking.
  • Website is criticized for not being mobile‑friendly; others argue that matters little for a desktop-only tool.

Business vs personal use; ecosystem lock‑in

  • For small, simple businesses GnuCash can work well.
  • For “real startups” and organizations needing tight integration with banks, payroll, tax systems, investors, and auditors, QuickBooks (or regional equivalents) is described as effectively mandatory.
  • Moving from GnuCash to QuickBooks or ERPs later can be painful; some advise not imposing GnuCash on accountants.

Granularity, categorization & missing features

  • Debate over tracking every receipt line vs coarse categories; many argue extreme granularity yields little actionable benefit.
  • Users want better autocomplete/suggestions for split transactions, vendor tracking without creating many accounts, and tag-based reporting.
  • Multi-currency and tax handling are possible but can be error‑prone and not tailored to some countries’ rules.

Alternatives mentioned

  • HomeBank, KMyMoney, MoneyManagerEx, Firefly III, actualbudget/YNAB-like envelope tools, ERPNext, Odoo, and others appear as options, each trading off simplicity, web access, or ecosystem support.