All work
Product· Live independent SaaS build

LedgerAI

An AI bookkeeper built on a real double-entry accounting engine

A full-stack financial operating system for small service businesses. The product hides accounting vocabulary behind a review inbox while preserving ledger integrity underneath—combining invoicing, expenses, reconciliation, receipts, tax workflows, and an assistant that can answer questions over the books.

Role · Product architecture and full-stack engineering

System anatomy

01AI Bookkeeping
02Tool-Based Assistant
03Document Extraction
04Guarded Automation
LedgerAI live product interface

Captured from the live product · October 2026

Open live product

The problem

Small-business owners need reliable books without learning chart-of-accounts mechanics. LedgerAI turns financial activity into reviewable decisions while keeping every accepted action consistent with a double-entry ledger and audit trail.

What the system does

Capability with an operating model.

Double-entry ledger with cash/accrual reporting and integrity checks

Invoices, estimates, bills, expenses, payments, credit notes, and recurring work

CSV/PDF statement import, receipt photo extraction, matching, and reconciliation

Rules and learned merchant memory with guarded AI categorization

Ask-your-books assistant, insights, tax center, and accountant export package

Tenant isolation, team roles, audit, recovery, MFA, and passkey authentication

Architecture

How it fits together.

01

FastAPI domain services around ledger, matching, receipts, tax, and reporting

02

PostgreSQL as the source of truth with transactional background-job queue

03

S3-compatible document storage for receipts and statements

04

Next.js 16 responsive PWA with extensive accessibility and e2e coverage

05

Provider gateway keeps LLMs limited to extraction and understanding—not money math

Key decisions

01

AI never owns the books

Models propose classification and extraction; deterministic services preserve accounting invariants.

02

Review, not accounting UI

Owners work through exceptions and decisions while journal mechanics remain underneath.

03

Correct by reversal

Posted financial history is preserved through reverse-and-repost workflows instead of silent mutation.

Explore another system