Raffles Consulting Services
GST InvoiceNow reconciliation should tie submitted invoice data to the GST return and document legitimate timing, scope and input-tax differences.
GST InvoiceNow reconciliation should compare invoice data transmitted to IRAS with the figures in the relevant GST return before that return is filed. The totals will not always match exactly. IRAS recognises legitimate differences, but the business must keep records that explain them and substantiate both its GST reporting and invoice-data submissions.
The close process should therefore produce a bridge, not force every difference to zero. Each reconciling item needs a category, amount, source document, owner and resolution.
Set the reconciliation cut-off before return approval
The IRAS GST InvoiceNow page says invoice data must be submitted by the earlier of the date the relevant GST return is filed and its filing due date. A business that files early brings forward its invoice-data deadline.
For this reason, put the submission extract and reconciliation on the return calendar. Freeze the source period, capture accepted and rejected transmissions, and record late corrections. The GST return approver should see the completed bridge before authorising filing.
Do not rely on a dashboard total without a transaction export. Keep invoice number, credit or debit note reference, customer or supplier, date, GST category, taxable value, tax amount, submission identifier and status.
Start from reportable transaction populations
IRAS generally requires invoice data for standard-rated and zero-rated supplies and purchases, plus exempt supplies, where the transaction is reported in the GST return. The exact transaction and document rules remain subject to the current e-Tax Guide.
In practice, create separate sales and purchase populations from the ledger. Map each tax code to the InvoiceNow GST category and the GST return box. Test the mapping after every accounting-system or software release.
Identify invoices that failed validation, were never sent or were transmitted twice. IRAS’s pilot findings highlighted poor validation, inconsistent category codes, duplicate corrections and incomplete transmission as common weaknesses.
Build a bridge by reason, not by plug
The official GST InvoiceNow FAQ says businesses should perform due diligence so submitted invoice data tally with the GST return. It also identifies legitimate differences including timing, supplies without invoices, input tax not claimed in full and corrections made in a later return.
| Difference | Example | Evidence |
|---|---|---|
| Timing | Payment triggers time of supply before the invoice is issued | Receipt, invoice and period calculation |
| No invoice required | Deemed supply or reverse charge reported in the return | GST working and source transaction |
| Input-tax treatment | Purchase tax is blocked, apportioned or not claimed | Attribution calculation and tax code |
| Correction timing | Error corrected in a later F5 rather than an F7 | Error log and later-return reference |
At the same time, give every difference a reason code that describes the tax fact. Avoid a broad manual adjustment code that conceals several unrelated causes. Finance should be able to trace the bridge from the return total to the individual records.
Separate transactions that need no invoice-data submission
IRAS lists transactions for which invoice data need not be submitted, including transactions without underlying supplies or purchases that are reported for GST purposes, reverse charge transactions, certain exempt financial services and import permits for goods.
Purchases from GST-registered suppliers where no input tax is claimed also fall outside the mandatory scope, although IRAS permits voluntary transmission using the stated category code. Decide the system treatment and apply it consistently.
As a result, maintain an exclusion register. Record the rule, ledger source, period total and reviewer. An exclusion is not missing data when the current guidance supports it and the evidence is retained.
Reconcile corrections without creating duplicates
When an invoice changes, use the correction or resubmission method in the e-Tax Guide and the solution’s approved workflow. Do not send a second unrelated invoice merely to overwrite the first. Link credit notes, debit notes and corrected records to the original submission.
Keep the latest accepted status and the history of attempts. Review sequence numbers and unique identifiers for duplicates. A correction that fixes the GST amount but leaves two active records can widen the reconciliation difference.
Investigate tax-code and master-data failures
For example, differences often begin upstream. A supplier may be coded as GST-registered when it is not, a customer country may be missing, or a product may use the wrong tax code. Route exceptions to the owner who can correct the source data rather than posting a recurring period-end journal.
Track rejection rate, duplicate rate, unsubmitted eligible invoices, manual category overrides and aged exceptions. Review trends with the InvoiceNow-Ready Solution Provider or Access Point Provider, while keeping tax responsibility with the GST-registered business.
Retain one signed period file
The period file should contain the ledger populations, transmission extracts, reconciliation bridge, exception log, tax-code mapping, correction history, return workings and approval. Record the software version and extract time so the result can be reproduced.
In addition, compare the final bridge with the next period’s opening exception list. Items carried forward should keep the original invoice reference, tax amount, reason and promised resolution date. Close them only when the transmission status, accounting record and GST treatment agree. This prevents a timing difference from becoming a permanent unexplained balance.
Have a reviewer who did not prepare the bridge test a sample from both directions: return to invoice data and invoice data to return. Record the sample, exceptions and conclusion. This catches omitted records as well as unsupported amounts.
The Singapore transfer-pricing workflow remains the tax pillar cornerstone. The InvoiceNow transaction map defines what to send, while the supplier onboarding guide covers vendor data. The Corporate and International Tax Consulting hub lists related guidance.
For this reason, a good reconciliation can contain differences. What matters is that every difference is legitimate, quantified and supported before the return is filed.