Proof, not promises
Accounting you can verify
Don't take our word for the math. LineLedger ships end-to-end accounting proofs you run yourself — on real data, with downloadable evidence and SHA-256 hashes you can re-check. The engine proves itself on your machine, not on ours.
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.
php artisan proof:generate
php artisan test --compact tests/Feature/Proof
One ScenarioBuilder backs both the command and the test suite, so
the published page and the CI gate can never drift apart.
Common questions
- What is the verification page?
- A public, unauthenticated page built into LineLedger at /verification. It runs real end-to-end accounting scenarios on seeded data and shows the reports they produce, so the engine proves itself on your own install rather than on a demo we control.
- 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 design. Run php artisan proof:generate on your install to build and validate the scenarios, or php artisan test tests/Feature/Proof to run them as tests. The source data and generated reports are downloadable, each with a SHA-256 hash, and the full application source is on GitHub under the GNU AGPLv3 — so you should get the same numbers, to the cent.
- Why not just show me the proofs on your site?
- Because a page we host proves something about our server, not about the code you are about to run. One ScenarioBuilder backs both the published page and the test suite, so the proofs you generate locally are the same ones the CI gate runs — verified where it actually counts.