Could a small data entry error lead to a full tax review for your company?
IRAS reviews form part of Singapore’s self-assessment system and are not automatically a sign of wrongdoing. Selection is largely risk-based, using data matching and AI-driven nudges during e-filing to flag unusual entries for review.
This short guide sets expectations for local business owners. It explains what a review means, why you might be selected and how prompt, professional action helps reduce disruption.
We preview major trigger clusters such as inconsistencies across filings, unusual cash movements, GST refund positions, payroll mismatches and reconciliation gaps. Small errors can escalate if not corrected early.
Think of “audit-ready” as an operating standard: clean books, consistent filing and organised supporting documents for every material figure. The payoff is fewer queries, faster resolution and stronger compliance that supports growth.
Key Takeaways
- Selection often reflects risk profiling, not presumption of evasion.
- Even minor data gaps can prompt deeper enquiries.
- Maintain consistent records and reconciliation to lower risk.
- Adopt an “audit-ready” routine for smoother resolutions.
- Swift professional response reduces disruption and cost.
Why IRAS audits happen in Singapore and what an audit really means
Understanding why tax reviews occur helps companies respond calmly and correctly.
A tax review is a formal check to confirm a business has declared income accurately and paid the right tax. Inspectors will compare financial statements, filed returns, bank activity and supporting records to verify figures. This is a verification process, not an automatic accusation of wrongdoing.
Self-assessment and selection
Under the self-assessment model, the system relies on businesses to file honestly. Reviews validate that model by sampling returns and following up where information looks inconsistent.
Data, risk and AI in selection
The inland revenue authority uses risk-based selection, industry focus, third-party mismatch checks and occasional random reviews. Analytic tools cross-check filings and benchmark performance. Patterns such as sudden margin drops or repeated large refunds can raise a risk score.
MyTax Portal also offers AI “nudges” when entries deviate from past history or norms. Treat those prompts as a compliance signal: double-check figures and supporting documentation before submission.
- Mindset: See a review as structured verification.
- Practical step: Respond promptly with clear reconciliations and source documents.
- Alignment: Ensure reported figures match third‑party information to reduce follow-up queries.
“Timely, organised responses shorten the process and limit disruption.”
Types of IRAS audits you may face and how they differ
Not every tax review looks the same; the approach depends on the type of examination.

Desk checks and portal document requests
Desk checks begin with targeted queries sent through myTax Portal. The authority asks for clarification on specific line items and uploads of supporting documents.
Good readiness means indexed invoices, bank statements, ledgers and clear workings that tie back to filed figures. These files close queries quickly and keep review scope limited.
On-site inspections and systems reviews
Field visits go deeper. Inspectors may interview staff, count inventory, observe workflows and test how transactions flow from operations into accounting.
These visits focus on systems integrity—POS, invoicing and approval controls—because weak processes can create reporting risk.
Investigation reviews and when evasion is suspected
Investigation reviews are higher-stakes. They occur where indicators suggest deliberate under-declaration or fraud. Expect meticulous requests for information and careful handling of communications.
Practical steps: stay professional, respond within deadlines, and ensure your replies match the stated scope and years under review. Early, organised cooperation and accurate evidence shorten timelines and improve outcomes.
| Type | Typical access | Focus | Quick readiness tips |
|---|---|---|---|
| Desk check | myTax Portal uploads | Line items and supporting documents | Indexed invoices, reconciliations |
| Field visit | On-site inspection | Processes, controls, staff interviews | System logs, approval trails |
| Investigation | Broad document demand | Possible evasion or fraud indicators | Legal counsel, complete evidence pack |
| Outcome focus | Response time matters | Scope limited by years under review | Match responses to scope and dates |
Common IRAS audit triggers Singapore businesses should know
Many reviews begin because an entry or movement looks out of step with a business’s usual pattern.
There is no definitive public list, but real-world cases cluster around anomalies, inconsistency and weak supporting evidence.
Inconsistencies across tax returns, GST records and financial statements often come from simple coding, timing or mapping errors. These mismatches can show as differences in income, tax returns or tax claimed and will prompt further queries.
Key risk patterns to watch
Large year-on-year swings in income, profit margins or expenses look risky unless you can back them with contracts, invoices and management notes.
Unusually high deductions, capital allowances or repeated losses need clear schedules and eligibility support. Heavy cash takings or irregular transactions without deposit trails raise immediate questions.
Late, incomplete or non-responsive filing behaviour increases perceived risk. Third-party mismatches with suppliers, customers, CPF Board or ACRA are a major driver of modern reviews.
| Trigger | Why it flags | Quick prevention |
|---|---|---|
| Inconsistent filings | Data mapping or timing errors | Reconcile returns to statements before submission |
| Large year swings | Unexplained income or expense moves | Keep contracts, invoices and explanations |
| Cash/irregular transactions | Weak deposit trails | Daily cash controls and POS reconciliation |
| Third‑party mismatches | Data from CPF/ACRA or trading partners | Align reported figures with external records |
Prevention mini‑check: reconcile across filings, keep documentary proof for every material amount and record business reasons for unusual movements.
Financial statement red flags that IRAS systems often detect
Automated systems rapidly spot numeric gaps, so tidy ledgers are your first defence against unnecessary queries.
Out-of-balance figures and reconciliation gaps
Systems flag mismatches: tools compare ledgers, bank feeds and filed returns to find out-of-balance figures. Regular bank, AR/AP and GST control checks are non-negotiable.
Typical reconciliation gaps include a bank balance that does not tie to the cash book, sales recorded in the POS but missing from the revenue ledger, or GST control accounts that differ from filed returns.
Reporting errors that resemble under-declared income or inflated expenses
Reporting mistakes that can look like under-declared income include missing sales invoices, incorrect revenue cut-off and netting off income against expenses without support.
Expense-side errors that may resemble inflated costs include duplicate claims, misclassified personal expenditure and unsupported accruals or provisions.
“Every material amount should trace from source to ledger to statement.”
Adopt periodic management reviews that test the reasonableness of margins and ratios. Document year-end adjustments with full workings and approvals to reduce the appearance of arbitrary entries during an audit.

| Red flag | Why systems flag it | Quick action |
|---|---|---|
| Out-of-balance totals | Numeric mismatch between ledgers and bank data | Reconcile bank, cash book, AR/AP immediately |
| Missing invoices | Revenue gaps on filed statements | Locate source invoices and amend records |
| Unsupported accruals | Large unexplained expense amounts | Provide workings, approvals and supporting documentation |
GST risk areas that frequently trigger IRAS audit queries
When sales, refunds and declarations do not align, GST queries quickly follow.
Output tax accuracy is a primary focus. Verify that 9% GST is charged on taxable sales and reported in the correct period.
Validate output tax by reconciling the sales ledger to GST returns, confirming tax codes in invoicing and POS systems, and ensuring credit notes adjust returns correctly.
Input tax and blocked items
Input tax claims attract scrutiny where supporting evidence is weak or where blocked items (for example passenger cars or staff family benefits) are claimed inadvertently.
Implement an invoice approval checklist so every claim links to a supplier invoice and payment record.
Zero-rated supplies and export evidence
For zero-rated supplies, retain export evidence such as bills of lading, airway bills or export permits. Organise these by shipment and invoice reference to make checks straightforward.
Refund positions and ongoing risk signals
Consistent refund positions can raise a profiling flag. Document legitimate commercial reasons—export-heavy sales or capital expenditure cycles—to pre-empt queries.
GST health check: monthly reconciliation, exception reporting for unusual tax codes and periodic reviews of refund patterns with supporting evidence.
Keep readable digital receipts and documents so each claim traces from supplier invoice to payment to ledger entry. For practical guidance on historical audit outcomes, see the GST audits by IRAS – results.
Corporate income tax triggers tied to revenue and expense treatment
Tax examiners concentrate on whether reported income truly reflects the company’s economic activity.
Revenue recognition timing and completeness of declared income
Revenue timing is a frequent focus in income tax reviews. Reconcile invoiced revenue, cash receipts and contract milestones to the declared income each period.
Timing risks include late invoices raised after year‑end, advance payments posted in the wrong period, and project billing that spans accounting years. Keep schedules tied to contracts and payment terms to support cut‑off decisions.
Expense deductibility and the “wholly and exclusively” test
Expenses must be incurred wholly and exclusively for producing taxable income. Separate private spending from business costs and document mixed‑use items with clear apportionment.
Unsupported expenses can be disallowed during an audit, leading to additional tax and penalties. Perform a pre‑filing review of high‑risk categories such as entertainment, motor costs and large one‑off items.
Related‑party transactions and arm’s length expectations
Related‑party transactions draw scrutiny if pricing or terms are not defensible. Ensure management fees, shared services and intercompany loans have agreements, invoices and transfer‑pricing support.
Maintain a documentation pack with contracts, workings and explanations of commercial benefit. This helps respond quickly to IRAS queries and reduces escalation risk.
“Keep the profit and loss story consistent: numbers, contracts and explanations should align.”
| Issue | Why it flags | Quick remedy |
|---|---|---|
| Revenue cut‑off | Income recorded in wrong period | Contract tie‑out and invoice schedule |
| Mixed or personal expenses | Not wholly for trade | Apportionment schedules and receipts |
| Related‑party pricing | Non‑arm’s length terms | Agreements, benchmarking and invoices |
Control suggestion: run periodic internal reviews so P&L narratives match operations and you can explain figures consistently in case of queries by IRAS.
Employment and payroll reporting issues that can prompt review
Small payroll errors can create large follow-up requests because reporting feeds multiple government databases.
Employee pay data is highly matched across systems. Mismatches between payroll, CPF returns and accounting information often trigger queries quickly.
AIS reporting: salaries, bonuses and benefits-in-kind
Ensure AIS entries reflect actual payroll runs. Report salaries, bonuses and benefits-in-kind in the correct categories and periods.
Run pre-submission checks against payroll registers and the general ledger. Keep clear workings for bonus calculations and benefit valuations so figures tie back to source data.
CPF mismatches and payroll recordkeeping gaps
Differences between CPF contribution schedules and payroll outputs are a frequent contact point with the IRAS team. Reconcile CPF files with payroll reports each month.
Keep employment contracts, bonus approvals, benefit policies, receipts and supporting calculations in a central folder by year of assessment. These documents shorten review time and reduce the chance of penalties.
“Prompt, organised payroll information limits disruption and helps resolve queries faster.”
Assign clear ownership. Designate a payroll lead to manage data integrity, document retention and correspondence timelines.
- Employee master data accuracy check.
- Variance review for bonus months.
- Consistent mapping to reporting categories and ledgers.
Industry-specific risk factors in Singapore and why some sectors get more scrutiny
Certain sectors attract closer scrutiny because their cash flows and workflows create more opportunities for unrecorded transactions.

Why industry focus matters: authorities adopt sectoral profiling because some lines of business show higher error rates. Cash intensity, complex billing and volatile margins increase perceived risk and therefore the chance of review.
F&B, retail and other cash‑heavy operations
F&B and retail often handle large daily cash takings and frequent small sales. This raises the possibility of till differences, voids or discount misuse.
Practical controls reduce exposure: daily till reconciliation, manager sign‑off for voids, segregation of duties for cash handling and tight refund rules.
Construction and project-based revenue
Project firms face timing questions. Progress billings, retention sums and subcontractor invoices can shift income and expenses across a year.
Keep consolidated project files with contracts, variation orders, invoices and cost allocations. That pack justifies movements quickly during any review.
Operational best practice:
- Segregate cash duties and require approvals for exceptions.
- Perform regular stock counts that reconcile to cost of sales.
- Track project margins monthly to spot coding or cut‑off errors early.
| Sector | Typical pressure points | Quick control |
|---|---|---|
| F&B / Retail | Cash leakage, POS‑to‑bank mismatches | Daily till reconciliation, manager sign‑off |
| Construction | Progress billing, retention, subcontractor costs | Project file with contracts and cost schedules |
| Other service firms | Complex workflows, multi‑stage invoicing | Monthly margin benchmarking and coding reviews |
“Industry focus reflects statistical patterns, not an accusation — it helps you target controls where errors most often occur.”
How to keep records audit-ready under the five-year record retention rule
Establishing an audit‑ready filing routine turns record retention from a task into an operational strength. The law requires businesses to keep core records for at least five years. That applies to source documents and accounting files that substantiate filed positions.
What to retain
Keep sales invoices, supplier invoices, receipts, credit notes, bank statements and ledgers. Also store supporting schedules for key balances so figures are explainable.
Digital copies and audit trail
Scanned or native electronic copies are acceptable if legible. Name and index files so each transaction traces from source to payment to ledger to return.
Operational habits to reduce missing items
- Attach invoices to payment requests and require approval evidence.
- Run monthly exception reports for missing documents.
- Keep contemporaneous documentation for deductions, input tax claims and capital allowances rather than recreating them later.
- Use a retention calendar and access controls so records remain secure over the required years.
“A routine of spot checks trains teams and keeps documentation ready when needed.”
How to prepare when you receive an IRAS audit notice
Start by noting exactly which years and which items the notice covers — clarity at the outset saves time.
Read the scope carefully. Identify the scope, the specific years of assessment and each deadline. Mark those dates and required submissions on a single timeline so you can prioritise tasks.
Information windows are often 14–21 days. Desk requests arrive via myTax Portal. If your documents are voluminous, request a reasonable extension early and state why you need more time.
Internal review checklist
Reconcile management accounts to filed returns and tax returns. Tie GST figures to control accounts and confirm payroll totals match AIS and CPF records.
Prepare clear workings that explain material movements. Avoid sending unorganised stacks of files — structure answers to match each question.
Document pack to assemble
Gather sales invoices, bank statements, expense invoices and receipts. Include payroll registers, employment contracts and key commercial contracts. Label everything by year and reference the returns line items they support.

How to respond professionally
Keep communications professional, prompt and factual. Assign a single point of contact to manage submissions, version control and the communication log.
Do not speculate. Provide evidence‑backed explanations and note when you will supply further documents. Consider engaging professional tax services to review your responses and ensure consistency.
“A single, organised response aligned to the notice scope shortens the review and reduces follow‑ups.”
| Action | Why it matters | Typical timeframe | Quick tip |
|---|---|---|---|
| Read notice and map scope | Prevents missed deadlines | Day 1 | Create a submission timeline |
| Internal reconciliation | Align returns with ledgers | 3–7 days | Prioritise material amounts |
| Assemble document pack | Supports each queried line | 7–14 days | Index by reference and year |
| Respond and follow up | Professional tone speeds closure | Within window or extended date | Use one contact and clear workings |
How the IRAS audit process typically runs from start to resolution
A mapped sequence helps teams move from notification to closure with fewer surprises. Begin by listing responsibilities so you know who will retrieve documents and who will answer technical questions.
Notification and information gathering windows
Notices usually set a short window for documents. The information stage often gives 14–21 days. Use a tracking table with requested items, owner and submission date to avoid missed deadlines.
Interviews, follow-up questions and system walkthroughs
Field reviews may include interviews and system walkthroughs. Prepare staff to explain sales‑to‑cash, procure‑to‑pay and payroll workflows so answers match documented procedures.
Findings letters, additional assessments and supplying evidence
After review, a findings letter may propose an additional tax amount. You can submit further evidence to clarify or dispute points before final assessment.
Managing timelines and requesting extensions
Desk reviews can finish in weeks when documents are clear. Complex investigations may last months or up to a year. Request reasonable extensions early and keep communications orderly.
Practical tip: plan for potential payment, track deadlines and respond with concise, evidence‑backed explanations to reduce penalties and limit escalation.
Conclusion
Simple routines — reconciliations, indexed records and prompt replies — cut most review risk.
Preparation is the best strategy: disciplined bookkeeping, digital audit trails and regular internal reviews make tax questions easier to answer. A short quarterly tax health check helps spot anomalies and correct them before they grow.
Where a company finds an error early, the Voluntary Disclosure Programme can reduce penalties and sometimes lower them to 0% or 10% — but it does not apply once an audit has begun for the same items.
Weak records and slow replies increase disruption and raise the chance of deeper investigation. Strengthen retention for the required years, formalise controls, and consider professional services for reviews or representation when stakes are high.
When figures reconcile, evidence is organised and explanations are consistent, an iras audit becomes a manageable compliance exercise rather than an operational shock.
FAQ
What does an IRAS audit mean and should I assume wrongdoing?
How does IRAS select businesses for review?
What types of reviews might my company face?
Which reporting issues commonly prompt a review?
How do third‑party data mismatches trigger enquiries?
What financial statement errors attract attention?
Which GST practices are high risk?
What corporate income tax matters are often queried?
What payroll and employment reporting can lead to checks?
Do certain industries face more scrutiny?
What records must I keep and for how long?
How should I prepare after receiving an audit notice?
What does the typical audit process involve from start to finish?
Can I appeal or dispute IRAS findings?

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.