For your bookkeeper
What your client's ledger looks like to you.
Your client uses Muntin Ledger to read vendor invoices. This page is what you, the bookkeeper, need to know about the data shape, the export path, and the privacy story.
The export schema
Each row exports to a CSV. The columns your books expect: date, vendor name, tax ID when present, invoice number, line items, total, and a per-row confidence score. The CSV is signed.
Sync to QuickBooks and Xero
Posting from the ledger to QuickBooks Online is live (one-way, dry-run by default). Xero is wired but not live in private beta. If your client is on Sage or another system, the CSV export covers the same path.
The audit log
Every action in your client's account is hash-chained. You can verify the chain at any time via /audit. A bookkeeper who needs to defend a posted bill has the receipt.
What we read and what we never read
We read your client's invoice content with templates and rules — never a language model. We do not read your client's email, calendar, or bank feed. We never train a model on their data; we do not have a model to train.