Every EPC bidding on residential rooftop work in India right now is, whether they’ve framed it this way or not, competing inside a government scheme. PM Surya Ghar Muft Bijli Yojana has become the dominant reason homeowners are calling installers in 2026, and the subsidy math — up to ₹78,000 per household — is now baked into nearly every customer conversation before you even get to your own pricing. The EPCs winning the most volume aren’t necessarily the ones with the sharpest per-watt quote. They’re the ones who’ve turned the scheme’s mechanics — vendor empanelment, ALMM compliance, DISCOM documentation — into a repeatable operational process instead of a source of rejected claims and frustrated customers.
This guide is written for the EPC side of that equation: what the scheme actually requires from your business, where claims and installations most often go wrong, and how to build a workflow around it that doesn’t depend on any one person remembering every DISCOM’s quirks.
Key Takeaways
- PM Surya Ghar subsidy is tiered by system size — ₹30,000 (1 kW), ₹60,000 (2 kW), ₹78,000 (3 kW and above, capped) — and it's currently the single biggest demand driver in residential solar.
- Vendor empanelment is registered per DISCOM, not nationally. Expanding into a new state means new registration, not an automatic extension of your existing approval.
- ALMM compliance has to be checked at the procurement stage, before a purchase order goes out — not at installation, when a non-compliant module is already on the roof.
- Most rejected or delayed claims trace back to field documentation gaps: GIS-tagged photos, consumer-detail mismatches, incomplete technical sign-offs — all preventable with a structured checklist.
- Set customer expectations around subsidy timeline as a range, not a promise. The install is what you control; DISCOM processing time isn't.
Want to check the exact subsidy for a specific system size and state? Use our free PM Surya Ghar Subsidy Checker — it calculates central and state top-up subsidy, and net customer cost, for any size and state in seconds.
What PM Surya Ghar Means for EPC Volume in 2026
PM Surya Ghar Muft Bijli Yojana launched with a target of 1 crore households — 10 million rooftop solar installations — and by mid-2026 the scheme had crossed somewhere in the range of 45 to 50 lakh installations, with government statements pointing toward a revised near-term target of 75 lakh households by the end of the year. Whatever the exact figure is by the time you’re reading this, the direction is unambiguous: this is not a pilot program winding down. It’s the primary channel through which residential solar demand is flowing right now, and it’s still ramping.
For an EPC, that has a specific operational consequence: your pipeline is increasingly full of leads who found you because of the subsidy, not because of your brand or your pricing. That changes what they expect from the first conversation. They’ve usually already seen the ₹78,000 headline number somewhere — a neighbor, an ad, a WhatsApp forward — before they call you. If your team can’t immediately and accurately place their system size into the right subsidy slab, confirm your DISCOM standing in their area, and give a realistic timeline, you’ve already lost ground to whichever competitor can.
The Subsidy Structure, in EPC Terms
The subsidy is tiered by system capacity, and the tiers matter more to your sales conversation than most EPCs treat them:
- 1 kW system: ₹30,000
- 2 kW system: ₹60,000
- 3 kW and above: ₹78,000 (this is the cap — a 5 kW or 8 kW system does not receive more than 3 kW does)
Eligible system sizes for the scheme run from 1 kW up to 10 kW, tied to household electricity consumption and rooftop capacity. Several states also layer their own additional subsidies on top of the central amount — these vary by state and change more often than the central figures do, so treat any state-level number as something to confirm fresh for each project rather than something to memorize once and reuse.
The mistake worth avoiding here isn’t complicated, but it’s common: quoting the ₹78,000 figure to every customer regardless of system size, because it’s the number everyone’s heard. A customer sizing a 2 kW system who’s expecting ₹78,000 based on what a neighbor told them is a customer who’s going to be upset with you when the actual subsidy comes in at ₹60,000 — even though you had nothing to do with the neighbor’s system size. Getting the slab right, out loud, at the point of quoting, is a small thing that prevents a specific and avoidable category of customer complaint later.
Vendor and DISCOM Empanelment
Before you can install a single PM Surya Ghar–linked system, your company needs to be an empaneled vendor — registered and approved to operate under the scheme. This is where a lot of growing EPCs hit a wall they didn’t see coming.
Registration happens at one of three scopes, and the scope you choose determines both where you register and how large a Performance Bank Guarantee (PBG) you need to post:
- State-level: Registers you to operate within a single state, through that state’s DISCOM. PBG requirement around ₹2,50,000.
- Multi-state: Covers two or more states, registered through REC Limited rather than a state DISCOM directly. PBG requirement of roughly ₹2,50,000 per state covered.
- National: Covers all states and union territories, also through REC Limited. PBG requirement around ₹25,00,000 — a meaningfully higher bar, reflecting the broader scope.
The registration itself happens through the vendor portal, and typically requires: your company’s PAN and GST registration, incorporation or partnership documents, a cancelled cheque or passbook for the firm’s bank account, proof of at least three technically trained personnel (Suryamitra or SCGJ certified), a scanned copy of your PBG valid for at least five years, and a signed declaration as a service provider on company letterhead. Most DISCOMs and REC Limited will also want the physical original PBG submitted to their office before final approval — the online upload alone doesn’t close out the registration. Budget 7 to 15 working days for approval once your documentation is complete, longer if anything needs to be resubmitted.
Here’s the part that catches expanding EPCs off guard: state-level empanelment does not transfer across state lines. If you’re approved in Maharashtra and you win a project in Gujarat, you are not automatically empaneled there — you need a separate state-level registration, or you needed to have registered Multi-State or National from the start. This isn’t a minor bureaucratic footnote. It’s the difference between being able to service a lead the day it comes in versus discovering, project already sold, that you can’t actually execute in that state yet. If multi-state growth is anywhere in your plan for the next year, it’s worth registering for that scope now rather than state-by-state as you happen to win work in each one.
ALMM Compliance in Procurement
ALMM — the Approved List of Models and Manufacturers — is MNRE’s official list of solar module and cell manufacturers whose products are eligible for use on government-linked installations, PM Surya Ghar included. Every module you install on a subsidy-linked project needs to come from a currently ALMM-listed manufacturer and model.
The costly version of this mistake isn’t installing an obviously non-compliant product on purpose. It’s installing something that was compliant, or that a supplier represented as compliant, without checking the current list at the moment of purchase. The ALMM list isn’t static — manufacturers and specific models move on and off it — so a module that was fine for a project six months ago isn’t automatically fine today. If a non-compliant module gets caught at DISCOM inspection, you’re not looking at a paperwork delay. You’re looking at a system that may need to be re-hardwared with compliant equipment, on a roof you’ve already been paid to finish, with a customer who’s now had two installation visits instead of one.
The fix is a matter of where in your process the check happens. Verifying ALMM status at installation — when the crew is already on-site with the modules in hand — is too late to do anything but discover the problem. Verifying it at procurement, before the purchase order goes out, means a non-compliant module never makes it to the truck in the first place. If your inventory management system’s material catalogue can flag ALMM status as a required field on every solar module SKU, that check becomes automatic rather than something one careful person on your team has to remember to do every single time.
The Application-to-Disbursal Timeline
The full path from a customer’s first application to subsidy money actually landing in their account runs through several sequential steps, and being able to walk a customer through this accurately — without either over-promising or sounding evasive — is a genuine sales advantage.
- Registration: the customer registers on the national portal using their mobile number and electricity consumer number, and submits their rooftop solar application specifying desired system capacity.
- Feasibility approval: the DISCOM reviews and approves technical feasibility for that connection and capacity.
- Installation: the empaneled vendor — your company — installs the system using ALMM-compliant equipment.
- Net metering: the installation is registered for net metering, which requires its own DISCOM approval step.
- Inspection: a DISCOM inspection verifies the installation matches what was approved and installed correctly.
- Disbursal: subsidy transfer to the customer is meant to follow within roughly 30 days of a successful inspection.
In practice, the honest answer to “how long will this take” is a range, not a date. DISCOM backlog varies significantly by region and by season — expect it to slow down during the periods when application volume spikes nationally. The single biggest lever you control over how fast this moves is documentation completeness on first submission; incomplete submissions don’t just delay, they often mean starting part of the process over. Setting the expectation with your customer as “typically a few weeks to a couple of months, depending on your DISCOM’s current processing time” — rather than promising a specific week — is both more honest and, over enough projects, better for your reputation than optimistic promises that don’t hold up.
Where Claims Get Rejected
Most PM Surya Ghar claim rejections and delays don’t come from anything dramatic. They come from small documentation gaps that were entirely preventable at the point of installation:
- GIS-tagged photo issues: required installation photos that aren’t tagged correctly, or don’t cover the angles the portal expects.
- Consumer-detail mismatches: the name or property details on the subsidy application don’t precisely match the registered electricity connection.
- Incomplete technical verification: a sign-off or inspection record that’s missing a required field, or that exists in someone’s inbox instead of the system of record.
Every one of these is a field-execution problem wearing a paperwork costume. The fix isn’t hiring more back-office staff to chase down missing documents after the fact — it’s making the documentation itself a mandatory, structured part of the installation workflow, so the GIS-tagged photo gets captured correctly the first time, at the site, by the technician who’s already there, instead of being reconstructed from memory three weeks later when a DISCOM inspector asks a question nobody can answer cleanly. A project workflow that won’t let a technician mark an installation complete without the required photos and sign-offs attached turns this from a hope into a gate.
Building PM Surya Ghar Into Your Operations
None of the mechanics above are individually complicated. What makes PM Surya Ghar hard to run at volume isn’t any single step — it’s that a miss on any one project, in any one DISCOM’s process, becomes a delayed subsidy and an unhappy customer who’s likely to tell other people about it. That risk compounds as your project count climbs, which is exactly when a lot of growing EPCs feel PM Surya Ghar go from an opportunity to a liability.
A few specific places this connects directly to how SolarOps360 is built:
Lead Management — capturing system size and rough subsidy eligibility at first contact means your sales conversation starts accurate instead of correcting a customer’s ₹78,000 assumption three calls later.
Project Workflow — gating installation completion on the required documentation (ALMM-verified components, GIS-tagged photos, technical sign-offs) means the audit trail exists because the workflow required it, not because someone remembered to build it after the fact.
Inventory Management — flagging ALMM compliance at the material catalogue level means procurement decisions are checked before a purchase order goes out, not after a module is already on a roof.
Quotation & Invoicing — itemizing the subsidy amount separately from the customer-paid amount in every quote keeps the numbers honest and traceable, instead of a single bundled figure that’s easy to misremember or misquote.
If you’re running a handful of PM Surya Ghar projects a month, a well-organized spreadsheet and a disciplined team can hold this together. The scheme’s growth trajectory suggests that “a handful a month” is not where most ambitious EPCs are going to stay. Book a demo to see how SolarOps360 handles PM Surya Ghar volume as a built-in part of the workflow, rather than a set of manual checks bolted on top of it.
