EDGE BGP submission: keep the applicant in control

An EDGE BGP submission must remain the applicant company’s act. Enterprise Singapore states that vendors and third parties must not apply, manage the grant or submit a claim on the company’s behalf. Advisers can help the company understand requirements and prepare documents, but the applicant must own the facts, decisions, declarations, portal access and final submission. A simple responsibility map protects both the application and the company’s confidential information.

Name the applicant's accountable owner

Appoint an employee or officer who understands the business problem, budget and proposed project. This person should coordinate contributors, confirm facts and control the timetable. The owner does not need to write every document, but must be able to explain the application without reading a vendor script. Record a deputy so deadlines do not depend on one person’s availability.

Set a separate final approver with authority to accept the declarations and commercial risk. The preparer and approver should review the same locked version. Keep Corppass and BGP access limited to authorised company users. Never share credentials, one-time codes or browser sessions with a vendor or external consultant.

Separate advice from submission

The current EDGE FAQ says application and claim submission and payment must not be made by vendors or third parties on behalf of the company. Translate that rule into tasks. An adviser may explain official criteria, review a draft and identify missing evidence. The company must decide what is true, enter the information and submit it.

A vendor may provide its quotation, proposal, credentials, technical scope and delivery evidence. It should not choose the applicant’s forecasts, write unsupported benefit claims or answer declarations about ownership and eligibility. If the vendor supplies draft wording, the business owner must verify and rewrite it in the company’s own factual terms.

Control the working file

Keep a company-controlled folder with the application narrative, financial model, quotations, declarations, supporting records and review comments. Give external parties only the material needed for their role. Personal data, ownership evidence and bank records should remain in the approved secure location, not in shared vendor drives or email chains.

Use version numbers and a document index. Mark draft, reviewed and final states. Record the source for every material figure, especially sales projections, job outcomes and cost savings. This allows the applicant to correct a number before submission and answer later questions without asking the vendor to reconstruct the file.

Run a declaration review

Before submission, read every declaration aloud with the accountable owner. Check registration, local ownership, group size, project start, payments, supplier relationships, concurrent funding and eligibility. Compare answers with current corporate and accounting records. An old application or a vendor questionnaire is not evidence that the present declaration remains accurate.

Stop if a statement is uncertain. Obtain internal evidence or official clarification. Do not select the closest answer simply to finish the portal form. Where the project requires legal or tax advice, record the professional conclusion separately and make sure the BGP answer reflects the actual arrangement rather than a simplified sales description.

Keep payment and claim work with the company

The applicant should contract and pay in the manner supported by the selected activity. Finance must reconcile invoices and bank evidence to approved costs. For internationalisation, the market entry setup page explains when an overseas entity may pay and be recharged, but the Singapore applicant still needs a sufficient documented trail.

At claim stage, the company should collect deliverables, confirm full payment, recheck eligibility and submit through its authorised account. Vendors can answer factual questions about their work. They should not control the claim narrative, retain the only copies of evidence or submit on the applicant’s behalf.

Retain the final audit trail

Save the submitted version, acknowledgement, portal reference and later correspondence. Record who submitted, who approved and which source documents supported the declarations. If the portal times out, read the current status before trying again. A quiet screen does not prove failure, and duplicate actions can make the record harder to reconcile.

The vendor relationship review supports conflict checks, while the ERP vendor-route guide helps test a proposed provider. Keep both connected to the business support cornerstone without handing submission authority away.

Use a practical responsibility table

Create rows for eligibility, ownership, forecasts, quotation, technical scope, declarations, portal entry, approval, submission, clarification and claim. Give each row one accountable company owner and list any adviser or vendor contribution. Avoid shared accountability labels that make it unclear who verifies the answer. The final column should identify the evidence the owner will retain.

During review, ask the vendor to confirm its own scope and credentials, not the applicant’s business facts. Ask an adviser to identify gaps and source requirements, not to approve management forecasts. Ask finance and corporate reviewers to confirm payment, group and ownership data. This division produces better evidence while keeping the applicant responsible for the final statements.

Revisit the table when staff, advisers or vendors change. Revoke unnecessary access and transfer working records to the new owner. If a consultant relationship ends, the company should still hold the complete application and claim file. This continuity is particularly important where the project runs for many months and a later claim depends on decisions made before implementation started.

Good support makes the applicant’s evidence clearer while leaving authority where it belongs. The company should understand every answer, control every portal action and be able to defend the submitted file after the vendor has left the project.