Fix PM Suryaghar Portal Errors: 2026 Troubleshooting Guide

A PM Suryaghar portal error at the wrong moment can stall your ₹78,000 rooftop solar subsidy by weeks. The national portal at pmsuryaghar.gov.in handles applications from every DISCOM in India through a single login funnel, and the same OTP failure, K-number rejection, or Aadhaar mismatch that blocks a Jaipur household also blocks one in Surat or Pune. In 2026, after two years of live traffic, the error patterns are well-mapped — and almost every one of them has a fix you can run yourself in under an hour. This guide takes you through each error category, the exact text the portal shows, the root cause on either the portal or the DISCOM side, and the step-by-step recovery path.

If you’re staring at a red banner that won’t go away, jump straight to the layer that matches your symptom. If you’re about to apply, read it end-to-end as a prevention checklist — the application that doesn’t trigger an error is the one that ships fastest.

Direct answer. PM Suryaghar portal errors fall into seven categories: OTP and login failures, Aadhaar–bill name mismatch, consumer-number or K-number not found, sanctioned-load mismatch, document upload format failures, bank account not Aadhaar-seeded for DBT, and vendor selection greyed out. Most portal-side errors clear within 24–72 hours; DISCOM-side fixes take 7–15 days. The ₹78,000 maximum central subsidy on pmsuryaghar.gov.in stays valid for 3 kW and above, provided you resolve any error before the 15-day auto-close window.

If your application is sitting at “Pending” or “Document Deficiency” right now, the clock is ticking — auto-closure happens 15 days after the deficiency notice, after which you must start over. So fix the error first, then read the rest for prevention.

Why PM Suryaghar Portal Errors Happen

The PM Suryaghar portal isn’t a standalone application — it’s a thin federation layer that sits on top of every DISCOM’s billing database in India. When you enter your consumer number, the portal makes a real-time API call to your DISCOM’s IT system, pulls your account details, sanctioned load, and meter status, and renders the response back to you. That single architectural choice — central UI plus distributed DISCOM APIs — is the root cause of nearly every error you’ll see.

When your DISCOM’s API is slow, your portal hangs at “Fetching account details.” When their database has stale Aadhaar–consumer linkage from a 2019 KYC drive, you get an Aadhaar mismatch even though both your documents are correct today. When the Ministry of New and Renewable Energy (MNRE) team pushes a new validation rule mid-week, OTP delivery breaks for 36 hours until the SMS gateway is reconfigured. None of these are “your” errors — they’re system errors that surface in your session.

The other half of the architecture is the Direct Benefit Transfer (DBT) pipe. Even after your DISCOM commissions the meter, the subsidy money flows through the Public Financial Management System (PFMS), which checks your Aadhaar–bank seeding via the National Payments Corporation of India (NPCI) mapper. If your bank told NPCI in 2022 that your old account was Aadhaar-seeded, but you closed that account last year, the DBT bounces with a “Bank Not Seeded” code — even though your current bank account does have your Aadhaar.

Understanding this matters for one practical reason: knowing whether an error is portal-side, DISCOM-side, or DBT-side tells you whether to retry in 30 minutes, raise a ticket on the portal, walk into a DISCOM office, or visit your bank branch. The seven-layer map below maps every common error to its owner.

Across roughly 4,200 PM Suryaghar applications we tracked through Heaven Green’s customer pipeline in 2024–2025, here’s how the error frequency breaks down — and how quickly each category resolves.

The 7-Layer Suryaghar Portal Error Map

We’ve named the framework we use internally — “The 7-Layer Suryaghar Portal Error Map” — because every error you’ll see in 2026 maps to exactly one of seven layers. Once you know which layer your error belongs to, you know who owns the fix and how long it will take. If you’re about to read a frustrating help-desk reply that says only “contact your DISCOM,” this map gives you the actual technical context the help-desk agent didn’t share.

Layer	Error family	Typical codes	Owner	Fix time
1	OTP and login failures	OTP-001, LOGIN-002	Portal (MNRE)	1–6 hours
2	Aadhaar–bill name mismatch	ADM-205	Consumer + DISCOM	7–15 days
3	Consumer / K-number not found	KMN-101	DISCOM	3–10 days
4	Sanctioned load mismatch	SLM-220, LE-301	DISCOM	15–25 days
5	DT capacity exceeded	DTC-301	DISCOM	30–60 days or accept cap
6	Document upload failure	DOC-150, DOC-152	Consumer	< 1 hour
7	Vendor selection / DBT seeding	VEN-401, BNS-410	Consumer / Bank	1–7 days

The seven layers are sequential in the application funnel — you can’t trip Layer 5 before you’ve cleared Layer 1, and a Layer 7 error means you’ve already cleared the first six. That sequence is useful diagnostically: if you’re stuck on Layer 3, ignore advice about document formats (Layer 6) — it doesn’t apply to your problem yet.

Below we walk through each layer with the exact portal text, the underlying cause, the precise recovery steps, and the time you should give it before escalating. Where a layer covers more than one error pattern (like Layers 4–5, which both relate to capacity), we group them. Where a layer needs a dedicated section because the recovery is involved (Layers 1, 2, 3, 6, 7), we give it its own H2.

For broader context on how the portal funnel works end-to-end — including the screens you’ll see before any of these errors can appear — read our PM Suryaghar complete guide first, then come back here for the troubleshooting layer.

OTP and Login Errors (Layer 1)

OTP and login failures are the loudest and most common Layer 1 error. You enter your mobile number, hit “Send OTP,” and either nothing arrives, the same OTP gets reused, or the portal says “Invalid OTP” three times before locking you out. Across our sample, OTP issues accounted for 14% of all first-attempt errors and 41% of “the portal isn’t working” customer tickets.

There are four distinct sub-causes, and the fix differs for each.

Sub-cause A: SMS gateway congestion. Between 6 PM and 10 PM IST, the portal sees its highest traffic. The MNRE SMS aggregator throttles delivery, and your OTP may arrive 5–8 minutes late — by which point you’ve hit “Resend” twice and now the system has three pending OTPs for the same session. Fix: wait 10 minutes, refresh the page, request a fresh OTP between 11 AM and 4 PM, and enter the most recent code only. Do not click “Resend” repeatedly.

Sub-cause B: DND registration blocking transactional SMS. Some telecom operators incorrectly flag MNRE’s OTP route as promotional, and your DND status blocks it. Fix: SMS “START” to 1909 from the affected number to whitelist transactional SMS, then retry after 30 minutes. Airtel and Vi users see this more than Jio.

Sub-cause C: Mobile number mismatch with Aadhaar. If the portal is doing an Aadhaar OTP (some screens do this for KYC, not the login OTP), it sends the code to the mobile number registered in your Aadhaar — not the one you typed. If your Aadhaar still carries a mobile number you stopped using, the OTP goes there. Fix: update your Aadhaar mobile number through the UIDAI portal or a nearby Aadhaar Seva Kendra. Allow 5–7 days for propagation.

Sub-cause D: Session timeout giving a “Login failed” error after correct OTP. The portal kills sessions after 20 minutes of inactivity. If you typed the OTP after a delay, the back-end discards it as expired. Fix: clear cookies, close all browser tabs, open a fresh incognito window, and complete login within 5 minutes of the OTP arriving.

If none of the four fixes work and the error code shown is OTP-001 or LOGIN-002, the issue is on the MNRE side — call the helpline at 1800-180-3333 or email pmsuryaghar@gov.in with a screenshot. Portal-side outages are typically resolved within 6 hours.

Aadhaar–Bill Name Mismatch (Layer 2)

The error reads “Aadhaar Demographic Mismatch” with code ADM-205, and it shows up the moment you submit your consumer number on Stage 2. The portal pulls your name from the DISCOM database and compares it to your Aadhaar via the UIDAI demographic API. If the two don’t match exactly, you’re blocked — even if the difference is “Rajesh Kumar” on Aadhaar and “Rajesh K.” on the bill.

This is the highest-frequency Layer 2 error, hitting 22% of first-attempt applications. The fix is either consumer-side (update one document) or DISCOM-side (update the billing record), and choosing correctly saves 7–10 days.

Step 1: Decide which record is wrong. The “correct” version is whichever matches your PAN, bank account, and ration card. If your Aadhaar has the full name and your DISCOM bill has only initials, update the bill. If your Aadhaar still uses your maiden name and your bill carries your married name, update the Aadhaar.

Step 2A: If updating the DISCOM bill. Visit your DISCOM customer service centre with your Aadhaar, latest bill, and a name-correction form. The DISCOM updates the billing record within 7–15 days. Some DISCOMs let you do this online — Tata Power, Adani Electricity, and MSEDCL all have a “Change of Name” digital form.

Step 2B: If updating Aadhaar. Visit an Aadhaar Seva Kendra with supporting documents (PAN card, marriage certificate, gazette notification). Update takes 7–10 days to propagate to the UIDAI demographic API that the portal queries.

Step 3: Resubmit on the portal. Once one record matches the other, return to the portal, log in with your old session reference number (it stays alive for 30 days), and resubmit. The ADM-205 flag clears automatically once the demographic check passes.

Mismatch type	Frequency	Recommended fix	Time
Initials vs full name	41% of ADM-205	Update bill — easier	7–15 days
Spelling variation (Rajeev / Rajiv)	24%	Update whichever has fewer downstream uses	7–15 days
Married vs maiden name	18%	Update Aadhaar with marriage certificate	10–14 days
Surname order swap	11%	Update bill via name correction form	7–10 days
Different person entirely	6%	Property transfer + Aadhaar update — both	30+ days

For a full taxonomy of name-mismatch and other rejection patterns, see our PM Suryaghar rejection reasons breakdown. If you’re in Gujarat — where the bill name format is especially strict — read the PM Suryaghar Gujarat complete guide for the state-specific paperwork.

A subtle variant of ADM-205 occurs when both documents are correct individually, but the DISCOM hasn’t pushed an updated record to the central API. We’ve seen this in Maharashtra’s MSEDCL territory — the customer updated their name three months ago, the bill prints correctly, but the API still returns the old name. The fix here is to file a written grievance with the DISCOM’s IT helpdesk asking them to “push the updated demographic record to the PM Suryaghar API.” It’s clunky, but the fix is 3–4 days.

Consumer Number / K-Number Not Found (Layer 3)

Code KMN-101 (“K-Number Not Mapped”) is the second-most-common error, hitting 18% of first-attempt applications. The portal returns “Consumer details not found for this account” and stops you cold. Three sub-causes account for nearly all instances.

Sub-cause A: Wrong field on the bill. Each DISCOM uses a different label — JVVNL uses “K-Number,” Tata Power Mumbai uses “Consumer Number,” MSEDCL uses “Consumer Number” but the field that the portal wants is actually “Account Number.” Reading the wrong field is the single most common reason for KMN-101. Fix: match your DISCOM to the field name in the table below, find that exact field on your bill, and re-enter.

DISCOM	Field name on bill	Length	First-digit hint
JVVNL / JdVVNL / AVVNL (Rajasthan)	K-Number	10–11	Zone-code prefix
MSEDCL (Maharashtra)	Consumer Number	12	Begins with 0
Tata Power Mumbai	A/C Number	9	—
Adani Electricity Mumbai	CA Number	12	—
BSES Rajdhani / Yamuna (Delhi)	CA Number	9–10	—
Tata Power-DDL (Delhi)	CA Number	8	—
Torrent (Surat / Ahmedabad)	Service Number	8	—
DGVCL / PGVCL / UGVCL / MGVCL (Gujarat)	Consumer Number	11	—
TANGEDCO (Tamil Nadu)	Service Connection Number	12	District code prefix
UPPCL (Uttar Pradesh)	Account Number	10	—

Sub-cause B: Stale DISCOM API mapping. New connections or connections that recently changed plans aren’t always synced to the portal API. The DISCOM has you, but the portal can’t see you. Fix: wait 48 hours after your most recent bill is generated, then retry. If it still fails after a full bill cycle, raise a ticket on the portal with your DISCOM name and account number — MNRE escalates to the DISCOM’s IT team within 3 days.

Sub-cause C: The portal hasn’t loaded your DISCOM yet. A handful of small DISCOMs (mostly cooperative-society electricity boards in remote areas) aren’t yet integrated. Fix: check the official list of integrated DISCOMs at pmsuryaghar.gov.in. If your DISCOM is missing, you cannot apply yet — wait for integration or contact MNRE for a manual application path.

If you’re applying for a connection that was inherited or transferred, the mapping is almost certainly stale — the DISCOM’s billing system has the new owner but the central API still has the previous one. File a written name-transfer confirmation request with your DISCOM and ask them to push the updated record to the PM Suryaghar API. This typically clears within 5–7 days.

Sanctioned Load and Capacity Errors (Layers 4–5)

Layers 4 and 5 cover capacity errors — your home’s sanctioned load and the local distribution transformer’s headroom. Both block the application at the feasibility stage, but the recovery path is different.

Layer 4 — Sanctioned Load Mismatch (SLM-220). Your bill shows a sanctioned load of 2 kW, you applied for a 3 kW solar system, and the portal rejects with “Proposed capacity exceeds sanctioned load.” Solar capacity must equal or be less than your DISCOM-sanctioned load, full stop. The fix is a load enhancement request through your DISCOM, which adds 15–25 days but saves the entire application.

Steps to enhance sanctioned load:

1. Download the load enhancement form from your DISCOM’s website (or pick it up at the customer service centre).
2. Fill in the new requested load — round up to the nearest standard slab (3 kW, 5 kW, 7 kW, 10 kW). Don’t ask for less than your intended solar capacity.
3. Submit with your latest bill, ID proof, and a one-page reason note (“installing rooftop solar under PM Suryaghar — need 3 kW sanctioned load”).
4. Pay the enhancement fee — typically ₹500–₹2,000 depending on the DISCOM and the kW step.
5. DISCOM engineer inspects the existing connection (1–2 days), confirms the meter can handle the load.
6. Updated sanctioned load reflects on your next bill (10–25 days from submission).
7. Restart the PM Suryaghar application with the new bill attached.

Layer 5 — Distribution Transformer Capacity Exceeded (DTC-301). This is a tougher error. Your sanctioned load is fine, but the local distribution transformer (DT) that feeds your home is already loaded above 90% of its name-plate rating. Adding solar export to the same DT would push it past safe limits, so the DISCOM flags your application with a conditional clearance — usually offering export capping (you can install solar but can’t export above X kW to the grid). For most residential 3 kW systems, accepting the conditional clearance is the right move; the financial impact on payback is under 6%.

If you want full export rights, you need the DISCOM to upgrade the DT. That’s a 30–60 day project that the DISCOM funds, and the priority depends on neighbourhood load growth. Push for it only if you’re installing 5 kW or above where the export economics matter.

For a deeper walkthrough of how DISCOM-side feasibility works in practice, the PM Suryaghar JVVNL process article shows the exact six-stage funnel with timelines. The principles apply across most Indian DISCOMs even though the names differ.

Document Upload Failures (Layer 6)

Layer 6 errors are the easiest to fix — they’re almost always under your control — but they account for 19% of all first-attempt portal errors because the spec isn’t published clearly. The portal expects:

• File format: PDF, JPG, or PNG only. HEIC (iPhone default), WEBP, and TIFF are rejected.
• File size: under 2 MB per document. Some DISCOMs cap at 1 MB.
• Resolution: 300 DPI minimum for scanned documents. Mobile photos at 72 DPI pass for roof photos but often fail for Aadhaar and bills.
• Aadhaar mask: the first 8 digits of your Aadhaar number must be masked. Upload unmasked Aadhaar and you trigger error DOC-152 (“PII compliance failed”) instantly.
• Bill currency: dated within the last 3 months and showing “Paid” status. Unpaid bills are rejected.

Document	Common failure	Fix
Aadhaar (front + back)	Unmasked, exceeds 2 MB	Use UIDAI masked download, compress to under 1 MB
JVVNL/MSEDCL/Tata bill	Older than 3 months, not “Paid”	Download fresh bill, pay outstanding, then upload
Bank passbook page	Blurred IFSC	Re-photograph in good light, ensure IFSC and account number are sharp
Roof photograph	HEIC format, wide-angle	Convert to JPG, shoot at native 1x, daytime, all 4 corners visible
Property ownership proof	Sale deed too large	Upload only the first 3 pages (parties, schedule, signature) at 300 DPI
Self-declaration form	Unsigned, wrong template	Use the portal-generated template — don’t substitute your own

The Aadhaar masking workflow trips up more people than any other Layer 6 error. To mask Aadhaar correctly: log in to myaadhaar.uidai.gov.in, click “Download Aadhaar,” tick “Masked Aadhaar,” verify with OTP, and download. The first 8 digits will show as XXXX-XXXX, only the last 4 visible. This is the only file format the portal’s PII checker accepts.

Compressing files without quality loss: for PDFs above 2 MB, use a desktop tool like ILovePDF’s “Compress PDF” or the inbuilt “Reduce File Size” option in Preview (macOS) or Adobe Acrobat. For JPGs, set quality to 85% and resolution to 1500×2000 — that’s enough to pass the readability check and small enough to upload.

If your upload completes but the portal still says “Document not visible,” the file passed size and format checks but failed the OCR readability check. Re-shoot the document in better light, avoid shadows, and ensure all four corners are inside the frame. For a printable list of accepted documents with sample formats, download our Suryaghar document checklist PDF.

Vendor Selection and Empanelment Errors (Layer 7)

You’ve cleared six layers, your feasibility is approved, and now you’re on the vendor-selection screen — and the “Select Vendor” dropdown shows greyed-out names or returns “No vendors available in your area.” Layer 7 errors are the final hurdle before installation, and they break down into vendor-side, bank-side, and portal-side causes.

The most common Layer 7 errors:

1. 1
   Vendor dropdown is empty (VEN-401). Your DISCOM hasn't pushed its empanelled vendor list to the portal yet, or your pin code falls outside the vendor service-area filter. Wait 24 hours, then raise a portal ticket if still empty.
2. 2
   Your chosen vendor is greyed out. Vendor has hit their monthly quota or hasn't renewed empanelment for the current quarter. Pick the next-best vendor or wait until quota resets on the 1st of next month.
3. 3
   "DBT Bank Not Seeded" (BNS-410). Your bank account exists but NPCI's mapper doesn't see it as Aadhaar-linked. Visit your bank branch, submit an Aadhaar seeding form, and confirm seeding via the NPCI mapper portal in 2–3 days.
4. 4
   Vendor quote not appearing in portal. The vendor's quote was generated outside the portal flow. Ask the vendor to re-issue the quote through their portal login — DISCOM cannot approve out-of-band quotes.
5. 5
   "Vendor KYC pending" warning. Vendor's GST or PAN refresh is overdue on the portal. Vendor side; ask them to update their KYC documents — usually a 1-day fix.
6. 6
   "Capacity exceeds vendor quota." The vendor has fulfilled their state-allocated kW for the month. Pick a vendor with remaining capacity or wait for quota reset.

The DBT Bank Not Seeded error (BNS-410) deserves its own callout because it’s the single error that delays subsidy disbursement after installation is complete. Even if your application sailed through every other layer, if your Aadhaar–bank seeding is broken when the meter is commissioned, the PFMS payment bounces and you have to resubmit bank details. To pre-empt it, check seeding before you apply: visit resident.uidai.gov.in/bank-mapper, enter your Aadhaar, and confirm which bank is marked as your “primary seeded” account. If it isn’t the bank you want the subsidy to land in, visit that bank branch and submit an Aadhaar seeding form. NPCI updates within 48 hours.

Need a vendor that handles every error layer for you? Heaven Green Energy is empanelled across 22 DISCOMs in India and runs portal applications end-to-end — including pre-checking your Aadhaar seeding, K-number mapping, and sanctioned load before submission. Talk to our PM Suryaghar specialist →

For applicants who want to do the entire portal walkthrough themselves with screenshots, our step-by-step how to apply for PM Suryaghar guide pairs naturally with this troubleshooting layer — read it before you start, and keep this open in another tab while you apply.

When to Escalate to the MNRE Helpdesk

Not every error needs an MNRE ticket. Escalating too early wastes your 15-day clock; escalating too late means auto-closure and a full restart. Here’s the rule we use internally: try the self-fix first, give it the time published in the layer map, and escalate only after that window has lapsed.

How to file an effective MNRE escalation:

• Channel: call 1800-180-3333 (toll-free, 9 AM–8 PM IST) or email pmsuryaghar@gov.in. The email route is better for documented escalations because it generates a ticket number you can track.
• Include: your Application Reference Number (ARN), the exact error code shown, a screenshot, the DISCOM name, and the date the error first appeared.
• Set expectations: MNRE acknowledges within 24 working hours and resolves portal-side issues in 3–5 working days. DISCOM-side issues take longer because the ticket has to be relayed.
• Don’t: call multiple times in one day, raise duplicate tickets, or contact your local DISCOM office for portal errors — they can’t help with central portal issues.

Verdict. Treat the MNRE helpdesk as a second-line resource, not a first call. Roughly 71% of portal errors resolve themselves within 24 hours if you wait through DISCOM API sync cycles, and another 18% resolve via the self-fix paths above. Only the residual 11% — genuinely stuck applications — benefit from escalation. Knowing which 11% to escalate, and when, is the difference between a 60-day timeline and a 120-day timeline.

The official PM Suryaghar grievance tracker (accessible after login) gives you a public ticket ID for every escalation. Save the ID; reference it on every follow-up call. Tickets without an ID get lost in the queue.

How Heaven Green Energy Helps with Portal Errors

We run PM Suryaghar applications across 22 DISCOMs and roughly 4,200+ residential rooftop systems each year. The portal is the single biggest source of friction in the customer journey, and over the last two years our operations team has built a pre-flight check that eliminates 80%+ of common error categories before the application is even submitted.

Here’s what our PM Suryaghar specialist team does for every customer:

• Pre-application audit. We verify your K-number, sanctioned load, Aadhaar–bill name match, and Aadhaar–bank seeding before opening the portal — catching Layer 2, 3, 4, and 7 errors at zero cost to you.
• Document preparation. Aadhaar masking, bill compression, ownership proof scanning, all done to the exact spec the portal accepts. Layer 6 errors drop to near-zero.
• DISCOM relationship management. We’re in direct contact with the renewable energy cells at JVVNL, MSEDCL, BSES, Tata Power, Adani, and most Gujarat DISCOMs. When a Layer 3 or Layer 4 issue needs DISCOM-side action, our coordinator routes it through the right desk.
• Portal monitoring. Once your application is submitted, we monitor its status daily and flag any deficiency within hours — so you never lose your 15-day window.
• Escalation handling. If MNRE escalation is needed, we file the ticket on your behalf with the correct ARN, screenshots, and DISCOM context. Our average MNRE resolution time is 4 working days against the industry 7–10.
• Vendor empanelment. Heaven Green is empanelled across all major DISCOMs, so the vendor selection greyed-out problem doesn’t apply to our customers.

Pair these with our broader services:

• Residential Solar — full-stack 1–10 kW rooftop systems with the ₹78,000 PM Suryaghar subsidy handled end-to-end.
• Solar EPC Services — turnkey installation backed by performance guarantees and 25-year O&M.
• Solar Calculator — see your subsidy, savings, and payback for your specific DISCOM bill in under a minute.
• Contact our PM Suryaghar desk — talk to a specialist who knows your DISCOM’s error patterns.

If you’re applying yourself but want a sanity check before submission, our team will review your documents and pre-fill checklist over a 20-minute call at no cost. That single call has prevented hundreds of avoidable rejections in 2025.

Frequently Asked Questions

Why is my PM Suryaghar OTP not coming?

Usually it’s SMS gateway congestion — between 6 PM and 10 PM IST the MNRE OTP route throttles delivery and codes arrive 5–8 minutes late. Wait 10 minutes, refresh the page, and request a fresh OTP between 11 AM and 4 PM. If your number is on DND, SMS “START” to 1909 to whitelist transactional SMS and retry after 30 minutes. If the OTP still doesn’t arrive after these fixes, the issue is on the MNRE SMS aggregator side — call 1800-180-3333.

What is the K-Number Not Mapped error and how do I fix it?

KMN-101 means the portal can’t find your consumer record in the DISCOM API. The most common cause is entering the wrong field from your bill — DISCOMs label their primary identifier differently (K-Number for JVVNL, Consumer Number for MSEDCL, CA Number for BSES, Service Number for Torrent). Cross-check the field name against your DISCOM, re-enter, and the error usually clears immediately. If it persists after 48 hours, your DISCOM hasn’t synced your record yet — raise a portal ticket.

How long does an Aadhaar name mismatch take to fix on PM Suryaghar?

Updating your DISCOM bill takes 7–15 days through the customer service centre; updating Aadhaar at a Seva Kendra takes 7–10 days plus 2–3 days for UIDAI demographic API propagation. Pick whichever record has fewer downstream uses to update. Once one matches the other, log back into the portal with your existing application reference number — it stays valid for 30 days — and the ADM-205 flag clears automatically.

Can I install solar above my sanctioned load under PM Suryaghar?

No — your solar capacity cannot exceed your DISCOM-sanctioned load. If you want a 3 kW system and your sanctioned load is 2 kW, file a load enhancement request first. Enhancement takes 15–25 days and costs ₹500–₹2,000 in DISCOM fees. Skipping this step triggers a Sanctioned Load Mismatch error (SLM-220) at the feasibility stage. Heaven Green can file the enhancement and the PM Suryaghar application in parallel to compress the total timeline.

What does “DBT Bank Not Seeded” mean and how do I fix it?

BNS-410 means your bank account exists but NPCI’s mapper doesn’t see it as Aadhaar-linked, so the subsidy DBT can’t reach you. Visit your bank branch with your Aadhaar card and submit a “Bank Account Seeding with Aadhaar” form — most banks have this online too via net-banking. NPCI updates within 48 hours. Confirm the change on the UIDAI bank mapper before resubmitting on the portal.

Why is my vendor selection dropdown empty?

Three reasons: your DISCOM hasn’t pushed its empanelled vendor list to the portal yet, your pin code falls outside vendor service areas, or every empanelled vendor has hit their monthly kW quota. Wait 24 hours and retry. If still empty, raise a portal ticket with VEN-401 as the error code. Heaven Green Energy is empanelled across 22 DISCOMs, so our customers don’t encounter this — but if you’re applying without a vendor pre-selected, it’s worth filing the ticket and waiting through the next monthly quota reset (first of the month).

How long can a PM Suryaghar application stay open before auto-closure?

The portal auto-closes applications 15 days after issuing a document deficiency notice if you don’t respond. The application reference number (ARN) itself stays valid for 30 days from initial submission for resubmission. Beyond 30 days, you must start a fresh application — the old ARN is dead. The fastest way to avoid auto-closure is to log into the portal every 3 days, check for any deficiency flags, and respond the same day they appear.

What documents commonly fail upload to PM Suryaghar?

Aadhaar files where the first 8 digits aren’t masked (use the masked Aadhaar download from UIDAI, not your own photo), bills older than 3 months or unpaid, blurry passbook scans where IFSC isn’t readable, and HEIC roof photos from iPhones (convert to JPG first). File size cap is 2 MB per document; some DISCOMs cap at 1 MB. Use a PDF compressor like ILovePDF or Adobe Acrobat to get under the limit without losing readability.

Can I change my bank account after submitting the PM Suryaghar application?

Yes, but only before commissioning. Until the DISCOM signs off the bidirectional meter, you can update bank details on the portal under “Profile → Bank Details.” After commissioning and the first DBT attempt, changes require a fresh grievance ticket to MNRE with proof of the new account’s Aadhaar seeding. Process takes 7–10 days. The simpler fix is to confirm bank seeding before applying, then leave it alone.

Is there a phone number for PM Suryaghar portal support?

Yes — call 1800-180-3333 (toll-free, 9 AM to 8 PM IST). Email pmsuryaghar@gov.in for written escalations that need a ticket number. Have your ARN, error code, screenshot, and DISCOM name ready before calling. The helpline is staffed by MNRE contractors who handle portal-side issues directly; for DISCOM-side issues they route the ticket but resolution depends on the DISCOM. Average resolution time is 3–5 working days for portal-side and 7–15 for DISCOM-side.