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
Prepare masked payment rows
Use vendor code, payment ref, current amount, prior comparable amount and verified approval status. No bank details.
Privacy Remove personal names where not needed, phone numbers, email IDs, personal records and bank details. Use role, employee code or aggregate business facts.
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.
What is that?
A Project is a folder in ChatGPT that keeps your instructions and files for every chat inside it. It's on the free plan too. Checked 14 Nov 2026.
What is that?
A Project in Claude is a workspace with its own instructions and files that every chat inside it uses. Checked 14 Nov 2026.
What is that?
A Gem is a custom Gemini that loads your instructions before every chat. Free on every plan; you create it on a computer. Checked 14 Nov 2026.
What is that?
Signed in with a work account, Microsoft's Copilot Chat applies enterprise data protection: your prompts aren't used to train its models. Checked 14 Nov 2026.
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.
Keep actual business records in your own workbook; ask AI for the method using column headings and rules only.
Excel A:F ref, vendor code, current amount, prior comparable amount, new vendor, approved status. Rule [Review rule]. Give formulas for prior comparison if positive, review flag for new vendor, amount increase or pending approval, sum all payments and flagged amount once per row. No payment approval or bank details. Tell me exactly where to paste formulas or set up the local steps. Use fictional examples only; do not ask for actual company records. Hold every duplicate ref and missing/nonpositive amount, distinguish source totals from unique ready-for-review totals.
Run locally, verify every result against source records, and have the responsible person or professional approve before acting.
- P250% rise. ₹15,000 vs ₹10,000.
- P3New vendor. ₹10,000; verify locally.
- P4Approval pending. ₹10,000 held.
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.
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?
If your whole team does this, we'll set it up for all of them in one session.