How to Implement a CSR Project Under the Companies Act: A Practical Step-by-Step Guide

A CSR project should not begin with a fund transfer. For a finance or CSR head, the safer starting point is a documented chain from legal eligibility to Board approval, implementation and evidence.

1. Confirm applicability and obligation

Establish whether Section 135 applies and calculate the prescribed obligation. Applicability is tested using the immediately preceding financial year; the spending obligation is generally 2% of average net profits of the three immediately preceding financial years, calculated under the Act and rules.

2. Define the project

Document purpose, beneficiaries, geography, duration, budget and measurable outputs. Then map the project to Schedule VII. “Socially useful” is not itself a statutory eligibility test.

3. Check exclusions

Test the proposal against the CSR Rules. Exclusions include activities in the normal course of business, political contributions, specified employee-benefit activities, marketing sponsorships and activities undertaken to fulfil another statutory obligation.

4. Select the implementation route

CSR may be undertaken directly or through permitted implementing entities. Where an implementing agency is used, verify eligibility, registration and supporting documents before releasing funds.

5. Obtain governance approval

The CSR Policy, projects and annual action plan should pass through the company’s prescribed governance process. Board papers should show why the project qualifies and how it will be monitored.

6. Release and monitor

Maintain sanction letters, agreements, utilisation evidence, invoices, progress reports and bank records. The Board must satisfy itself that funds are used for the approved purpose.

7. Handle year-end correctly

Reconcile approved expenditure, actual utilisation and the remaining obligation. If money is unspent, classify the amount correctly and apply the applicable transfer mechanism.

What this means for management

The strongest workflow is eligibility → project classification → due diligence → approval → implementation → utilisation monitoring → reconciliation → reporting. CSR becomes easier to defend when every step leaves an evidence trail.

Start with a legal eligibility memo

Before a project reaches the CSR budget, prepare a short eligibility memo. It should record why Section 135 applies, the calculated obligation, the proposed Schedule VII category, the implementing route and the principal exclusions considered. This single document prevents the common situation in which a project is approved commercially first and its legal classification is debated later.

Build the project file before releasing money

A project file should contain the concept note, beneficiary profile, geography, duration, budget, milestones, implementation agreement and monitoring design. If an implementing agency is involved, retain its registration and eligibility records, CSR registration details where required, governing documents, financial information and due-diligence assessment. The objective is not paperwork for its own sake. It is to establish a traceable link between the approved project and the expenditure actually incurred.

Separate approval from execution

The company should distinguish the decision to approve a project from the operational act of implementing it. Procurement, fund release, vendor selection and project monitoring should follow the company’s internal controls. Finance should not rely solely on an implementing partner’s narrative report; it should reconcile bank records, utilisation evidence and approved budgets.

Close the project deliberately

At completion, compare sanctioned amount, released amount, eligible expenditure and unspent balance. Obtain completion or utilisation documentation, record the outcome against the original objective and determine whether any unspent amount attracts a statutory transfer route. A clean closure makes the annual CSR reconciliation substantially easier.

Management checklist

For each project, management should be able to answer six questions: Is it legally eligible? Who approved it? Who is implementing it? What evidence proves utilisation? What outcome was targeted? What happens to any unspent amount? If these answers are documented before year-end, CSR compliance becomes a controlled process rather than a retrospective exercise.

Editorial verification note

Primary: Companies Act, 2013, Section 135/Schedule VII and Companies (CSR Policy) Rules, 2014. Secondary: current MCA guidance/notifications. Recheck amendments and filing instructions immediately before publication.

A practical internal control model

Assign four owners: business for project delivery, CSR/secretarial for legal and governance checks, finance for expenditure and reconciliation, and senior management for escalation. A monthly project tracker should show approved budget, spend, implementation status, missing evidence and forecast unspent amount. This division of responsibility reduces the risk that one team assumes another team has completed a statutory step.

A practical management lens

For management review, the project note should also state what could make the project fail: delayed approvals, weak partner capacity, procurement delays, beneficiary access or an unrealistic implementation period. Each risk should have an owner and mitigation. This converts CSR implementation from a simple spend plan into a managed programme. It also gives the Board a better basis for understanding why actual spend may differ from the approved budget and whether a delayed project should remain in the annual action plan.

Final review point

The implementation agreement should also define reporting frequency, permitted use of funds, change-control procedure, audit or verification rights, treatment of unspent funds and consequences of non-performance. These clauses are especially valuable where the implementing partner controls a significant portion of the project budget. A clear agreement reduces the risk that the company discovers a compliance problem only after the project has ended.