Singapore GST InvoiceNow Requirement: Who Is Affected & When

Key takeaways

• An existing GST registration is different from a new voluntary application; an old incorporation date does not remove the current voluntary-applicant condition.
• The later rollout uses 2025 total supplies, including exempt supplies, so the accounting revenue figure alone may assign the wrong year.
• A missing 2025 return history and filed nil returns are different evidence problems; do not automatically give both businesses the smallest supplies band.
• Network registration, activation of submissions to IRAS, and successful delivery are separate checks. Record all three before closing the implementation task.

Match your registration route to a start date

Singapore GST InvoiceNow applies by registration cohort, subject to the exclusions below. The matrix separates phases already operating from the announced later rollout and pairs each route with the record needed to substantiate it. Dates and thresholds were checked against the current IRAS implementation schedule on 8 September 2026.

Read the existing-business bands as mutually exclusive: a business already assigned to 2028 does not move to 2029 merely because it also falls below S$1 million. The joint IRAS and IMDA rollout announcement establishes the later stages; those future dates do not make every existing business subject to mandatory transmission today.

The application date selects the new-registrant cohort; the effective GST registration date starts its submission obligation. IRAS confirms that distinction in its e-Tax Guide, section 5 . Neither date is the day an accounting subscription was purchased.

Check exclusions before assigning a cohort

The overseas-entity exclusion is narrower than foreign ownership. It covers specified overseas businesses requiring section 33(1) local GST agents and vendors under the Overseas Vendor Registration (OVR) pay-only or full regime. It does not cover a foreign company merely because its headquarters is abroad when it has a Singapore branch or establishment. Local businesses with overseas establishments are also outside that overseas-entity exclusion. These boundaries appear in paragraph 5.25 of the IRAS guide .

A business liable to register wholly because of reverse charge is separately excluded. Having some reverse-charge transactions is insufficient if another basis also creates the registration liability. Check the basis on which the business registered, rather than searching its ledger for any imported-service entry.

For a newly established local company, forming a company in Singapore creates the underlying entity; GST registration and InvoiceNow onboarding have their own records and completion dates. Foreign shareholders do not convert that local entity into an overseas vendor. A business that is not GST-registered has no GST InvoiceNow obligation under this rollout, although its customers may request electronic invoicing commercially.

Resolve the 2025 supplies evidence

Use Box 4 for prescribed accounting periods ending in 2025 when assessing a remaining existing business. That total includes standard-rated, zero-rated and exempt supplies. Periods are selected by their end dates, even where they began in 2024; replacing them with January-to-December management accounts can change the result. IRAS explains the calculation in its implementation FAQs, questions 1.9–1.11 .

Apply these boundary tests to the evidence you actually hold. They are planning illustrations, not client cases:

• Check an exact threshold. With a full-year total of S$200,000, the scheduled date is 1 April 2028. A total of S$200,001 moves into the 2029 band. Do not round the source total before selecting the row.
• Annualise a short history. Suppose eligible return periods cover 100 days and Box 4 totals S$60,000. The 365-day equivalent is S$60,000 × 365 ÷ 100 = S$219,000, placing the business in the 2029 band rather than 2028. Retain the period dates and calculation.
• Distinguish zero from absent. Filed nil returns can establish zero supplies and the 2028 phase. With no GST returns ending in 2025, there is no equivalent calculation to perform; IRAS says the implementation date will be communicated later.

IRAS began notifying businesses registered before 2026 of their dates from mid-2026. If a notification is missing or conflicts with your worksheet, check the IRAS notification and date-calculator guidance and resolve the difference before approving a migration deadline. Do not invent a 2025 turnover figure for a business registered later.

A claimed compulsory application that IRAS approves voluntarily because the supporting forecast evidence is insufficient can enter the current voluntary cohort. Preserve the approval basis alongside the application: distinguishing compulsory and voluntary registration triggers matters here because it can change the InvoiceNow start date. This is specifically addressed in IRAS FAQ 1.5 .

Prepare the submission route before your start date

InvoiceNow exchanges structured invoice data over the Peppol network. The Infocomm Media Development Authority (IMDA) accredits providers; the GST submission feature sends data onward to IRAS. A Peppol listing alone does not establish that this feature is active. IRAS notes that in-house enterprise onboarding may take as little as three months, with most setups completed within a year, depending on readiness and configuration. Treat this as a planning indication, not a guaranteed delivery period; see its onboarding instructions .

1. Confirm the solution route. For packaged software, check its provider against the accredited InvoiceNow-Ready Solution Provider list. For an in-house enterprise system, involve an IMDA-accredited Access Point Provider and identify the integration work.
2. Register the correct entity. Have the provider register the business in the SG Peppol Directory using its Unique Entity Number (UEN), obtain the Peppol ID, and activate submissions to IRAS. Check that the entity in the software matches the GST registration.
3. Test representative records. Include a sales invoice, purchase invoice and credit note, plus any relevant transaction originating outside the network. Assign someone to resolve rejected records and retain the IRAS acknowledgement IDs returned through the solution.

Ask for evidence of successful IRAS receipt , rather than relying on a screenshot showing an invoice sent to a customer. The official acknowledgement guidance in FAQ 3.20 identifies the acknowledgement ID as receipt evidence. Your finance owner should also reconcile the submission population to the underlying records and document exclusions; a successful transmission does not itself validate the GST treatment.

Apply the earlier-date rule to each GST return

Once your business is subject to the requirement, invoice data is due by the earlier of the actual filing date and the due date of the relevant GST return. The relevant period depends on the transaction date: generally the document issue date for invoiced supplies, with invoice-date or permitted posting-date treatment for purchases. Configure those rules with the provider using the IRAS submission-scope and deadline instructions .

For example, if the relevant return is due on 31 October but you file it on 20 October, the invoice data deadline is 20 October. Filing late does not move that deadline beyond 31 October. This comparison is a scheduling rule, not an invitation to hold every invoice until return preparation: arrange regular transmission and review failed submissions before authorising the return.

The population is broader than invoices exchanged with another Peppol user. Relevant sales and purchase data, including credit notes, can require solution-extracted submission even when the customer is outside the network. IRAS permits aggregation for specified point-of-sale supplies, simplified invoices and petty cash purchases. Its exclusions include reverse-charge transactions, import permits, certain exempt financial transactions and entries without underlying supplies or purchases.

Keep the return-filing and record-retention work active. If transmission fails, the practical response is to identify the rejected record, correct the data with the provider, resubmit through the solution and confirm receipt. If the GST return itself is wrong, assess that tax correction separately; retransmitting invoice data does not amend the return. Do not treat calibrated initial enforcement as a general exemption from compliance.

Set an InvoiceNow date you can substantiate

Set your InvoiceNow date only when the route, evidence and assigned phase agree. For a current new voluntary applicant, make transmission readiness part of the GST registration work. For a remaining existing business, retain the 2025 calculation and IRAS notification, then schedule provider work backwards from the applicable future start date.

Escalate an unexplained date conflict, unclear exclusion or absent return history before signing off the implementation plan. When the start date is settled, name a finance owner for recurring submission checks and an integration owner for technical failures. The useful handover contains the date rationale, activation evidence and retrievable acknowledgement records—not merely a software purchase confirmation.