When a notice arrived for a small café, the owner felt a jolt. She thought it meant wrongdoing, but the visit was a structured review by IRAS to check the accuracy of her goods services tax return. The team looked for clear records and simple explanations.
The aim here is practical. This short guide defines the title and description of the review from initial notice to outcome. It shows how a business can respond professionally, keep disruption low and protect cash flow.
Effective preparation means tidy books, an audit trail that anyone can follow, and a repeatable way to produce documents quickly. Selection for review does not equal blame. The goal is correct tax outcomes and fair compliance.
This article previews each stage, from selection and contact methods to visit, data listings, interviews, adjustments and dispute options. It also explains why getting this right matters for ongoing operations and governance.
Key Takeaways
- IRAS reviews are risk‑based checks, not automatic accusations.
- Prepare with clean records, clear trails and ready personnel.
- Follow defined stages to reduce disruption and protect cash flow.
- Know your rights on adjustments and how to raise concerns.
- Treat the review as a compliance exercise that strengthens controls.
What a GST audit is and what IRAS is trying to achieve
These reviews test whether transactions and reports line up across your books. They are a structured check of whether GST has been accounted for in business dealings and then correctly declared in GST returns.
How checks verify information
- Supply classification: whether supplies are standard-rated, zero-rated or exempt.
- Charging and accounting: whether tax was applied and recorded correctly.
- Input claims: whether input tax is supported and legitimately claimed.
- Completeness: that values in returns match ledgers and documents.
Key purposes of the programme
IRAS aims to ensure compliance with tax laws, to educate businesses, and to spot areas where rules or guidance could be clearer.
Why selection is not proof of wrongdoing
Being selected for review does not mean you made errors. Cases are examined fairly and the review is also a chance to strengthen controls and reduce future compliance risk.
How businesses are selected for a GST audit in Singapore
Selection is driven by risk indicators rather than proof of wrongdoing. IRAS reviews span many industries and include periodic compliance checks to see if companies follow reporting rules.
Risk-based selection combines automated scoring with sector profiles. That means audits target areas where returns, filings or behaviour look unusual compared with peers.
Common triggers that raise scrutiny
- Inconsistencies between returns and accounting records, or out‑of‑balance figures.
- Large or unusual deductions, sudden losses, or unexpected year‑to‑year swings.
- Cash‑heavy transactions with weak paperwork, or irregular supplier/customer flows.
- Late, incomplete or repeated non‑responses to information requests.
- High‑risk sectors such as F&B, construction and retail due to volume and cash handling.
Types of review range from standard compliance checks to investigation‑style enquiries. Most selected audit cases are routine; being selected does not mean you committed an error.
Respond promptly and keep clear records. For more on obligations and terms, see our terms and conditions.
gst audit singapore process: what to expect from start to finish
A review usually unfolds in clear stages, so you can plan staff time and documents.
Initial contact often arrives by email or letter. That is followed by requests for listings and key records. Telephone interviews clarify queries and set timings for any visit.
Field visits focus on workflows, controls and how transactions are recorded in your accounting system. Allocate a point‑of‑contact and allow sufficient time on the day for demonstrations and questions.
Verifying identity and third‑party checks
IRAS officers carry an authority pass. To confirm identity, call IRAS at 6351 2044 or 6351 2046 before letting anyone in.
Inspectors may seek confirmation from customers, suppliers or banks to verify the genuineness of transactions. Keep contracts, invoices and bank receipts matched to ledger entries.
What a system demonstration covers
Be ready to show how sales and purchase flows move from source documents into your software. Explain GST codes, controls around edits and credit notes, and how exceptions are handled.
An audit necessarily is a verification exercise. A calm, organised walkthrough reduces follow‑ups and helps the review close faster.
Preparing before IRAS contacts you further
Start with a targeted review of past returns to spot gaps and simplify corrections. A short, focused check reduces disruption and gives your team clarity on next steps.
Pre‑audit readiness checklist
- Assign owners: confirm who is responsible for GST, who extracts system data and who will coordinate replies.
- Map data sources: identify ledgers, sales systems and filing locations for quick retrieval.
- Prepare a contact list: include staff, advisors and software support for rapid queries.
Reconciling returns and ledgers
Reconcile output and input tax totals to the general ledger. Ensure figures in gst returns match accounting reports and note any variances.
Document adjustments and the business reason for each difference so you can explain them promptly.
Classification and input‑claim checks
Spot mis‑coding between standard‑rated, zero‑rated and exempt supplies and keep evidence for each treatment.
Review input tax claims: verify invoices, confirm business purpose, and flag mixed‑use or blocked items that need stronger support.
Structured packs with reconciliation schedules, indexed paperwork and a clear map showing where each figure comes from will improve your chance of success. If you find errors, consider early correction—IRAS may reduce penalties under its voluntary disclosure framework. Strong record discipline keeps a review from becoming a disruptive document hunt.
Documents and data IRAS can request during a GST audit
Gathering the right paperwork beforehand saves time and avoids repeated requests. Prepare an indexed folder that groups background, transaction support, listings and control documents.
Business information IRAS may ask for includes how the company operates, main revenue streams, supply‑chain arrangements and who performs key finance roles. Explain roles clearly and attach org charts if helpful.
Supporting documents typically requested are invoices, contracts, payment evidence and export paperwork for zero‑rated supplies. Ensure each transaction traces from ledger to invoice to bank receipt without gaps.
Self‑review checklists and examples
Officers may ask you to complete checklists for specific claims, such as pre‑registration input tax or bad debt relief. Prepare underlying computations and evidence alongside the completed form.
“The Comptroller may require information, documents, computers and software to verify returns.”
Legal powers are set out under Section 84 of the GST Act. The Comptroller can obtain information, records, computers and computer programmes for verification.
| Request category | Typical examples | Why it matters |
|---|---|---|
| Business background | Organisational chart, bank details, sales channels | Shows how figures arise and who is responsible |
| Transaction support | Invoices, contracts, payment receipts, export docs | Substantiates claims and zero‑rated supplies |
| GST listings & data | Sales and purchases listings, reconciliations | Links returns to ledger totals |
| Controls & checks | Policies, self‑review checklists, internal reconciliations | Demonstrates consistent procedures |
Practical response tips: clarify the request scope, agree realistic timeframes, preserve original records and avoid altering documents once the review starts. Where clarification helps, use the official overview of audits by IRAS to confirm expectations.
Sales and purchases listings that support your GST returns
Well-structured listings are the link between your accounting records and the numbers declared on returns.
Accepted file formats for listings
Data listings should be submitted in Microsoft Excel, Microsoft Access or delimited text (txt / csv). These formats let reviewers run checks quickly.
Non-data listings such as narrative summaries or scanned attachments are acceptable as Microsoft Word or Adobe Acrobat (PDF) files.
Required fields for sales listings
Ensure every sales line includes:
- Invoice date and invoice number
- Customer name and a concise description of goods or services
- Invoice amount excluding GST and the GST amount (where applicable)
- Destination of goods for exports, where relevant
Required fields for purchases listings
Purchases must show the following for each transaction:
- Invoice date and invoice number
- Supplier name and the supplier’s GST registration number
- Itemised description, value excluding GST and GST amount (where applicable)
Common extraction pitfalls: missing supplier registration numbers, inconsistent invoice numbering, mixed GST treatments and incomplete destination fields for exported goods.
Quality checks before submission: reconcile listing totals to GST return boxes and your general ledger. Confirm each line item is backed by invoices and supporting documents. Make reports repeatable by using the same filters, codes and period cut‑offs to reduce queries during an audit.
| Listing type | Preferred formats | Key fields |
|---|---|---|
| Sales | Excel, Access, txt/csv | Invoice date, number, customer, description, value excl. GST, GST, destination |
| Purchases | Excel, Access, txt/csv | Invoice date, number, supplier, supplier GST reg. no., description, value excl. GST, GST |
| Non‑data appendices | Word, PDF | Contracts, scanned invoices, transport documents |
How to respond during the audit to keep things moving
Organise one reliable point of contact to streamline all communications with officers. That coordinator logs requests, confirms deadlines and ensures answers are consistent.
Co-operating with access, workspace, interviews and copy requests
Operational cooperation means granting access to premises, records and documents. Provide a dedicated room and make staff who own key workflows available for interviews.
Allow reasonable copying and data extracts. Keep a duplicate set of what you give and note the time and format of each delivery.
Providing timely, complete and accurate replies
Answer requests promptly and fully. Short, accurate returns reduce follow‑up queries and cut the time the review takes.
Being truthful early, including disclosing irregularities and omissions
If you find errors, disclose them early with explanations and corrective steps. Early honesty often improves outcomes and shows good compliance intent.
| Action | Practical step | Benefit |
|---|---|---|
| Appoint coordinator | Single contact for all queries | Consistent replies; fewer delays |
| Request log | Track items, dates and delivery format | Clear audit trail; avoids disputes |
| Copy handling | Provide legible copies; retain originals | Protects records; enables rebuttal |
“Obstructing or hindering an officer is an offence punishable by fine up to $10,000 and/or up to 12 months’ imprisonment.”
Audit outcomes, timelines and how to manage disputes
Completion time varies, yet many cases reach closure within twelve months when records are ready. The length of a review depends on business size, transaction complexity and how quickly you supply clear documents.
Typical completion time and what affects duration
Most cases finish within 12 months. Delays arise from incomplete replies, weak evidence, mismatched returns and ledgers, and slow scheduling of staff interviews or system demonstrations.
Possible adjustments, assessments and penalties
IRAS will notify outcomes in writing and may raise assessments to correct reported values. The outcome letter usually sets out the basis of adjustment, reasons for any penalties and the sums due.
Penalties and serious treatment for fraud
Incorrect returns can attract penalties up to 200% of tax undercharged or over‑claimed. Fraud receives harsher action, including fines and imprisonment. Note the Missing Trader Fraud surcharge: a 10% add‑on may apply where denied input tax involves known risky arrangements.
When and how to object
If you disagree, object promptly in writing within the statutory time. Support your case with reconciliations, original invoices and a clear narrative that explains any differences.
“Respond quickly, organise evidence clearly and ask for clarification of any point you do not accept.”
| Step | What to include | Benefit |
|---|---|---|
| Review outcome letter | Basis of adjustment, penalty reasons, amounts | Clear starting point for objection |
| Prepare objection | Reconciliations, invoices, timeline of events | Stronger case; reduces escalation risk |
| Seek professional help | Advisor correspondence, legal view if needed | Better chance of favourable resolution |
Conclusion
Treat selection for review as an opportunity to sharpen controls rather than a sign of failure. With clear records and timely replies, an audit becomes manageable and often short.
Keep three practical pillars in place: reconciled returns and ledgers, robust supporting documents and listings, and clear internal ownership across finance and accounting systems.
Invest in staff training, computerised accounting and quarterly self‑checks to reduce future risk. Maintain an “audit‑ready” pack each quarter so reviews take less time and cause less disruption.
Where needed, seek professional advisory services to validate treatments and strengthen evidence. Learn more about SG vOffice services at about SG vOffice if you want external support.
FAQ
What is the purpose of a GST audit and what is IRAS aiming to achieve?
How do officers check the accuracy of information in my returns?
Why might my business be selected for review even if there are no errors?
What common triggers increase the likelihood of being chosen for a compliance check?
How will IRAS contact my business and what forms can the review take?
What should I expect during a premises visit and how can I verify the officer’s identity?
Can IRAS contact our customers, suppliers or banks as part of a review?
How should I demonstrate transaction recording in our accounting system?
What preparatory steps should I take before IRAS makes further contact?
How do I spot and fix classification issues in my past returns?
Which input tax claims commonly need stronger support?
What business information and arrangements might IRAS ask me to explain?
Which supporting documents should I provide for transactions such as invoices and exports?
What are self-review checklists and when will I need them?
What statutory powers does IRAS have to obtain documents, computers and software?
What file formats are acceptable for sales and purchases listings?
What are the required fields for sales listings?
What fields must a purchases listing include, particularly regarding suppliers?
How should my team co-operate during the verification to keep the review efficient?
What is important when replying to IRAS requests?
Should I disclose irregularities or omissions early in the review?
What are the consequences of obstructing an officer under Section 66 of the GST Act?
How long do typical reviews take and what affects the duration?
What outcomes can arise from a compliance check?
What penalties apply for incorrect returns and for fraud?
How do I object if I disagree with an assessment or decision?
Dean Cheong, CEO of VOffice, is a Singapore-based specialist in scaling B2B businesses. His work centers on optimizing sales operations, launching effective go-to-market strategies, and leveraging CRM tools to drive consistent revenue expansion. With a foundation in business banking and finance from Nanyang Technological University, Dean brings both strategic insight and real-world execution to every engagement.