Raffles Consulting Services
An EDGE annual cap allocation register tracks requested, offered and claimed support across activities before a company commits its shared cap.
EDGE annual cap allocation should be recorded before a company starts several supported activities in the same cap year. List each proposal, the amount requested, any Letter of Offer amount, claims paid and the balance still uncommitted. Management can then decide which projects deserve the shared support without treating an application as an award.
Enterprise Singapore’s current EDGE page states that a company can receive up to S$100,000 a year across all eligible activities. The shared cap refreshes on 1 April. It also states that up to S$30,000 of that amount may be used for single-function digital solutions, integrated enterprise systems and selected automation activities.
Start with the correct cap period
Open the register with the period from 1 April to 31 March. Record the company’s UEN and the date on which the official cap information was checked. Do not organise the register by financial year, calendar year or project start date unless those dates happen to match the official period.
The Enterprise Support and Grants hub explains the wider support landscape. The Singapore business support decision guide remains the pillar cornerstone. This register addresses the narrower task of allocating one company’s current EDGE capacity.
Separate requested support from committed support
An application amount is a planning figure. It does not prove approval. Create separate columns for the estimated support, amount requested, amount stated in an accepted Letter of Offer, approved variations and amount reimbursed. Keep the status visible so a draft or pending case does not consume the balance as if it were final.
Where management wants to reserve capacity for a later project, show it as an internal planning reserve. Do not call it an official reservation. Enterprise Singapore decides the support outcome, and the live service or formal correspondence remains authoritative for each case.
| Register field | What to record | Evidence |
|---|---|---|
| Cap period | 1 April to 31 March | Dated official page check |
| Activity | Current EDGE area and activity name | Application record |
| Requested support | Amount submitted for assessment | Portal receipt |
| Offered support | Amount and conditions offered | Accepted Letter of Offer |
| Paid support | Claim amount reimbursed | Claim outcome and bank record |
| Planning reserve | Internal estimate for a later activity | Management decision |
Identify the activities subject to the S$30,000 sub-limit
The official EDGE information describes a S$30,000 limit within the overall S$100,000 cap for specified digital and automation activities. Tag each relevant case in the register. Then calculate both the overall remaining balance and the remaining amount for the sub-limited group.
Do not assume that every technology project belongs in that group. Use the live activity description and the official application route. The EDGE project area selection record explains how to connect the business problem, activity and supplier scope before using the allocation register.
Record decisions across departments
Several teams may plan projects against the same UEN. Ask finance, operations, technology, sustainability, human resources and overseas-market owners to disclose proposed applications. Give one person responsibility for the consolidated register, while leaving each project owner accountable for its facts and delivery.
Use a short monthly review when several applications are active. Compare new proposals, approved amounts, variations, withdrawn cases and paid claims. A withdrawn or rejected application may change the planning balance, but the owner should preserve the official outcome rather than deleting the line.
Compare projects on commercial value
The cap should not make a weak project attractive. Compare the underlying problem, expected benefit, total cost, cash-flow exposure, delivery risk and readiness. Also show whether management would proceed if support is lower than expected or unavailable.
Enterprise Singapore states that EDGE support is reimbursed after the activity is completed and full payment has been made. Therefore, the register should sit beside the cash-flow forecast. A high support estimate does not remove the need to fund supplier payments and manage the claim conditions.
Update the register when an offer changes
Enter the Letter of Offer amount and conditions only from the actual document. If the project scope, cost or outcome changes, record the approved variation separately. Do not overwrite the original amount because the history explains why the remaining allocation changed.
The EDGE application receipt guide explains how to keep proof of submission. A receipt confirms that an application entered the official system. It does not establish that the company has secured the requested amount.
Model the effect of a lower support offer
For each proposed activity, add a simple sensitivity view. Compare the full project cost with the requested support, a lower support amount and no support. Show the cash required in each case and the point at which management would pause, reduce or redesign the project.
This comparison keeps the commercial decision separate from the application. It also helps the company avoid committing the whole cap to the first visible opportunity without considering a later project that may create more value.
Keep group companies and UENs distinct
Where a group has several Singapore entities, keep a separate register for each UEN. Add a group summary only for management planning. Do not transfer unused capacity between companies or assume that one entity’s eligibility, application or Letter of Offer applies to another.
Record intercompany dependencies where they affect the project. For example, one entity may own the system while another pays a supplier. Resolve the true applicant, contracting party, beneficiary and payer before submission. The allocation register should expose those facts rather than hide them in a group total.
Close the cap year with a reconciliation
At the end of March, compare the register with every Letter of Offer, variation, claim outcome and official account view available to the company. Carry no unsupported balance into the new period. Mark projects that continue operationally after the refresh, because their delivery obligations remain even when a new annual cap begins.
An EDGE annual cap allocation register gives management one defensible view of shared support across multiple activities. It protects the strongest projects, exposes double counting and keeps applications, offers, claims and internal plans in their proper places.