- Net metering rules change by state — caps, models, fees and timelines all differ.
- Empanelment is per-state and not portable; register again in each DISCOM.
- Use one shared workflow plus a per-state rule sheet, not a single process.
- The biggest risk is applying one state's rule in another — verify before each quote.
- Keep every figure verified and current against the SERC and DISCOM.
Working net metering across multiple states is not about learning one process. It is about running one clean system that holds a different rule set for each DISCOM. Net metering is governed by each State Electricity Regulatory Commission, so the cap, model, fee and timeline change at every state line. This playbook gives you a framework to track all of it.
What changes when you cross a state line
Almost everything operational changes across a state line, even though the core idea of net metering stays the same. Export is still netted against import in kWh. But the capacity cap, the metering model above the cap, the fees, the deposits, the timelines and the settlement rules are all set locally and all differ.
That is why a process built for one state quietly breaks in the next. A quote that assumed a 500 kW net metering cap fails where the state caps lower or shifts to net billing. A timeline that worked in one DISCOM is wrong in another. Verify each figure with the SERC and DISCOM, and never carry a number across a border. Our net vs gross vs net billing guide explains the models you will meet.
Why multi-state operating is hard
Multi-state operating is hard because the rules are many, local, and moving. A growing EPC has to hold dozens of small differences in mind across teams, and any one mistake can stall a job or break a proposal. The difficulty is not the work; it is the bookkeeping of the rules.
The portability trap
The most expensive trap is assuming empanelment travels. It does not. DISCOM empanelment is per-state, so being approved in one state does not let you work in the next — you register and empanel again, and carry a bank guarantee for each. Read our DISCOM empanelment guide before you promise a client in a new state.
The per-state tracking framework
The framework is simple: for each state you work in, keep one rule sheet with the same seven fields, all verified and dated. This turns a messy memory problem into a checklist anyone on your team can read. Fill one row set per state, and update it whenever a rule changes.
Caption: One rule sheet per state, seven fields each. Source: SERC / DISCOM regulations — re-verify every 30 days against MoP/MNRE/SERC.
Date every field
Put a "verified on" date next to each figure. Net metering rules change with each amendment, and a number that was right last quarter can be wrong now. A dated sheet tells your team when a figure is stale and needs a fresh check before the next quote.
Before you enter a new state
Before you enter a new state, run the framework once as a go or no-go check. If you cannot get empanelled, or the cap and model make the economics weak, it is better to know before you promise a client. Treat entry as a decision, not a default.
- Empanelment first. Confirm you meet the DISCOM criteria and budget the bank guarantee.
- Cap and model. Check the net metering cap and whether large systems shift to net billing or gross.
- Fees and deposits. Verify the fee schedule so your quotes are accurate — see charges and fees by state.
- Timelines. Note the feasibility and meter-install windows so you can set client expectations.
- Settlement. Confirm the carry-forward and surplus payout rules for the export story.
Running jobs in parallel across DISCOMs
Running jobs in parallel works when each job carries its state's rule set with it, not a shared default. The crew on a job should see that state's cap, fee and timeline, so a worker who moves between states never applies the wrong figure by habit.
Build one workflow with state as a field, and let the rule sheet drive the steps. When a feasibility window differs by state, the job in each state should track its own clock. Our capacity limits by state table is the kind of reference you pull into each job's setup.
Team and document setup
Your team and document setup should mirror the per-state structure. Keep each DISCOM login, empanelment certificate, bank guarantee and renewal date filed by state, so nothing lapses and no one hunts for a password mid-application.
One owner per state
Name one person responsible for each state's rules and renewals. They keep the rule sheet current and flag when a SERC issues a new order. This avoids the common failure where everyone assumes someone else is watching the regulation, and no one is.
Common multi-state mistakes
Most multi-state mistakes come from carrying a habit across a border. Knowing the common ones lets you design them out of your process.
- Quoting one state's cap everywhere. Always pull the local cap before sizing.
- Assuming empanelment travels. Register fresh in each state and budget each bond.
- Using a stale figure. Date every rule and re-verify on a cadence.
- Missing a renewal. Track every empanelment and guarantee expiry per state.
- One inbox for all DISCOMs. Keep logins and records filed by state, not in one pile.
How SuryaHub helps you run many states cleanly
SuryaHub keeps each state's cap, fee, timeline, empanelment and job inside one government-workflow system, with state as a field on every job. Run each project from application to commissioning and the crew sees the right rule for the right state, every time. This is exactly the bookkeeping problem SuryaHub is built to remove. SuryaHub is pre-revenue; real pilots are Suryantra Energy and RGESPL, and every per-state figure is a verify-current value, not a guarantee.
Run every state on one system
See how SuryaHub holds a different rule set per DISCOM without confusion.
Related guides
Frequently asked questions
Is net metering the same across all states in India?+
No. Net metering is governed by each State Electricity Regulatory Commission and run by each DISCOM, so caps, metering models, fees, timelines and settlement rules differ by state. The core idea is the same, but the figures change. An EPC working in two or more states must verify each rule per state.
Can an EPC use one net metering process for every state?+
No. An EPC cannot use one process for every state, because each DISCOM sets its own caps, fees and timelines. The right approach is one shared workflow with a per-state rule sheet that captures the local figures. Verify each state regulation, and update the sheet whenever a rule changes.
What should an EPC check before entering a new state?+
Before entering a new state, an EPC should check empanelment eligibility with the DISCOM, the net metering capacity cap, the metering model, fees and deposits, the feasibility and meter-install timelines, and the settlement rules. Verify each figure with the SERC and DISCOM, because every state sets its own.
Is DISCOM empanelment valid in more than one state?+
No. DISCOM empanelment is per-state and not portable, so an EPC registers and is empanelled separately in each state and carries a bank guarantee for each. A multi-state EPC tracks every empanelment and renewal date so no listing lapses. Verify each state empanelment notice before you expand.
What is the biggest risk when an EPC works across states?+
The biggest risk is applying one state rule in another, such as quoting the wrong cap, fee or timeline, which can break a proposal or stall a job. A per-state tracking framework that is verified and kept current removes this risk. Keep one rule sheet per state and check it before every quote.
How does SuryaHub help EPCs operate across multiple DISCOMs?+
SuryaHub keeps each state cap, fee, timeline, empanelment and job in one workflow, so a crew can run net metering correctly in any DISCOM without confusing the rules. SuryaHub is pre-revenue; real pilots are Suryantra Energy and RGESPL, and every per-state figure is a verify-current value, not a guarantee.
Sources & references
This is a synthesis page. The per-state figures live in the linked state spokes, and every one comes from a SERC or DISCOM source. Always re-verify the headline facts against the current regulation before you quote, so your states never contradict each other.
- Ministry of Power (MoP) ↗
Central rules and metering policy.
- Ministry of New & Renewable Energy (MNRE) ↗
Rooftop solar scheme guidelines.
- Central Electricity Authority (CEA) ↗
Technical and metering standards.
Written by the SuryaHub team · reviewed against MoP / MNRE / SERC sources · updated 19 June 2026.
Method: High-refresh page. This is a synthesis of the per-state spokes; each cross-referenced cap, model, fee and timeline is re-verified every 30 days against MoP/MNRE/SERC and the linked state spokes to avoid contradictions. SuryaHub is pre-revenue; only Suryantra Energy and RGESPL are real pilots.
Change log: 19 Jun 2026 — first published.