Raffles Consulting Services
Control an SRG reporting boundary change by reconciling group entities, reporting period, first-report status, provider scope, costs and disclosures.
An SRG reporting boundary change can affect the report, provider scope, eligibility analysis and project cost at the same time. A new subsidiary, disposal, restructuring or revised consolidation conclusion should not be handled only in the emissions workbook. The company needs one dated record that explains what changed and whether its first ISSB-based climate-report project still matches the grant application.
Freeze the original report boundary
Record the applicant, reporting entity, group structure, financial year, planned publication date, first-report conclusion and compliance timeline used at application. List subsidiaries, joint arrangements and other operations included or excluded, with the basis for each decision. Link the boundary to the provider quotation and data-owner map.
The current Sustainability Reporting Grant page supports a company’s first sustainability report incorporating ISSB-based climate-related disclosures before the applicable mandatory timeline. The current SRG FAQ addresses group situations, reporting periods, qualifying costs and deliverables. The company should obtain formal reporting advice where its consolidation or disclosure conclusion requires it.
Assess each boundary change across four records
For every acquisition, disposal, merger, new listing, parent-report change or reporting-policy decision, update the entity map, data inventory, consultant scope and cost schedule. State the effective date and whether comparative or partial-period information is needed. Do not delete an entity from the source register merely because it is later excluded from the report.
Test first-report status and exemption facts again. A group reorganisation can change which company publishes, which activities appear in a parent’s report and whether the applicant is still before its mandatory timeline. Compare the result with the SRG group and first-report boundary guide.
Reconcile provider work and the grant file
Ask the consultant and assurance provider to identify the changed procedures, data, fee and timetable. Separate grant-supported work from recurring reporting, unrelated sustainability advice and work created after the supported first report. Keep revised quotations, approvals and assumptions rather than overwriting the original scope.
Before claim closeout, reconcile the final published report, compliance statement, assurance work, invoices, training records and equipment or software costs with the accepted project. Escalate a material change through the required authority route before relying on it. A provider’s willingness to continue does not establish grant acceptance.
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 business support decision guide 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
- Original boundary frozen
- Change event dated
- First-report status retested
- Provider scope updated
- Final report and costs reconciled
The SRG reporting boundary change is controlled when the final report population, first-report conclusion, provider work, costs and grant record all tell the same dated story.