Is Your Payroll and Leave Software Ready for 2027? The Vendor Questions to Ask in October

Almost certainly not, and the honest way to find out is to put the question to your software vendor in writing this month. A new set of employment cost rules takes effect on 1 January 2027, and in a small company the rules are rarely the problem. The problem is that the rules live inside software somebody else maintains, on a version you may not be on, with settings nobody in your office has opened since installation day. October is the month to ask. A vendor who has to patch an older version needs weeks of notice, and December is when every one of their customers asks at the same time.

What actually changes at the start of 2027?

Four separate things reach into payroll, leave and HR records more or less at once:

• CPF contribution rates step up again for older employees, principally those above 55 and up to 65. Both the employer share and the employee share move, and the way the money splits across the Ordinary, Special and MediSave accounts is set at the same time.
• Retirement and re-employment ages sit at 64 and 69. This is a contracts and HR records matter rather than a payroll calculation, but it drives age-based letters, renewal dates and anything in your system that triggers on a birthday.
• Wage floors move. Local Qualifying Salary and the Progressive Wage Model step-ups change the lowest legal pay for certain roles, and they change how many local staff count toward your foreign worker entitlement.
• Parental leave entitlements are mid-expansion. Shared leave and paternity provisions have been widening in stages, so leave balances, carry-forward rules and the policy wording staff actually read all need a look.

The precise figures are published by CPF Board and MOM. Your vendor should be quoting them back to you, with a date. If the vendor asks you for the numbers, that is your answer about how ready they are.

Why is the software the risk and not the rules?

Because the rules are free, public and short, while the software is none of those things. Across small Singapore companies the same three failure modes come up again and again.

You are on a version that no longer receives updates. This is common with payroll installed on one office PC years ago. The statutory table inside it is frozen. Nothing warns you.

The update arrives but a manual override beats it. Somebody once typed a fixed CPF amount or a fixed contribution rate into one employee's record to fix a one-off problem. That hard-coded value quietly outranks the new table for that person, and that person is usually a long-serving senior employee, which is exactly who the 2027 change affects.

Nobody owns the calculation. Payroll runs in a spreadsheet, or a part-time bookkeeper works it out by hand, and the knowledge is in one person's head.

These failures are quiet, which is what makes them expensive. CPF underpaid in January surfaces later as a shortfall plus late payment interest, and you pay it from cash you have already allocated elsewhere. CPF overpaid is your working capital sitting in somebody's retirement account for months. Underpaying a Progressive Wage floor is not a rounding error at all: it reaches your work pass renewals and your licence conditions.

Which questions should you send your vendor this month?

Send them in one email, ask for a written reply, and keep it. Five questions is enough.

1. Which version are we on, and is it still supported? A good answer names your version and confirms support in writing. A vague answer is the finding.
2. Will the 1 January 2027 statutory changes arrive automatically, and on what date? You want a release date in December, not a promise to look into it.
3. Does the update cost anything, and does it need our server or PC touched? Cloud payroll on a current subscription usually includes statutory updates. An unsupported on-premise install is the expensive case, and you would rather discover that in October than on 2 January.
4. Which employee records contain manual overrides on CPF, wages or leave? Ask for the list. Every name on it has to be reviewed by a human before the first 2027 payroll.
5. Does the system handle retirement and re-employment age triggers and the current parental leave rules, or do we track those outside it? Knowing which parts the software does not cover tells you what your own checklist has to carry.

What if payroll is a spreadsheet or an outsourced bookkeeper?

Then the questions are the same, pointed at a person instead of a product. Ask your bookkeeper to confirm in writing that they are aware of the 1 January 2027 changes, which of your employees are affected, and when they will update their template. If payroll is a spreadsheet you maintain yourself, the one change worth making now is to stop typing rates into cells and move them into a single clearly labelled settings area, so next year's change is one edit instead of a hunt. Outsourcing does not move the liability. CPF and MOM obligations rest with the employer, whoever presses the buttons.

How do you prove the change actually worked?

Do not test the whole payroll. Test four people: one employee above 55, one employee on a Progressive Wage role, one parent likely to take leave, and one ordinary case as a control. Run a trial payslip for each in December against January dates, check the CPF figure against the published table by hand, and save a copy. That is roughly an hour of work, and it is the only evidence you will have if a question arrives in March. Keep it with your payroll records, not in somebody's inbox.

What should the next ten weeks look like?

October: send the five questions, get written answers, and get the override list.

November: clear the overrides, update contract templates and the staff leave policy, and confirm the update release date.

December: apply the update, run the four trial payslips, and file the proof.

January: check the first real payroll against the trial before you approve it, and check the first CPF submission actually went through.

Done this way the cost is a few hours of attention spread over ten weeks. Left to January, the same work happens under deadline pressure, with a payroll already paid and a correction to unwind.

Frequently asked questions

Do we have to pay for a software update to stay compliant?

Usually not, if you are on a current subscription with a supported vendor, as statutory updates are normally part of what you already pay for. The cost appears when you are running an old installed version that is out of support, where the realistic options are a paid upgrade or a move to a maintained system. That decision is far cheaper to make in October than in the first week of January.

Our payroll is outsourced. Is this still our problem?

Yes. The employer carries the obligation for correct CPF contributions, correct wages and correct leave, regardless of who processes the payroll. A written confirmation from your provider that they are ready for 1 January 2027 does not transfer the liability, but it does tell you whether to worry, and it gives you something to point at if the figures come out wrong.

What if we discover in February that January was underpaid?

Fix it immediately and voluntarily. Shortfalls can be paid with the arrears plus late payment interest, and self-reporting an honest error is treated very differently from one found during an inspection. The practical lesson is that a single checked payslip in December is worth more than any amount of corrective work in February.