PROMPT BRO
Owners desk

Payment approval list with unusual items flagged

Signing 60 payments at 6:55 pm because the bank cuts off at 7

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

By hand30–60 min
With AI5 min
Per week · estimate
Easier on your office computer.Send to my computer
I usePick yours. We'll show the right steps.

Prepare masked payment rows

Use vendor code, payment ref, current amount, prior comparable amount and verified approval status. No bank details.

First time? Try it on fake data first:

Privacy Remove personal names where not needed, phone numbers, email IDs, personal records and bank details. Use role, employee code or aggregate business facts.

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

Whenever I send the next details, use this format. Payment week: [Payment week] Review rule: [Review rule] I'm attaching payment-review.xlsx. A. Validate unique payment refs, vendor code, positive numeric current amount and supplied approval. Hold all duplicate refs, missing/invalid amounts or approvals; prior missing/zero is not a percentage denominator. Compare current/prior only when prior positive and flag supplied rule. Do not assume a new vendor's routing is verified. If an earlier step (bill match, GRN or dispute) holds a bill or line, hold that payment row too, even when its approval says Yes, and leave it out of the ready-for-review amount. B. Show total known listed amounts (explicitly including any duplicate source rows), flagged amount once per source row, and separate unique complete ready-for-review amount. List reasons and held duplicates; no duplicate is payable. Never net or delete rows silently. C. Questions for accounts and approval checklist; no payment, no approval. Use only supplied facts and numbers. Separate facts from suggestions and label suggestions clearly. No invented reasons, commitments or figures. A person checks before sending, paying or deciding.

Set it up once. Save the approved report format and decision rules, not private records. Pick your tool at the top to see how.

After that, each time: send the new approved facts and current rules; review before acting.

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)
₹55,000payment list
3flagged rows
₹35,000flagged value
  • P250% rise. ₹15,000 vs ₹10,000.
  • P3New vendor. ₹10,000; verify locally.
  • P4Approval pending. ₹10,000 held.
Before you trust it

Then send this: Re-add known listed and flagged amounts, unique ready-for-review total, verify positive amounts, duplicate refs, approvals and percent flags; no payment approval.

If it goes wrong
Approves payment

Reply: "Review only."

Invents vendor history

Reply: "Use supplied status."

Asks bank details

Reply: "Codes only."

Sir ne bola urgent. Ab bolo: ho gaya.

Did it work?