Raffles Consulting Services
Control an EIS YA 2026 company filing across qualifying spend, grants, the tax return, deduction records and any cash payout application.
An EIS YA 2026 company filing needs one controlled sequence. IRAS states that companies claim enhanced deductions or allowances in the Corporate Income Tax Return. A cash payout application is available only after the return is filed and is due by 30 November 2026 for companies. The same qualifying expenditure cannot be used for both benefits.
Freeze the qualifying-spend schedule
List each EIS activity, supplier, invoice, incurred date, amount, grant or subsidy, GST treatment and supporting document. Confirm active Singapore business operations and the relevant basis period. Apply the correct activity cap and remove ineligible or unsupported cost before choosing a benefit.
The IRAS Enterprise Innovation Scheme guidance states that qualifying expenditure is net of government grants or subsidies and sets the current deduction, allowance and cash payout rules. Keep the filed Year of Assessment separate from accounting labels used in the ledger.
Choose deduction or cash payout deliberately
Compare the enhanced deduction or allowance with the 20% cash conversion for eligible activities, using the company’s tax position and cash needs. Note that the new AI adoption activity for YA 2027 and YA 2028 does not have a cash payout option. Record the authorised decision before preparing forms.
For a cash payout, verify the three full-time local employee condition and the minimum qualifying spend. Confirm that the company, rather than a related entity, incurred the cost unless an applicable recharge rule is satisfied and documented.
File, apply and read back
Complete the EIS details in the Corporate Income Tax Return and reconcile them to the schedule. File the return before opening the cash payout application. Submit any payout application by the current company due date and retain the acknowledgement, files sent and bank details through the approved secure process.
After filing, check portal status, assessment, queries and payment. Correct discrepancies through the proper route. Keep the original schedule, filed return and later adjustment as separate versions so another reviewer can reproduce the final tax position.
Use a two-person deadline check
Assign one preparer and one reviewer to confirm the company return status, payout eligibility, due date and portal availability. Run the check early enough to resolve a rejected return or access issue. The reviewer should compare the submitted totals with the approved schedule and save the acknowledgement without recording credentials or sensitive login evidence in the project file.
Turn the decision into a controlled file
Use a dated decision record that identifies the applicant, business need, current official source, chosen route, responsible owner, costs, milestones and evidence. Separate facts already verified from forecasts and assumptions. A catalogue listing, supplier statement, consultant recommendation or portal acknowledgement does not establish approval. The company remains responsible for its declarations and commercial decision.
Give each quotation, contract, invoice, payment and deliverable a stable reference. Preserve earlier versions and explain material changes instead of silently replacing them. Where the authority, tax adviser, auditor or another professional must decide a point, record the open question and obtain the required view. Do not convert uncertainty into a confident eligibility statement.
Review before commitment and again before closeout
Run four reviews: suitability, authority, implementation and closeout. At suitability, test the entity, activity and business outcome. Before commitment, freeze the proposed scope, vendor and financial assumptions. During implementation, compare actual work with approved terms. At closeout, reconcile deliverables, accepted results, invoices, full payment, operating evidence and obligations that continue.
Name the person who may approve each stage and the records that person must see. Procurement should not treat a draft application as permission to contract. A project team should not treat supplier completion as company acceptance. Finance should not treat a submitted claim as cash received. Clear status words prevent accidental commitments and weak reporting.
Handle exceptions without rewriting history
Maintain an exception log for changed facts, delayed milestones, supplier variations, cost movements, missing records and failed tests. State the effect on scope, eligibility, timing and expected value. If an authority decision or formal variation is required, use the published route before relying on the change. Silence and helpdesk receipt are not approval.
If a material defect appears, pause the affected acceptance, filing or claim item. Keep original evidence, assign corrective action and set a review date. Do not backdate records, move costs between categories or adjust a baseline after seeing the result. A candid exception with an owned resolution is more credible than a clean-looking file that cannot explain what happened.
Plan handovers before the original project team disperses. The handover should identify the current version, source locations, system access owner, next review date, open exceptions and any condition that continues after payment or filing. Restrict personal, financial and commercially sensitive records to authorised users, while giving each responsible owner enough information to perform the assigned control. Record the external event that should trigger an earlier review, such as a changed programme page, revised authority letter, supplier failure or material business change.
Verify the final outcome independently
Ask someone who did not prepare the final pack to compare the decision, current official source, approved terms, deliverables, payments and operating evidence. Recalculate totals and sample source records. The reviewer should be able to reproduce the conclusion without relying on the preparer’s memory. Record unresolved points with named owners and dates.
Use the Singapore tax cornerstone for the wider decision and keep this article as the narrower operating guide. After submission, preserve the receipt and reconcile questions, adjustments and the final registered or paid outcome. Continue any reporting, retention, asset-use or other condition that survives closeout.
Practical review checklist
- Spend schedule frozen
- Grant offsets applied
- Benefit choice approved
- Return filed first
- Submission and outcome read back
The filing is complete when the company can trace each qualifying dollar from source evidence through the chosen EIS benefit, filed return, submission acknowledgement and final IRAS outcome.