Skip to content

LedgerTB 1.0.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 11 Aug 20:50
· 44 commits to main since this release
v1.0.0
efab479

LedgerTB is desktop double-entry bookkeeping for client work. Your books live in an encrypted file on your machine — no server, no accounts, no one else holding your data — and your AI assistant can work in them at a permission level you choose.

Download

Windows: LedgerTB-1.0.0-windows-x64-setup.exe — run the installer; no administrator rights needed.

Windows will show a SmartScreen warning that says the publisher is unknown. That warning is accurate — this build's publisher identity isn't verified yet, which is not the same as the software being unsafe: the source is auditable and every build comes from CI. Click More info → Run anyway. A signed build is planned as an update.

Mac: LedgerTB-1.0.0-mac.zip — unzip and drag LedgerTB to Applications. Notarized by Apple; it opens with no warnings.

What you get

  • Real double-entry books. Clients, chart of accounts, journal entries, trial balance worksheet with adjusting entries, statements, general ledger, close package export. Unbalanced entries never post.
  • Your data stays yours. The book file is encrypted with a passphrase only you hold, backups are encrypted and verified, and every change is written to an audit trail.
  • Bring any chart of accounts. Numbered, QuickBooks-typed, or no numbers at all — imports whole, with numbers assigned by type when they're missing.
  • Work with your AI assistant. An MCP server lets Claude (or any MCP client) read your books, stage imports, draft entries, or post — you pick the level: read-only, propose-for-review, or post. Each book is authorized separately, and the setting lives outside the assistant's reach. Everything the assistant does is attributed, logged, and queued on the Assistant Review page for your sign-off. The ledger is append-only for everyone, assistant included.
  • Firm mode. Keep book files on a shared drive with in-use locking, one writer at a time.

Before you put real client work in it

Open Data Safety first. It runs a short checklist — disk encryption, book encryption, file permissions, a verified backup — and tells you plainly what's covered and what isn't. Set your book file somewhere your firm's encrypted backup actually reaches; the default location is not part of any backup plan you haven't set up yourself.

The practitioner stays responsible for the books. LedgerTB enforces the mechanics — balanced entries, an append-only ledger, an audit trail — but every judgment in your books is yours, whether you made it directly or accepted a suggestion from the assistant. The software is provided as-is, without warranty (MIT).

(If you tested a pre-release build under the old ProBooks name: your books, backups, and settings all keep working — see the README's note. LedgerTB installs as its own program; remove the old ProBooks entry by hand.)

Full changelog: https://github.com/charliebarmore/LedgerTB/commits/v1.0.0

Assets 8
Loading