Do all Singapore companies need to file corporate income tax returns every year—even if dormant or with no income?

For Singapore corporate income tax filing, the operational risk usually isn’t “not knowing the rule”—it’s assuming dormancy or zero revenue means there’s nothing to do. In practice, most Singapore companies are expected to file a corporate income tax return each Year of Assessment unless IRAS has explicitly waived the filing requirement for that YA. If you miss a filing because you never checked your waiver status (or you assumed the waiver is automatic), you create avoidable catch-up work and governance issues for directors and finance teams.

This guide gives you a clear yes/no answer, then a step-by-step playbook: how to confirm whether IRAS has granted a waiver (and how to verify it), how to choose the right return type at a high level (C‑S Lite / C‑S / C), and how to keep records so you can stay compliant even when the company is dormant.

So—is annual corporate tax filing required in Singapore?

Yes—as a working rule, Singapore companies should plan to file a corporate income tax return every year.

The practical exception is when IRAS explicitly waives the requirement to file a return for a specific Year of Assessment (YA). The key word is “explicitly”: a waiver is not something to assume based on business inactivity.

What this means for operators

Treat filing like an annual control cycle:

• Default position: “We must file.”
• Only switch to “no filing required” when you have clear IRAS confirmation (e.g., via myTax Portal status and/or IRAS correspondence) that a waiver applies for that YA.

Why ‘dormant’ and ‘no income’ are not safe shortcuts

A company can be dormant operationally or have no revenue, yet still:

• have bank interest or other minor income,
• incur expenses,
• have intercompany transactions,
• maintain assets/liabilities,
• need to support future audits, investor queries, or due diligence.

From an implementation standpoint, it’s safer to build a process that checks waiver status and documents the decision than to rely on assumptions about activity level.

What’s the simplest annual workflow to confirm whether you have an IRAS filing waiver?

Use an annual workflow that ends with a documented “file / waiver” decision for the specific YA. The objective is not theory; it’s a repeatable internal control.

Step 1: Assign one owner and one reviewer

Set clear responsibility:

• Owner (preparer): Finance manager, accountant, or outsourced provider.
• Reviewer (approver): Director, CFO, or delegated authorised officer.

A common failure mode is “everyone assumed someone else checked.” Put names against tasks.

Step 2: Check your tax mail and notices first (the fastest signal)

Operationally, IRAS correspondence is often the clearest prompt.

• Look for letters/notices that indicate whether a return is required for the YA.
• Store the document in a central “Tax > YA20XX > IRAS Correspondence” folder.

If you can’t find any letter, do not conclude you’re waived. Move to the portal check.

Step 3: Verify status in IRAS myTax Portal (don’t rely on memory)

Log in to IRAS myTax Portal (with appropriate authorisation) and check the company’s filing obligations/status for the relevant YA.

Practical tips for finance teams:

• Use a standard checklist screenshot set (e.g., “filing required/waived status page”) and save it with the YA file.
• If access depends on a specific employee’s Singpass/CorpPass setup, confirm access early, not in the week you intend to file.

Step 4: Treat “no clear waiver evidence” as “must file”

If the portal/correspondence does not clearly show a waiver for that YA, operate on the assumption that:

• a return is required, and
• you should prepare to file the appropriate form.

This single decision rule prevents most missed filings caused by dormancy assumptions.

Step 5: Record the decision in a one-page “YA filing memo”

Create a lightweight internal record (one page is enough) capturing:

• YA in scope
• waiver status (Yes/No)
• evidence (portal screenshot reference and/or IRAS letter date)
• who checked, who approved, and when
• next action (file form type / monitor)

This memo becomes valuable when directors change, finance staff rotate, or you go through bank/investor due diligence.

If the company is dormant or has no income, what should you do differently—without skipping controls?

Dormant/no income changes the workload, not the discipline.

The practical risk: “silent years” that break your compliance trail

Where dormant companies get into trouble operationally:

• bank accounts still exist but statements aren’t archived,
• small expenses occur (registered office, secretary, bank fees) but aren’t captured,
• prior-year working papers can’t be found later,
• the team stops checking portal messages.

Even when there’s nothing to pay, you still want a clean annual record that shows:

• what happened (or didn’t happen), and
• why the company concluded filing was waived or required.

A “dormant company tax filing Singapore” operating routine (minimal but defensible)

Run this once per year:

1. Confirm there were no transactions (bank statements, invoices, expense claims).
2. Update a simple dormant register: bank account status, contracts, assets/liabilities.
3. Perform the waiver check (portal + correspondence).
4. If filing is required: prepare the relevant form with consistent supporting schedules.
5. Archive records for the YA with a retention label.

Don’t let dormancy block corporate housekeeping

Even with no operations, finance should still coordinate with company secretarial and management functions on:

• changes in directors/shareholders (if any),
• whether the company intends to resume activity,
• whether bank signatories and access rights are current.

You’re not “doing more compliance”—you’re keeping a coherent corporate record that avoids expensive reconstruction later.

How do you choose between Form C‑S (Lite), Form C‑S, and Form C at a high level?

Once you conclude “must file,” the next operational decision is selecting the correct return type. You don’t need to memorise every eligibility detail to run an effective workflow—you need a high-level triage and a clear escalation path.

First: know what each form is for (in plain terms)

• Form C‑S (Lite): A simplified corporate income tax return designed for smaller, straightforward cases.
• Form C‑S: A simplified corporate income tax return for companies that meet certain qualifying conditions (generally broader than C‑S Lite).
• Form C: The full corporate income tax return, typically used where simplified filing is not applicable or where the company’s situation requires fuller reporting.

Eligibility conditions can change, and they can involve multiple criteria. Before finalising which form you use, verify against the latest IRAS guidance for the YA.

A practical triage approach for finance teams

Use this decision ladder:

1. Start by checking whether simplified filing may apply (C‑S Lite / C‑S).
2. If anything about your fact pattern feels “non-standard,” pause and confirm rather than forcing a simplified form.
3. If simplified filing does not apply, proceed with Form C.

Common “non-standard” triggers that warrant a quick confirmation

Without going into technical thresholds, examples that often justify extra care include:

• complex group/intercompany arrangements,
• significant one-off transactions (asset sales, restructuring-related items),
• unusual revenue recognition patterns,
• cross-border elements.

The goal is not to overcomplicate. It’s to avoid choosing the wrong form and having to rework the submission.

Keep your workflow stable even when criteria change

Build your process so it doesn’t depend on someone remembering rules:

• maintain a short “Form selection checklist” updated annually,
• link the checklist to the latest IRAS reference page (review before each filing season),
• require reviewer sign-off on the final form choice.

If your team uses an external advisor (including Paul Hype Page & Co. as an implementation partner), align early on who confirms eligibility and who documents the basis for the selected form.

What documents and records should you keep to stay compliant—even while dormant?

Record-keeping is where dormant companies most often fall behind, because the work is invisible until something goes wrong.

The operational baseline: retain supporting records for at least 5 years

As a practical minimum, keep tax computations, accounts, schedules, and supporting source documents for at least 5 years, and check the latest IRAS guidance before acting in case requirements are updated.

This is not just a tax point. It affects:

• your ability to respond to IRAS queries,
• due diligence for funding, sale, or licensing,
• director comfort on governance.

What “supporting records” means in real life

For most SMEs, a defensible file set includes:

• management accounts / financial statements used for the YA
• tax computation working papers
• general ledger and trial balance
• bank statements and reconciliations
• key contracts (where relevant to revenue/expenses)
• invoices, receipts, and payment records
• fixed asset register (if any)
• intercompany agreements and schedules (if any)
• IRAS correspondence and portal screenshots supporting the filing/waiver decision

For dormant companies, the record set may be smaller—but it should still show:

• evidence of inactivity (e.g., bank statements showing no activity beyond charges), and
• evidence of annual waiver check / filing decision.

How to organise records so you can retrieve them years later

A simple folder structure beats a complex one:

• Tax > YA20XX >
• 01_IRAS_Correspondence
• 02_Portal_Screenshots
• 03_Accounts_TB_GL
• 04_Tax_Computation
• 05_Supporting_Documents
• 06_Final_Submission

Controls to add:

• naming convention (date + document type)
• restricted access for sensitive payroll/bank documents
• a retention label: “Keep until [Month/Year] (min 5 years; confirm latest IRAS guidance)”

Don’t ignore systems risk: access, passwords, and continuity

Even good records fail if the company cannot access them:

• ensure finance email addresses and portal access are not tied to a departed employee only
• store credentials and access instructions securely (with appropriate governance)
• document who can retrieve IRAS correspondence and who can approve filings

These are small operational steps that prevent “we can’t log in” crises.

How do you implement an annual tax-filing control calendar that doesn’t depend on heroics?

A workable control calendar is less about dates on a spreadsheet and more about building repeatable checkpoints.

Build around milestones, not last-minute deadlines

Deadlines can change and differ by YA and filing mode; rather than hard-coding dates into an evergreen process, anchor on milestones:

• Milestone A: Data readiness (books closed, bank recs done)
• Milestone B: Waiver status confirmed (portal/correspondence evidence stored)
• Milestone C: Form choice confirmed (C‑S Lite/C‑S/C) with reviewer sign-off
• Milestone D: Draft return prepared and internal review completed
• Milestone E: Submission archived (final PDF/acknowledgement + working papers)

Define RACI for each milestone

Example:

• Responsible: Finance staff / outsourced accountant
• Accountable: Director/CFO
• Consulted: Tax advisor (if needed)
• Informed: Company secretary (if relevant to status changes)

Add two “stop-the-line” controls

These two controls catch most real-world failures:

1. No waiver evidence = proceed to prepare filing (don’t wait).
2. No portal access = escalate immediately (don’t wait until the week of filing).

Measure compliance like an operations process

Simple metrics help management oversight:

• % of YAs with a completed “YA filing memo”
• % of filings where submission and acknowledgement are archived within 48 hours
• number of access escalations (portal/CORPPASS issues) per year

This turns tax filing from a once-a-year scramble into a manageable business routine.

What does a ‘good’ filing/waiver evidence pack look like if IRAS asks questions later?

Think in terms of an “audit-ready pack” even if you never get asked—because building it is cheaper than reconstructing it.

The minimum pack (for each YA)

• Waiver decision evidence:
• IRAS letter/notice (if any), and/or
• myTax Portal screenshots showing filing requirement/waiver status
• The internal “YA filing memo” (who checked, who approved, conclusion)
• If filed: final submission copy/acknowledgement + key working papers
• Core financial support: TB/GL and bank reconciliation or bank statements

The dormant-company version

If dormant and waived, your pack should still contain:

• portal/letter evidence of waiver (for that YA)
• bank statements showing inactivity (or only minimal bank charges)
• a short statement of no transactions and any ongoing obligations (e.g., registered office fees)

Why this matters commercially

A clean evidence pack reduces friction when:

• onboarding a new accountant or finance manager
• applying for credit facilities
• preparing for investment or sale
• responding to board or shareholder governance questions

It’s a cost control measure: you avoid paying later to recreate records.

When should you escalate to an advisor instead of guessing?

You don’t need an advisor for every YA, but you do need a clear escalation trigger so the team doesn’t “wing it.”

Escalate if any of these are true

• You cannot clearly confirm waiver status in the portal/correspondence.
• The company’s status changed during the year (e.g., restarted operations, new revenue stream).
• There are cross-border or non-routine transactions.
• You’re uncertain which form is appropriate (C‑S Lite/C‑S/C) and internal knowledge is limited.
• Records are incomplete and would require reconstruction.

What to ask for (so the engagement stays practical)

If you involve an advisor such as Paul Hype Page & Co., keep the scope operational:

• confirm the annual filing requirement vs waiver (based on evidence)
• validate the high-level form selection
• help design a repeatable internal workflow (templates, checklists, retention structure)
• assist with cleanup where prior-year records are disorganised

This keeps the focus on implementation and control, not just one-off form preparation.

Conclusion

For Singapore corporate income tax filing, the practical answer is straightforward: plan to file every Year of Assessment unless IRAS has explicitly waived filing for that YA. Dormant status or no income does not, by itself, remove the obligation.

To execute reliably, run a simple annual playbook: (1) assign an owner/reviewer, (2) check IRAS correspondence and verify status in myTax Portal, (3) treat the absence of a clear waiver as “must file,” (4) select the right return type at a high level (C‑S Lite/C‑S/C) and confirm against the latest IRAS guidance, and (5) retain supporting records in an organised pack for at least 5 years (and verify current IRAS requirements before finalising your retention policy).

If you want this to run smoothly year after year, build it as an operations process—documented decisions, consistent evidence, and clear escalation triggers—rather than a last-minute compliance task.