Frappe Books review: an honest 2026 look for small business

In brief: Frappe Books is worth evaluating if you run a solo or small operation that needs double-entry bookkeeping, invoicing, and point-of-sale on a desktop, with data stored locally and no subscription. It is a weaker fit if several people must work on the same books at the same time, if you need multi-currency accounting, or if your jurisdiction requires specific tax or report formats: open issues in the repository cover exactly those areas. Before production use, verify the core financial reports against your own sample transactions and test backup and restore before any upgrade.

This review is a source and documentation review of the public frappe/books repository as of August 13, 2026. No local installation or runtime testing was performed, so behavior in your environment remains to be verified.

Key facts at a glance

Item	Value
Review date	2026-08-13 (snapshot)
License	AGPL-3.0
Stars	4,884 (snapshot at review date)
Forks	1,130
Primary language	TypeScript
Latest release	v0.36.0, published November 6, 2025
Open issues	224
Verification level	Observed (source and documentation review)

What Frappe Books is

The maintainers describe Frappe Books as free accounting software aimed at small and medium businesses, and the README positions it as an answer to expensive, complex accounting tools. It is an Electron desktop application with a Vue.js front end and a local SQLite database, so it runs offline and keeps financial data in a file on each machine rather than in a central server.

Feature claims in the README include a dashboard, point of sale, double-entry accounting, invoicing, billing, payments, journal entries, and the standard financial reports: general ledger, profit and loss, balance sheet, and trial balance. Installers for Windows, macOS, and Linux are published on the releases page, and the README also documents Homebrew and Flatpak installation.

Who should consider it

Frappe Books is a reasonable candidate when all of these conditions hold: you are a solo founder, freelancer, or small team; one person at a time can do the bookkeeping; your books are single-currency; your accountant can accept standard reports or file handoff; and you are comfortable owning backups and upgrades yourself.

It fits well for retail or service businesses that want a point-of-sale-style flow without a subscription, and for environments with unreliable internet where offline-first work matters. Because the data model is local, you also avoid hosting and monthly fees.

When to look elsewhere

If two or more people must work on the same company file concurrently, if you invoice or hold balances in multiple currencies, or if your country requires a specific chart of accounts, tax rules, or report filings, treat Frappe Books as unproven for your case until you test it. Open issues cover multi-instance backup and sync, multi-currency support, and country-specific chart-of-account problems such as the open Tunisia chart-of-accounts issue.

Maintenance signals worth reading

At the review date the repository shows 4,884 stars, 1,130 forks, and 224 open issues. Releases in 2025 were steady: v0.33.1 in August, v0.34.0 and v0.34.1 in September, v0.35.0 in October, and v0.36.0 in November. According to its release notes, v0.36.0 added a party ledger, terms and conditions on the print template, multiple item selection in the item master, and Swiss localization. After November 2025 the release cadence paused: GitHub records the last push to the repository on May 28, 2026, and no newer release was available at review time.

Several long-running open issues matter more than the star count:

Profit and loss reports showing incorrect data, opened January 2024 and still open.
Trial balance and balance sheet showing incorrect data, opened January 2024 and still open.
Incorrect rounding for JPY amounts, opened November 2023 and still open.
A foreign key constraint failure after an in-app update, opened March 2025 and later reopened.
Failure to launch from a .deb install on Ubuntu 24.04, opened January 2025 and still open.
An open feature request for multi-currency support, and an open request for backup and sync between instances, labeled formidable-request.

These are user reports, not verified defects, and the release notes for v0.36.0 do not claim to fix them. The project is maintained enough to be viable, but its core-report bugs are exactly the kind you do not want to discover after entering a year of real transactions.

Deployment and data concerns

Deployment is desktop-first: download an installer for your platform, or use Homebrew or Flatpak. No server component is described in the README; it is packaged as a standalone desktop application, and the README describes the local SQLite file as the store for all financial data. That has consequences:

You own the backup strategy. Copy the database file on a schedule, and test that you can open a copy on a clean machine.
Upgrades can touch the schema. Users have reported an update failure with a foreign key constraint error, so back up before every upgrade and keep the previous installer.
Linux packaging is not trouble-free. The Ubuntu 24.04 launch issue has been open since January 2025.
Multi-machine or multi-user workflows have no built-in answer. The backup-and-sync issue asks how five to ten people could work on one company, and it remains open and labeled as a large request.

License is another deployment consideration. Frappe Books is AGPL-3.0. For internal desktop use that is usually straightforward, but if you modify the source and distribute the result, or offer a modified version over a network, the AGPL terms apply; have that reviewed before building a product or service on top of it.

Limitations and what is unknown

Because this is a documentation review, what is unknown matters: whether the latest release behaves correctly with real charts of accounts, whether the open report issues affect your specific setup, and how the app behaves after repeated upgrades. Nothing in the available release notes for v0.36.0 addresses the open profit-and-loss or trial-balance reports, which does not prove the issues persist but does mean you should not assume they are fixed.

Known limitations from the issue tracker include multi-user concurrency, multi-currency books, zero-decimal currency rounding like JPY, and country-specific charts of accounts. Translation coverage is broad but uneven, with one open issue reporting an English/French language mixup, so verify your language before committing.

What to check before production

Run a pilot company with realistic sample transactions and reconcile the ledger, profit and loss, balance sheet, and trial balance to expected values.
Confirm the chart of accounts and tax setup match your country. Regional additions such as the Swiss localization in v0.36.0 show this work is ongoing, not universal.
Test backup and restore by copying the SQLite file and opening the copy on another machine.
Perform a dry-run upgrade: install the latest release, open an existing company file, and confirm there are no schema errors.
Decide how data reaches your accountant: exports, print templates, or direct file handoff.
If you plan custom development, confirm the build toolchain from the README (Node.js v20.18.1, npm, and yarn) and factor in ongoing maintenance of your fork.
Review AGPL implications before redistributing modified builds.

Alternatives and evaluation questions

Frappe Books competes with two broad categories: web-based ERP and hosted accounting systems, which solve multi-user and centralized access but add hosting cost and connectivity requirements, and other desktop or self-hosted tools with different maturity and license trade-offs. The right comparison depends on your constraints rather than on feature lists.

Useful evaluation questions:

How many people need to enter or review transactions, and do they work on the same company at once?
Do you have more than one currency, or currencies without decimals such as JPY?
Which tax regimes and report formats does your accountant or regulator require?
Who is responsible for backups and upgrades if the tool is free?
What integrations do you need: bank feeds, e-invoicing, or API access?
Do you plan to modify or redistribute the software?

Verdict

For a solo founder, small shop, or freelancer with single-currency books and a tolerance for maintaining their own backups, Frappe Books is a credible free option: established, desktop-friendly, offline-capable, and actively enough maintained. For multi-user teams, multi-currency operations, or anyone whose reporting accuracy depends on jurisdiction-specific rules, plan to pilot and verify it rather than assume it works. The open report issues and the pause in releases since November 2025 mean the safe path is a small pilot with backup drills before any real financial data goes in.

How I can help

At XP812, I help businesses evaluate and operationalize open-source business software like Frappe Books: building and packaging customized versions, setting up backup and upgrade procedures, validating charts of accounts and reports, and developing the integrations a local workflow needs. If you are deciding between Frappe Books and a fuller ERP or hosted accounting system, I can map your requirements to a shortlist and a pilot plan.