Proof, not promises
Accounting you can verify
Don't take our word for the math. LineLedger publishes end-to-end accounting proofs — run on real data, with downloadable evidence and SHA-256 hashes you can re-check. Clone the repository and the engine proves itself on your own machine.
Three proofs, run on real data
Each scenario runs the full posting engine and reads the result straight back off the general ledger — the same code that keeps your books.
Three-year closing trial balance
Hundreds of transactions a year across 2023–2025, closed and rolled forward. The trial balance ties out to the cent at every year-end — net income closes to equity, and the books carry cleanly into the next year.
Imported trial balance
Opening balances replayed into a fresh set of books, proving an import lands perfectly balanced before you post a single new transaction.
QuickBooks journal import
A full-history general ledger replayed from a QuickBooks export — every journal re-posted, accounts mapped, contacts linked — and the result reconciled against the source.
Evidence you can download
The seeded source data and the reports each proof generates are downloadable, every file stamped with a SHA-256 hash. Pair that with the full source on GitHub and you can confirm the numbers yourself — no trust required. That is what open source buys you that a demo video cannot.
Common questions
- What are the verification proofs?
- A set of end-to-end accounting scenarios that run against seeded data and publish the reports they produce. They live in the repository alongside the code, so the same proofs run on your own checkout — you never have to take our word for the arithmetic.
- Why does this matter?
- Most accounting software asks you to trust the math behind a closed-source black box. Because LineLedger is open source, you can both read how every balance is computed and watch it proven on real data — with evidence you can download and re-check yourself.
- Can I reproduce the results?
- That is the whole point. The source data and the generated reports are published with a SHA-256 hash each, and the full application source is on GitHub under the GNU AGPLv3. Clone it, run the proofs, and you should get the same numbers, to the cent.