A call that sounds like the director: what accounting should do
A voice can be built from a recording on the site and from a conference. Confirming a payment by the voice on the line is a weak rule.
The director is "on the line", in a hurry, asking to pay an invoice or to read out an SMS code. The voice matches. The background matches. This is no longer a rare story from the news about large companies. A short clip from your site or a talk is enough for a phrase to sound familiar. An employee who "did not fall for it" may fall for it next time if the rule depends on recognizing a voice.
A rule that survives a good voice is not about tone. Money and codes are not confirmed on the same call. You call back a number that was in the contract or on the internal list before this conversation. An SMS code is not read out to anyone, including a person who introduced themselves as management. If the call pushes urgency, that is a reason to stop, not to speed up.
What to prepare before the call happens
- A list of two people who may start an unusual payment. Not the whole office.
- Callback numbers are written down in advance, not "find it in the letter".
- The site does not keep a long video of the director next to the bank details if you can do without it.
- After a suspicious call there is someone to write to, and a false alarm is not shamed.
Lexora does not promise "deepfake detection". That is a poor service for a small company. We close what usually breaks after the call: the mail the tone of the thread was taken from, and the site where the details and the video sit. If a code was already read out or a payment left, we start with incident response, not with a memo. A memo makes sense afterwards, when the payments have been stopped.
Related Lexora services
Did someone ask to read out a code?
Do not call back the number from that same call. Write to us and use the number you had before.