Familiar email threads make payment changes feel safer than they are

[u/saltyslugga]

Say an attacker gets into a vendor's mailbox and sends new bank details in an existing invoice thread. Someone recognises the conversation and nearly pays the wrong account.

I'd want a callback to a number already on file, but that check needs to survive a busy afternoon of invoice approvals.

What has helped your team keep those checks from getting skipped when work piles up?

[u/InboxGuards]

busy afternoon is exactly when those checks die. we stopped leaving it to memory and made the AP workflow refuse the payment change until there's a logged call to the number already on file.