How To Prevent Payroll Fraud? - Krowme

Krowme

How To Prevent Payroll Fraud?

You may have come across this Straits Times article: Former HR exec jailed 4 years for cheating firm of S$454,000 using ex-employees’ payroll details, where a HR executive, tasked with maintaining her employer’s payroll system, exploited a loophole where she discovered that workers’ data would still remain in the system even after they have resigned. She transferred almost S$500,000 to her own bank accounts over a span of one-and-a-half years.

Based on what’s mentioned in this article, we could identify some issues with the company’s HR and Payroll processes that could have prevented the crime committed by the HR executive.

Issues that led to the Payroll Fraud and how these incident could have been prevented

Article Snippet #1

“She had joined the firm in April 2018 and her duties included handling the payrolls of employees and construction workers and being solely responsible for maintaining the company payroll system, which was linked to the firm’s account with United Overseas Bank.

For the employees’ payroll, Fu was involved in recording salaries and transferring money from them back to the company for certain expenditures that were not covered by the company.

The finance department would tell Fu about the amounts to be clawed back from staff members.”

From the above snippet,

It seems that the employees are using the company credit card to make various payments, after which, the HR personnel will need to do a check to see which expenses should be covered by the company. She will need to then reach out to the employees to claw back the expenditure.

This leads to time wasted and high chances for human error and loopholes, eg. the HR personnel could have gotten the expenditure back but failed to report this and kept the money for herself instead.

To prevent such issues from happening, instead of employees using the company credit card (after which a HR personnel needs to double check to ensure that expenses are valid and then chase employees to return the cash), we recommend that employees always make payment first through a Claims platform, and then submit claims for the payments made.

This ensures that all claims are being tracked in a system and all the HR personnel needs to do is check that all the claims are valid and only do payroll for claims that are valid.

Article Snippet #2

As for the construction workers’ payroll, she was involved in salary payments to those from Formwork’s subcontractor, Yong Tai Construction, whenever Formwork needed extra manpower.

Formwork did not pay these workers directly but would issue a cheque to Yong Tai for their salaries. Fu soon realized that the names and addresses of some employees remained in the system even after they had resigned.

She then modified these employees’ payrolls, such as by keying in certain amounts to be transferred to them. She also keyed in money to be transferred to Yong Tai’s workers for their salaries, even though Formwork would issue a separate cheque for the salaries.”

From the above snippet we gather that,

  1. The Formwork HR Personnel reduced the payment amount to be sent to Yong Tai Construction’s employees.
  2. The Formwork HR Personnel banked the remaining money (money from cheques minus money paid to Yong Tai Construction’s workers) to herself by updating the bank details of employees who have resigned with her own bank details.
  3. There seems to be a gap in the process where it does not seem like the Formwork Finance Department had a track record of the amount that Ms Fu managed to get back, or the payroll that Ms Fu was handling, as according to the article, Ms Fu was only found out when another HR personnel took over her when she was away on holiday.

How Could This Crime Be Prevented?

In today’s day and age with higher standards of living, we should not simply just rely on an individual that we trust based on gut feeling to handle Payroll Matters manually. 

It also takes a lot of work to manually ensure that employee data is always up to date as the HR personnel will need to take note of:

  1. All the no pay leaves (or worse, the no pay time off which is calculated in hours instead of days)
  2. Overdue claims
  3. Ensuring that resigned staff are removed from the system.

All of the above points can add up and may lead to loopholes in the system. Handling payroll matters manually also increases the risks of human error. We should take all precautions to ensure utmost security when it comes to Payroll. Also, why put in all the time and effort when an automated software can easily take that load off you, so you can focus on more important stuff you have on hand.

To sum it up, Payroll is extremely sensitive and it is important to implement the best practises when it comes to your Payroll.

How does using a well-designed HRMS/Payroll Software help prevent unwanted issues like leaking of information, human errors in money management or money theft from occurring?

1. Security is held to the utmost standard

Make sure that the HR Software vendor prioritizes their security. Check whether if they have a team (preferably in-house) that does constant checks and upgrades to ensure that the system is kept secure. This prevents loopholes and hackers from accessing the system. Another way to check that the HR software is secure is to see if they have any security certifications.

2. Any updates on the HRMS can be automatically synced to the Payroll system

Whenever an employee has resigned, applies for leave, or has an approved claim: ALL updates can be linked & updated to the Payroll system. This greatly reduces any manual updates or any room for human error, which ensures a much cleaner and streamlined process where the employee data is always up to date.

I hope that this article helps you understand why it is important in this day and age to have a good HRMS and Payroll System in place.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>