Do I Need to File a Corporate Income Tax Return for My Singapore Company Every Year, and How Does IRAS Decide?

For most Singapore companies, Singapore corporate income tax filing is treated as an annual operating requirement—unless IRAS has specifically waived filing for that Year of Assessment (YA) or has instructed otherwise. The practical problem is that real companies don’t sit neatly in “active” versus “inactive”: you may be newly incorporated but not started, between projects, holding IP, winding down, or “dormant” in a business sense but still receiving bank interest or other income. IRAS’s decision triggers (commencement, income derived, first accounts closure, dormancy status) can change what you must do each YA. This guide gives you a scenario-based workflow you can run each year: what to check in IRAS notifications, which return type applies (Form C‑S (Lite), Form C‑S, or Form C), and how to execute e‑filing in myTax Portal with the right controls.

What is the default rule—do Singapore companies generally file corporate income tax every YA?

Yes—operationally, you should assume annual filing is expected for each YA unless IRAS has granted a waiver for that YA and/or IRAS has instructed you that no return is required.

Two practical points matter for owners and finance teams:

• IRAS drives action through YA-specific notifications (letters / portal notices). Those notices are your “go/no-go” trigger each year.
• Even if you believe you have no income, you still need a decision and evidence trail: either (a) you file the required return for that YA, or (b) IRAS has explicitly waived / not required filing.

From a workflow perspective, treat corporate tax filing like an annual control cycle:

1. Check IRAS notifications for the YA (myTax Portal + company mail address).
2. Confirm your company’s scenario (new/not started, active, dormant, ceased).
3. Confirm whether IRAS requires a return and which form type is available.
4. Prepare the minimum accounts/tax data set for e‑filing.
5. File via myTax Portal and retain proof + working papers.

This approach prevents two common operational failures: (i) ignoring an IRAS notice because “we had no activity”, and (ii) filing the wrong return type because the company’s status changed mid-year.

How does IRAS decide whether a company must file—what are the real-world triggers?

In practice, IRAS’s filing expectation for a YA ties back to a few decision triggers that map closely to how your business is actually operating.

H3: Trigger 1 — Has the company commenced business?

“Commencement” is not just an incorporation date. A company can be incorporated but not yet commenced if it has not started revenue-generating operations and is still in pre‑business setup.

Operationally, commencement can be indicated by actions such as:

• issuing invoices or providing services
• acquiring trading stock for sale
• signing customer contracts and beginning delivery
• hiring operational staff for revenue activity

Why this matters: once the company is operating, IRAS typically expects annual compliance behaviour (accounts, tax computations, filings), even if profit is low or nil.

H3: Trigger 2 — Was any income derived in the basis period?

Filing questions often hinge on “we had no revenue”. But “income” can be broader than sales.

Examples that can create income even when you consider yourself inactive:

• bank interest credited to the company
• rental income
• service fees
• gains that may be treated as revenue in nature (fact-specific)

You do not need to solve every tax technicality to run the filing workflow. You do need a control step to identify whether anything that looks like income was derived—because it influences whether “dormant” is really dormant, and what needs to be declared.

H3: Trigger 3 — When is the first set of accounts closed (basis period vs YA)?

New companies often miss filings because they assume “we haven’t closed accounts, so there’s nothing to file.” IRAS works on Year of Assessment (YA), which relates to a basis period (generally the financial period ending in the preceding calendar year).

Your first accounts closure is a key operational milestone because:

• it anchors your first basis period
• it determines what period your first tax return covers
• it affects whether your internal reporting is ready for filing when IRAS issues notices

H3: Trigger 4 — Is the company formally dormant and has IRAS waived filing?

“Dormant” is commonly used in business talk, but the compliance consequence depends on whether IRAS treats the company as dormant and whether a filing waiver applies for that YA.

A practical control rule: dormancy is not a self-declared exemption. If you want to rely on a waiver or a “no filing required” position, you need IRAS confirmation and you need to keep the supporting documentation.

H3: Trigger 5 — IRAS notification overrides assumptions

Even when your internal scenario suggests one path, the IRAS notice for that YA is the operational instruction. If you receive a filing notice, treat it as actionable unless IRAS confirms otherwise.

If there is any mismatch (e.g., you believe dormant but IRAS issued a filing requirement), your next step is not to ignore it—it is to clarify with IRAS and document the outcome.

What is the year-by-year workflow to decide “file vs waived” without guessing?

Use this as an annual playbook your finance team or corporate service provider can run.

H3: Step 1 — Pull the IRAS instruction set for the YA

For each YA, gather:

• myTax Portal notices (corporate income tax)
• any physical letters sent to the registered address
• prior YA filing outcome (what was filed, what was waived)

Control: assign an owner (e.g., Finance Manager / outsourced accountant) and a reviewer (director/CFO) so notices are not missed.

H3: Step 2 — Confirm the company’s scenario for the basis period

Classify the company for the relevant financial period:

• Newly incorporated, not commenced
• Active trading / service operations
• Dormant (no business activity; confirm income reality)
• Ceased / winding down / strike-off in progress

Document the classification with evidence:

• bank statements (to detect interest/receipts)
• general ledger extracts
• invoices issued (or confirmation of none)
• payroll/CPF activity (if any)

H3: Step 3 — Determine whether a return is required and which type

Based on IRAS instructions and your scenario:

• If IRAS requires a return: identify whether Form C‑S (Lite), Form C‑S，还是 C表格 is applicable/available for e‑filing.
• If you believe a waiver should apply: confirm whether IRAS has granted it for that YA.

Important: eligibility rules and thresholds can change. Avoid hard-coding assumptions into SOPs—build a step to verify the current IRAS criteria at the time you file.

H3: Step 4 — Prepare the “minimum viable filing pack”

You want the smallest complete set of inputs that supports accurate filing and reduces rework:

• finalised accounts for the relevant period (or management accounts where appropriate, aligned to filing requirements)
• tax computation working paper
• schedules for common items (revenue, expenses, capital allowances where relevant)
• support for any claim positions taken

Keep attachments high-level in your workflow documentation because IRAS requirements may change; always verify what must be submitted and what must only be retained.

H3: Step 5 — E‑file on myTax Portal and archive proof

After filing:

• save the acknowledgement / submission receipt
• store the final filed figures, return type, and YA in a compliance register
• store your working papers with version control

H3: Step 6 — Post-filing controls

Run two checks:

• Did IRAS issue any follow-up queries/adjustments?
• Do you need to update next year’s assumptions (e.g., newly active, newly dormant, change in financial year end)?

This is where firms like Paul Hype Page & Co. typically add the most value: not by “filling a form”, but by setting up a repeatable annual workflow, ensuring the scenario classification is defensible, and making sure IRAS instructions and internal accounting reality stay aligned.

Scenario 1: We just incorporated and haven’t started business—will IRAS still expect a return?

This is one of the highest-friction scenarios because it feels like “nothing happened”, yet IRAS processes run on system triggers and YAs.

H3: What to expect

You may still receive IRAS correspondence about corporate income tax filing for a YA, even if:

• you have not issued invoices
• you have not signed customers
• you have not hired staff

H3: What your team should do (practical sequence)

1. Confirm “not commenced” with evidence:

• bank statements showing minimal activity
• no revenue records
• nature of expenses (setup costs, professional fees

2. Check if any income was derived anyway:

• bank interest is a common surprise

3. Read the IRAS YA notice carefully:

• does it instruct you to e‑file?
• does it state “no filing required” (if applicable)?
• If IRAS requires filing, proceed to file using the return type made available.

H3: Control risks to watch

• Missing the first accounts closure linkage: if you delay closing your first accounts, you can end up rushing compliance when filing is triggered.
• Overlooking “small income” items: a bank account with interest can shift your dormancy narrative.

H3: Operational tip

Even for a pre‑commencement company, keep bookkeeping up to date. The goal is not full finance sophistication; it is to avoid a year-end scramble and to be able to explain, clearly and consistently, what happened in the period.

Scenario 2: We are actively trading—what should the filing process look like end-to-end?

For active companies, the question is rarely “do we file?”—it is “how do we file reliably every year without disruptions?”

H3: Your internal filing timeline should be driven by readiness, not panic

Instead of building a calendar around generic deadlines, build the workflow around these readiness gates:

• Accounts close completed for the financial period
• Tax computation prepared and reviewed
• Return type confirmed in myTax Portal (C‑S (Lite) / C‑S / C)
• E‑filing access confirmed (authorised staff, CorpPass access)

H3: What to prepare before anyone logs into myTax Portal

Create a standard “tax close folder” each year:

• final trial balance + GL
• reconciliations (bank, AR/AP)
• fixed asset schedule (if any)
• management representation notes for judgement areas (e.g., unusual income/expense)
• prior year filing references

This reduces the most common execution failure: preparing tax computations from incomplete or shifting accounts.

H3: What to do when your business changed mid-year

If your company had events like:

• new revenue lines (e.g., subscription + services)
• overseas income flows
• group intercompany charges
• restructuring or cessation of a division

Treat this as a “tax fact pattern change” requiring an internal review step before filing. The aim is not to over-complicate; it is to avoid filing a return that does not match the business reality.

H3: Who should own what (a simple RACI)

• Owner (Responsible): finance lead / outsourced accountant
• Approver (Accountable): director / CFO
• Consulted: operations lead (for business changes), HR/payroll (for headcount cost changes)
• Informed: shareholders / group finance (where relevant)

This is basic governance, but it prevents “accounting knows one story, operations lived another story” misalignment that leads to IRAS follow-ups.

Scenario 3: We think the company is dormant—does that mean no corporate tax filing?

Not automatically. Dormancy can reduce compliance burden only when the status is consistent with IRAS expectations and (where applicable) a waiver is granted.

H3: First, sanity-check what “dormant” means in your records

Before you assume anything, confirm:

• no revenue / trading receipts
• no business expenses that suggest ongoing operations
• no staff payroll activity (if any, understand why)
• no income such as bank interest, rental, or service fees

If there is any income, your company may not be dormant in the way you assume, even if business operations feel paused.

H3: Then, check what IRAS told you for the YA

Run a simple decision tree:

• If IRAS issued a filing notice: treat as required unless IRAS confirms a waiver/no filing.
• If IRAS did not require filing for that YA: retain the notice/record and still keep books/records to support dormancy.

H3: Practical implementation steps if you want to manage dormancy properly

• Maintain minimal bookkeeping (bank reconciliations, expense classification).
• Avoid unnecessary transactions that create “activity signals”.
• If circumstances change (e.g., you restart business), update internal status early so you are ready for the next YA.

H3: Control point

Dormancy is often broken unintentionally by:

• leaving funds in interest-bearing accounts
• charging/receiving management fees within a group
• letting a one-off consultancy invoice slip through

None of these are inherently “wrong”, but they change the compliance story. If you are managing multiple entities, build a quarterly check on each entity’s bank statements and intercompany postings so dormancy assumptions remain true.

Scenario 4: We ceased operations or are striking off—do we still have to file for the YA?

Ceasing operations and striking off are business events; they do not automatically switch off IRAS filing expectations for the relevant YA(s).

H3: Separate three ideas that are often confused

• Stopped trading (no new sales)
• Company still exists (still incorporated, may have bank account, liabilities, or residual transactions)
• Formally struck off / wound up (legal status changes via ACRA processes)

A company can stop trading but still have transactions that affect tax filing (final collections, expense settlements, bank interest, asset disposal).

H3: What to do when you receive an IRAS filing notice during wind-down

1. Identify whether the notice relates to a period when the company still had any transactions.
2. Close the accounts properly for that final period (including any cessation costs).
3. File the required return type for that YA, unless IRAS confirms otherwise.

H3: Practical risk management during strike-off planning

If you are planning a strike-off, treat tax filing as one of the “closure gates”:

• ensure you have filed all required YAs up to the relevant period
• ensure you can evidence no outstanding tax matters
• maintain access to myTax Portal / CorpPass until everything is completed

Where companies get stuck is not the strike-off form itself, but unresolved filings, mismatched records, or loss of access to digital accounts. Build a checklist and assign ownership before directors or staff move on.

How do we decide between Form C‑S (Lite), Form C‑S, and Form C without turning it into a technical exercise?

Most teams don’t need a deep legal analysis; they need a repeatable way to select the return type available for their company and YA.

H3: Start with what myTax Portal makes available for the YA

In practice, the available return type(s) shown in myTax Portal and/or stated in IRAS correspondence is your starting point. Eligibility can depend on IRAS criteria (which may change), so avoid relying on last year’s assumptions.

H3: Use a simple “complexity filter”

Even before you confirm eligibility details, classify your company’s tax profile:

• Low complexity: straightforward trading/service income, few adjustments, no special claims
• Medium complexity: some adjustments, fixed assets/capital allowances, group charges
• Higher complexity: cross-border elements, significant one-off transactions, complex tax positions

As complexity increases, you should expect more internal review and stronger documentation—regardless of whether the form is C‑S (Lite), C‑S, or C.

H3: What each form generally signals (high level)

• Form C‑S (Lite): intended for simpler cases (subject to IRAS conditions). It generally reduces data entry.
• Form C‑S: for companies that meet IRAS conditions for simplified reporting but are not in the Lite subset.
• C表格: the full form, used when simplified forms are not applicable or not available.

Important accuracy note: do not hard-code thresholds or eligibility rules into your SOP unless you are verifying them against the latest IRAS guidance at time of filing. IRAS may revise qualifying conditions.

H3: Attachments and supporting documents—what to operationalise

Instead of memorising what to attach, build this control:

• Before filing, check IRAS’s current e‑filing instructions for that YA and form type.
• After filing, retain the core supporting pack (accounts, computations, schedules) even if not uploaded.

This is the difference between “we submitted something” and “we can support what we submitted if queried later.”

What are the exact myTax Portal steps for e‑filing, and what internal controls should sit around them?

IRAS corporate income tax filing is done via 或纸质提交。 (e‑filing). The screen flow can change, but the operational steps and controls are stable.

H3: Pre-step — make sure access and authorisations are not the blocker

Before filing season:

• confirm the company has the right digital access arrangements (e.g., authorised users via corporate digital access channels)
• confirm who can submit vs who can prepare
• maintain a shared compliance email/address for receiving IRAS messages

H3: E‑filing execution (practical sequence)

1. Log in to 或纸质提交。 under the company profile.
2. Navigate to 企业所得税 functions and select the relevant Year of Assessment (YA) filing.
3. Confirm the form type shown/required for that YA (C‑S (Lite), C‑S, or C).
4. Complete the required fields using your finalised accounts and tax computation.
5. Validate key numbers against your working papers (see control list below).
6. Submit the return and download/save the acknowledgement.

H3: Key validation controls before clicking “Submit”

Treat these as mandatory checks:

• YA selected matches the basis period/accounts you prepared
• revenue figure ties back to accounts
• tax adjustments are supported by schedules
• any claims are documented (even if not attached)
• director/approver sign-off captured (email approval is fine if controlled)

H3: Post-submission controls

• save a PDF/screenshot of submission confirmation
• update your compliance tracker: YA, form type, submission date, preparer, reviewer
• store the final data pack in a read-only folder to prevent later edits

If you are running multiple entities, these controls matter more than the mechanics of data entry—they prevent “filed under wrong YA”, “filed draft numbers”, and “no evidence of review” situations that create downstream cost.

Note: IRAS portal features and requirements can change. Your SOP should include a step to confirm the current IRAS e‑filing instructions at the time you file.

What should we check in IRAS letters and portal notices before we decide anything?

IRAS notifications are not just reminders—they often contain the decision cues for that YA.

H3: A practical checklist for each YA notice

When you receive an IRAS letter/portal notice, extract and record:

• which YA it refers to
• whether it states a return is required (and by when)
• 这个 return type required/available
• any special instructions (e.g., specific declarations)
• how IRAS expects you to respond if you believe filing is not required

H3: Why this matters operationally

Two companies with identical activity levels can receive different instructions depending on IRAS’s records and prior filings. Your workflow should therefore treat “notice content” as a data input, not background noise.

H3: When to escalate internally

Escalate to a director/CFO (or to your tax advisor) when:

• the notice conflicts with your scenario (e.g., you believe dormant but notice requires filing)
• the company had unusual transactions in the period
• you changed financial year end, business model, or group structure

The goal is to resolve ambiguity early—before a missed filing becomes a broader compliance and governance issue.

结论

For Singapore companies, the practical answer is: corporate income tax filing is generally expected every YA unless IRAS has waived filing for that YA and/or explicitly instructed otherwise. The reliable way to manage this is not to debate “active vs inactive” in the abstract, but to run an annual scenario workflow: (1) pull the IRAS YA notice and myTax Portal status, (2) classify the company’s real operating state (new/not commenced, active, dormant, ceased), (3) confirm the return type available (Form C‑S (Lite), Form C‑S, or Form C), and (4) execute e‑filing with basic governance—owner, reviewer, evidence pack, and archived submission proof. If your internal view and IRAS instructions don’t match, treat that as a prompt to confirm directly with IRAS and document the outcome. Where teams want a repeatable, multi-entity process, Paul Hype Page & Co. can help design and run the annual compliance workflow so filings stay aligned to both business reality and IRAS’s YA-specific requirements.