expense-capture

The most expensive failure in expense entry is not speed, it is invention. A misread total, a guessed merchant name, a tax amount reverse-engineered from a subtotal — none are obvious on a single receipt, but they compound into reconciliation headaches at month-end and credibility problems during an audit. expense-capture bakes a hard discipline into the workflow: transcribe exactly what is visible, flag what is not, and never let a field land without a traceable source on the image.

The plugin enforces rules across six core fields: dates keep their original printed format, merchant names preserve their abbreviations, amounts carry their currency symbol, tax is recorded only when the receipt explicitly separates it, and categories are drawn from the ledgers own list rather than improvised. Recording is not a one-shot action but a batch loop: transcribe each receipt with inline flags, reconcile row count and amount totals against the source images, re-verify flagged fields against the image once more before submission, and write to the ledger only after explicit user approval, reporting failures rather than blindly retrying.

It suits finance and operations teams that process a batch of paper or screenshot receipts daily and need every ledger row to point back to its source image during audits. One honest caveat: image quality remains the bottleneck, and illegible receipts stay flagged for human review. Tax rules vary by jurisdiction, so the plugin reads only what is printed and never computes what should be there — tax judgment remains with the accountant.