1 January ERP Go-Live: When to Time an Accounting Cutover in Singapore (And When Not To)

1 January is the right go-live date for a new ERP or accounting system only if three things are true at once: your financial year ends 31 December, your GST accounting period ends on the same day, and you have the December manpower to run the old and new systems side by side. For most Singapore SMEs at least one of those is false. If so, the better answer is to cut over on 1 December with a one-month parallel run, or to wait for 1 April. A 1 January go-live signed off in late November is not a project — it is a bet placed in the one month when despatch is at its heaviest and half the office is on leave.

Why does 1 January look like the obvious cutover date?

Because it is clean on paper. Opening balances are the closing balances of a completed financial year. There are no part-year comparatives to reconcile, no half-migrated year-to-date payroll figures, and no awkward conversation with your auditor about which ledger the transaction actually sat in. Employers submitting employment income under IRAS' Auto-Inclusion Scheme report on a calendar year, so a 1 January payroll cutover also means one system owns one full year of salary data.

Vendors reinforce this, because a 1 January start makes their implementation plan look tidy and lets them bill configuration work in Q4. None of that is dishonest. The problem is that the date is chosen for the accounting calendar and the sales calendar, and nobody checks it against the operations calendar.

When is 1 January genuinely the right choice?

Commit to it if you can answer yes to all four:

• Your financial year ends 31 December. If it ends 30 June or 31 March, 1 January hands you a mid-year cutover disguised as a clean one.
• Your GST accounting period ends 31 December too. Quarterly filers on the Jan–Mar cycle qualify. If your quarter ends 30 November or 31 January, going live on 1 January splits a return across two systems.
• December is not your heaviest month. A B2B services firm with a quiet December is a very different risk from a retailer coming off 11.11 and Black Friday into Christmas.
• You have a named person who is not on leave in December and whose job for that month is the cutover, not their day role plus the cutover.

When should you refuse the date and move it?

Push to 1 April — the start of a new GST quarter for Jan–Mar filers, and comfortably clear of both the 1 March AIS submission deadline and Chinese New Year on 17 February 2027 — if any of the following apply.

Your December is peak trading. Your master data is not clean: duplicate customer records, stock codes that exist in three spellings, supplier bank details nobody has verified. Your opening stock figure depends on a physical count you have not scheduled. You are still negotiating scope with the vendor in November. Or your team has never seen the new system outside a demo.

Moving the date is not a failure. Going live on dirty data is how a system that works perfectly becomes "the new system is wrong" within three weeks — and once your own staff stop trusting the numbers, you are running two sets of books informally, in spreadsheets, which is exactly the position you paid to leave.

What does a workable October-to-January timetable look like?

If you are holding to 1 January 2027, the work starts now, not in December.

• First half of October: freeze scope in writing. Extract your current chart of accounts, customer, supplier and item masters to a spreadsheet and look at them properly. Decide what will not migrate.
• Second half of October: clean the masters and sign off the chart of accounts. This is the single highest-value fortnight in the whole project. Also settle grant paperwork now if you intend to claim support — approval timelines do not bend for your go-live date.
• November: configuration, then a full migration rehearsal using a real data extract. Not a sample. The whole file. Expect it to fail the first time; that is the point of a rehearsal.
• Late November: second rehearsal, plus user testing with the three or four people who will actually key transactions. Schedule your stocktake. Confirm December leave.
• 1 December: start entering December transactions in both systems, or at minimum run a full parallel on sales invoices and payments. This is the month that tells you the truth.
• 31 December: close, count, and load verified opening balances.
• January: legacy system goes read-only, not deleted. Keep it accessible for at least a full filing cycle.

If that timetable cannot fit, you have your answer about the date.

How do you protect GST, payroll and e-invoicing through a cutover?

Three rules. First, never split a GST accounting period across two systems — your F5 is due one month after the period ends, and reconstructing half a quarter from an archived database under deadline is miserable work. Cut over on a period boundary or not at all.

Second, payroll follows the calendar year. Mid-year migration means carrying year-to-date wages, CPF and deductions across accurately, and CPF contributions are still due by the 14th of the following month regardless of which system you are wrestling with. If payroll must move, move it at 1 January even if finance moves later.

Third, if your new system will transmit e-invoices, test transmission on live credentials before go-live, not after. Singapore's InvoiceNow requirements are phasing in through 2026, and "the invoice was raised but never reached the customer's system" is a cash-collection problem, not an IT problem.

What is the smallest decision you can make this month?

One page, signed by the owner, before October closes: the go-live date, the named cutover owner, the last day masters can change, the parallel-run scope, and the rollback trigger — the specific condition under which you stay on the old system and try again in April. Agreeing the rollback condition while everyone is calm is what stops a bad go-live from becoming a bad quarter.

Frequently asked questions

Can we go live on 1 January without a parallel run?

You can, and small service businesses with low transaction volume often do. But without a parallel run your first real validation is your first month-end close in the new system — in February, while you are also handling year-end filings. A one-month parallel on sales and payments only is a reasonable middle option.

Our financial year ends 30 June. What is our equivalent date?

1 July is your clean cutover, with the parallel run through June. If you cannot wait that long, pick a GST period boundary and accept that year one will have comparatives split across two systems — tell your auditor before you do it, not after.

How long should we keep the old system running?

Read-only access through at least one full filing cycle, including the next corporate tax filing, plus an exported copy of the underlying data in a format you can open without the vendor's licence. Records must be retained for five years, and "the subscription lapsed" is not an acceptable answer to a query.