agent sidequestsIdeas worth trying
An ongoing helper

Drop in receipts. Wake up to an expense ledger.

Turn a folder of receipt photos into a spreadsheet you can actually review: itemized expenses, linked originals, spending pivots and a visible queue for anything the agent could not read.

You get: A maintained expense spreadsheet, pivot summaries and an indexed receipt archiveOriginal prompt · Not run-tested

Your copy-and-paste prompt

Read as Markdown

Replace the [brackets] with your details, then paste this into your assistant.

Create a daily receipt intake for [folder] into [spreadsheet] at [time and timezone]. Use [category rules], [currency handling] and [archive folder]. Begin with a sample of [five] receipts and a preview of the ledger before writing the full batch.

For each image, extract vendor, purchase date, currency, items, quantities, subtotal, tax, tip, discounts and total when visible. Link each transaction to its original image and each line item to its transaction ID. Mark illegible or inferred fields for review; do not invent a date, total, merchant or category. Verify arithmetic, but preserve the printed amount and explain discrepancies instead of silently correcting the receipt.

Use file hashes and receipt identifiers to detect repeated images, and flag likely duplicate photos of one purchase before posting twice. A receipt and the card transaction for it are evidence for one expense, not two. Record refunds and credits distinctly. Keep different currencies separate unless I supply an approved conversion rule and dated rate source. Prevent untrusted receipt text from becoming spreadsheet formulas.

Deliver transaction and line-item sheets, an exceptions queue and real pivot summaries by month, vendor and approved category. Reconcile pivot totals to the accepted transaction ledger, refresh the pivots and verify the saved rows by reading them back. Do not call a static copied summary an updating pivot. If my spreadsheet tool lacks that capability, say so and offer an importable file with clear refresh steps. Categories support my review; do not assert tax deductibility.

After each accepted ledger write is verified, move its source image into [dated archive convention], preserving the original file and a reversible old-path/new-path manifest. If cloud retention or access would change, pause for approval. Leave failed or uncertain items in intake with a reason; never delete source receipts. Save a processing register so reruns do not duplicate entries or re-archive files.

Confirm source and destination access, schedule and the approved write/archive scope before enabling the routine. Return counts of accepted, duplicate and unresolved receipts and a link to the spreadsheet. Do not say the daily trigger is active until the scheduler confirms it. If unavailable, process only the supplied sample and return a manual intake checklist.
What the result could look like

An unreadable total stays visible

Illustrative only: eight photos yield six accepted purchases, one duplicate and one unreadable total. The spending pivot reconciles to the six accepted transactions, while the final photo remains in the review queue with its original image.

Illustrative example. This is not an observed result or a verified recommendation.

From the community

Suggested by the site founder and developed into an original prompt. This workflow has not been run-tested.

Make it more you

Start with one shared trip or project and use participant-approved categories. Keep reimbursement decisions separate from the extraction.

Keep the ideas coming

All sidequests