CPF Reconciliation for Singapore SMEs: Fix the Additional Wage Ceiling Before December Bonuses

If your company pays bonuses in December, run your CPF reconciliation in November, before the final payroll run of the year — not in February while you are preparing IR8A. The reason is mechanical rather than clerical: the Additional Wage (AW) ceiling is calculated on the whole year's Ordinary Wages, so the year-end bonus is the single payment most likely to breach it. An error caught in November is a line adjustment in the December payroll. The same error caught in February is a refund application or a late-payment penalty, and if IR8A has already gone out, an amended submission as well.

What is actually being reconciled at year-end?

Most SMEs think of CPF reconciliation as one check. It is really four ledgers that should agree and frequently do not:

• What payroll computed — the contribution the payroll system calculated each month.
• What was actually submitted and paid — the CPF EZPay records, which can differ after a mid-month correction, a re-run, or a manual off-cycle payment.
• What the accounts show — the CPF payable and CPF expense balances in your GL.
• What will appear on IR8A — the wage figures that flow into the AIS submission due by 1 March.

A variance between any two of these is normal during the year. A variance that survives into January is the one that costs money, because by then it has been baked into a statutory filing.

Why does the Additional Wage ceiling cause most of the errors?

Ordinary Wages are capped monthly. The OW ceiling rose to $8,000 a month from 1 January 2026, the final step of the announced increases. Additional Wages — bonuses, commission paid other than monthly, ex-gratia payments — are capped annually instead, and the formula is subtractive:

AW ceiling = $102,000 − total Ordinary Wages subject to CPF for the year.

That subtraction is where the trouble starts. An employee earning $8,000 or more every month has $96,000 of OW subject to CPF, leaving an AW ceiling of only $6,000. A $20,000 bonus attracts CPF on $6,000 of it and nothing on the rest. Most payroll systems handle this correctly if the year's OW figures behaved predictably. The failures happen when they did not:

• a mid-year salary increase that moved someone above or below the OW ceiling
• unpaid leave or no-pay months that reduced total OW and therefore raised the AW ceiling
• a leaver, where the AW ceiling has to be recomputed at cessation rather than projected to December
• an employee who crossed an age band (55, 60 or 65) mid-year, changing contribution rates part-way through
• a Singapore PR in their first or second year, on graduated rates, where the anniversary falls mid-year
• the annual January rate revisions for senior workers, which several years of Budget announcements have phased in

Rates and ceilings change often enough that you should confirm the current figures against the CPF Board's own tables rather than against last year's spreadsheet. That verification step is itself a reconciliation item.

When exactly should the reconciliation run?

The useful window is narrow and it is open now:

• Late October — freeze and extract year-to-date OW and AW per employee. Project each person's December position.
• Early November — investigate exceptions and decide corrections while there is still a payroll cycle left to carry them.
• December payroll — apply corrections in the same calendar year, so the adjustment lands in the year it belongs to.
• January — final AW true-up once actual bonus amounts are known.
• By 1 March — IR8A and AIS submission, using figures that have already been checked twice.

Working the other way round — filing first and reconciling when something bounces — is how SMEs end up amending submissions in April.

What can be automated, and what still needs a person?

The reconciliation is a good automation candidate because it is repetitive, rule-based and entirely numeric. What can be automated:

• a monthly three-way variance report across payroll, CPF EZPay and the GL, flagging any employee whose three figures disagree by more than a cent
• a rolling AW ceiling projection per employee, updated every payroll run rather than calculated once in December
• automatic flags for age-band crossings and PR anniversaries in the coming quarter
• an exception list for anyone whose OW changed by more than a set percentage during the year

What still needs judgement is classification: whether a given payment is an Ordinary Wage or an Additional Wage. An allowance paid monthly and wholly for that month is OW; the same amount paid quarterly is AW. Director's fees, ex-gratia payments and retention bonuses all need a decision, not a formula. Automate the arithmetic and the flagging; keep a human on the roughly five percent of payments where the classification is genuinely a call.

How much does it cost to find the error late?

The two failure directions are not symmetrical. An underpayment is settled by paying the shortfall plus late-payment interest, charged monthly from the due date — the cost scales with how long the error sat undetected, which is the whole argument for checking in November rather than March. An overpayment is worse operationally: it requires an error-in-contribution refund application, the employee's share has to be returned to the employee, the refund takes weeks to process, and any IR8A already filed on the wrong figures has to be amended. Neither is catastrophic. Both are avoidable, and both consume finance time in the exact weeks when finance has none to spare.

What does a finished reconciliation look like?

You are done when you can produce, for every employee on the payroll in 2026: total OW subject to CPF, the resulting AW ceiling, total AW paid, the CPF actually contributed, and the difference between that figure and what CPF EZPay recorded — with every non-zero difference explained in writing. If that file exists in November, the IR8A season in February becomes a submission task rather than an investigation.

Frequently asked questions

Is the year-end bonus subject to CPF?
Yes, as an Additional Wage, but only up to the AW ceiling — $102,000 less the total Ordinary Wages already subject to CPF for that year. For higher earners the ceiling is often largely used up by November, so only part of the bonus attracts CPF. Calculate the remaining headroom per employee before the bonus is approved, not after it is paid.

Do we still need to reconcile if a payroll vendor handles everything?
Yes. The vendor computes; the employer remains liable for the contribution and for what appears on IR8A. Vendor systems are generally correct on steady-state salaries and less reliable on mid-year changes, leavers and age-band crossings — which is precisely what the reconciliation is looking for. Ask your vendor for the YTD OW/AW extract; if they cannot produce it on request, that is a finding in itself.

Can CPF reconciliation be fully automated?
The variance checking, ceiling projection and exception flagging can be automated completely and should run monthly rather than annually. Payment classification and the treatment of irregular items still need review. In practice a well-built check turns a two-day December scramble into a twenty-minute monthly review of a short exception list.

Verify current CPF contribution rates, wage ceilings and submission deadlines against CPF Board and IRAS publications before acting; this article describes process, not tax or legal advice.