Raffles Consulting Services
Prepare an SFEC supported programme source capture before 1 December 2026, separating current evidence, wallet readiness and provider claims.
An SFEC supported programme source capture should prove that a proposed workforce initiative appears on the current official route before a company assumes the redesigned credit will offset its cost. The fresh S$10,000 wallet launches on 1 December 2026. Until the relevant official platforms are aligned and the company can read its own account, planning evidence must remain separate from confirmed eligibility and use.
Create the SFEC supported programme source capture
Record the programme name, administering agency, official page, support type, employer and project criteria, supported cost, provider, application route, relevant dates and source capture date. Save the exact page or notice relied upon. A provider brochure, course catalogue label or earlier SFEC list is not proof for the redesigned wallet.
MOM’s 3 November 2026 Parliamentary answer states that the redesigned SFEC will launch on 1 December 2026 with a fresh S$10,000 online wallet for eligible companies, and that information would be aligned across Government platforms before launch. The Enterprise Workforce Transformation Package factsheet describes the package and phased workforce support.
Separate programme support from wallet use
Document the underlying programme approval and the proposed SFEC offset as separate decisions. Confirm the employer, employee, project and provider facts required by the programme itself. Then record the wallet balance, authorisation and offset only after official account readback becomes available.
Do not infer that a generally relevant training course, an EDGE activity or a workforce technology purchase is SFEC-supported. If official sources conflict, preserve the versions and obtain clarification through the stated channel. Treat a helpdesk acknowledgement as receipt of a question, not confirmation of support.
Refresh the evidence at launch and commitment
Recheck official sources on or after 1 December before committing based on the redesigned credit. Verify the signed-in company identity, wallet status, current supported programme and application or offset route. Capture who performed the check and which facts remained subject to assessment.
Keep the gross programme cost, direct support, employer out-of-pocket amount and SFEC offset in separate ledger fields. Reconcile approval, invoice, payment, wallet movement and final outcome. If the programme or wallet position changes, update the business decision without rewriting the earlier source record.
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 workforce transformation partner 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
- Official programme source saved
- Underlying criteria recorded
- Wallet assumption separated
- Launch-date refresh assigned
- Final cost and offset reconciled
The source capture is reliable when the company can reproduce the official programme basis, separate it from wallet eligibility and refresh both before commitment and final reconciliation.