GST InvoiceNow transaction map: what to send and exclude

A GST InvoiceNow transaction map should separate four things: reportable supplies, reportable purchases, excluded transactions and purchases that are not reportable for input tax. It should then show the source system, GST category code, transaction date and correction process for each flow.

The map is a finance control, not just a software setting. IRAS still expects the GST return and the transmitted invoice data to follow the underlying transactions and GST treatment.

Identify the legal entities and systems

Start with every Singapore GST registration in the group. List the UEN, GST registration number, accounting system, billing system, expense tool, point-of-sale system and any manual journal source. Identify overseas branches and shared service centres that create entries for the Singapore registration.

For this reason, the current IRAS GST InvoiceNow page says GST-registered businesses must submit invoice data using InvoiceNow-Ready Solutions in phases. Overseas entities and businesses registered wholly because of reverse charge are excluded businesses. A Singapore business that has reverse charge transactions is not automatically an excluded business.

Confirm the implementation date separately. The transaction map should work for testing before activation and for live submissions after activation.

Map reportable supply flows

List standard-rated, zero-rated and exempt supplies that produce invoices or equivalent documents. Include sales invoices, credit notes, debit notes, customer self-billing where applicable, related-party charges and recoveries of expenses. Mark the document type and where its GST code is assigned.

In practice, IRAS states that the transaction date for supplies is the document issue date where an invoice is or will be issued. For other supplies, it is generally the date posted into the accounting system. The relevant GST return is the return covering the accounting period when that transaction occurs.

Test unusual flows rather than only the main sales ledger. These include deposits, milestone billing, net settlement between related parties, rebates and bad-debt adjustments. The map should say whether a new invoice record is sent, an earlier record is corrected or the item is handled outside the data scope.

Map purchase and input-tax flows

For purchases with a supplier invoice, IRAS permits the transaction date to follow the document issue date or the posting date where the business claims input tax by that posting method. Use the method that matches the accounting and GST process. Do not switch dates only to move data between returns.

At the same time, Separate purchases from GST-registered suppliers, zero-rated purchases and other reportable purchase types from non-reportable purchases. The IRAS e-Tax Guide gives examples of non-reportable purchases, including purchases from non-GST-registered suppliers, blocked input tax expenses, exempt purchases and certain out-of-scope purchases.

Add a vendor-GST-status check and a blocked-input-tax flag. If the accounting system defaults every local invoice to a reportable purchase, the submission can include data that does not support an input tax claim.

Create a controlled exclusion list

IRAS excludes transactions with no underlying supply or purchase that are reported only for GST purposes. Examples include deemed supplies and goods exported without a sale. Reverse charge transactions, exempt financial services, exchange or loan of digital payment tokens and import permits are also excluded from the data scope.

As a result, an exclusion should have a rule, owner and reason code. Avoid a free-text omit button. Review the exclusion list against the current official guide whenever IRAS changes the scope.

Sample both sides of the rule. Pick records that the system excluded and confirm that exclusion was correct. Then pick reportable records from the source ledger and confirm that they reached the submission file. Testing only transmitted invoices will not find transactions that disappeared before validation.

Design correction and exception handling

Decide what happens when an invoice fails validation, a supplier’s GST status is wrong, a credit note arrives late or the accounting entry changes after transmission. Give finance a daily exception queue with the source record, error, owner, action and resubmission status.

For example, the IRAS InvoiceNow FAQ addresses common scenarios such as expense recovery, branches and reverse charge. Use it with the e-Tax Guide instead of inventing a general rule from one invoice example.

Reconcile submitted records to the sales and purchase ledgers by accounting period. Then reconcile the GST category totals to the relevant GST return boxes. Investigate differences before the return is filed.

Keep a change log for tax codes, mapping tables and software releases. A small configuration change can affect thousands of records. The log should show the request, approval, test evidence, deployment date and first-period review.

Meet the transmission deadline

In addition, Invoice data must reach IRAS by the earlier of the date the relevant GST return is filed and its filing due date. A business that files early shortens its own submission window. Put the InvoiceNow reconciliation before the return approval in the close calendar.

Keep evidence of transmission status, rejected records, corrections and the final reconciliation. The access point or software provider operates the technical channel, but the GST-registered business remains responsible for the tax treatment and complete return.

The Singapore transfer-pricing workflow remains the tax pillar cornerstone. The GST InvoiceNow date guide identifies the implementation phase, while the supplier onboarding guide covers vendor data. The Corporate and International Tax Consulting hub lists related guidance.

For this reason, a useful transaction map makes exclusions visible and reviewable. It gives finance a way to explain both why a record was transmitted and why another record was left out.