One theory of fraud suggests that fraudsters begin their slippery slope into crime with a “test.”3 That is, they put together a fraudulent transaction or event and “float” it out into the entity’s environment to see if they can get away with the fraud. If that first instance gets noticed, the fraudster usually has a predetermined “excuse” for why it happened, often the “oops, I made a mistake” defense. If it goes unnoticed, the fraudster usually proceeds to the third item in this list.
The IT auditor needs to be aware that if he/she finds an unexplained anomaly or variance, and goes to the party responsible, and that person says “oops,” there is some probability, no matter how small, that it is a “test” transaction. The IT auditor should exercise due diligence in obtaining independent verification where feasible and should obtain it before approaching the party responsible for the transaction, where feasible— especially where circumstances increase suspicion. For example, in one fraud case, the auditor came to the responsible party and asked why a certain account amount was exactly double what it should have been. The accounting clerk stuttered, having been surprised, and the auditor himself gave the person an opportunity to use the “oops” defense, as he said to her, “You must have accidentally double paid the vendor.” In reality, it was a fraud scheme and not an overpayment.
One theory of fraud suggests that fraudsters begin their slippery slope into crime with a “test.”3 That is, they put together a fraudulent transaction or event and “float” it out into the entity’s environment to see if they can get away with the fraud. If that first instance gets noticed, the fraudster usually has a predetermined “excuse” for why it happened, often the “oops, I made a mistake” defense. If it goes unnoticed, the fraudster usually proceeds to the third item in this list.
The IT auditor needs to be aware that if he/she finds an unexplained anomaly or variance, and goes to the party responsible, and that person says “oops,” there is some probability, no matter how small, that it is a “test” transaction. The IT auditor should exercise due diligence in obtaining independent verification where feasible and should obtain it before approaching the party responsible for the transaction, where feasible— especially where circumstances increase suspicion. For example, in one fraud case, the auditor came to the responsible party and asked why a certain account amount was exactly double what it should have been. The accounting clerk stuttered, having been surprised, and the auditor himself gave the person an opportunity to use the “oops” defense, as he said to her, “You must have accidentally double paid the vendor.” In reality, it was a fraud scheme and not an overpayment.
การแปล กรุณารอสักครู่..

One theory of fraud suggests that fraudsters begin their slippery slope into crime with a “test.”3 That is, they put together a fraudulent transaction or event and “float” it out into the entity’s environment to see if they can get away with the fraud. If that first instance gets noticed, the fraudster usually has a predetermined “excuse” for why it happened, often the “oops, I made a mistake” defense. If it goes unnoticed, the fraudster usually proceeds to the third item in this list.
The IT auditor needs to be aware that if he/she finds an unexplained anomaly or variance, and goes to the party responsible, and that person says “oops,” there is some probability, no matter how small, that it is a “test” transaction. The IT auditor should exercise due diligence in obtaining independent verification where feasible and should obtain it before approaching the party responsible for the transaction, where feasible— especially where circumstances increase suspicion. For example, in one fraud case, the auditor came to the responsible party and asked why a certain account amount was exactly double what it should have been. The accounting clerk stuttered, having been surprised, and the auditor himself gave the person an opportunity to use the “oops” defense, as he said to her, “You must have accidentally double paid the vendor.” In reality, it was a fraud scheme and not an overpayment.
การแปล กรุณารอสักครู่..
