{"id":"acct-bank-change-request-checklist","audience":"accounting","category":"finance-work","track":"finance","technique":"verification","level":"beginner","title":"Build a verification checklist for a vendor bank-change request","free":false,"task":"A vendor emailed new bank details and asked you to use them for the next payment. Write a prompt for a checklist of exactly 5 lines, each starting \"- [ ]\", from the policy and the email. End with a sixth line starting \"Status:\" that says HOLD. Plain text, under 110 words. Don't tell anyone to ignore or report the email as fraud; the checklist only verifies.","materialLabel":"Vendor email and AP policy (attached to your prompt automatically)","material":"EMAIL received Nov 5, from accounts@brightline-freight-billing.example\nSubject: Updated banking details - urgent\n\"Hello, our bank has changed. Please send the Nov 12 payment of $14,820.00 to the new account below. Routing 021000021, account 88100422. Please confirm by return email. Thanks, Mara Collins, Accounts Receivable\"\n\nAP POLICY EXCERPT (rev. Aug 2026)\n- Changes to vendor bank details require a signed change form from the vendor.\n- Call the vendor back at the phone number in the vendor master (not a number in the email) and speak to a contact already on file.\n- A second AP team member must review the change before it is saved.\n- Do not release payment to changed details until the callback is logged.\n\nVendor master: Brightline Freight, contact on file Mara Collins, AR, phone 555-0134, email domain brightlinefreight.example. The sender's domain in this email is different from the one on file.\nPayment of $14,820.00 is scheduled for the Thursday Nov 12 run.","rules":[{"type":"plainText"},{"type":"maxWords","max":110},{"type":"maxBullets","max":5}],"promptHints":[{"label":"Gives the checklist shape","patterns":["- \\[ \\]","exactly 5"]},{"label":"Covers callback and form","patterns":["callback","signed","change form"]},{"label":"Mentions the domain","patterns":["domain"]},{"label":"Ends with status","patterns":["status: hold","status"]},{"label":"Bans fraud conclusion","patterns":["(do not|don'?t).*(fraud|ignore)"]}],"mistakes":[{"title":"Calling the number in the email","why":"The AI suggests replying to the email or calling the number it lists.","fix":"Say: \"Callback uses the number in the vendor master, not the email.\"","checks":["r0"]},{"title":"Missing the domain mismatch","why":"The AI doesn't notice the sender's domain differs.","fix":"Add: \"Note that the sender's email domain differs from the domain on file.\"","checks":["r1"]},{"title":"Declaring fraud","why":"The AI says this is a scam and tells staff to delete it.","fix":"Add: \"The checklist only verifies. Don't call it fraud.\"","checks":["r2"]},{"title":"Markdown extras","why":"The AI adds bold labels, headings and a closing note.","fix":"Say: \"Plain text, no bold. Output only the lines asked for.\"","checks":["plainText","maxBullets"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting and runs past word limits.","fix":"Ask for fewer words than the real cap and keep each line short.","checks":["maxWords"]}],"hint":"The policy has verification steps and the email has a red flag. Ask for the five steps, the domain note and a HOLD status.","rubricLabels":["Has five checklist lines starting \"- [ ]\" covering the signed change form, a callback to the phone number in the vendor master (555-0134, not from the email), second-person review, and logging the callback before releasing payment","Notes that the sender's email domain differs from the one on file","Ends with a line starting \"Status:\" that says HOLD and doesn't tell anyone to ignore the email or declare it fraud"]}