Do Singapore companies still need to file YA 2026 corporate tax if there’s no activity—and what happens if you’re late?

YA 2026 corporate income tax filing is one of those obligations that quietly becomes expensive—not because tax is payable, but because many teams assume “no activity = no filing”. IRAS expects most Singapore-incorporated companies to file their YA 2026 corporate income tax return by 30 November 2026 unless a waiver has been granted. That expectation applies even to newly incorporated companies, pre-revenue startups, holding companies with no income, and businesses that are dormant or loss-making. The practical challenge is knowing whether you should submit a nil/zero return versus requesting a waiver, and how to respond if deadlines are already missed. This guide focuses on the most common SME mistakes and the fixes—so owners, directors, and finance leads can decide what to do next, what to prepare, and how to reduce late-filing fallout.

Are you assuming “no activity” means “no filing”—and is that the main trap for YA 2026?

Yes—this is the single most common and costly misconception.

IRAS’ default position is straightforward in practice: if you have a Singapore-incorporated company, you should expect to file for YA 2026 by 30 November 2026 unless IRAS has granted you a waiver. “No sales” or “no bank movements” does not automatically remove filing obligations.

Fix: separate “business activity” from “filing obligation”

A company can have little or no commercial activity and still have:

• statutory responsibilities as a Singapore-incorporated entity;
• expenses (even small ones) that must be reflected in accounts and tax computation;
• IRAS correspondence triggered by prior filings, estimated chargeable income (ECI) expectations, or prior-year patterns.

The better framing for management is:

• Question 1: Has a filing waiver been granted for YA 2026?
• Question 2: If not, can we file accurately as a nil/zero position (or loss position) without guessing?
• Question 3: If we are late, what is the fastest path to “file first, explain second” (where appropriate) to stop escalation?

If your team starts with these questions, most downstream errors—late filing, unnecessary penalties, messy back-and-forth with IRAS—become avoidable.

Do you understand the difference between a nil/zero filing and a filing waiver—and why teams mix them up?

Many finance teams treat “nil filing” and “waiver” as interchangeable. They’re not.

What a nil/zero filing means in practice

A nil/zero filing is still a filing. You are submitting the corporate income tax return (and related information) with:

• zero revenue / zero taxable income, or
• a loss position, or
• no tax payable after applying available exemptions/reliefs (where applicable).

You still need underlying support: basic accounts, tax computation logic, and consistency with your financial records.

What “waiver granted” means in practice

A waiver (when IRAS grants it) typically means IRAS does not require the company to file a corporate income tax return for that Year of Assessment.

Key operational implications:

• You should not assume a waiver continues year-to-year. A prior-year waiver does not automatically cover YA 2026.
• A waiver is not the same as “we chose not to file.” It is an IRAS decision/position for that YA.
• Even if a waiver is granted, you still need internal finance hygiene (books and records) so you can respond if IRAS asks questions later or if circumstances change.

Fix: set one internal rule

Use this internal rule for YA 2026:

• If you do not have written confirmation / clear status that a waiver is granted for YA 2026, plan to file by 30 November 2026.

This prevents the common scenario where the company stays silent, misses deadlines, and then has to scramble under enforcement pressure.

Are you relying on last year’s waiver or “it was fine before”—and what breaks in YA 2026?

A frequent trap is operational complacency: “IRAS waived us last year, so we’re fine again.” That logic breaks quickly when:

• the company’s status changes (e.g., starts hiring, pays vendors, opens new bank accounts);
• the group structure changes (e.g., a dormant entity becomes a holding company receiving funding, making investments, or incurring corporate costs);
• IRAS’ system expectations change based on prior interactions.

Fix: treat waiver status as a YA-specific decision point

For YA 2026, run a short “waiver verification” check early:

• Did IRAS explicitly waive filing for YA 2026 (not YA 2025)?
• Have there been any changes in activity, expenses, funding, or group transactions?
• Is the company still able to support its status with clean records if questioned?

If you cannot answer those confidently, plan for a nil/zero or loss filing rather than waiting.

Practical governance tip

Assign a single owner (director or finance lead) to sign off this statement internally:

• “Waiver confirmed for YA 2026” or “Return will be filed by 30 Nov 2026.”

This prevents the responsibility from floating between a director, a bookkeeper, and an external preparer.

If your company is dormant, what are the common YA 2026 filing mistakes—and how do you fix them?

Dormant companies are disproportionately exposed to late-filing problems because there’s often no active finance team watching mailboxes and IRAS notifications.

Common mistakes

1. Assuming dormancy automatically means no tax return is required.
2. No one monitors IRAS notices because the business is “inactive.”
3. Books are not kept current, so even a nil filing becomes hard to do accurately.
4. Confusing ACRA dormancy/accounting positions with IRAS tax filing expectations.

Fix: decide between “file nil” and “request waiver” early

For a dormant company, your decision is usually:

• File a return with nil/zero or loss figures (supported by accounts), or
• Request a waiver if you are eligible and IRAS grants it.

Operationally, the safest approach is:

• If waiver is not already granted for YA 2026, prepare to file by 30 Nov 2026.

What to prepare even if nothing happened

Even “nothing happened” needs documentation:

• a simple set of management accounts or financial statements reflecting the period;
• bank statements showing no transactions (or minimal admin transactions);
• schedules for any corporate secretarial, bank, professional, or compliance costs;
• confirmation of the company’s principal activities and any changes.

This is what allows a clean nil/loss filing rather than a rushed, error-prone submission.

If you’re a pre-revenue startup, what goes wrong when you file YA 2026 as “nil” without thinking?

Pre-revenue startups often do have activity—just not revenue. The traps are usually around classification and support.

Common mistakes

• Treating “no revenue” as “no tax position” and ignoring that expenses and funding exist.
• Filing a return without reconciling to:
• payroll records (if any),
• contractor invoices,
• subscriptions and SaaS,
• director reimbursements,
• grants (where applicable),
• foreign currency items.
• Losing track of whether costs should be capitalised or expensed in accounts (this affects the story your numbers tell, even if tax payable is zero).

Fix: build a minimal but defensible filing pack

For YA 2026, your finance lead should be able to produce:

• P&L and balance sheet (even if small);
• a clear expense ledger mapped to bank transactions;
• payroll summaries (if applicable) and CPF-related supporting records (where applicable);
• a simple tax computation bridge: accounting profit/(loss) → adjustments (if any) → chargeable income (often nil) or loss.

Management decision point

If your startup is planning fundraising, due diligence, or an exit, clean filings matter beyond tax:

• they reduce due diligence friction;
• they prevent “unknown compliance gaps” from becoming negotiation issues;
• they keep corporate records consistent across advisors.

The practical message: file like a company that expects scrutiny later, even when tax payable is zero today.

If you’re a holding company with no income, what are the hidden triggers that still make YA 2026 filing necessary?

Holding companies often assume they are “passive” and therefore exempt from filing. In practice, holding companies frequently have:

• professional fees (audit, accounting, corporate secretarial);
• bank charges;
• director fees;
• foreign investment-related costs;
• intercompany transactions (management fees, recharges, funding flows).

Common mistakes

• Declaring “no income” while ignoring intercompany arrangements.
• Forgetting that “no dividend received” does not mean “no transactions.”
• Not preparing documentation for loans, capital injections, or shareholder funding.

Fix: document the holding company story

To file confidently (nil/zero or loss) or to support a waiver request, maintain:

• a schedule of intercompany balances and movements;
• board resolutions and agreements supporting funding flows;
• bank reconciliations and fee breakdowns;
• a short narrative of the company’s activity for the year (“held 100% investment in X; incurred $Y in professional fees; no income received”).

This reduces the risk of contradictory filings across the group and prevents “surprise questions” later.

If your company has only expenses (or only small admin costs), what’s the right way to treat it for YA 2026?

“Only expenses” is not the same as “nil.” It’s usually a loss position, not a zero position.

Common mistakes

• Filing “zero” everywhere without reflecting real expenses.
• Failing to reconcile expenses to bank statements (especially when multiple cards or e-wallets are used).
• Mixing personal and company spending, then trying to unwind it at filing time.

Fix: run a simple close process before filing

Even for a small company, run a lightweight month-end/quarter-end close before YA filing:

1. Collect all bank statements and card statements.
2. Tag each transaction to an expense category (accounting ledger).
3. Separate personal vs company items and document reimbursements.
4. Confirm any accruals (unpaid invoices) and prepayments.
5. Produce a draft P&L and balance sheet.
6. Prepare a basic tax computation bridge.

Who should own this?

• If there is no finance hire, the director should appoint a named person (internal or outsourced) responsible for:
• bookkeeping completeness,
• monitoring IRAS correspondence,
• coordinating signatures/approvals.

A recurring failure pattern is “everyone thought someone else was handling it.”

If your company ceased business, what are the YA 2026 traps that lead to penalties anyway?

Ceasing business operationally does not always align neatly with IRAS’ filing timelines and system expectations.

Common mistakes

• Assuming that stopping operations automatically stops filing obligations.
• Not monitoring mail/email after ceasing, resulting in missed notices.
• Leaving accounts incomplete for the cessation period.

Fix: treat cessation as a finalisation project, not an event

Management should run a “tax closure checklist”:

• confirm the last day of operations and document it internally;
• ensure bookkeeping covers the full period up to cessation;
• reconcile final payroll/contractor payments (if any);
• ensure bank accounts and balances are tracked and explained;
• decide whether a nil/loss return is required for YA 2026 (unless a waiver is granted).

If cessation is part of a broader restructuring, ensure the person coordinating corporate changes is aligned with whoever is responsible for tax filings—misalignment here is where surprises occur.

What does late-filing escalation usually look like—and why is “wait and see” the worst response?

IRAS enforcement typically escalates in stages when a filing is missed. The exact sequence and timing can vary, but the pattern is usually:

1. Missed deadline (e.g., YA 2026 return not filed by 30 Nov 2026).
2. Reminders / follow-ups requesting submission.
3. Stronger enforcement actions may follow if non-compliance continues, which can include penalties and, in some cases, summons actions.

Common mistakes

• Waiting for “one more reminder” before acting.
• Trying to negotiate outcomes before filing (“Can you waive penalties first?”).
• Filing a rushed, inaccurate return just to stop enforcement—creating bigger issues later.

Fix: file first (accurately), then address remediation

A practical response plan when you are already late:

• Step 1: Confirm what is outstanding (which YA, which forms/requirements, what IRAS is asking for).
• Step 2: Prepare a clean filing pack (accounts, computation logic, key schedules).
• Step 3: Submit as soon as possible to stop the non-filing from continuing.
• Step 4: If penalties have been issued, respond with facts—what happened, what has been done, and what controls are now in place.

The business objective is to reduce uncertainty and prevent repeat issues. Even where relief is possible, it is rarely helped by delay or incomplete information.

If you receive an IRAS penalty notice or summons-related correspondence, what should you do immediately?

The first goal is control: stop the situation from drifting.

Immediate actions (same week)

• Do not ignore the notice. Assign one person to own the response.
• Identify the exact YA and filing requirement referenced.
• Check whether the return has actually been filed (and whether submission was successful).
• Gather your supporting documents before replying:
• accounts / management P&L and balance sheet;
• bank statements and reconciliations;
• expense schedules;
• prior-year filings/positions (including any waiver confirmations);
• correspondence history with IRAS.

Avoid these common missteps

• Replying with long explanations without committing to a filing date.
• Claiming “nil activity” without documentation.
• Sending inconsistent numbers across emails versus the filed return.

Fix: respond like a finance function, not a distressed inbox

A disciplined response looks like:

• “We have identified the missing submission for YA 2026 (or the relevant YA). We will file by [date]. We have implemented [specific control] to prevent recurrence.”

If you are working with an external tax agent, provide them full access to the history early—late-stage partial sharing is how errors repeat.

Conclusion

For YA 2026, the operationally safe assumption is that most Singapore-incorporated companies must file their corporate income tax return by 30 November 2026 unless IRAS has granted a waiver for that YA. The biggest avoidable mistake is treating “no activity” as a substitute for either (a) a proper nil/zero or loss filing supported by accounts, or (b) an approved waiver.

The next step for owners and finance teams is to run a simple decision check: waiver confirmed for YA 2026 or not; if not, prepare the minimum defensible filing pack (accounts, reconciliations, computation bridge) and assign a named internal owner to drive submission and monitor IRAS correspondence. If you are already late, prioritise an accurate filing and structured remediation response to reduce escalation risk. Where useful, Paul Hype Page & Co. can support with a practical YA 2026 readiness review, cleanup of nil/loss filings, and late-filing response coordination—so the company’s tax position is clear, consistent, and controlled.