Last researched: 3 September 2026. The accounting standard, retention, filing and data protection rules are taken from ACRA, IRAS, the Singapore Statutes, the PDPC and the Big Four Singapore practices cited, checked on that date. Implementation timelines and costs are Singapore partner and agency figures and are labelled as such.
Most ERP implementation advice is generic: discovery, configuration, data migration, testing, training, cut-over, the same six phases everywhere. Singapore’s implementation is not generic in six places, and they are what decide whether the project succeeds. Three workstreams decide whether it goes live cleanly: GST tax code design and the IRAS Audit File, the InvoiceNow connection and the UEN master data behind it, and the payroll journal. Two rules decide what happens to the old system: the five-year retention requirement under the Companies Act and the tax Acts, and IRAS’s position that historical transactions don’t need migrating but must stay retrievable. And one accounting-standard change decides how the new chart of accounts should be built: SFRS(I) 18, effective for periods beginning on or after 1 January 2027, with comparatives required from 1 January 2026 — so any chart of accounts designed in the second half of 2026 needs to be built for it now.
This guide covers those in turn, then the PDPA obligations that travel with the data into the cloud, the filing calendar the project has to fit around, and the timelines and costs Singapore partners publish. It’s part of our Singapore ERP series: the Singapore ERP buyer’s guide covers choosing the system, and the cost guide covers what to budget.
Key takeaways
- SFRS(I) 18 replaces SFRS(I) 1-1 for annual periods beginning on or after 1 January 2027, with full retrospective application, so the 2026 comparatives must be presentable under the new standard. It introduces operating, investing and financing categories in the income statement, two mandatory subtotals, and a single note for management-defined performance measures. The chart of accounts is where it lands.
- Records must be kept for at least five years: from the end of the financial year under the Companies Act, from the relevant year of assessment for income tax, and from the end of the accounting period for GST. Electronic records are acceptable without approval.
- IRAS states that there is no requirement to migrate historical transactions into new accounting software, but the old system’s transactions must remain retrievable for five years. That is a decommissioning plan, not a migration plan.
- The three Singapore workstreams that stall projects are GST tax code design with an IAF test, InvoiceNow onboarding with UEN clean-up, and the payroll journal. EY advises planning for 10% to 20% of invoices to fail InvoiceNow validation on the first attempt.
- Do not cut over in the last weeks of a GST quarter. IRAS grants at most two weeks’ extension for a new accounting system, and none for staff shortages or year-end closing.
- Singapore partners quote three to six months for a normal mid-market project, and a local agency benchmarks three to five months for under 20 users and five to eight for 20 to 50. AFON recommends budgeting services at no less than one and a half times the software cost.
The three Singapore workstreams
These three determine the go-live date more than any other configuration decision in the project.
GST tax codes and the IRAS Audit File. The GST F5 return is just a summary of the tax codes on posted transactions — so tax code design is the GST project. It needs default codes by general ledger account and by counterparty, so that blocked expenses, exports, imports under any scheme the company holds, and reverse charge purchases land in the right box without the person posting the document knowing the rules; and it needs a test that proves it, which is the IRAS Audit File generated from migrated data before go-live. The IAF will not generate in some systems if a supplier record is missing its UEN or GST number, which makes it a useful master data test as well. IRAS keeps a register, the ASR+, of software whose F5 and F8 filing by API it has tested; where the system is not on it, the return is keyed into myTax Portal from a report. Our GST F5 and F8 guide covers the configuration decisions in detail.
InvoiceNow and the UEN clean-up. The GST InvoiceNow Requirement already applies to new voluntary GST registrants and reaches existing businesses in phases from 1 April 2028 to 1 April 2031 by annual supplies, and IRAS notified businesses of their dates from mid-2026 (IRAS, checked 2 September 2026). The system being installed now is the one that will comply, so the connector, the access point and the activation of the IRAS submission belong in the project scope. The work that takes the time is the master data. EY’s Singapore tax practice calls it the number one technical risk, advises validating customer UENs, standardising address formats and reviewing product and GST coding before go-live, and suggests planning for 10% to 20% of invoices to fail validation on the first attempt (EY Singapore, 25 May 2026). Give the UEN clean-up its own owner and its own deadline in the data migration plan. Our InvoiceNow guide has the timetable and the accreditation lists.
The payroll journal. No global ERP in our buyer’s guide does Singapore payroll, so the project includes a second product and one monthly journal into the ledger: salaries and allowances, employer CPF and SDL, employee deductions, levies and net pay, split by cost centre where the chart needs it. Where the payroll vendor publishes a connector, use it; where it does not, the ERP partner builds or maps one, and the mapping needs an owner after go-live. The CPF rate changes on 1 January 2027 and the SFRS(I) 18 chart changes will both touch that mapping within a year of most 2026 go-lives. Our payroll and CPF guide covers the products and the rates.
Timing the cut-over
The Singapore-specific timing constraint is the GST quarter. GST returns and payment are due one month after the end of the accounting period, and IRAS’s stated position is that this is a reasonable deadline and extensions are not granted as a matter of course. The exceptions it lists are narrow: one month for a newly registered business’s first return, and two weeks for a documented computer breakdown, the purchase of new accounting software or an IT system, key accounting staff on long medical leave, a restructuring, or errors submitting through seamless filing software by API. The reasons it will not accept include staff resignation without handover, year-end closing, new accounts staff who do not know GST, and not enough manpower (IRAS, Due dates and requests for extension, checked 2 September 2026). A go-live in the last fortnight of a quarter therefore puts the first F5 from the new system, and the last from the old, into the same month, with at most a two-week cushion. The first month of a quarter is the safe window, and the first month after the financial year-end is better still, because the opening balances are the audited ones.
SFRS(I) 18: designing the chart of accounts for 2027
The Accounting Standards Committee issued SFRS(I) 18 and its equivalent FRS 118, Presentation and Disclosure in Financial Statements, on 4 October 2024. It applies to annual reporting periods beginning on or after 1 January 2027 and replaces SFRS(I) 1-1 and FRS 1. ACRA’s announcement says the scale of change depends on each entity’s current practices and IT systems, and tells entities to start their assessment now (ACRA, 4 October 2024, primary). The underlying IFRS 18 was issued by the IASB on 9 April 2024 with the same effective date and applies retrospectively, so the comparative year, which for a December year-end is 2026, must be presented under the new standard (PwC, 19 June 2024). Early adoption is permitted under IFRS 18. ACRA’s issuance announcement and its 2024 accounting-standards-news archive state only the 1 January 2027 effective date and say nothing about early application — whether Singapore entities may adopt SFRS(I) 18 early could not be confirmed from ACRA’s own pages, checked 3 September 2026 (ACRA, issuance announcement; ACRA, 2024 standards news). A company considering early adoption should raise it directly with ACRA or its auditor rather than assume the IFRS 18 position carries across. SFRS(I) 19, which allows eligible subsidiaries without public accountability to give reduced disclosures, was issued on 25 October 2024 with the same 2027 effective date (ACRA, primary).
What changes is presentation, and presentation is driven by how the ledger is coded. Income and expenses must be classified into operating, investing, financing, income tax and discontinued operations categories, with two new mandatory subtotals, operating profit and profit before financing and income taxes. Management-defined performance measures, the adjusted profit figures companies use in their reporting, must be disclosed in a single note and reconciled to the standard’s measures. There is new guidance on how items are aggregated and disaggregated. And the cash flow statement’s indirect method starts from operating profit (PwC Singapore, updated 5 December 2025; Deloitte, Financial reporting in Singapore 2024 roundup, January 2025).
| SFRS(I) 18 requirement | What it means for the ERP |
|---|---|
| Income and expenses classified into operating, investing, financing, income tax and discontinued operations | Every profit and loss account, or a reporting dimension on it, needs a category tag; the financial statement mapping in the ERP or reporting tool has to produce the categories and the two subtotals |
| Foreign exchange differences follow the category of the item that gave rise to them | One “FX gain/loss” account is no longer enough; exchange differences on trade balances, on borrowings and on investments need separate accounts or dimensions, and the revaluation routine must post to them |
| Main business activity assessment for entities that invest or provide financing | Holding companies, property investors and financing entities need a documented assessment, and in a group the assessment may differ by subsidiary, requiring reclassification on consolidation |
| Management-defined performance measures in one note, reconciled | The adjustments behind EBITDA and similar figures need to be identifiable in the ledger, not in a spreadsheet |
| Aggregation and disaggregation guidance | Line items that combine dissimilar things need splitting; account granularity and dimensions decide whether that is possible without journals |
| Retrospective application with 2026 comparatives | A chart of accounts designed in late 2026 should carry the tags from day one, so that the comparative year does not have to be reclassified by hand |
Sources: PwC Singapore, IFRS 18, updated 5 December 2025; Grant Thornton Singapore, IFRS 18 advisory, checked 2 September 2026; Deloitte, Get ready for IFRS 18; IFRS Foundation, classification of foreign exchange differences on intragroup monetary items, 2026. The ERP implications are our synthesis of those sources.
PwC Singapore’s list of the work involved is the one to give an implementation partner: chart of accounts definition and mapping, ERP reconfiguration, financial master data re-evaluation, data disaggregation levels, and changes to closing processes and controls. It also notes that foreign exchange differences must follow the same category as the income or expense that generated them, that hedging gains and losses follow the hedged item, and that the main business activity assessment may differ between group and subsidiary levels (PwC Singapore). Grant Thornton Singapore describes the same translation of the standard into chart of accounts, ERP and reporting tool changes (Grant Thornton). For a company implementing in the second half of 2026, the cheapest time to do this is now, while the chart is being built; for a company already live, it is a reconfiguration project to complete before the 2027 opening balances.
Records, retention and the old system
Three laws set the retention period and they agree on five years, counted from different points. Section 199 of the Companies Act requires a company to keep accounting records for not less than five years from the end of the financial year in which the transactions were completed (Companies Act 1967, s199, primary). IRAS requires source documents, accounting records and schedules and bank statements to be kept for at least five years from the relevant year of assessment for income tax, so records for the 2018 financial year, assessed in 2019, could be discarded from 2024 (IRAS, Record keeping requirements, updated 22 January 2026). GST-registered businesses must keep records for at least five years to support their GST declarations (IRAS, Keeping records, updated 10 August 2026). Electronic records are acceptable without IRAS approval, provided there are internal controls over their integrity, completeness, accuracy, availability and reliability (IRAS, Record Keeping Guide for GST-registered Businesses, twelfth edition, 30 January 2026).
IRAS answers the migration question directly. There is no specific requirement to migrate the transactions recorded in the existing accounting software into the new one. However, the company must continue to retain, and be able to retrieve, the transactions recorded in the existing software for at least five years from the year of assessment or the end of the GST accounting period, along with the source documents, schedules and bank statements behind them (IRAS). That settles two arguments that come up in every project. You do not need to load five years of history into the new ERP; opening balances and open items are enough for the accounts, and history can be loaded selectively for analysis. And you cannot simply cancel the old subscription. A read-only licence, a restorable database backup, or a full export of ledgers, tax listings and the IRAS Audit File for every open period all satisfy the rule; a cancelled cloud subscription with no export does not. Ask the outgoing vendor what post-termination access costs, and put the decommissioning plan in the project.
ACRA’s filing is a separate output. Companies file financial statements in XBRL through one of three routes: preparing them in the BizFinx tool and filing through Bizfile, filing in simplified XBRL directly from approved accounting software, or engaging a corporate service provider (ACRA, Ways to prepare and file, updated 6 February 2026). None of the mid-market ERPs in our buyer’s guide advertises native ACRA XBRL output in its own documentation, and we found no evidence any of them appear as a seamless-filing accounting software option on that ACRA route; XBRL is prepared from the ERP’s financial statements by the accountant or the corporate secretary, checked 3 September 2026.
PDPA: the obligations that follow the data
An ERP holds personal data about employees, customers and suppliers, and the Personal Data Protection Act’s obligations apply to it wherever it is hosted. The PDPC lists them: accountability, notification, consent, purpose limitation, accuracy, protection through reasonable security arrangements, retention limitation, transfer limitation, access and correction, and data breach notification (PDPC, Data protection obligations, 3 April 2023, primary). Three matter for an implementation. Transfer limitation: personal data may be transferred overseas only where the recipient is bound to a standard of protection comparable to the PDPA, which is the question to settle when a cloud ERP is hosted in Australia, Japan or an unnamed Azure region. Retention limitation: personal data must not be kept once it is no longer needed for a business or legal purpose, which conflicts with five-year record retention and needs a written policy to resolve. And breach notification: a breach likely to cause significant harm or of significant scale must be notified to the PDPC as soon as practicable and no later than three calendar days (PDPC, Before you report a data breach). Financial penalties have applied since 1 October 2022: the PDPC’s own announcement states that the cap rose from a fixed S$1 million to 10% of an organisation’s annual turnover in Singapore for organisations with annual local turnover exceeding S$10 million, whichever is higher, so the S$1 million cap remains the ceiling for organisations at or below that turnover (PDPC, Amendments to enforcement under the PDPA, September 2022, primary, checked 3 September 2026), consistent with the law-firm summary this article originally cited (Allen & Gledhill). Our NetSuite in Singapore guide and the NetSuite vs Business Central comparison cover where those two systems host Singapore data.
The filing calendar the project has to fit around
For a company with a December year-end, the statutory year looks like this. GST returns are due one month after each quarter, on 30 April, 31 July, 31 October and 31 January, with GIRO deductions on the 15th of the following month. Employment income must be submitted to IRAS under the Auto-Inclusion Scheme between 1 February and 1 March. The estimated chargeable income is due within three months of the year-end, so by 31 March, unless the company qualifies for the waiver. The annual general meeting must be held within six months of the year-end for a non-listed company, and the annual return must be filed within seven months of the year-end, eight months if the company keeps an overseas branch register (ACRA, Deadline and requirements for annual returns, checked 3 September 2026, primary). Form C-S or Form C is due on 30 November (IRAS, Basic guide to corporate income tax, updated 7 August 2026). CPF is due monthly by the last day of the month. On top of that sits the company’s InvoiceNow phase date. A project plan that lands go-live in the first month of a GST quarter, after the AGM and before the AIS window, gives the finance team the most room.
Timelines and what partners charge
Singapore partners are consistent about duration. AFON quotes three to six months for a normal SAP Business One or Business Central project and warns that going live in three weeks is the exception; it recommends budgeting services at no less than one and a half times the software cost (AFON; AFON, SME guide to ERP). Axxis bands Business One projects at about a week for a simple four-user deployment, four to five weeks for an eight-user distributor, and about three months for a twenty-user manufacturer (Axxis). A Singapore agency benchmarks packaged ERP at three to five months for under 20 users and five to eight months for 20 to 50, with custom builds at five to twelve months (Freemansland, 16 June 2026). On cost, the same agency’s June 2026 estimates are S$15,000 to S$25,000 to implement SAP Business One, S$25,000 to S$60,000 for Odoo and S$30,000 to S$60,000 for NetSuite for a 25-user SME (Freemansland, 13 June 2026), and Axxis’s on-premises bands run from S$15,000 to S$150,000 by complexity. Our cost guide collects every published figure. For eligible SMEs the PSG covers up to half of a pre-approved package, applied for before any payment; our PSG guide explains the timing against the claim deadline, which matters because the grant is paid only after the system is live and used.
Three Singapore buyer scenarios
Three implementations, three different verdicts on timing.
A S$20 million distributor with a December year-end, signing for SAP Business One in October 2026. Plan go-live for 1 April 2027, the first day of a GST quarter and after the year-end close, and treat the new chart of accounts as an SFRS(I) 18 chart from the start, since the 2027 financial statements will need 2026 comparatives in the new format. Run the IAF from migrated data in March, clean the supplier and customer UENs in February, and keep the old system on a read-only licence for five years.
A group holding company with three subsidiaries already live on NetSuite. The implementation is done; the 2027 work is an SFRS(I) 18 reconfiguration, not a new project. The holding company needs a main business activity assessment, the subsidiaries may classify differently, FX accounts need splitting by category, and the consolidation mappings need the new subtotals. Start in the second half of 2026 so the 2026 comparatives come out of the ledger, not out of a journal.
A 15-person services firm moving from a legacy desktop package to Xero. Export the ledgers, tax listings and IAF for every period from the old package before the licence lapses, and store them where they can be retrieved for five years. Load opening balances only — nothing more. Register the Peppol ID and activate the IRAS submission early: the firm’s InvoiceNow phase depends on its 2025 supplies, and Xero already supports it.
Questions to ask the implementation partner
Will the chart of accounts be built for SFRS(I) 18, and who tags the categories? Ask to see how the two subtotals and the FX split will be produced.
What is the cut-over date relative to the GST quarter, and what is the plan for the last old-system F5 and the first new one?
Show us the IRAS Audit File and an InvoiceNow submission generated from our migrated data.
What is the decommissioning plan for the old system, and what does five years of retrievable access cost?
Where is our data hosted, who are the sub-processors, and what is the breach notification process?
Which payroll product, and who owns the journal mapping after go-live?
Frequently asked questions
When does SFRS(I) 18 apply?
Annual reporting periods beginning on or after 1 January 2027, applied retrospectively, so the 2026 comparatives must be presented under it.
Do I have to migrate five years of history into the new ERP?
No. IRAS says there is no requirement to migrate historical transactions, but the old system’s records must remain retrievable for at least five years.
How long must accounting records be kept in Singapore?
At least five years under the Companies Act, the Income Tax Act and the GST Act, counted from the financial year-end, the year of assessment and the GST period respectively. Electronic records are acceptable.
When is the best time to go live?
The first month of a GST quarter, after the year-end close. IRAS gives at most two weeks’ extension for a new accounting system and none for staff shortages.
Does the ERP file my ACRA financial statements?
Not the XBRL filing, in the products we reviewed. That is prepared in ACRA’s BizFinx tool or by a corporate service provider from the ERP’s statements.
How long does an ERP implementation take in Singapore?
Three to six months for a normal mid-market project on partner figures; three to five months for under 20 users and five to eight for 20 to 50 on a local agency’s benchmark.
Sources
- ACRA, Issuance of SFRS(I) 18 and FRS 118, 4 October 2024, and Accounting standards news 2024. Primary source.
- ACRA, Ways to prepare and file financial statements in XBRL, updated 6 February 2026; Deadline and requirements for annual returns, checked 3 September 2026; and AGM due dates and requirements, updated 11 February 2026. Primary source.
- Companies Act 1967, section 199, Singapore Statutes Online. Primary source.
- IRAS, Record keeping requirements for companies, updated 22 January 2026; Keeping records (GST), updated 10 August 2026; Record Keeping Guide for GST-registered Businesses, twelfth edition, 30 January 2026. Primary source.
- IRAS, Due dates and requests for extension; GST InvoiceNow Requirement; Basic guide to corporate income tax, updated 7 August 2026. Checked 2 September 2026. Primary source.
- PDPC, Data protection obligations, 3 April 2023; Before you report a data breach; and Amendments to enforcement under the PDPA, September 2022, checked 3 September 2026. Primary source.
- Allen & Gledhill, PDPA financial penalty changes, checked 3 September 2026. Law firm.
- PwC, IFRS 18 Presentation and Disclosure, 19 June 2024, and PwC Singapore, IFRS 18: redefining financial performance reporting, updated 5 December 2025. Professional services firm.
- Deloitte, Financial reporting in Singapore 2024 roundup, January 2025, and Get ready for IFRS 18. Professional services firm.
- Grant Thornton Singapore, IFRS 18 advisory, checked 2 September 2026. Professional services firm.
- IFRS Foundation, Classification of foreign exchange differences on an intragroup monetary liability, 2026. Standard-setter.
- EY Singapore, GST InvoiceNow: a data and technology implementation, 25 May 2026. Professional services firm.
- AFON, SAP Business One and The ultimate SME guide to ERP systems, checked 2 September 2026. SAP, Microsoft and NetSuite partner.
- Axxis Consulting, SAP Business One pricing, checked 2 September 2026. SAP partner.
- Freemansland, ERP implementation timeline Singapore, 16 June 2026, and Top ERP systems for Singapore SMEs 2026, 13 June 2026. Agency blog; estimates are theirs.