Question: Could a routine review change the way your company treats record keeping and compliance?
An IRAS review is often part of the Self‑Assessment system and does not always mean wrongdoing. Clear books and tidy digital trails make queries administrative rather than confrontational.
Preparation is a business habit: disciplined bookkeeping, reconciliations and simple internal controls keep risk low. The typical process moves from notification to information gathering, follow‑up questions, findings and resolution.
Today, tax authorities use data analytics and AI more widely. High‑quality records and prompt responses reduce scrutiny and cut the chance of penalties.
This guide shows a calm, step‑by‑step approach. You will learn about desk versus field reviews, how to read the letter, what documents to gather, common focus areas such as GST, corporate income tax and employment tax, and sensible next steps when errors arise. Seek early professional advice for complex cases.
Key Takeaways
- An IRAS review can be routine; it does not always imply misconduct.
- Good bookkeeping and clear digital trails cut risk and speed resolution.
- The usual process: notice, information request, queries, findings, resolution.
- Data analytics and AI increase scrutiny; reconciliations matter now more than ever.
- Audit readiness is a discipline of people, systems and internal controls.
- Get early professional support for complex or high‑risk issues.
Understanding an IRAS audit in Singapore and why it happens
Not every review from the revenue authority signals wrongdoing; many are standard health checks on filings. The inland revenue authority runs checks to deter non-compliance, protect system integrity and confirm that reported figures reflect real transactions.
Audits are not always punitive: routine checks, industry focus and random selection
Selections follow three routes: routine or random reviews, industry campaigns aimed at high‑cash or complex sectors, and risk profiling based on data anomalies. The revenue authority singapore may target specific trades when patterns look unusual.
How analytics, AI and third‑party matching spot discrepancies
IRAS uses data analytics and AI for cross‑year checks, benchmarking and quick nudges during e‑filing. Automated prompts flag numbers that stray from history or peer norms.
Common triggers and what a trigger really means
Frequent signals are unusual income swings, sudden spikes in expenses, persistent GST refunds and profit margins out of line with peers. Third‑party matches — CPF, ACRA or supplier records — often create discrepancies that prompt reviews.
“A trigger is a starting point, not a finding.”
The best defence is routine prevention: accurate tax filings, regular reconciliations and clear documentation make reviews administrative rather than adversarial.
How to prepare for IRAS audit Singapore before any letter arrives
A steady compliance rhythm keeps queries short and factual, not adversarial.
Build an audit-ready culture with clear governance
Audit-ready means written policies, approval matrices and segregation of duties. These show consistent tax and compliance intent. Keep a simple tax governance note that explains who signs off on filings and returns.
Run regular internal reviews
Set a repeatable cadence: monthly reconciliations, quarterly GST checks and year‑end health checks. Regular review finds small errors early and reduces follow-up information requests.
Train employees and tidy documentation standards
Train every employee who handles revenue, payroll, procurement or accounting. Teach what supporting documents are needed and how to store them with consistent naming and version control.
Keep clean digital trails: match bank payments to ledger entries and retain audit logs that show who changed records and when. Strong routines cut disruption and shorten any subsequent review.
Know what type of IRAS review you are facing
Knowing which review you face shapes the next steps and who should lead the response.
Desk reviews and what a letter usually asks
Desk audits are mostly handled by correspondence. IRAS will send a letter or email with a list of documents and questions.
Typical requests include specific invoices, bank statements, schedules and reconciliations. Responses are filed via myTax Portal and often close the matter quickly when records are clear.
Field reviews and on-site checks
Field reviews involve an on-site visit, system walk-throughs and operational checks.
Officers may interview staff, test internal controls and view live records. Treat these as time-sensitive and factual engagements.
When an enquiry becomes an investigation
An investigation is broader and more formal. IRAS can gather statements and expand the scope across years and tax areas.
Best practice: engage a tax adviser or legal counsel early if the matter escalates. The notice content — the named years, the tax type and the letter wording — is your starting point for a disciplined response plan.
Read the IRAS audit notice properly and set up your response plan
A clear reading of the notice gives you the facts you need to plan a calm and efficient reply.
Confirm scope, tax type and Years under review
Start by identifying the tax type and the exact years named in the letter. Note any specific line items under review and the scope of requested information.
Map deadlines and plan extension requests
Deadlines are commonly 14–21 days and may extend to 30 days in serious inquiries. Create a workback schedule from the stated deadline.
If you need an extension, contact the assigned officer early, explain the volume of records, and propose a realistic new timeline.
Appoint a single liaison and keep one narrative
Assign a single point of contact — a finance manager, accountant or tax agent — to liaise with officers. This reduces confusion and ensures consistent messages.
Document every touchpoint: emails, calls and uploaded files. Map each line in the letter to the schedules and attachments you provide.
| Task | Owner | Internal cut-off |
|---|---|---|
| Identify tax types and years | Finance lead | Day 2 |
| Gather requested information | Accounting team | Day 10 |
| Internal review and sign-off | Head of finance | Day 13 |
| Submit via portal / request extension | Designated liaison | Day 14 |
Next step: success often depends on record quality and completeness under local retention rules; gather source documents with care.
Get your documentation and records audit-ready under the five-year rule
Retention requirement: Businesses must keep accounting and transaction records for at least five years after the relevant filing period. That span covers source materials and the ledgers that support a tax position.
Source documents to compile include sales and purchase invoices, receipts, credit and debit notes, and bank statements. Organise these by year and by transaction cycle so each invoice links to a bank entry.
Accounting pack and digital backups
Prepare the general ledger, trial balance, financial statements and tax computations with clear cross-references to supporting schedules. Export accounting software files and keep backups (for example, Xero or QuickBooks exports) plus reconciliation reports.
Evidence for specific treatments
For GST zero-rated exports, include bills of lading, export permits and shipping manifests that demonstrate movement of goods. Keep a concise schedule tying each claim back to the underlying invoice and bank proof.
Document hygiene and an audit file index
Scan legibly, use consistent file names and ensure pages are complete. Apply the same filing logic across all years to avoid apparent discrepancies.
- Return → computation → ledger → invoice → bank proof: index every item.
- Keep a short audit file index listing file names and the claim they support.
Focus areas IRAS commonly tests during a tax audit
Tax reviews typically focus on a few predictable risk areas that businesses must check first.
GST compliance checks
Output tax accuracy is tested against sales records at 9%. Officers check for missing invoices and mismatched rates.
Input tax on blocked items, such as company cars or family benefits, often leads to adjustments when claims lack clear documentation.
See the GST audits overview for common expectations.
Corporate income tax
Checks focus on revenue recognition timing and correct accruals at year‑end. Revenue must tie to bank receipts and contracts.
Expense claims must be wholly and exclusively for business. Provide invoices, purpose notes and approvals for contested items.
Employment tax
Payroll and AIS reporting for bonuses and benefits‑in‑kind must match filings. Reconcile pay runs with submitted schedules.
Related‑party transactions
Expect documentation proving arm’s length prices: agreements, pricing notes and benchmarking for services or goods.
- Run a revenue‑to‑bank tie‑out.
- Sample top expenses and check proofs.
- Confirm GST rate application on representative invoices.
| Area | Typical checks | Key evidence | Common pitfalls |
|---|---|---|---|
| GST | Output completeness; blocked input claims | Sales invoices; shipping docs; purchase invoices | Wrong rate; missing export evidence |
| Income tax | Revenue cut‑off; expense legitimacy | Contracts; bank statements; approvals | Timing errors; personal expenses claimed |
| Employment | AIS reporting; benefits‑in‑kind | Payroll reports; benefit logs | Unreported bonuses; mismatched pay runs |
| Related parties | Arm’s length pricing | Agreements; transfer pricing notes | No documented rationale |
Manage the audit process smoothly from submission to findings
A clear submission pathway keeps questions targeted and shortens the overall review timeline.
Information gathering and submission
Package responses point-by-point. Match each request in the list with the relevant schedule and upload via myTax Portal. Label files so officers can find the exact proof without extra notes.
Include a short cover note for complex items explaining the linkage between ledgers, supporting documents and bank entries. This reduces rounds of questions and speeds the tax review.
Handling follow-up queries
Keep one master narrative and a single contact for all queries. Ensure computations align with your ledgers and that anyone replying uses the same wording.
Create a “one source of truth” audit folder that contains final versions of submitted records, a simple index and a change log. This prevents conflicting explanations during later clarifications.
Findings letters, adjustments and disagreement workflow
Findings letters usually set out the proposed adjustments, the basis and any additional tax or related revisions. Read the letter carefully and map each point back to what you submitted.
“Respond with evidence and a clear technical note rather than an emotional objection.”
If you disagree, identify the specific issue, supply extra evidence and present a concise, technical argument. Keep approvals timely so responses meet deadlines and the overall audit lifecycle shortens.
Handle interviews, meetings and on-site visits professionally
When officers arrive, a clear plan and a single point of contact keep interactions efficient and factual. Brief the team and confirm system access so requested documents are at hand.
Preparing staff and systems for a field walkthrough
Ensure access and order: make user accounts ready and group requested files by date and type. Place key records in a single, indexed folder for quick retrieval.
Run a short briefing for each employee who may speak with officers. Explain escalation routes and the role of the company liaison.
Answering questions accurately without guessing
Be precise and truthful. If an employee cannot recall details, say they will verify the information and follow up with supporting documents.
Avoid speculation. Clear answers, backed by records, preserve credibility and shorten the review. Maintain consistent responses across services and teams.
Keeping a contemporaneous log of queries and documents
Record every question asked, which documents were viewed, and the explanations given. Note any deadlines or instructions provided during the visit.
When formal statements are recorded, read them carefully and correct factual errors before signing. Request an interpreter if needed and initial any amendments.
“Disciplined handling of interviews can materially affect outcomes where intent or credibility is questioned.”
Penalties, errors and voluntary disclosure: reducing financial and reputational risk
A single missed deadline or incorrect entry may trigger substantial financial and reputational consequences. Firms must act swiftly when mistakes are found and follow a clear decision process.
What can go wrong:
- Late filing and late payment — fixed penalties plus interest and further charges.
- Incorrect returns from negligence — penalties commonly range up to 100–200% of the undercharged tax.
- Wilful evasion — penalties may reach 400%, with possible fines or imprisonment in serious cases.
Potential outcomes: additional tax, multiplied penalties and operational disruption from prolonged enquiries. Reputation, banking relationships and staff morale can all suffer when reviews escalate.
Voluntary Disclosure Programme (VDP): disclose issues before the authority notifies you and you may receive much lower penalties — sometimes 0% or a small percentage. VDP is usually unavailable for items already under formal review, so timing is critical.
Decision framework: quantify exposure, trace root causes, fix controls and seek professional advice before any formal disclosure. Clear records and prompt, accurate disclosure reduce overall risk and help restore compliance.
Conclusion
A steady compliance routine protects cash flow and reputational standing when queries arise.
Preparing before any letter arrives means disciplined bookkeeping, clear digital trails and regular internal reviews. These habits make most reviews administrative and short-lived.
When a notice reaches you, confirm scope and years, set deadlines, appoint a single liaison and submit a structured pack of documents and reconciliations. Desk reviews often close in weeks; field audits may take months.
Keep in mind the distinction between a routine audit and a formal investigation. Seek early professional advice if issues widen and consider voluntary disclosure promptly to reduce penalties.
Good readiness strengthens reporting, cuts disputes and makes everyday tax processes simpler.
FAQ
What typically prompts a review by the Inland Revenue Authority of Singapore?
Are reviews always punitive?
How does IRAS identify risks using technology?
What are common red flags that invite closer inspection?
What should a business do before receiving any notification?
How often should internal reviews be run?
What are the main types of IRAS reviews?
How should one respond after receiving an audit notice?
Which years must companies retain records for?
What documents are commonly requested?
How important are digital records and backups?
What record-keeping practices reduce risk during a review?
Which areas does IRAS focus on most often?
How should documents be submitted to IRAS?
What if IRAS asks follow-up questions?
How should staff be prepared for on-site visits or interviews?
What are the risks of giving incorrect answers during a meeting?
What outcomes can result from an unfavourable finding?
Can penalties be reduced and when is disclosure beneficial?
When should a business consider engaging a tax professional?
How can companies minimise future review risk?
Dean Cheong is a Singapore-based B2B growth strategist and the CEO of VOffice. He helps companies scale revenue through sharper sales execution, CRM implementation, and go-to-market strategy, backed by a strong foundation in business banking and finance from Nanyang Technological University and a track record of driving sustainable, performance-led growth.