PROMPT BRO
Accounts desk

Check expense claims before reimbursement

A ₹40 chai bill with a ₹400 'misc' next to it

Tested Claude Opus 5.5, medium effort · 15 Nov 2026 · on the practice files

By hand2–3 hrs
With AI30 min
Per week · estimate
Easier on your office computer.Send to my computer
I usePick yours. We'll show the right steps.

Make a claim working sheet

Use claim ref, employee code, category, amount, bill present and manager approval. Keep the actual bills locally.

First time? Try it on fake data first:

Confirm the policy

Copy approved limits and bill/approval requirements. Use the sample to practise.

Privacy Use employee codes and claim facts; remove names, personal addresses, payment details and medical bills. Delete bank account numbers; replace customer UPI IDs and phone numbers.

Fill the orange boxes
You send (the "prompt": the message you paste into your AI tool)
claims.xlsx

Whenever I send a claim list for [Claim period], check it. Limits: [Approved per-claim limits]. Rules: [Other approved rules]. A. Table of every claim, amount, category, supplied limit and checks; hold if over limit, bill missing, approval missing or category unclear. B. List passing and held claims with reasons; sum both and total. Do not reduce or reject claims automatically. C. Draft a short (up to 6 lines) request for missing information with [Employee name] and [Claim ref] placeholders. Use only my data. GST rates, HSN and TDS rates only from my supplied figures; never guess tax treatment. This is a first pass; a person checks and posts any final entries in Tally/Busy. Do not repeat personal identifiers from the data (personal names, phone numbers, email or postal addresses, bank account numbers, UPI IDs, PAN, Aadhaar, GSTIN or other registration numbers) unless the output genuinely needs one; use the code, ref or row instead, and copy any needed identifier exactly. Keep masked values masked; never guess, complete or unmask them. Line limits count body lines only, not subject, greeting or sign-off. Keep every required fact; if they do not fit, say so instead of dropping one.

Set it up once. Save approved policy and checking format, not real claim details. Pick your tool at the top to see how.

After that, each time: send the new masked claim list and current limits.

First time? Try it in a normal chat: paste and send.

Which model? Use your tool's strongest model with thinking turned on.

In your AI tool: attach the files with the + button, paste, send.

What you'll get back (example, from the practice files)
₹2,900claimed
₹1,200pass checks
3held claims
  • C2₹500 meals. Above ₹400 limit; hold.
  • C4Bill missing. ₹600 travel; ask for bill locally.
  • C5Approval missing. ₹600 travel; manager must confirm.
Before you trust it

Then send this: Check each claim against the limits, bill and approval, add all amounts again and reconcile passing + held to submitted total.

If it goes wrong
It caps a claim automatically

Reply: "Flag full claim, don't change amount."

It asks for actual bills

Use dummy data or the local claim list only.

It invents policy

Reply: "Only my limits and rules."

Sir ne bola urgent. Ab bolo: ho gaya.

Did it work?