Raffles Consulting Services
Prepare an EIS training claim where employees are centrally hired or seconded, with work, recharge and headcount evidence.
EIS training claims can become difficult when the person attending the course is employed by a related entity but works for the claimant. The current rules allow certain centralised hiring and secondment arrangements, subject to evidence and conditions. A controlled schedule helps the group show who worked where, who bore the cost and which entity uses the employee for the claim.
Map the employee and cost path
Identify the legal employer, claimant, work location, reporting line, course, invoice, payer and recharge. Record the period during which the employee works for the claimant and whether that work is sole or shared. Reconcile payroll, intercompany entries and training costs. A group policy or organisation chart alone may not show the actual arrangement.
The current IRAS Enterprise Innovation Scheme page covers enhanced deductions for qualifying training expenditure during YA 2024 to YA 2028. Check the current course and business conditions separately. Do not treat every staff-development cost as qualifying merely because it improves capability.
Evidence the arrangement and bona fide purpose
The IRAS EIS e-Tax Guide describes conditions for individuals deployed through centralised hiring or secondment. The claimant should be able to produce documents supporting the work arrangement and recharge of employment costs, show bona fide commercial reasons, and demonstrate that the person works solely for the claimant entity for the relevant arrangement.
Use signed deployment terms, reporting evidence, role records, time or work output where appropriate, recharge calculations and accounting entries. Explain the commercial rationale for centralised hiring or secondment. Avoid creating documents only after the tax claim begins. Contemporaneous operating evidence is more persuasive than a retrospective memo that cannot be tied to actual work.
Prevent duplicate headcount and expenditure use
The guide indicates that the employee whose cost is recharged does not contribute to the related employing entity’s requisite headcount for the arrangement. Build an entity-by-entity employee schedule and test the same person against any cash-payout headcount condition. Reconcile the training expenditure so the same cost is not claimed by both entities.
Connect the file to the EIS cash conversion guide and the Job Redesign+ evidence guide. Keep the tax analysis linked to the transfer-pricing cornerstone where intercompany recharges are material.
Keep one controlled record
Create a dated record that connects the decision, current official source, approved scope, responsible owner, milestones, costs and evidence. Distinguish proposed, approved, completed, submitted and paid items. A portal receipt, report or invoice proves one event, not the complete outcome. Preserve earlier versions and explain material changes instead of replacing history.
Assign each document to a named owner and use consistent identifiers across quotations, contracts, invoices, payments and deliverables. Where an authority or professional adviser must decide a point, record the dependency instead of substituting an internal assumption. Management remains responsible for declarations, commercial choices and continuing obligations.
Review the work in stages
Use four reviews: suitability, authority, implementation and closeout. At suitability, confirm the entity, activity and business need. Before commitment, freeze the proposed scope and supporting facts. During implementation, compare actual work with approved terms. At closeout, reconcile deliverables, cost, payment, operating results and obligations that continue.
Name the person who may approve each review and the evidence that person must see. Procurement should not treat a draft application as authority to contract. A project team should not treat vendor completion as company acceptance. Finance should not treat claim submission as receipt. These distinctions protect both operating quality and the integrity of declarations.
Manage exceptions without rewriting history
Maintain an exception log for delayed milestones, changed suppliers, cost movements, technical limits, missing evidence and failed tests. State the effect on scope, eligibility, timing and business value. Where authority approval is needed, use the published route before relying on the change. Silence, a draft upload or a helpdesk acknowledgement is not approval.
If a material defect appears, pause the affected acceptance, filing or claim item. Preserve original evidence and assign corrective action. Do not backdate documents, move costs between categories or alter a baseline after seeing the result. A transparent exception with an owned resolution is more credible than a clean file that cannot explain the actual project.
Finish with independent readback
Ask a person who did not prepare the final pack to compare the decision, current official source, approved terms, deliverables, invoices and operating evidence. Recalculate totals and test source records. Record unresolved items with owners and dates. The reviewer should be able to reproduce the conclusion without relying on the preparer’s memory.
After submission, preserve the receipt and reconcile questions, adjustments and final outcomes to the controlled record. Continue retention, reporting, asset-use or other conditions that survive closeout. Completion means management can explain what was decided, what was delivered, what supports it and what still needs attention.
Schedule a later review suited to the decision. Compare expected results with actual operating, financial and compliance evidence. Record benefits that did not appear, new risks and actions still open. Before a later commitment or filing, check the live official source again without deleting the evidence used for the earlier decision.
Keep the decision usable for the people who operate it. Provide a short handover that identifies the current version, responsible owner, next review, open exceptions and source locations. Restrict sensitive records to authorised users, while giving each operational owner enough information to perform the assigned control. Test the handover with a real item rather than assuming that a shared folder is understood.
Practical review checklist
- Legal employer and claimant mapped
- Sole deployment evidenced
- Recharge reconciled
- Commercial reason documented
- Duplicate headcount and cost tests completed
EIS training under centralised hiring or secondment needs one consistent story across employment, work, recharge, headcount and tax schedules. The group should be able to prove the arrangement without counting the same employee or cost twice.