PROMPT BRO
Purchase desk

Goods receipt rows with shortages flagged

Challan says ten boxes. The truck has eight.

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

By hand1 hr
With AI15 min
Per day · estimate
Easier on your office computer.Send to my computer
I usePick yours. We'll show the right steps.

Prepare receiving details

Use PO line, item, ordered quantity, actual received and condition. Count actual goods; do not copy ordered quantity as receipt. Supply unique GRN/PO line refs, SKU/unit and inspection-confirmed accepted, rejected and pending quantities; do not let AI decide acceptance.

First time? Try it on fake data first:

Privacy Remove bank account numbers, PAN, personal phone numbers and emails. Use vendor business names or codes, item codes and approved commercial details.

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

Whenever I send the next details, use this format. Receipt date: [Receipt date] Receipt rule: [Receipt rule] I'm attaching receipts.xlsx. A. Draft one row per unique receipt/PO line with SKU, unit, ordered, physically received, inspection-approved accepted, rejected and pending inspection quantities. Use only supplied inspection results; never assume received equals accepted. Validate nonnegative numeric values and accepted + rejected + pending = received; hold missing/conflicting or duplicate refs and excess/shortage. Show ordered minus received separately from accepted quantity. B. Count exact undamaged, shortage, excess and damage; list exceptions. C. Internal questions for stores/purchase. Provide a copyable handoff with PO line, GRN ref, SKU/unit, received, inspection-approved accepted, rejected, pending and evidence/status. No posting, acceptance decision or automatic bill approval. Use only supplied facts, quotes and approved terms. Flag missing GST, freight, payment days or delivery instead of assuming. Check stock against physical count or software before ordering. A person checks before sending, ordering, paying or posting.

Set it up once. Save the approved format and comparison rules, without vendor records. Pick your tool at the top to see how.

After that, each time: send the new details and confirm the latest approvals and stock.

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)
2pass checks
3held lines
5PO lines
  • L22 short. 10 ordered, 8 received.
  • L32 excess. 10 ordered, 12 received.
  • L4Damaged. Condition flag even though qty matches.
Before you trust it

Then send this: Recheck unique refs, ordered/received difference, accepted + rejected + pending = received, inspection evidence and all condition flags. Never substitute received for accepted.

If it goes wrong
Uses ordered as received

Reply: "Use actual count only."

Ignores damage

Reply: "Flag condition separately."

Posts GRN

Reply: "Draft only."

Sir ne bola urgent. Ab bolo: ho gaya.

Did it work?