Many of the first reports on InvoiceNow tend to start with the timeline for when the mandate begins to come into effect. While informative, this alone isn’t what makes the InvoiceNow mandate something that heads of finance and IT in Singapore are looking at today. More important is the operational shifting – and the reasons why an increasing number of businesses are linking up to the Peppol network even before the mandate gives them the impetus to do so.
The quick answer to that is from November 2025 the tax authority (IRAS) started requesting that some GST-registered firms supply invoice information directly through the InvoiceNow network to the IRAS, and that will phase in up until 2031 when the requirement will be inclusive to basically every GST-registered company in Singapore.
However, the mandate should primarily serve as a wake-up call – prompting companies to deal with operational issues with invoicing processes, master data, many of which have been bypassed by finance operations in the past. Early movers adopt InvoiceNow by being proactive.
What InvoiceNow actually is, briefly
The Singapore national network called InvoiceNow operates under the Peppol framework, enabling businesses to exchange structured business documents electronically. For companies looking to connect their ERP or accounting systems to this network, Peppol e-invoicing in Singapore provides a structured approach to digital invoice exchange and compliance readiness. IMDA launched InvoiceNow as the first Peppol Authority outside Europe in 2019. The network uses the Peppol four-corner model, allowing structured invoices to move between trading partners through Access Points and into their accounting or ERP systems.
The addition of the GST InvoiceNow Requirement introduces the Fifth Corner IRAS. If a GST-registered business sends out or receives a qualifying InvoiceNow invoice, the tax information is automatically communicated to the IRAS as the structured invoice is sent to the trading partner. Let's be exact here, as it was somewhat vaguely implied in several explanations-IRAS isn't actually one of the Peppol endpoints, but the taxpayer submits, via either their InvoiceNow-ready solutions or Access Points, the relevant tax information in IRAS’ own data format separate to the Peppol network. One invoice two data flows, basically.
This is the structure change. The implication to the business is less about the underlying machinery and more about your GST reporting posture.
The actual driver: near real-time visibility changes the risk calculus
Currently, most Singapore businesses reconcile their GST quarter-over-quarter, identify any errors there and fix them before filing the GST. With GST InvoiceNow, invoice-level data can now reach IRAS close to transaction-time; it's not saying that every invoice is scanned or checked in real-time, but the time between "an error occurred" and "IRAS is now aware it has occurred" is significantly shortened.
To a business that already has a clean, controlled invoicing process (correct GST treatment on sales and purchases, the correct entity mapped to each invoice, consistent master data), this can largely be considered as upside. IRAS has confirmed that well-managed businesses reporting clean, verifiable InvoiceNow data could enjoy shorter, simpler GST audits since many reconciliation processes would otherwise be completed manually by the auditor. It could also help with identifying early warnings, such as incorrect charging of GST by non-GST-registered suppliers - this is surprisingly rampant, yet difficult to detect with manually entered processes.
To a business that still operates its invoicing process via spreadsheets, a manual entry driven system, or on a supposedly live ERP that has not been audited for over 3 years, the same real-time visibility can become the business's burden. The real-time visibility will not spawn additional errors-it can only provide proof of current, non-GSTInvoiceNow data.
This is fundamentally the key issue behind businesses opting to voluntarily adopt InvoiceNow over and above the stipulated mandatory timeframe; businesses who already realize the quality of their invoice data is not as pure as intended are now able to decide WHEN to find out about this and rectify it within reasonable parameters instead of facing the facts when they start the mandatory month in live transition.
The mandate timeline, and where most businesses actually sit
The rollout is phased by registration type and, later, by annual turnover:
As of 1st of November 2025, new incorporated companies that chose to register for GST voluntarily are required to submit their invoice data through InvoiceNow.
From 1 April 2026, this extends to all new voluntary GST registrants, regardless of incorporation date.
From 1 April 2028 through April 2031, the requirement rolls out progressively to remaining GST-registered businesses, based on annual turnover, with the government confirming at Budget 2026 that all GST-registered businesses will eventually be in scope.
If GST voluntary registration is not something you will need within the next immediate term, then perhaps the timeline isn't as alarming as the headlines suggest - although "within the next immediate term" does not necessarily mean "not your issue at all". While overseas businesses and those on reverse charge are initially not included in the mandate, the eventual trajectory is clear: to apply to all GST-registered businesses in Singapore by 2031, and IRAS has stated that they will progressively inform current GST-registered businesses about their individual deadline dates.
Further incentives for transitioning sooner rather than later: A SGD 1,000 grant was made available from 1 July 2026 to SMEs' onboarding efforts, along with complementary free InvoiceNow packages for GST-registered businesses. Larger companies linking up through an Access Point could receive a SGD 5,000 cash incentive, while companies linking a bespoke ERP system directly to the network can apply for the InvoiceNow Queen Bee Grant amounting to up to SGD 25,000. None of these are infinite - government grant windows typically close as regulations transition from incentivized to mandated, meaning those businesses factoring in costs of early adoption today are essentially dealing with much more affordable figures than at a later stage.
The part most articles skip: this is an ERP and master-data project, not a software toggle
This is where real world experience on this differs from everything else you read. Much of the content available implies that “adopt InvoiceNow – get InvoiceNow ready software, an InvoiceNow ID – that’s it”. That is functionally true, but practically… no.
Your Peppol ID will depend on your UEN, but your invoicing structure should depend on your organization structure. While there will be a reasonably straight path for a single legal entity in Singapore, for a group office with multiple subsidiaries across ASEAN, or for a company with many separate Singapore-registered entities operating under a single ERP, how you assign Peppol IDs and route invoices will have to take each entity into account; not each company globally. Fail on this first crucial step and you'll be wrestling with incorrect invoices, or misrouting GST data to IRAS.
The quality of your master data will be what decides whether the whole thing goes smoothly or horribly. InvoiceNow requires accurate customer/supplier identifiers, correct tax codes for GST treatment, and correctly listed entities details in the SG Peppol Directory; duplicates, mistyped UENs, outdated GST statuses and the likes of this very common occurrence for organically growing, ad-hoc-CRM or spreadsheet-centric client data will make themselves abundantly apparent as soon as invoice processing fails or, worse, transmittes corrupted data. Fill in the wrong field and the transmission gets rejected outright rather than simply reported as wrong.
The difference between choosing an InvoiceNow-ready solution versus an Access Point provider really matters. If you are accounting system, or an ERP system, is already InvoceNow-ready, then the process is going to be much simpler for you. If however your ERP system is not InvoiceNow-ready (more commonly found among companies running older, highly customized ERPs), then you are going to have to connect via a designated and IMDA-accredited Access Point Provider. This is a genuine integration decision as an AP will likely only perform the function of handling the transmissions and making any required file format transformations; it will not touch the internal workings of your ERP software, meaning that it is still largely up to your finance team (or the respective implementation partner) to map the invoicing information on your end accurately on your end. A large part of why businesses are so late with getting on the GST InvoiceNow bandwagon is because custom-built ERP systems are often severely underestimated when it comes to the complexity of data extraction and manipulation.
While localization and customization shouldn't be treated interchangeably in general, here's another instance. The InvoiceNow specification for GST invoice transactions require a very strict structure with regard to the template to follow and the data elements, tax codes etc. To submit. This is a localization problem. The solution should only address a set format; how business transactions and business procedures are mapped and handled by your ERP around this requirement (approval routings, multi-currency capability etc.) falls more within a customization issue, and both become easily confused when dealing with bespoke ERP solutions where they often get blended and the configurations can turn out very technically correct but operationally clumsy.
What a growing Singapore SME actually deals with
Imagine a trading company located in Singapore, with two subsidiaries: one that distribute to the local market and another one dealing with export into Malaysia and Indonesia. For a variety of reasons, this company had been invoicing through a mix of accounting package software (for the local subsidiary), and through manually created invoicing documents (for the export subsidiary’s side, because its volume of invoices did not justify a fully- fledged system). With GST InvoiceNow, both these entities will eventually be required to provide invoice data to the IRAS if both entities are Singapore GST registered and it implies that the manual process of the export subsidiary does not make any more financial or operational sense and it becomes a time bomb as this may only be discovered during a tax audit by IRAS.
In fact, this is one perfect example of a company that would benefit from integrating its two subsidiaries onto a single ERP system equipped with InvoiceNow capability, rather than struggling to bring two different systems into compliance.
The GST InvoiceNow Mandate is just what the company needs to finally rectify the problem it already had long before the GST InvoiceNow Mandate.
What to evaluate before choosing how to get there
Before selecting a provider or solution, it's worth working through a few questions rather than defaulting to whatever your current accounting software vendor offers:
Does your existing ERP or accounting platform have genuine InvoiceNow readiness, or does it require a bolt-on Access Point connection?
How many legal entities does your business operate in Singapore, and does your Peppol ID and invoice routing strategy account for each one correctly?
Is your customer and supplier master data clean enough to pass validation on day one, or does it need a cleanup project first?
Does your team need implementation support, or just a connection — an Access Point provider will get you transmitting, but won't necessarily fix underlying ERP or data issues?
Are you eligible for the current transition grants, and does your implementation timeline let you claim them before they tighten?
For SMEs that are already using, or considering an Odoo-based ERP solution this is also where localisation partners like Serpentcs become particularly relevant – their localization efforts in Singapore include everything from the GST configuration to an IRAS aligned chart of accounts and payroll/CPF setup as part of the account layer, rather than just InvoiceNow only – this may be important ifInvoiceNow readiness is required as part of a wider ERP rebuild, rather than simply as a standalone add-on – this is a better fit for smaller organisations consolidating multiple business functions within an organisation onto a single enterprise wide platform, than for larger organisations with extremely customised, long lived legacy environments, particularly an SAP or Oracle environment, where an Access point specialist, or a localisation partner already within the client's infrastructure would appear more logically suited to the needs of the organization. The selection criteria can therefore be critical when choosing a potential provider, as ultimately what you require is a specialist aware of both the technical specifications set forth by IRAS and the IMDA and a sufficient working knowledge of your current enterprise architecture to deliver an installation that meets and maintains compliance without being brittle.
The practical takeaway
Businesses going Peppol e-invoicing before they are required are not doing it for the thrill of a compliance project. They are doing it because the mandate reveals the kind of invoicing and data quality shortcomings that were significantly cheaper to address on a quiet, methodical day than they will be in the cutover. If your invoice data is already clean and your ERP is ready for InvoiceNow, you’ll basically flip a switch. If your invoice data needs cleaning and your ERP doesn’t support InvoiceNow yet, you can find that out best with time on your hands.
Looking for an Odoo ERP development company in Singapore? Let’s discuss your business needs, explore the right Odoo solution, and have a cup of coffee.
FAQ
InvoiceNow is Singapore’s national e-invoicing network built on the international Peppol framework. It enables businesses to exchange structured invoices electronically through Access Points, without relying on PDFs, emails, or manual data entry. The GST InvoiceNow Requirement adds a tax-reporting component, requiring relevant GST invoice information to be submitted to IRAS alongside the normal Peppol invoice flow.
The blog focuses on the GST InvoiceNow Requirement, which applies to GST-registered businesses. It explains that the requirement is being progressively extended to GST-registered businesses and is expected to cover all GST-registered companies in Singapore by 2031. Therefore, if a business is not GST-registered, it is not currently described in the blog as being within this GST InvoiceNow mandate.
If an ERP system is not InvoiceNow-ready, a business may need to connect it through a designated and IMDA-accredited Access Point provider. However, an Access Point generally handles invoice transmission and required format transformations; it does not automatically fix the company's internal ERP configuration, data, or master-data problems. The business or implementation partner still needs to correctly map invoice information and ensure that the data meets the required structure..
Yes. The blog mentions several incentives for businesses adopting InvoiceNow earlier. From 1 July 2026, SMEs can receive a SGD 1,000 grant for onboarding efforts, along with complementary free InvoiceNow packages for GST-registered businesses. Larger companies connecting through an Access Point may receive a SGD 5,000 cash incentive, while companies connecting a bespoke ERP directly to the network can apply for the InvoiceNow Queen Bee Grant of up to SGD 25,000. Businesses should consider eligibility and timing because these incentives may change as adoption becomes mandatory.
The blog explains that InvoiceNow operates using structured invoice information rather than traditional PDFs or manually entered documents. PINT-SG forms part of the structured format used for Singapore's InvoiceNow environment, with strict requirements for invoice data elements and GST tax codes. Following the correct structure is important because incorrect or incomplete information can result in transmission failures or rejected invoices rather than simply being identified later during a manual review.
The traditional Peppol model described in the blog is a four-corner model, where the sender's Access Point sends a structured invoice to the recipient's Access Point, which then makes it available to the recipient's accounting or ERP system. Singapore's GST InvoiceNow Requirement introduces what the blog describes as a fifth corner involving IRAS for the relevant tax information flow. Importantly, IRAS is not itself a Peppol endpoint; the relevant tax information is submitted separately to IRAS in its required data format while the structured invoice continues through the Peppol network.
Businesses with multiple Singapore-registered entities need to consider each legal entity separately when determining their Peppol IDs and invoice-routing structure. The blog explains that a company's Peppol ID depends on its UEN, so groups operating multiple Singapore entities cannot simply treat all entities as one global organization. Correct entity mapping and routing are important to prevent invoices from being misrouted or GST information from being incorrectly associated with an entity.
Delaying adoption can leave businesses with less time to identify and correct problems in their ERP, invoice processes, and master data. Issues such as incorrect GST tax codes, outdated GST statuses, duplicate records, incorrect UENs, or poor entity mapping can become visible when InvoiceNow validation and transmission begin. The blog's main point is that businesses with clean data and an InvoiceNow-ready ERP may have a relatively straightforward transition, while businesses with data-quality or ERP issues can face a much more difficult implementation if they wait until the mandatory deadline.
