Library › Cybersecurity AI › Finance and accounting
Find vendor bank changes that skipped the process
- For Finance and accounting
- You practice Setting limits and rules
- Time about 5 minutes
About this exercise
Review this month's vendor bank detail changes. Your process requires a call-back recorded to a number already on file and a second approver who is not the person who entered the change. List only the changes that break the process, numbered, as 'change ID - vendor - what's missing'. Plain text, under 70 words.
Common mistakes when you ask AI for this
- Not giving the process. The AI only catches the missing call-back and misses the self-approval. Try: Spell it out: "Call-back to a number on file, and a second approver who didn't enter it."
- Trusting the 'yes'. The AI sees 'Call-back recorded: Yes' and passes VC-33, even though the number came from the email. Try: Add: "A call-back only counts if the number was already on file."
- Reviewing every row. The AI comments on all 6 changes. Try: Say: "List only changes that break the process."
- Trusting the AI to count words. AI is bad at counting. Ask for "under 70 words" and it often lands well over. Try: Ask for less than the limit and cap each line: "each line under 15 words, under 50 words total."
- Letting markdown in. AI adds bold and headings by default, and in the audit file they show up as stray symbols. Try: Add: "Plain text only, no bold, no headings."
What a strong prompt includes
- Gives the process
- Lists only exceptions
- Shows the line shape
- Sets a word limit
- Asks for plain text
Related exercises
- Accept the buyer's counteroffer on three stated conditions (Sales AI · Sales and customer success)
- Accrue goods received but not invoiced at PO price (Finance AI · Accountants)
- Add dark mode by overriding your existing CSS variables (Coding AI · Software developers)
- Add input checks to your number guessing game (Coding AI · High school students)
- Add labels to a signup form without rewriting the page (Coding AI · High school students)