GST, InvoiceNow & IRAS filing in Singapore
The ledger only moves when the money does.
A working guide to the compliance tasks a cloud accounting setup in Singapore genuinely supports: GST treatment at the transaction, InvoiceNow submission data, IRAS return figures, and the close that has to happen before the filing deadline.
Where GST actually lives in the workflow
GST is set when the transaction is created, not when the quarter ends.
A sale takes its tax code when the invoice is raised. A purchase takes its code when the bill is entered. Keep that discipline and the GST return becomes a report you review rather than a reconstruction you perform. Let it slip and the last week of the quarter goes on chasing descriptions from three months ago.
The pattern matters more than any single platform: by the time you reach the return, the figures either already exist as a byproduct of ordinary bookkeeping, or they have to be rebuilt from memory. Most of the work in getting GST right is done in the two weeks before you think about it.
InvoiceNow and IRS filing, in order
InvoiceNow changes where the data comes from. IRAS filing stays your job.
InvoiceNow means invoice data moves in a structured format rather than being retyped into a portal later. Platforms that support it capture the invoice once and reuse the same record for GST and for record-keeping. Xero, for instance, highlights InvoiceNow support for Singapore alongside cloud access with MFA login.
The practical benefit is fewer transcription errors and less double entry. It is not a magic filing button, and it does not move responsibility onto the software. What it does move is where the clerical effort sits: on the person raising the invoice rather than on the person preparing the return.
What the software produces
- Structured invoice data ready for reuse in GST and record-keeping.
- GST return figures compiled from transactions you already coded.
- Submission data prepared on some plans, ready for you to review.
What it does not do
- Take responsibility for accuracy. Review and sign-off stay with you.
- Replace the obligation you hold as the registered business.
ACRA BizFile+ stays outside the ledger
Statutory filings are a different system.
Annual returns, changes to company particulars and registration matters do not flow through your accounting software. They sit with ACRA's BizFile+ portal, on a separate filing rhythm with its own deadlines.
This matters at handover. A founder hands the bookkeeping to a provider and assumes the archive covers everything, then discovers at year-end that the statutory side was never part of the arrangement. Businesses run by one person are the ones most likely to find out late, because there is no second pair of eyes asking who filed the annual return.
The fix is dull and cheap: write down which system owns which filing, and who is responsible for each entry. Do it once and it stops being a surprise.
Month-end close when a GST deadline is attached
Reconcile first, decide GST second, produce the figures last.
The close gets harder in the quarter that ends on a filing deadline. Sequence it deliberately and the deadline stops being the risk. Lock the period before you extract figures, because a transaction posted afterwards creates a mismatch that takes an afternoon to untangle.
-
First
Reconcile the bank
Every statement line matched, or explained in a note. Unreconciled items distort the tax figures later.
-
Second
Review receivables and payables
Check that the amounts owed line up with the documents behind them before they enter the return.
-
Third
Check unusual transactions
Mixed-purpose expenses, one-off purchases and anything with a GST treatment that is not obvious.
-
Fourth
Produce the return figures
Compile the GST return from data that is already coded, reconciled and reviewed.
-
Fifth
Lock the period
Post-lock adjustments go into the next period, so the filed figures and the ledger stay in agreement.
Skip the sequence and the extra work lands exactly where you least want it: in the week of the filing, when every hour you spend fixing the past is an hour not spent reviewing the present.
Why this belongs to the cash question
The GST quarter bulges in the weeks it collects.
Get GST treatment right and the quarterly filing becomes the point at which you know what the collection side actually holds. Get it wrong and the figures land too late to plan around. Either way, the compliance calendar and the cash-flow forecast are the same conversation.
Four question marks recur: is input tax being claimed on the right basis, are collections tracking toward the settlement, does the quarter close leave enough runway for the payment, and is the whole thing going to be reviewable if anyone asks.
Quarterly rhythm, twelve weeks
Weeks one to twelve
Weeks one to four
Collections build
Weeks five to eight
GST coding settles
Weeks nine to eleven
Close and review
Week twelve
Return filed
Treat the shape as a reminder rather than a forecast. Collections and payments move at different speeds in every business; what does not move is the date the figures are due. Read the fuller version in the cash flow reporting guide.
Where bundled support genuinely helps
Handing over the administrative layer.
Sleek operates where compliance and bookkeeping are tightly linked, offering incorporation, corporate secretarial and accounting support together. For a founder with no interest in learning a ledger, handing the whole administrative layer to one provider removes a category of work rather than a task.
The trade-off is visibility. You see reports, not transactions. That is acceptable if you want the numbers explained to you, and uncomfortable if you want to know which supplier the payment went to. Both are reasonable positions; the mistake is not choosing one on purpose.
Multi-entity and consolidation
One company is simple. A group is not.
Once there is more than one entity, GST treatment, intercompany transactions and consolidated reporting all step up in difficulty. This is where Oracle NetSuite enters Singapore shortlists, because consolidation and multi-subsidiary reporting are core to the product rather than bolted onto an SMB tool. SAP Business One Cloud handles multi-entity needs as part of a wider implementation.
Neither of those is a casual decision to make on a Tuesday afternoon. Both assume a finance function rather than one person with a laptop, and both bring implementation effort that the monthly fee does not include. If you are still a single entity, this is a chapter to remember rather than act on.
Keeping records that survive scrutiny
The useful test is not the deadline. It is whether you can produce the document.
Singapore requires business records to be kept for a defined period, and the practical version of that requirement is simple: can you produce a document for any transaction, quickly, without asking a former employee. Cloud storage solves the retrieval half of that problem, but only if the document is attached to the transaction at the time it is entered.
The failure mode this prevents is a shoebox scanned in year five. Attaching paperwork as you go costs a minute per transaction. Reconstructing it at the point of an enquiry costs a week, and you get to do it under someone else's deadline.
Three mistakes worth avoiding early
None of these are the software's fault.
All three are avoidable with a routine you can write on one page.
-
One
Coding from the bank feed with no description
The line gets matched, the amount balances, and six months later nobody can say what the payment was for. Write something on the entry while you still know. It costs ten seconds.
-
Two
GST on mixed-purpose expenses, unreviewed
Apportionment is a judgement, not a lookup. Recording GST on an expense that serves both business and personal use without checking the split is a quiet error that stacks up across a quarter.
-
Three
Leaving the first return until the deadline
The first GST return teaches you the shape of the ones after it. Do it early once, on a quarter that is already closed, and you learn the sequence while nothing is on fire.
The software does the arithmetic. You hold the obligation.
That framing survives every platform comparison on this site, and it survives the next round of product releases too. When a vendor claim reads as if the filing responsibility has moved, read it twice.
Where to take this next
Three pages worth reading in order.
-
First
Bank Feeds & Bank Reconciliation
Because GST treatment starts with coded transactions and a clean bank feed, not with the return.
-
Second
Compare Cloud Accounting Software
Where InvoiceNow support, GST handling and IRAS workflow sit alongside pricing and support models.
-
Third
How We Review and Update
The method behind these guides, and how we handle a platform change after publication.