Raffles Consulting Services
Map the Sustainability Reporting Grant eligibility window, application date, reporting period and first ISSB-based report.
The Sustainability Reporting Grant calendar depends on the company’s category, reporting period and mandatory climate-reporting timeline. It is not a general subsidy for any sustainability report. An applicant should confirm the eligible first ISSB-based climate report, apply before project commencement and keep the reporting project within the approved period.
Classify the company first
Record whether the company is Singapore-incorporated and listed, its market-cap category where relevant, annual revenue, total assets, parent reporting and present sustainability-report history. Use current ACRA or SGX information for the mandatory-reporting conclusion. EDB and Enterprise Singapore administer the grant but do not determine every company-law reporting question.
The official SRG page covers Singapore-incorporated listed companies and Singapore-incorporated companies with annual revenue of at least S$100 million, subject to the detailed category and timing rules. The project must concern the company’s first sustainability report incorporating the specified ISSB-based climate-related disclosures.
Map the published windows
For non-STI listed companies with market capitalisation above S$1 billion, the page lists eligible first reports for financial years commencing from 1 January 2024 through 31 December 2027 and an application deadline of 31 January 2028. Other listed companies have an eligible period through 31 December 2029 and a 31 January 2030 deadline.
Large non-listed companies and other qualifying non-listed companies have their own rows, with eligible financial years commencing through 31 December 2029 and a published deadline of 31 January 2030. Do not use the last deadline as the preferred filing date. Work backwards from the company’s financial year and proposed project start.
Apply before the project starts
The SRG page treats started work, third-party payment and signed third-party contracts before application as retrospective unless otherwise advised. Put procurement, engagement letters and software subscriptions behind an application control. Record who can commit the company and tell vendors that proposal discussions do not authorise commencement.
The official SRG FAQ encourages companies to apply before the start of the financial year for the report in scope, so that relevant costs across that year can be considered. Confirm the approved qualifying period and Letter of Offer before assuming that an early cost will be claimable.
Define the first-report boundary
List existing annual, sustainability, climate and parent-group reports. Determine whether any already incorporates the relevant ISSB-based climate disclosures and whether the Singapore company’s activities are included in a public parent report. The official page excludes companies that have already published such a report or reached mandatory compliance, subject to the current rules.
Each company is generally limited to one application for the first qualifying report, and the FAQ explains group treatment. Record the reporting entity, consolidation boundary, financial year, publication channel and board approval. Resolve boundary questions before appointing an adviser or buying reporting software.
Build the project and evidence plan
Map IFRS S1 climate-relevant provisions and IFRS S2 requirements to data owners, controls, estimates, governance and review. Identify greenhouse-gas data, transition risks, scenario analysis, targets and financial connections that need work. Use a gap analysis with responsible dates rather than a generic disclosure checklist.
Link the calendar to the SRG first-report fit guide and the sustainability strategy guide. The business support cornerstone helps compare grant support with the company’s independent reporting obligations.
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
- Company category evidenced
- Eligible report period confirmed
- Application precedes commitment
- Group boundary resolved
- ISSB workplan owned
An SRG application is timely only when the company category, eligible first report, financial year, project start and mandatory-compliance date agree. Build that calendar before procurement, then manage the disclosure work as a controlled reporting project.