Raffles Consulting Services
Prepare redesigned SFEC wallet authorisation roles for access, programme approval, reconciliation, staff changes and evidence.
SFEC wallet authorisation roles should separate access, programme selection, cost approval and reconciliation before the redesigned credit launches on 1 December 2026. A wallet balance is not permission for one person to choose a programme, commit the company and confirm the accounting alone. The employer needs simple roles that work without shared credentials or informal approval.
Separate access from business approval
Name the wallet administrator, programme owner, budget approver, finance reviewer and senior escalation owner. Define which person may view, prepare, authorise and reconcile a use. Keep government and company credentials with authorised users. A training provider or adviser may explain a programme but should not control the employer’s access or decision.
MOM’s 3 November 2026 written answer confirms a fresh S$10,000 online wallet for eligible companies from 1 December 2026. The Enterprise Workforce Transformation Package factsheet explains the three-resident-employee threshold and immediate offset design. Live platform terms should be read back at launch.
Approve the underlying programme first
For every proposed use, record the business need, eligible programme, participants, provider, dates, total cost, other support and expected out-of-pocket amount. Confirm that the employer and programme meet the live criteria. Do not treat wallet visibility, a provider quotation or an adviser statement as programme approval.
Prevent double funding by reconciling grants, course subsidies, other credits and company payment. Show the gross cost, each support source and the amount proposed for the wallet. Keep old SFEC reimbursement claims in a separate ledger because the redesigned wallet is a fresh mechanism.
Reconcile every use and staff change
After a transaction, compare the approved record, platform entry, provider invoice, attendance or programme evidence, company payment and wallet movement. Investigate reversals, cancelled programmes and balance differences. Finance should close the entry only after official readback, not when a request is submitted.
Prepare a handover route for resignation or absence. Remove access promptly, preserve the audit trail and assign outstanding reconciliations. On 1 December, verify the signed-in company identity, eligibility, opening balance and available programme information before the first commitment. If the wallet does not match the expected facts, pause and use the official support route.
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 old-credit and new-wallet transition 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
- Wallet roles assigned
- Credentials remain individual
- Programme approval recorded
- Other support reconciled
- Staff-change handover prepared
The redesigned SFEC wallet is ready for controlled use when access, programme approval, payment and reconciliation belong to named roles and every balance movement can be traced to official evidence.