The 16th Is Always a Problem
Promotions, new hires, and resignations rarely fall neatly on the 1st of the month.
A new hire starts on the 10th. A senior staff member resigns on the 22nd. A team lead’s promotion takes effect on the 16th. Every one of these creates a partial-month salary calculation that has to be done correctly the first time, because the employee will check the figure, the statutory contributions will be filed on it, and any error compounds into the next cycle.
In most Malaysian SMEs, this calculation is still done by hand. And it is the single most error-prone task in the payroll month.
Why Proration Is Harder Than It Looks
Proration sounds straightforward. Take the monthly salary, divide by working days, multiply by days worked. The problem is that none of those numbers are as fixed as they appear.
The denominator is a choice. Different companies use different methods to determine how a month is divided, and using the wrong one throws off the entire calculation.
The numerator is also a choice. For a new hire who started on the 10th, which days count? For a resigning employee, does their last day count as a full day or a partial day? For a mid-month promotion, is the 16th paid at the old rate or the new rate?
Then there are the statutory contributions. EPF, SOCSO, EIS, and PCB are all calculated on the gross salary for the month. When that gross is a blended figure, part old rate and part new rate, or part full month and part partial month, the statutory amounts also have to be recalculated correctly. A single error in the proration cascades into incorrect EPF deductions, incorrect SOCSO categories, and incorrect PCB withholding for that month.
This is why partial-month calculations consume more HR time than full-month payroll for the affected employees, and why disputes about mid-month changes are some of the hardest to resolve.
What Manual Proration Costs
When proration is done in Excel, every mid-month change is a fresh calculation from scratch.
The HR admin opens the employee’s record, checks the effective date, looks up the relevant rate, decides which denominator applies, calculates the partial salary, recalculates the statutory contributions on the new gross, and then keys the result into the payroll software. For each affected employee. Every month.
The errors that follow are predictable. A resigning employee disputes their final payslip because the prorated salary used the wrong denominator. A new hire’s EPF contribution is calculated on the full month instead of the partial period, and the discrepancy only surfaces when KWSP processes the submission. A promotion that took effect on the 16th was calculated entirely at the new rate, and the employee was overpaid by half a month before anyone noticed.
None of these are formula errors in the sense that the math was wrong. They are configuration errors that happen because the calculation lives in a spreadsheet that someone has to remember to update correctly every time.
When Proration Is a System Configuration
The fix is to stop treating proration as a manual calculation and start treating it as a payroll rule.
Inside TimeTec Payroll, proration is handled through pre-configured templates. The proration method is set once, and the system applies it consistently every cycle. For new hires, the system reads the joined date from the employee profile and prorates the salary automatically based on the configured method. For resigning employees, the HR admin sets the resignation date in the system, and the payroll prorates the salary up to that date. Statutory contributions, EPF, SOCSO, EIS, and PCB, are recalculated on the correct prorated gross for the period rather than a manually adjusted figure.
For mid-month salary changes such as promotions or revisions, the process works the same way. The HR admin records the salary adjustment with an effective date. The next payroll run automatically prorates the cycle between the old rate and the new rate based on that date. No manual splitting. No separate Excel calculation.
The result is consistency. The same employee scenario produces the same calculation every month, regardless of who is processing payroll, regardless of whether the regular admin is on leave, and regardless of how many partial-month employees the cycle includes.
Stop Recalculating Every Month
Proration is not a once-a-year exception. In any company with regular hiring, occasional promotions, and normal turnover, every payroll cycle has at least one partial-month calculation. In a hundred-person company, it is several.
Treating these as manual exceptions every month is what creates the dispute backlog. Treating them as payroll rules is what eliminates it.
The cleanest payroll cycle is the one where the system already knows what to do with the 10th, the 16th, and the 22nd.