If I'm empaneled as a PM Surya Ghar vendor in one state, can I install systems in a neighboring state?

Not automatically. State-level empanelment is registered per DISCOM, and approval in one state does not extend to another — even a neighboring one, and even under the same registration tier. If you win a project outside the state(s) you're currently empaneled in, you need a separate registration, or you needed to have registered Multi-State or National from the start.

What's the difference between State-Level, Multi-State, and National vendor registration?

State-Level registers you through a single state's DISCOM to operate in that state only, with a Performance Bank Guarantee (PBG) requirement around ₹2,50,000. Multi-State covers two or more states, registered through REC Limited rather than a state DISCOM directly, at roughly ₹2,50,000 PBG per state covered. National covers every state and union territory, also through REC Limited, with a PBG requirement around ₹25,00,000 — a meaningfully higher bar that reflects the broader scope.

Which states currently have the most PM Surya Ghar activity?

Adoption has shifted over the course of the scheme — Gujarat led earlier on, and by mid-2026 reporting had Maharashtra topping national installation numbers, with states like West Bengal and Jharkhand reported as lagging. Regional standings move as different states push their own outreach and DISCOM processing capacity, so treat any specific ranking as a snapshot to verify close to your planning date rather than a fixed fact.

Do different states have meaningfully different DISCOM documentation requirements?

Yes, in practice, even though the core national scheme rules are consistent. Individual DISCOMs vary in exactly what they want submitted, how their inspection scheduling works, and how quickly they process applications during high-volume periods. This is the main reason a workflow built around one DISCOM's habits doesn't automatically transfer cleanly when you expand into a new one — the underlying scheme is the same, but the operational texture at the DISCOM level isn't.

When should a growing EPC register for Multi-State or National instead of state-by-state?

If multi-state growth is a near-term plan rather than a someday idea, it's generally worth registering for the broader scope before you've already won a project in a state you're not empaneled in — the registration and approval process takes 7 to 15 working days once documentation is complete, which is time you don't have when a lead is expecting you to start next week. State-by-state registration makes sense if your expansion is genuinely opportunistic and unplanned; it's a weaker fit if you already know where you're headed.

DISCOM Empanelment State by State: What EPCs Expanding Across India Need to Know

A solar EPC that’s built a solid PM Surya Ghar operation in one state can hit a surprising wall the moment they win their first project across a state line: their empanelment doesn’t come with them. This isn’t a minor bureaucratic footnote — it’s the difference between servicing a lead the day it comes in and discovering, project already sold, that you legally can’t install it yet.

This is a guide to that specific problem: how empanelment scope actually works, what regional variation looks like in practice, and how to sequence expansion so it doesn’t stall a deal you’ve already won.

Key Takeaways

PM Surya Ghar vendor empanelment is registered per DISCOM, not nationally. Approval in one state doesn't transfer to another, even under the same registration tier.
Three registration scopes exist — State-Level, Multi-State, and National — each with a different Performance Bank Guarantee requirement and a different registration path.
Regional adoption and DISCOM processing speed vary meaningfully across states, and the leaderboard shifts over time — verify current standing rather than relying on old rankings.
If multi-state growth is part of your near-term plan, registering for the broader scope ahead of time avoids the 7-to-15-working-day approval wait landing in the middle of a live deal.

Once you’re empanelled and quoting customers, our free PM Surya Ghar Subsidy Checker calculates the exact subsidy and net cost for any system size in your state.

Why Empanelment Is Per-DISCOM, Not National

PM Surya Ghar is a central government scheme, but the actual approval, inspection, and empanelment infrastructure runs through DISCOMs — Distribution Companies — which are state-level entities. That structure is why your empanelment status is tied to the specific DISCOM(s) you registered with, not to the scheme nationally.

The trap this creates is specific and common: an EPC empaneled and operating successfully in, say, Maharashtra assumes that track record and approval status carries some weight if they pick up a project in Gujarat. It doesn’t. From the DISCOM’s perspective in the new state, you’re not empaneled there at all, regardless of your standing elsewhere — you need a registration that actually covers that territory.

The Three Registration Scopes

Vendor registration happens at one of three scopes, and choosing the right one upfront saves you from re-registering piecemeal as you grow:

State-Level: Registers you through a single state’s DISCOM, to operate in that state only. Performance Bank Guarantee (PBG) requirement around ₹2,50,000.
Multi-State: Covers two or more states, registered through REC Limited rather than any single state DISCOM. PBG requirement of roughly ₹2,50,000 per state covered.
National: Covers every state and union territory, also through REC Limited. PBG requirement around ₹25,00,000 — substantially higher, reflecting the broader operating scope.

The registration itself — regardless of scope — typically requires your company’s PAN and GST registration, incorporation or partnership documents, proof of at least three technically trained personnel (Suryamitra or SCGJ certified), a scanned PBG valid for at least five years, and a signed service-provider declaration. Most DISCOMs and REC Limited also want the physical original PBG submitted before final approval, not just the online copy. Budget 7 to 15 working days once your documentation is complete.

The scope decision is really a bet on your own growth plan. State-Level is the right call if you’re genuinely a single-state operation with no near-term expansion plan. The moment multi-state growth becomes a real possibility rather than a hypothetical, the math tends to favor registering broader before you need it — because the 7-to-15-day wait is far more painful when it’s blocking a deal you’ve already won than when it’s a planning-stage decision.

What Varies State to State, in Practice

The core PM Surya Ghar scheme rules — subsidy slabs, eligible system sizes, ALMM requirements — are consistent nationally. What varies is the operational texture at the DISCOM level: exactly what documentation a given DISCOM wants, how their inspection scheduling works, and how fast they move through applications, especially during high-demand periods.

Regional adoption has also shifted over the life of the scheme. Gujarat built an early lead in rooftop solar coverage under the program; by mid-2026, reporting had Maharashtra topping national installation numbers, while states like West Bengal and Jharkhand were reported as lagging behind. Whatever the current standing is by the time you’re reading this, the pattern that matters operationally is the same: adoption and DISCOM capacity aren’t uniform, and a state you haven’t worked in yet may process applications meaningfully faster or slower than the one you already know.

This is worth confirming directly — through your own empanelment application and early projects, or through current regional reporting — rather than assuming your home state’s DISCOM habits are representative of what you’ll find elsewhere.

Sequencing Expansion Into a New State

A practical sequence for entering a new state, rather than discovering the gaps mid-deal:

Confirm your registration scope covers it. If you’re State-Level only, this is step zero — check before you quote a project there, not after you’ve won it.
Register early relative to your sales pipeline, not in response to a specific deal. The 7-to-15-day approval window is manageable when it’s not blocking revenue.
Learn that DISCOM’s specific documentation habits before your first installation, ideally from a local hire, partner, or direct inquiry — not by discovering gaps at inspection.
Build in buffer on customer-facing timelines for the first few projects in a new state, until you have direct experience with that DISCOM’s actual processing speed.

The EPCs who expand smoothly aren’t the ones who move fastest into a new state — they’re the ones who’ve confirmed empanelment and documentation expectations before the first customer conversation happens there.

Running Multi-State Operations Without Losing Consistency

Once you’re operating across multiple DISCOMs, the operational challenge shifts from “are we empaneled” to “is every project in every state following the right process for that specific DISCOM.” That’s harder to hold together with a single generic workflow, because a checklist tuned to your home DISCOM’s habits doesn’t automatically fit a different one’s documentation quirks.

A project workflow with configurable stages per region — rather than one fixed sequence applied everywhere — lets you encode each DISCOM’s actual requirements once, so a technician in a new state follows the right process without your team having to remember it manually for every project. That’s less about any single expansion decision and more about what keeps multi-state growth from turning into multi-state inconsistency as your project count climbs.

Book a demo to see how SolarOps360 handles project workflows that vary by region without losing a consistent standard across your whole operation.