Verification
Proof you can runon your machine
Open a period-close, audit-chain, or receivable package and the cryptographic check runs locally — valid or invalid, surfaced on the spot. View signed certificates in the browser, or run the full check on Desktop or from the terminal.
Proof registry with purpose labels, period and invoice context, and verification pipeline
What you can verify
Built into the ledger — exports and share links for anyone who needs to confirm the math without trusting a PDF.
Period close
Zero-knowledge proof that your trial balance ties for a book and period — public inputs only, no line-item exposure.
Audit chain integrity
Hash-chained audit logs verified end to end. Run the integrity check any time; an altered entry breaks the chain and surfaces immediately.
Receivable attestation
Financeable invoice exports with witness bundles lenders and factors verify independently — the same packages Desktop and the CLI consume.
Three ways to verify
Start with a share link in the browser. Move to Desktop or the CLI when you need the full local check.
Verify workspace
Open a seller share link in the browser for attestation summary and package download — no login required for read-only checks.
Open Verify workspaceTripleBooks Desktop
Run the full cryptographic check on exported JSON on macOS or Windows. Pinned verification keys ship with the app.
Download DesktopOpen-source CLI
Script verification in CI, credit ops, or auditor workflows. Same engine as Desktop — axiomatic-receivable verify against exported packages.
See Desktop & CLITripleBooks Desktop
Local proof verification on macOS and Windows. Open exported JSON, run the same checks as the Verify workspace, and keep sensitive packages on your machine.
macOS 13+ (Apple Silicon and Intel) and Windows 10+. Touch ID sign-in on signed Mac builds.
Full Desktop & iOS details →$ axiomatic-receivable verify ./exports/proof.json
circuit·receivable-attestation
vk·pinned · open source
bundle_hash·matched
status·VALID
Proof verified locally
Same verifier engine bundled in TripleBooks Desktop — scriptable for CI, credit ops, and auditor workflows.
Theoretical foundation
Ledger-Native Triple-Entry Accounting
Double-entry bookkeeping keeps the books in balance, but independent parties still need evidence that reported state follows from complete, unaltered records. This paper lays out ledger-native assurance: verification artifacts produced during accounting close, with source anchoring, selective disclosure, and explicit scope for auditors and regulators.
Working paper · May 2026 · Matthew Rosendin
Encryption and isolation
Verification proves the numbers tie. Per-tenant databases, encryption at rest, and tamper-evident logging protect how those numbers are stored.