EDGE application receipt control on launch day

An EDGE application receipt is the evidence that a grant application entered the official system. It is not the same as a saved draft, an uploaded quotation or an internal approval. On 30 September 2026, when new business grant support moves to EDGE, companies should preserve the final submission package and independently read back the portal reference, applicant and timestamp.

Enterprise Singapore states that EDG, MRA and PSG ceased on 29 September and that applications from 30 September use the EDGE Grant. It also says ongoing submissions and projects under the former schemes continue to be processed. Therefore, the first launch-day control is to keep new EDGE work separate from old-scheme cases.

Decide which queue the project belongs in

List the UEN, project objective, grant route and current official status before anyone opens a new form. A submitted EDG, MRA or PSG case remains in its existing queue. An approved project follows its Letter of Offer. A project that never reached submission must be assessed against the live EDGE activity and conditions.

The Enterprise Support and Grants hub explains the wider support landscape. This control answers a narrower question: what proves that one new EDGE application was actually submitted by the intended business?

Freeze the commercial facts before submission

The applicant should approve the problem, activity, supplier scope, costs, outcomes and project ownership before the authorised user submits. Do not let grant language replace the underlying business case. Management should still be willing and able to undertake the work if support is lower than expected or not awarded.

Check group ownership, turnover, employment, operating location and the selected activity against current official questions. Keep the supplier quotation, internal budget and decision record together. If a contract, deposit, payment or work start has already occurred, record it honestly and obtain advice before making any declaration.

Assign one authorised submitter and one reviewer

Name the Corppass user who will submit and the colleague who will read back the result. Do not share passwords or ask a consultant to impersonate the applicant. The submitter can prepare the final portal answers, but the applicant remains responsible for the information and declarations.

The EDGE application authority guide sets out the access handoff. Recheck that authority on launch day because a prepared file can still fail if the correct entity, role or digital service is unavailable.

Distinguish the portal status from the file on the laptop

A finished document pack proves preparation. It does not prove transmission. Likewise, a browser confirmation can be incomplete if the user closes the window before the transaction finishes. The reviewer should sign into the official business account and confirm the reference and status from the application list.

Save the acknowledgement, but also retain a clean export or PDF of the final questions and attachments where the service permits it. If the portal does not provide a single export, keep a dated field-and-attachment index. Do not reconstruct answers later from working drafts.

Preserve an EDGE application receipt without exposing credentials

Store the receipt in the project file with a descriptive name, access controls and the final package. Do not include passwords, one-time codes, authentication headers or screenshots that reveal unrelated business records. The receipt should show enough to identify the applicant, transaction and outcome without becoming a credential record.

Send project staff a short status note with the reference, date and next action. Keep full financial statements, identity records and supplier material in the approved restricted location. A broad email chain is not the project archive.

Handle a missing or ambiguous receipt

If no reference appears, stop describing the case as submitted. Reopen the official account and check whether it is a draft, failed attempt or completed transaction. Save the exact error message and time. Ask the authorised user to resolve the status through the official support route rather than repeatedly submitting the same project.

A duplicate can create conflicting answers, attachment sets and responsibilities. Before retrying, compare the project title, applicant, activity and any partial reference. Record why a fresh submission is required and who approved it.

Keep approval and claim work separate

An EDGE application receipt does not promise support. Continue tracking requests, assessment and the final decision. If support is awarded, build the delivery and claim file from the Letter of Offer, accepted scope and current claim instructions. Do not treat the submitted budget as the final approved budget.

The Singapore business support decision guide remains the pillar cornerstone. It helps management compare grants with tax support and financing rather than making the EDGE receipt the only funding decision.

Close launch day with an independent readback

The submitter should show the official reference and status to the reviewer. The reviewer then matches the applicant, project, activity and attachments to management’s approved package. Differences remain open until corrected or explained through the proper channel.

A complete EDGE application receipt record gives finance, procurement and the project owner one reliable starting point. It shows that submission occurred, preserves what was sent and names the person responsible for the next official message, without turning a receipt into a claim of approval.