Raffles Consulting Services
Screen EDGE double funding risk by mapping every expense to current and past support, project purpose, invoice lines and authority decisions before applying.
EDGE can sit beside other business-support measures, but the same eligible expense cannot simply be funded twice. The current FAQ states that companies are not allowed to seek EDGE support after receiving grant approvals from Enterprise Singapore or another agency for the same eligible expenses. A useful screen therefore works at invoice-line and project-purpose level, not only by comparing programme names.
Create a complete support and expense register
List every current, approved, claimed and recently completed support arrangement for the applicant and connected project. Record agency, programme, activity, approval date, qualifying period, approved scope, supplier, invoice lines, cost categories and status. Include tax incentives or credits where they affect the net expenditure analysis, but do not assume they follow identical rules.
Use the EDGE overview for the current programme structure and the EDGE FAQ for the same-expense restriction. The selected activity page and each existing award remain necessary because a general description cannot decide a specific overlap.
Compare purpose, period and cost line
For each proposed EDGE cost, identify the deliverable and business outcome it buys. Compare supplier, service period, market, site, user group, asset, licence, employee and invoice line with prior support. A new invoice number does not make an unchanged cost new, while related projects may be distinct when their objectives and expenses can be evidenced separately.
Mark each line clear, overlapping, uncertain or excluded. Escalate uncertain items before submission. Do not split one economic cost across applications, rename a repeated deliverable or move a shared fee to a general category merely to avoid the screen.
Keep the conclusion current through claim closeout
Attach the register to procurement and finance review so later credit notes, scope changes and consolidated invoices are assessed. If another support decision arrives after the EDGE application, refresh the overlap analysis and use the published authority route for clarification or change.
Before the final claim, reconcile approved costs, actual invoice lines, payment, other support received and any tax treatment. Preserve written decisions and the assumptions supplied to each authority. A clean overlap file protects both the public claim and the company’s own project economics.
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 EDGE concurrent-activities 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
- Support register complete
- Invoice lines mapped
- Project purposes compared
- Uncertain items escalated
- Final overlap review signed
The screen is complete when every proposed EDGE expense has one traceable business purpose, one documented support treatment and no hidden duplication across invoices or programmes.