EDGE HRMS costs: separate subscription and maintenance

EDGE HRMS costs need a clean boundary before a company compares quotations or forecasts support. The current activity page permits software costs for a maximum of twelve months, while maintenance and GST are not supported. A bundled vendor price can therefore conceal unsupported periods and services even when the overall package meets an operational need.

Break the quotation into cost periods and services

Ask the vendor to separate licences by user and month, configuration, data migration, integration, training, implementation, support, maintenance, renewal, optional modules and GST. Match each item to a delivery date and acceptance record. If the supplier will not unbundle a multi-year price, obtain a reasonable written allocation rather than treating the full invoice as a one-year software cost.

The current EDGE HRMS activity page states that software costs are capped at twelve months and excludes maintenance and GST. It also states the current package cost and support ceilings. The EDGE FAQ explains that support remains subject to assessment and the accepted Letter of Offer.

Keep the commercial budget wider than the support forecast

Prepare one full ownership-cost schedule covering the initial project, maintenance, renewal, internal administration, data clean-up, payroll interfaces and exit or migration costs. In a second schedule, mark only the items used for the support forecast. Management should approve the full cash commitment without assuming that the authority will accept every marked item.

Test whether a discounted first year shifts cost into a later renewal or requires an unpriced service. Compare contract term, notice period, data export, service levels and price changes across vendors. Link the functional choice to the HRMS cost-savings and acceptance guide so a low initial subscription does not outweigh weak operating value.

Reconcile invoices and payment at closeout

Give each accepted item a reference to the approved quotation, contract line, invoice, full payment, deployment evidence and user acceptance. Exclude maintenance invoices, GST and software periods beyond the supported boundary from the claim schedule. Preserve them in the commercial ledger so the total project spend still reconciles.

Where the vendor changes scope or billing dates, compare the variation with the approved package before accepting it. Record how credits, free months or bundled support affect the allocation. The final file should let a reviewer reproduce both the company’s full cost and the narrower claimed amount without relying on a verbal explanation.

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

• Quotation unbundled
• Twelve-month software period isolated
• Maintenance and GST excluded
• Full ownership cost approved
• Invoices and payments reconciled

The EDGE HRMS cost file is ready when subscription months, maintenance, GST and implementation services are separately priced, approved, paid and reconciled to the deployed system.