Role access
Role-based access control with named users, not shared logins.
GST & record-keeping · compliance guide
Books that stay legible under one amber rule.
A working guide for Singapore SMEs: what your cloud accounting setup has to hold before every filing, and how to check for gaps before the deadline finds them.
- Tax-invoice particulars captured at creation, not added after the fact.
- Standard-rated, zero-rated, and exempt supplies separable in your chart of accounts.
- Five-year retention with an audit trail a standard user cannot erase.
- Retention floor
- Five years from the end of the relevant accounting period.
- Filing cadence
- Quarterly GST returns for most SMEs, reconciled to the bank first.
Security controls your GST records depend on
Data-protection rules sit underneath tax rules: a record you can no longer produce is a record you no longer keep. These are the controls a Singapore SME can check within a platform before trusting it with five years of filings.
Verify each of these in the vendor's own documentation before you sign — the answer is what matters, not the label.
The eight places a GST setup leaks
Each row below is a real configuration gap that turns a quarterly filing into a reconstruction. Read the row against your own platform and note which ones you cannot answer with confidence.
-
Tax invoice
Point-of-entry field
Every particular captured at the moment of invoice creation
Supplier name and GST registration number, invoice number and date, customer details, description, amount before GST, GST rate applied, and total. Your invoicing module should make each field available at creation — the tax invoice example in your own chart of accounts should match.
-
Three categories
Chart-of-accounts mapping
Standard-rated, zero-rated, and exempt supplies must be separable
Map a chart of accounts so each category flows to its own line. A GST return then becomes a set of report totals rather than a manual sort — configure this before your first filing, because reclassifying history is slow and easy to get wrong.
-
Audit trail
Deletion logging
Who created, edited, or deleted a transaction — and when
A real audit trail is retrievable in a form an auditor can follow, and a standard user cannot erase the history. Ask the vendor how deletions are logged; that answer is the difference between an audit trail and a simple activity feed.
-
Reconciliation
Weekly cadence
Bank reconciliation kept current so GST errors surface weekly
When reconciliation is current, the GST return reconciles to the bank as well, and errors become visible early. When it lags, mistakes surface during filing and get investigated under time pressure. Weekly is the practical cadence for most small teams.
-
Multi-currency
Dual-amount storage
Foreign-currency invoices still need GST treatment in SGD
Store the original currency amount and the SGD equivalent on the same transaction, with the rate documented. Platforms that keep only the converted amount create a gap when an auditor asks how the rate was determined.
-
Split invoicing
Mapping required
When invoicing lives outside the accounting platform
Summaries work only if they carry enough detail to reconstruct a tax invoice. At high volume the reconstruction risk grows, so plan the field mapping between the two tools deliberately rather than assuming it will hold.
-
Retention
Five-year minimum
Five years, still readable, even if you change platforms
Cloud storage handles the physical side; the work is ensuring records stay complete across the whole period. Export a full copy of your ledger annually and store it where you control access.
-
Test filing
Pre-filing check
Run one dry-run return before the first live filing
If any line of the sample return needs a manual adjustment, that is a configuration fix to make now — not at 11pm the night before the deadline. It is the single cheapest compliance test an SME can run.
Fields a GST return reads
10
A tax invoice carries ten particulars: supplier identity, GST registration number, invoice number, invoice date, customer details, description, amount before GST, GST rate, GST amount, and total. Your software should be able to produce every one of them without a spreadsheet.
Years records must be kept
5
Singapore GST rules require five years of retained records from the end of the relevant accounting period — retrievable, complete, and in a form an auditor can follow across that entire window.
What to check when you compare platforms
Two shortlists, two ruled tables. Read across a row and ask whether your current setup would answer yes. This is a checklist, not a rating — the vendor's own documentation is the source of truth.
Shortlist A · invoicing side
Does the platform produce a Singapore-ready tax invoice?
- Supplier name and GST registration number
- Invoice number and invoice date fields
- Customer name, address and GST number
- Line-level GST rate on each item
- Description of goods or services
- Total exclusive, GST amount and total inclusive
Shortlist B · ledger side
Does the ledger hold up when the auditor asks?
- Audit trail shows editor, action and timestamp
- Deletions logged, not just edits
- Standard user cannot erase the trail
- SGD and original currency on the same transaction
- Exchange rate documented at booking
- Full ledger export you control annually
Who this page is written for
Small teams, real GST exposure, no CTO on staff
Most Singapore SMEs running six to twenty staff hold GST registration because their turnover crossed the threshold, not because they set out to be tax experts. Records get filed because the deadline is fixed and the return is due — not because anyone in the room enjoys reading IRAS guidance at 11pm.
That is the shape this guide is written for. Every check below is something one person at a desk can verify, with or without an accountant in the room. Where a topic belongs to a specialist, the page says so and points you sideways rather than trying to replace them.
- Choose a platform that captures GST fields at the point of entry.
- Configure categories and currencies before the first filing, not after.
- Verify the audit trail and retention policy in writing before you sign.
Where to start
If you have no platform yet, begin with the choosing guide — it maps GST fields onto the shortlist criteria most Singapore SMEs actually compare.
If you are already running
Do the dry-run test filing described in the ledger rows above. One Friday afternoon spent on a sample return prevents a rushed quarter-end.
Questions we cannot answer
A guide is a starting point, not advice. For treatment of a specific transaction, engage a Singapore-registered tax professional — they will want to see your records, not a summary of them.
Keep reading where it helps
Three paths depending on where you are. Pick the one that matches your current state, or write to the editorial team if none of them does.
Choosing software
Which platforms hold GST fields without a spreadsheet
The choosing guide walks through the shortlist criteria Singapore SMEs actually compare — GST-ready invoicing, multi-currency handling, and the configuration work that follows a signed contract. It is written for the buyer, not the vendor.
Platform reviews
Where each named platform holds up
Reviews structured around role-based access control, reconciliation pace and export completeness — the three things a GST filing actually stresses.
Operations
Running the ledger without a filing scramble
A practical operations guide for the small team: weekly reconciliation routines, month-end close joins, and how to keep the record layout stable when staff rotate or grow.
Write to us
If a topic is missing, tell us
The editorial team rewrites this page when readers flag gaps. If your setup exposed a check we have not covered, send a note.