Raffles Consulting Services
Build an RIC qualifying period calendar that connects the award, expenditure, claims, continuing conditions, credits and recovery risk.
An RIC qualifying period may run for up to ten years, but the duration does not make every cost within that period qualifying. The approving authority’s award, project conditions and verified claims control the credit. A company needs one calendar that connects investment delivery, expenditure evidence, claim confirmations, tax-account credits and continuing commitments.
Translate the award into dated obligations
Extract the project start, qualifying-period end, expenditure categories, activity commitments, milestones, claim windows and reporting dates from the award. Identify conditions that apply throughout the period and those tested only at a milestone or closeout. Assign an accountable executive and an evidence owner to every item.
The IRAS RIC guidance states that each award has a qualifying period of up to ten years and describes the supported expenditure categories. The EDB incentive overview explains the investment context. The actual letter of award and authority correspondence remain decisive for the company.
Keep expenditure and credits in separate ledgers
Record vendor, invoice, payment, asset, employee or other source evidence for each expenditure item. Map it to the award category and period before including it in a claim. Separately track the approving authority’s confirmation and the credit posted by IRAS. A project cost, verified claim and available RIC balance are different records.
Where a project supports both capital and revenue expenditure, involve tax owners early. IRAS explains that the credit is treated as a government grant and may affect deductions or capital allowances. Preserve the net-cost computation and the year of assessment used. Do not wait until final tax filing to reconstruct a multi-year investment ledger.
Monitor continuing conditions and recovery triggers
Create monthly or quarterly checkpoints for economic activity, assets, jobs, expenditure, project changes and other award commitments. Define events that require escalation to the approving authority. Record decisions before changing the project. The ten-year window increases the chance that people, systems and suppliers will change, so the file must survive handovers.
IRAS states that credits may be recovered when award conditions are not met. Unused credits are applied first on a last-in, first-out basis, and an insufficient balance can produce a cash payment obligation. Include that consequence in the risk register. A long qualifying period is an operating commitment, not only a funding horizon.
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 RIC 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
- Award terms calendared
- Expenditure categories mapped
- Claim confirmations separated
- Tax treatment recorded
- Continuing conditions monitored
An RIC qualifying period is controlled when management can identify every dated condition, reproduce each claim from source records, reconcile the IRAS credit account and detect a recovery risk before it becomes a surprise.