EDGE digital solution: keep use within the applicant

EDGE applicant-only use matters when a group shares staff, systems or premises. Enterprise Singapore states that supported equipment or a digital solution must be used by the applicant entity, not by its subsidiary or another related party. The company should settle that boundary before buying group licences or designing shared workflows.

Identify the applicant precisely

Start with the UEN, legal name, business activities and operating locations in the application. List the employees and contractors who will use the solution for that entity. A brand, business unit or group name is not a legal applicant. Where staff work across companies, record which employer directs each task and which entity receives the result.

Compare the proposed deployment with the company’s contracts, payroll, invoices and data ownership. If the Singapore applicant sells the service and bears the operating cost, that supports the use case. If another group company owns the customer, staff and process, the proposed project may sit outside the applicant’s business.

Apply the official related-party boundary

The current EDGE FAQ says supported equipment or a digital solution should be used only by the applicant entity and not by a related party. Treat this as an operating rule, not wording to repeat in the application. Show how licences, accounts and data access will reflect it.

Do not assume that common ownership makes group use acceptable. A parent, subsidiary, sister company, shareholder business or overseas affiliate remains a different entity. If a central team provides services to the applicant, distinguish the service from the supported system’s users and obtain current official guidance where the facts are uncertain.

Map users and licences

Create a user register with name, employing entity, role, module and approval rights. Use company email domains and identity-provider groups where practical. Licences should be purchased for the applicant’s requirements. A group licence may be commercially attractive, but the supported cost and deployment still need a clear applicant-only basis.

Review generic accounts, external consultants, shared-service employees and system administrators. Some access may be needed to implement or support the system. Record the purpose, duration and restrictions. Technical access for support should not quietly become ordinary operational use by another company.

Control shared data

List the main datasets and identify their legal owner and business purpose. Customer, employee, supplier and financial records may contain group data even when the software account is held by the applicant. Separate databases or tenant controls may be required. Where data is imported, document the source and right to use it.

Test reports and exports. A dashboard that combines several entities can blur the boundary even if user accounts appear separate. Make sure the applicant can produce its own records, audit trail and evidence without relying on unrelated transactions. Apply normal privacy and confidentiality controls throughout the design.

Check intercompany arrangements

Review cost sharing, recharges, licences and service agreements. The applicant should not claim a group cost merely because part of the invoice was allocated to it. Match the supported amount to the applicant’s approved scope, actual rights and payment evidence. Keep any unsupported group element outside the claim schedule.

If a vendor invoices a parent or another group company, pause and examine the payment route before proceeding. The EDGE overseas-payment guide explains payment evidence for an overseas affiliate context, but the same discipline applies here: the Singapore applicant must have a genuine, documented cost and use case.

Test changes during the project

Ownership, restructuring, staff transfers or a new shared-service model can change the facts after approval. Add a trigger to legal, finance and human-resources checklists. Re-run the user and data map before licences are transferred or the solution is expanded to another entity.

The EDGE ownership-change guide explains the separate continuing-eligibility issue at claim. Applicant-only use should be checked alongside it. A company may still satisfy ownership eligibility while its actual deployment has moved to a different group entity.

Prepare a claim-ready record

Retain the contract, licence schedule, user export, configuration summary, deployment evidence, invoices, payment records and a short related-party statement. Ask an independent reviewer to sample users and transactions. The aim is to show real use by the applicant without exposing passwords or unnecessary personal data.

If mixed group use cannot be separated honestly, seek current official guidance and exclude unsupported costs. Do not create artificial accounts or retrospective documents. Management can still choose a group system for commercial reasons, but it should not assume that every shared benefit is supported by EDGE.

The cleanest applicant-only record links legal entity, users, data, licences and payments. When those five facts agree, the company can explain the project plainly and manage later group changes without rewriting history.

Document the boundary in four views

Prepare a legal-entity view, a user view, a data view and a payment view. The legal-entity view names the applicant and every related company. The user view lists the staff who will access the solution and their employing entity. The data view shows whose customers, transactions and records will be processed. The payment view identifies the contracting party, invoice recipient and bank account. All four should point to the applicant as the beneficiary.

Shared premises, common directors or a group brand do not remove the entity boundary. Where a central team supports several companies, define whether its users act for the applicant and how access is restricted. Configure separate tenants, roles, cost centres or datasets where appropriate. Do not rely on an internal recharge to turn another company’s use into applicant use. Ask Enterprise Singapore for written clarification when the operating model remains ambiguous.

Turn the rule into implementation controls

Include the boundary in the vendor brief and acceptance test. Require the user list, domain restrictions, administrator ownership, data migration source and reporting scope to match the applicant. Review trial accounts and sandbox access before go-live. A small access review can reveal that related-company staff were included by convenience, even though the application described a single-entity deployment.

Retain the approved application, contract, invoices, payment evidence, user export, licence allocation and system screenshots in one indexed file. At claim time, reconcile the paid licences and actual users to the approved scope. If the business later wants a group-wide deployment, treat that as a separate commercial decision and obtain programme guidance before changing the subsidised project. Clear boundaries protect the claim and produce cleaner internal accountability.