RIC or REG(E): choose the Singapore investment route

RIC and REG(E) can both appear relevant to a large decarbonisation investment, but they solve different policy and project questions. The Refundable Investment Credit supports substantial high-value investment across several activity types. The Resource Efficiency Grant for Emissions targets qualifying emissions-reduction projects by manufacturers and data centres. Management should compare purpose, expenditure, payment mechanics and commitments before approaching the responsible authority.

Start with the investment objective

Describe the new or expanded Singapore activity, productive capacity, jobs, technology, expenditure and economic contribution. Then state the emissions problem, baseline and proposed reduction. A project may have both an investment story and a resource-efficiency story, but the same cost should not be presented twice without explicit authority guidance.

RIC can support activities including new productive capacity, digital or professional services, headquarters, trading, research and development, and decarbonisation. REG(E) is presented by EDB for manufacturing companies and data centres investing in energy efficiency, reductions in non-carbon-dioxide greenhouse gases or other eligible emissions reductions.

Understand the RIC mechanism

The IRAS RIC page says approved credits are based on qualifying expenditure during an award period of up to 10 years and can reach up to 50% by expenditure category, with the final quantum set by the approving authority. Categories may include capital, manpower, training, professional, intangible, outsourced-work, materials and logistics costs depending on project type.

The credit can offset specified Singapore taxes. Unused credit is refundable in cash within four years after the company satisfies the conditions. At claim, the company may make an irrevocable election for tax set-off or cash on the prescribed schedule. Model that timing instead of treating RIC as an immediate grant receipt.

Test REG(E) fit separately

The EDB incentives directory describes REG(E) as support for manufacturers and data centres making projects that improve energy efficiency or reduce eligible emissions. Prepare the operational boundary, baseline energy or emissions data, technology case, implementation timetable and verification method before discussing quantum.

Check the current REG(E) information and authority guidance for detailed eligibility, eligible cost and measurement requirements. Do not transfer an RIC percentage or expenditure category into REG(E). Likewise, a strong carbon-abatement calculation does not by itself prove that a broad investment qualifies for RIC.

Compare economics on a net basis

Create a schedule for gross project cost, supported portion, company funding, tax treatment, capital allowances, financing and receipt dates. IRAS treats RIC as a government grant for tax purposes and explains that supported expenditure is generally considered net of the grant for relevant deductions or allowances. Obtain tax advice for the actual project.

Model base and downside cases without assuming an award. Include the cost of measurement, reporting, financing and continuing commitments. If a route changes the timing rather than the total economics, show working-capital needs during construction and ramp-up. Board approval should state the project remains commercially justified under the selected assumptions.

Prepare one fact base for authority engagement

Use a common project description, entity chart, expenditure schedule, employment plan, emissions baseline and milestone plan. Add a route comparison that marks facts, assumptions and questions. A consistent fact base reduces the risk that separate teams present conflicting capacities, dates or costs to EDB, Enterprise Singapore or IRAS.

Link the decision to the RIC investment guide, the REG(E) verification guide and the business support cornerstone. Preserve written authority responses and the final award terms.

Use a controlled implementation file

Keep one dated file that links the decision, approved scope, source evidence, responsible owner, milestones, costs and final acceptance. A status label should distinguish proposed, approved, completed, claimed and paid items. This prevents an application acknowledgement or a vendor invoice from being mistaken for a completed outcome.

Review the file when ownership, scope, eligibility or timing changes. Preserve the earlier version and the reason for the change. Where a formal adviser, auditor or authority is required, record that dependency rather than replacing it with an internal assumption. Management remains responsible for accurate declarations and the commercial decision.

Stage the decision before commitment

Use four review points: fit, application or authority engagement, implementation and closeout. At the fit review, confirm the applicant, activity and business need. At the application review, freeze the requested scope and preserve the submission. During implementation, compare actual work with the approved terms. At closeout, reconcile deliverables, cost, payment, evidence and continuing obligations.

Name the person who may approve each review point and the evidence that person must see. Procurement should not treat a draft application as approval to contract. The project team should not treat a vendor completion notice as company acceptance. Finance should not treat claim submission as payment. These distinctions protect both operating quality and the integrity of any support request.

Plan for changes and exceptions

Maintain an exception log for delayed milestones, substituted staff, changed suppliers, cost movements, technical limitations and missing evidence. State the effect on scope, business benefit, eligibility and timing. Where authority approval is needed, submit the change through the official route before relying on it. Silence or a portal upload should not be read as consent.

For a material defect, pause the affected acceptance or claim item, preserve the original evidence and assign corrective action. Do not rewrite a baseline after seeing the result, backdate a document or move a cost between categories to improve the appearance of compliance. A transparent exception with a resolution is stronger than a clean file that cannot explain the actual project.

Close the project with independent readback

Have a person who did not prepare the final pack compare the approved terms, latest deliverables, invoices, full-payment evidence and operating result. Recalculate totals and test several source records. Confirm that public, employee or customer claims remain accurate. Record unresolved items separately, with owners and dates, instead of hiding them in a completion statement.

After submission, retain the acknowledgement and reconcile any questions, adjustments and final receipt to the project ledger. Continue conditions that survive closeout, including record retention, asset use, reporting or outcome commitments. The project is finished only when management can explain what was approved, what was delivered, what was paid and what must still be maintained.

Practical review checklist

• Project purpose stated
• Expenditure mapped by route
• Cash timing modelled
• Tax interaction reviewed
• Duplicate support prevented

Choose RIC or REG(E) from the project’s real purpose and evidence, not from the largest headline percentage. A route comparison should show what activity is rewarded, when value is received, which costs remain unsupported and which commitments continue after approval.