Switching payroll providers is a data migration, not a subscription swap

Nothing about your legal identity changes when you switch payroll providers. Your CPF Submission Number stays yours, your Auto-Inclusion Scheme registration stays yours, and CPF Board and IRAS will still come to you, not the vendor, if something goes wrong. What actually moves in a switch is data: year-to-date contributions, gross wages, leave balances, and the employment records you are required to keep. Get that transfer wrong and the new provider starts its first cycle from bad numbers, which is a worse problem than a slow handover.

This is a narrower question than how to choose the provider you are switching to; that decision is presumably behind you. It is also a different problem from setting up payroll for a first employee, which starts from zero. A switch starts from a live, running payroll with a full year of history attached to it, and that history is what needs careful handling.

What stays with your entity, regardless of provider?

Three things do not move, because they were never the provider’s to hold.

The CPF Submission Number. CPF Board’s own description is direct: the CSN is tied to your entity’s Unique Entity Number, not to the people or systems that operate it day to day. A new provider does not apply for a new CSN on your behalf; it works within the one your entity already has. The scenario that does require a new CSN is different: employees moving to an entirely new legal entity, a new UEN, not a change of vendor for the same company.

AIS registration. The Auto-Inclusion Scheme is registered by the employer through the myTax Portal, and that registration is yours, not the provider’s. A new provider files under your existing registration. You do not reregister because you changed who does the filing.

The statutory liability. CPF Board and IRAS hold the employer responsible for accurate, on-time contributions and filings, full stop. That does not shift during a transition, and it does not shift because an outgoing provider was slow to hand something over. Whatever goes wrong during a switch, the regulator’s letter still has your entity’s name on it.

What actually has to transfer?

This is the part that takes planning, because none of it is automatic.

• Year-to-date CPF contributions per employee. The new provider needs accurate figures for what has already been contributed this year to calculate the remainder of the year correctly. Handing over a clean, employee-by-employee schedule matters more than handing over a summary total.
• Year-to-date gross wages. Same logic: a new provider working from incomplete wage history is working from a guess, not a record.
• Leave balances. Annual leave and sick leave entitlements taken and remaining, as at the handover date, for every employee. This is an HR record, not a CPF record, and it is easy to overlook in a transition that is framed as a “payroll” switch.
• Employment records. Key Employment Terms already issued, itemised payslips already generated this year, and anything else MOM expects you to be able to produce. MOM’s retention rule for current employees is the latest two years, and one further year after an employee leaves. That clock does not reset because you changed vendors; the records from the outgoing provider’s period still count towards it.
• Bank and disbursement details. GIRO arrangements and payment particulars used to actually pay salaries need to move cleanly, or the first payday under the new provider is the day you find out something did not transfer.

None of this is exotic. It is the same information any provider needs to run payroll correctly. The difference in a switch is that it already exists somewhere else, held by an outgoing party who has less incentive to make the handover smooth than the incoming one does.

Why does a mid-year switch complicate the IR8A?

You do not file two IR8A forms because you changed providers mid-year. Your entity files one IR8A per employee for the calendar year, because your entity, the employer, has not changed. The rule that each employer reports only for the period an employee was under its employment matters when an employee moves between two different companies, two different UENs, during the year. A vendor switch is not that: it is the same employer, the same UEN, throughout.

What does change is where the numbers behind that single filing live. Instead of one system holding the full year’s figures, you now have January through the switch date sitting in the outgoing provider’s records, and the switch date through December sitting in the new one’s. Assembling one accurate IR8A means reconciling both, which is exactly why the year-to-date handover described above is not a formality. A provider that starts its half of the year from an estimate, rather than the outgoing provider’s actual figures, hands you a filing built on a guess for at least part of the year.

No CPF Board or IRAS page sets out specific guidance for mid-year vendor changes, transferring year-to-date figures, or the mechanics of a handover between two payroll providers. That is a genuine gap in what the regulators publish, not an oversight in this article. The position above is built from what each rule says on its own terms, IR8A’s per-employer scope and the standing filing obligation, not lifted from a guide that does not exist.

Where does a parallel run earn its cost?

A parallel run means both providers calculate the same payroll cycle, side by side, before you commit to the new one alone. It costs a month of double effort and, usually, nothing else, since most providers will run one comparison cycle as part of onboarding.

It earns that cost in exactly the situation a switch creates: two systems, two sets of assumptions about wage components, allowances, or CPF-eligible items, and one chance to catch a mismatch before it reaches CPF Board rather than after. Run it against a normal month, not a bonus month or a month with unusual leave activity, so a genuine discrepancy is not buried under noise from something else. If the comparison cycle lands before an AIS filing deadline, that is deliberate, not a coincidence to avoid.

Where it does not earn its cost: a very small headcount with simple, uniform pay structures, where reconciling two providers’ outputs by hand takes about as long as just checking one provider’s numbers carefully. Use judgment on scale, not a blanket rule.

A short migration sequence

Run this roughly in order, adjusting for your own notice periods and provider timelines:

1. Set an effective date that does not sit inside a CPF due-date window or an AIS filing period, if you have the choice.
2. Request the full handover data set from the outgoing provider in writing: year-to-date CPF and wages per employee, leave balances, KETS and payslips issued, bank particulars. Ask for a usable export, not a locked report.
3. Load and check that data with the new provider before the first live cycle, not during it.
4. Run one parallel cycle, comparing both providers’ output for the same period, and resolve any mismatch before relying on the new provider alone.
5. Confirm access changes: end the outgoing provider’s operational access to your systems and data once the handover is verified complete, and set up whatever access the new provider genuinely needs.
6. File the year’s single IR8A from reconciled full-year figures, not from whichever provider happens to hold the more recent data.
7. Retain both providers’ records for as long as MOM and IRAS require, on the entity’s own systems if either provider’s access will end. Remember these are two different clocks: IRAS’s five-year rule for corporate income tax records, and MOM’s rule for employment records specifically, the latest two years for current employees and one further year after they leave. Meeting one does not satisfy the other.

The honest limit

There is no official checklist for this, from CPF Board, IRAS, or MOM. Employers doing this for the first time are, in effect, applying general rules to a specific situation the regulators have not written a guide for. That is not a reason to skip the mechanics above; it is a reason to be more careful with the handover than a published playbook would require, because there is no fallback document to check your work against.

If your own switch is more complicated than this, multiple entities, a mix of local and foreign employees, or a provider that is not cooperating with the handover, that is a conversation worth having before the effective date, not after. We run payroll processing for employers who would rather a transition like this was planned in writing than reconstructed from memory once something has already gone missing.