Singapore’s GST InvoiceNow: a data and technology implementation, not just a tax project

The IRAS GST InvoiceNow mandate is an ERP and data integration effort, not a GST-only change.

Singapore is moving from voluntary digitalisation to mandatory compliance. The Inland Revenue Authority of Singapore (IRAS) has launched the GST InvoiceNow Requirement, a phased mandate requiring businesses to transmit invoice data directly to the government via the national InvoiceNow network.

This is not just a tax project. While the mandate is administered under the goods and services tax (GST) regime, the change is driven by technology, structured data, system interoperability and real-time application programming interface (API) integration.

The tax-related outcomes such as faster audits, reduced fraud and automated filings are merely the consequences of getting the data and technology right. Treating InvoiceNow as a narrow tax exercise increases delivery risk while approaching it as a core data and systems upgrade can unlock wider benefits.

Singapore is not the first to implement an e-invoicing mandate. Many jurisdictions in Latin America and Europe have introduced e-invoicing and transaction reporting. Their experiences highlight common delivery risks and lessons learned. Some industries, such as financial services, may face additional technical and operational complexity.

In this article, we outline the local deadlines and technical requirements, and summarise lessons learned from other markets, through a data and technology implementation lens.

What is the GST InvoiceNow Requirement? (A technology-first view)

The GST InvoiceNow Requirement mandates that GST-registered businesses use solutions compatible with the InvoiceNow network to transmit invoice data to the IRAS. Rather than exchanging portable documentation format (PDF) invoices via email (which are images or documents intended for human eyes), InvoiceNow uses the global Peppol (Pan-European Public Procurement Online) standard to send structured digital data directly between seller's accounting software to the buyer's system and provide the IRAS with a copy for tax administration.

In practice, a supplier today may email a PDF invoice, which is largely unstructured data. The recipient then re-keys the details into their system. With InvoiceNow, structured extensible markup language (XML) data can flow system-to-system, eliminating manual entry. The IRAS also receives the same structured data at the point of transmission.

This introduces a "five-corner model" to Singapore's e-invoicing framework. In addition to the sender, the sender's access point, the receiver's access point and the receiver, the IRAS now serves as the fifth corner, allowing near real-time receipt of transactional data.

Organisations should therefore plan for process changes, particularly in accounts payable (AP). Invoice data will be received into the enterprise resource planning (ERP) system through an access point, and AP teams will need controls to apply or confirm the correct tax coding and manage exceptions.  

Why would this matter to for technology leaders? Your ERP system, accounting system or billing platform must be able to generate, send and receive Peppol Business Interoperability Specifications (BIS) 3.0 compliant XML via a secure and certified access point technology with tax requirements applied to the data set.

Key implementation timeline

The IRAS is rolling out the requirement in phases. While a soft launch began in May 2025, the mandatory dates are already in effect for some businesses and approaching for others.

• Effective 1 November 2025: Newly incorporated companies that register for GST voluntarily within six months of incorporation.
• Effective 1 April 2026 (Current phase): All new voluntary GST registrants (regardless of incorporation date or business structure).
• Effective 1 April 2028: New compulsory GST registrants and existing businesses with annual supplies S$200,000 or less.
• Effective 1 April 2029: Existing businesses with annual supplies S$1 million or less.
• Effective 1 April 2030: Existing businesses with annual supplies S$4 million or less.
• Effective 1 April 2031: Existing businesses with annual supplies more than S$4 million.

What data must be transmitted?

Businesses are required to transmit structured data covering transactions for standard-rated supplies (9% GST), zero-rated supplies (exports), exempt supplies and standard-rated purchases (where input tax is claimed). Currently some exclusions apply for the financial services industry but there may be more to come.

Where a customer has not adopted InvoiceNow, the supplier must collate and transmit the relevant invoice data to the IRAS separately via an approved solution. The data must be transmitted to the IRAS by the earlier of the date the GST return is filed, or the official filing due date.

The required data fields include (among others) the buyer UEN, seller UEN, invoice date, line descriptions, quantities, unit prices, GST treatment codes and tax amounts. If required fields are missing or incorrectly formatted, invoices may fail technical validation and be rejected in near real time rather than being identified later during an audit.

Lessons from the other markets: data and technology risks

As Singapore implements GST InvoiceNow, it can draw on lessons from more than 90 jurisdictions that have already implemented e-invoicing mandates. A consistent theme is that programmes struggle when organisations treat them as tax only changes, rather than as data, process and systems transformation supported by tax expertise.

Lesson 1: Platform readiness and resilience

Defects in government platforms were identified close to go-live, requiring a complete IT rebuild and an indefinite delay.

Technology implication: The government IT infrastructure needs to be tested at scale and designed for peak loads, including GST filing periods when many businesses submit data in a short window.

For businesses: plan your implementation so you can proceed even if external timelines shift. When governments defer go-live dates, the expectation of readiness typically remains.

Lesson 2: Changing technical requirements

Technical requirements can change close to implementation dates, which may require additional development and testing effort.

Technology implication: work with your access point provider to understand which parts of the Peppol standard are stable and which may evolve. Build your integration to be schema-agnostic where possible and use a transformation layer that can be reconfigured without rewriting core systems.

Lesson 3: Late onboarding

When businesses transit into InvoiceNow late, it will create bottlenecks at access point providers and implementation partners. Late onboarding can also increase operational disruption, as suppliers and customers adjust to new invoice exchange and exception management processes. 

Technology implications: access point providers have finite implementation capacity, as do strategic implementation partners. Large organisations should engage providers and partners 24 to 36 months before their target go-live date.

Lesson 4: Data quality is the #1 technical risk

A common issue is treating e-invoicing as a "plumbing project" without addressing master data quality and tax technical considerations.  Real-time tax validation requires accurate and standardised data between your system and the government database.

Data implications: organisations often find issues such as invalid customer tax identifications (IDs) and Unique Entity Numbers (UENs) only when invoices start failing validation. Remediating master data late in the programme can be costly and may affect billing cycles and cash collection.

Start with a targeted data readiness plan: validate customer UENs, standardise address formats and review product and GST coding to support consistent downstream processing.

Lesson 5: Avoid the "IT only" delivery model

The most common failure is treating e-invoicing as an IT project solely owned by technology teams, with tax and finance stakeholders involved only during testing.

A more effective approach: Treat it as a cross-functional data governance programme with clear ownership:

• Technology: systems integration, API development and data transformation.
• Tax and finance: GST treatment rules, filing deadlines and audit requirements.
• Operations: Workflow design, exception handling and customer communication.
• Procurement: Vendor selection, and contract negotiation with access point providers.

Some jurisdictions faced technology issues, while others succeeded but struggled with business adoption and readiness. Singapore can learn from all the jurisdictions which have gone live already.

How to prepare from a data and technology standpoint

With the 1 April 2026 phase now in effect and major implementation waves coming in 2028, organisations should start planning early. The actions below focus on data, process and technology enablement, alongside tax requirements.

1. Adopt an InvoiceNow-ready solution
Select an InvoiceNow-ready solution that fits your business model and integration needs. For many organisations, this will involve assessing the providers in the IRAS ASR+ list. Look beyond cost to consider integration options, support model and scalability.

2. Run a data quality audit
This is the top technical risk. Assess customer and supplier master data including UENs, addresses and product and GST coding. Real-time validation means errors can surface immediately and disrupt billing and collections, if not managed properly.

3. Establish a cross-functional steering committee
E-invoicing affects tax, finance, IT, business units and operations. Establish a steering committee early and define decision rights, for example, who approves changes to GST treatment logic, who manages the access point provider and service levels, and who resolves rejected invoices.

4. Consider large enterprise and financial services complexity
Where API integration and legacy systems are in scope, plan this as a software delivery programme with dedicated resources. Engage access point providers early – often 24 to 36 months ahead of go-live – and budget for middleware and testing.

5. Design an exception handling workflow
Assume 10-20% of invoices to fail validation on the first attempt. Design a workflow to review, correct and resubmit rejected invoices.

The bottom line: a data and technology project with tax requirements

The GST InvoiceNow initiative is not an extension of the tax filing process. It is a fundamental upgrade to billing and data infrastructure. The tax outcomes of faster audits, reduced fraud and automated filings are benefits of getting the technology implementation right, not the project itself.

Organisations that succeed typically run this like other major systems changes, with steering committees, sprint cycles, data migration plans, user acceptance testing and go-live cutover plans. Those that fail would have typically treated it as "something for the tax team to handle" and started preparations late, facing compressed timelines, limited vendor capacity and higher operational risk.

Singapore's staggered timeline through 2031 offers ample lead time but this is meaningful only if organisations use it to improve data quality, integrate systems and embed e-invoicing into day-to-day processes and controls.

A number of our EY entities in Singapore have adopted GST InvoiceNow from 10 May 2026 using a phased approach, with the remaining entities scheduled to onboard in early 2027.

With our experience, we are ready to help you onboard.

-ends-

The author of this article is Liza Drew, Partner, Financial Services Indirect Tax, Ernst & Young Solutions LLP.