LOCAL FILES. CLEAR RESULTS.

Receipt ledger

Turn a pile of receipt photos into a clean expense ledger: merchant, date, amount, tax and category per photo, duplicates blocked locally, anomalies flagged, ready to export for reimbursement.

About this tool

Expense claims die in the camera roll: thirty receipt photos, each needing merchant, date, amount and category typed into a ledger before reimbursement. This tool reads the whole batch with the vision model behind your own API key and returns a dated ledger table, with a category you can adjust per row before exporting the CSV your finance process actually wants.

Two local safeguards run before and after the model. Identical photos are hashed in your browser and skipped, so the same receipt never gets claimed twice by accident. After extraction, dates and amounts are normalized locally and anything suspicious — a future date, a missing amount, an unusually large total — is flagged for a human look rather than passed through quietly.

How to use Receipt ledger

  1. Add your provider API key in the key panel (vision-capable model recommended).
  2. Drop up to 30 receipt photos. Exact duplicates are blocked locally before any model call.
  3. Review the ledger: adjust any category, check the flagged rows, then export.
  4. Export as CSV in a reimbursement-ready layout.

Keep the original files and inspect the exported result before publishing or sharing it.

Frequently asked questions

How are duplicates detected?

Each photo is hashed in your browser before upload to the model; the same photo twice in one batch is skipped and listed.

What gets flagged?

Unparseable dates, dates in the future, missing amounts and unusually large amounts are flagged for a human look. Nothing is hidden.

Can I change a category?

Yes — every row has a category dropdown. The export uses the categories as you leave them.

Where do my receipts go?

Each photo is sent only to the AI provider behind your own key, directly from your browser.

Related tools