Raffles Consulting Services
Reconcile an EDGE HRMS package reference ID with the vendor quotation, licences, services, applicant facts and intended deployment before BGP submission.
An EDGE HRMS package reference ID should represent the solution the company actually intends to buy. The current activity route asks the applicant to build a solution package on SMEs Go Digital, generate a package reference ID through Corppass and use it for the Business Grants Portal application. A mismatch between that package, the quotation and the planned deployment can create avoidable questions even when the selected product is pre-approved.
Freeze the business requirement before building the package
List the employee groups, payroll rules, leave, claims, benefits, performance processes and interfaces that the HRMS must support. State which functions are essential for the first release and which are optional. Use the current EDGE HRMS activity to check the supported software-cost boundary, delivery period, applicant conditions and required projection.
Record the current process volume and control failures so the cost-savings forecast has an observable baseline. Do not choose licences or services only because they appear in a grant package. The final configuration must solve a defined operating problem and remain supportable by the company after implementation.
Reconcile the vendor quotation to the solution package
Create a line-by-line schedule showing product name, package, licence quantity, subscription period, professional services, taxes, discounts and excluded maintenance. Match the schedule to the SMEs Go Digital package before generating the reference ID. Ask the vendor to correct ambiguities rather than relying on an email explanation that is not reflected in the formal quote.
Record the date, preparer and Corppass user who generated the package reference ID. Keep the package output with the quotation and application working paper. If the package is rebuilt, withdraw the old reference from the file and explain why the version changed instead of leaving two apparently valid versions.
Plan deployment and claim evidence at application stage
Identify the Singapore deployment location, administrator, implementation owner, data-migration boundary, user testing and unique identifier expected at completion. The EDGE FAQ explains the wider applicant, project and claim controls. Confirm the final Letter of Offer before treating any planned component as approved.
At closeout, compare the accepted package with the deployed software, licence record, invoice, payment, completion image and unique identifier. Keep unsupported maintenance, extra years and later enhancements outside the claim schedule. A pre-approved solution still needs an applicant-owned acceptance decision.
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 Singapore business support decision 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
- Business need fixed
- Quotation normalised
- Package reference retained
- Deployment owner assigned
- Claim evidence mapped
The package is ready when the quotation, reference ID, licence plan, deployment facts and evidence plan describe one controlled HRMS purchase without unexplained extras.