PM-KUSUM farmer land & KYC document pack: the EPC's pre-bid collection checklist

The PM-KUSUM farmer documents checklist for EPCs is the land and KYC pack you gather from a farmer before you bid or apply. Get it right early and a clean title, matched names and a valid bank account stop a project from stalling after award. This guide gives you the pack and a reusable structure.

Which documents to collect from a farmer

The PM-KUSUM farmer documents checklist for EPCs splits into two buckets: land documents and KYC documents. Land documents prove the farmer owns or controls the plot. KYC documents prove who the farmer is and where the subsidy gets paid. You also add proof tied to the component — a pump bill for Component C, or a no-grid declaration for Component B.

One rule sits above the whole list. Accepted document types and category-certificate rules vary by state nodal agency. Always verify the exact accepted set against the relevant state application portal before you collect, because a document one state accepts may not satisfy another. Start at the PM-KUSUM hub for the wider scheme picture.

Why collect farmer documents before you bid

Collect farmer documents before you bid because a paperwork problem after award is far more expensive. A disputed title, a name that does not match across papers, or a missing 7/12 extract can freeze a PM-KUSUM project once the clock is running.

The cost of finding out late

In a Component A bid, you commit a bid security and a delivery timeline. If the land you counted on turns out to be jointly held with an absent co-owner, you lose weeks chasing consent — or lose the parcel. Checking the pack pre-bid turns a late surprise into an early decision.

Pre-bid checks save your bid security

A short pre-bid review — title, area, owner name, bank account — tells you whether to bid on this farmer's land at all. It is cheaper to walk away before you bid than to forfeit a guarantee after. Build the check into your pipeline, not your panic.

Land documents (Component A)

Land documents are the heart of a PM-KUSUM Component A pack, because the plant sits on the farmer's land for years. You need to prove ownership or a firm lease, a clean title, and the area that matches the plant size.

Ownership, the 7/12 extract and title

• Ownership proof — a sale deed, patta or record of rights in the farmer's name.
• 7/12 extract or record of rights — the latest extract showing area, owner and crop entry.
• Title and encumbrance check — confirm a clear title and no dispute or loan charge on the parcel.
• Lease agreement — if the land is leased, a signed lease that covers the full project term.

Names matter here. The owner name on the 7/12 extract should match the Aadhaar and bank records. A mismatch is one of the most common reasons a file is sent back. For lease wording and term length, see the land lease agreement guide.

KYC documents (Aadhaar, PAN, bank, photo)

KYC documents identify the farmer and route the subsidy. They apply to every component, so collect them whether you are bidding a Component A plant or applying for a Component B or C pump.

The standard KYC set

• Aadhaar card — for e-KYC and to match identity across the other documents.
• PAN card — where the SNA asks for it on the application.
• Bank account proof — a passbook page or cancelled cheque for the subsidy transfer.
• Passport photo — a recent photo for the application form.
• Mobile number — an active number linked for OTP and application updates.

The bank account is easy to overlook and costly to get wrong. The subsidy lands in that account, so confirm the name, IFSC and number before you apply. For the wider eligibility picture, see farmer eligibility and documents.

Category certificates (SC / ST / OBC vary by SNA)

Category certificates may be part of the pack when an SC, ST or OBC benefit or quota applies to the farmer. The rule is not uniform: whether a certificate is needed, and in what format, depends on the state nodal agency.

Because category rules vary by SNA, do not assume the format from one state works in another. Check the relevant state application portal for the current category-certificate rule before you collect, and note its validity date. A certificate that has expired or uses an old format is a fixable problem only if you catch it pre-bid.

Component A land docs vs Component B/C pump docs

Component A and Component B/C need different packs, because they solve different problems. Component A is a land project; Component B and C are pump projects. The KYC core is shared, but the supporting documents diverge.

What changes between the components

• Component A leans on land: ownership, 7/12 extract, title and a lease for the plant footprint.
• Component B (standalone pump) leans on a declaration that the farm has no working grid connection for the pump.
• Component C (grid-pump solarisation) leans on proof of the existing electricity connection or pump bill.

The shared core — Aadhaar, bank proof, photo and mobile — stays the same. So you can run one base pack and bolt on the component-specific documents. SNA rules still vary, so verify each component's list against the state application portal.

Common rejection reasons — and how to avoid them

Most rejected farmer files fail for a few repeated reasons. Knowing them lets you fix the pack before it goes in, not after it bounces.

• Name mismatch across the 7/12 extract, Aadhaar and bank account — make the name identical or attach an affidavit.
• Stale 7/12 extract — pull the latest record of rights; an old extract may miss a change of owner.
• Unclear title or a loan charge on the parcel — resolve the encumbrance before you bid Component A.
• Wrong bank details — a closed account or wrong IFSC delays the subsidy transfer.
• Expired category certificate or wrong format — re-issue it to the SNA's current rule.
• Blurred or partial scans — every page must be clear, complete and current.

Treat each rejection reason as a checklist item. Walk the pack against this list before submission and most files clear on the first pass.

How to organise and store the pack

Organise the pack so any team member can find a document in seconds, because a PM-KUSUM application can stall while you hunt for one missing scan. A consistent structure beats a folder of loose photos every time.

A reusable folder structure

• One folder per farmer, named with the farmer ID and village so it sorts cleanly.
• Sub-folders for land, KYC and component proof, matching the buckets in this guide.
• Clear file names — for example 7-12-extract, aadhaar, bank-proof — not IMG_2043.
• A status sheet that marks each document as collected, verified or missing.
• Version and date on documents that expire, like the 7/12 extract and category certificate.

Store the pack where the whole project team can reach it, with access control, rather than on one salesperson's phone. SuryaHub's document store and project management keep the pack with the project, so it follows the job from bid to claim.

Who is responsible for collecting the pack

The EPC or developer is responsible for collecting and checking the farmer pack, even though the farmer supplies the documents. The SNA holds the EPC to the application, so the EPC owns the quality of what goes in.

In practice, a field or sales person collects the documents at the farmer's plot, and a back office checks them against the SNA's accepted list. Splitting collection from verification catches errors early. Whoever you assign, write down who checks each pack and when, so nothing slips between the field and the application.

The farmer document pack checklist

Here is the pack in one place — each document, what it is, and which component it applies to. Use it as the base structure and adjust to your SNA's accepted list.

How SuryaHub helps you run the document pack

Collecting the pack is one job; keeping it with the project is the harder one. SuryaHub stores each farmer's documents with the project, runs the work from SNA and application steps through execution to the subsidy claim, and flags what is collected, verified or missing — so a clean pack follows the job from bid to claim. SuryaHub is pre-revenue; the only real pilots are Suryantra Energy and RGESPL, and every document rule here is one to verify with your SNA, not a guarantee.

Related guides

Frequently asked questions

Sources & references

The document rules and component requirements come from primary government sources. Accepted document types and category-certificate rules vary by state SNA — verify against the relevant state application portal at publish before you collect.

• Ministry of New & Renewable Energy (MNRE) ↗

  Scheme guidelines and the document rules for each component.

• PM-KUSUM National Portal ↗

  The application process and component-wise requirements.

• State nodal agency / state application portal ↗

  The authority on accepted document types and category-certificate rules — verify here before you collect.