GST InvoiceNow Data Readiness: How Finance Teams Can Prepare Invoice Data for IRAS Submission

While most learning about the e-Invoicing initiative of Singapore focuses on the platforms and access points, the fact of the matter is that an invoice submission to IRAS hinges on its data. This is because under GST InvoiceNow, GST-registered organizations will have to submit their invoice data to IRAS via the InvoiceNow Network. Any weaknesses in data relating to customers, taxation or numbering would then be transferred to every single invoice that is created. The following six points list areas of GST InvoiceNow readiness.

1. Timeline and scope

New voluntary GST registrants have been in scope since 1 April 2026, while IRAS has advised existing registrants of their implementation dates since mid-2026. As far as existing registrants are concerned, the schedule is phased; new compulsory registrants and businesses with supplies of up to SGD 200,000 annually become subject to the requirement from 1 April 2028, and up to SGD 1 million in 2029, SGD 4 million in 2030 and above SGD 4 million in 2031.

The requirement affects every GST-registered business, so planning InvoiceNow Singapore at a group level requires identification of each registered entity, the date and internal owner of it.

2. Master da`ta

The accuracy of invoice data depends on accuracy of the record data it is derived from. Businesses are registered in the SG Peppol Directory with their UEN number, so the entity master data should be accurate, updated and non-redundant. Master data related to customers and suppliers require the same attention: legal name, GST registration number and address are needed.

Peppol ID used by trading partners exchanging invoices across the network is based on the UEN number of the partner, so the absence of the number or its inconsistency could hamper it.

3. Tax coding and invoice fields

For structured invoices, every tax classification and amount needs to be in its own field. It is common practice to assess how the ERP codes GST for standard rated, zero rated, exempt, and out-of-scope supplies, and verify the line amounts, discount, rounding, and total.

The Singapore e-invoicing solution provider can provide the field specification used for IRAS InvoiceNow submission, which will facilitate a field-by-field comparison of what the ERP generates. Problems are simpler to solve now than when in live use, especially where free text fields are used to hold information which would appear in a defined field under a structured format.

There could also be differences in currency, date format, and unit of measure values that must be catered for with a defined rule.

4. Documents beyond the standard sales invoice

It is a fact that having an approach that includes standard sales invoices alone creates room for other areas of weakness. For instance, credit notes, debit notes, adjustments, foreign currency invoices and recurring billing all must be considered.

It is worth noting that while according to IRAS guidance, invoices that are transmitted over the Peppol network differ from invoices that are directly extracted from a business’s solution and therefore have different submission processes. It is always helpful to understand which process will apply to which transaction. Recurring and batch billing should be specifically considered because if there is any mistake in the template, then many documents will be affected.

The Peppol network does not support business to consumer transactions; therefore, how such sales will be treated is advisable to verify from IRAS guidance.

5. Testing and reconciliation

The technical onboarding process includes dealing with the accredited access point by the IMDA, integration with IRAS and activation of the submission functionality. Next, a test with a sample of actual invoices is more meaningful than a test with clean invoices.

The submitted information could be compared with the company’s ledger and the GST return, making sure the figures and amount of tax reconcile, while recording each failed submission and its reason. Reconciliation process for the GST InvoiceNow has higher value compared to the testing as it will keep working during growth of the volume of transactions and entities involved.

The parallel processing done prior to implementation will demonstrate how the process works with the company’s own data. The edge cases found in the previous stages should also be included into the test set. This includes the credit notes and invoices to customers with incomplete data.

6. Ownership and monitoring

Data readiness does not end once a system goes live. In many companies, finance is responsible for master data and tax codes, IT is responsible for integration and connectivity, and tax or compliance is responsible for understanding and interpreting the rules. Clarifying in advance which group will be responsible when a submission is late or missing data saves time when the deadline is approaching.

Basic performance indicators like percentage of data accepted the first time, number of open exceptions, and time taken to resolve exceptions provide good insight into the current situation and reveal recurring root causes. Reviewing these metrics monthly, along with other last-minute processes, helps maintain data quality.

Readiness checklist

The checklist below condenses the six areas into questions that finance, IT and tax teams can work through together.

Conclusion

Data preparation is the part of the programme that finance teams’ control most directly. A confirmed timeline, clean master data, aligned tax coding, tested edge cases, reconciled results and named owners reduce the likelihood of surprises when submission starts, and they make later phases easier to absorb as business volumes and entity structures change. Treating the work as an ongoing control rather than a one-time project helps organisations keep pace with changes in rules and systems.