- Name mismatch across Aadhaar, bill and bank is the #1 DBT failure — pre-check it.
- Use only ALMM List-I + DCR equipment (List-II cells mandatory from 1 June 2026).
- A non-empanelled vendor or self-install auto-disqualifies the claim.
- Missing commissioning / net-metering certificates or photos hold the payout.
- Run a pre-submission QC checklist on every job — almost all rejections are avoidable.
A rejected PM Surya Ghar subsidy is not just lost paperwork — it is an angry customer who blames you for money the government never sent. The good news: almost every rejection comes from a short list of avoidable causes, and each one is catchable before you submit. Here are the nine, the fix for each, and a QC checklist to run on every job.
Why PM Surya Ghar subsidy claims get rejected
The subsidy is paid to the customer by DBT after commissioning, and the government validates the claim against equipment, vendor and identity data before releasing it. A failure in any one check stops the payout — and because the money goes to the customer, a rejection lands on your reputation even when the cause is the customer's own bank details.
The fix is discipline at the front of the job, not firefighting at the end. Catch the identity and equipment issues at the lead and procurement stage, and the claim clears. The nine reasons below are ordered roughly by how often they bite.
The 9 rejection reasons — and how to fix each
Name mismatch across Aadhaar, electricity bill and bank
The #1 DBT failure. NPCI matching is strict — if the name on the Aadhaar, the electricity bill and the bank account do not match, the transfer fails even after commissioning.
Fix: Pre-check all three names at the lead stage. Get the customer to align them (bank KYC update or bill name correction) before installation, not after the claim stalls.
Non-Aadhaar-seeded bank account
DBT only works to a bank account that is Aadhaar-seeded and active in the NPCI mapper. An unseeded or dormant account silently blocks the payout.
Fix: Verify Aadhaar seeding before the install. Ask the customer to confirm seeding at their bank, or have them check the NPCI status, so the account is ready when the subsidy is released.
Non-empanelled vendor or self-installation
Only an empanelled vendor for that DISCOM can carry the subsidised job. A self-install or a non-empanelled vendor auto-disqualifies the claim at the technical-sanction gate.
Fix: Confirm your empanelment is active for the customer’s DISCOM before scheduling, and never let a customer self-install part of the system. Empanelment is per-DISCOM and not portable.
Non-ALMM equipment caught at inspection
Modules must be on the ALMM List-I and DCR-compliant. Non-ALMM or non-DCR equipment is caught at the DISCOM inspection and rejects the subsidy outright.
Fix: Source only ALMM List-I modules with DCR cells, and from 1 June 2026 cells from ALMM List-II manufacturers. Verify the model is currently listed before you buy — listings change.
Sanctioned-load mismatch
If the system capacity exceeds the customer’s sanctioned load without a load enhancement, the file is rejected or held — the connection cannot legally support it.
Fix: Check the sanctioned load against the proposed system at quoting. Raise a load enhancement with the DISCOM before sanction if the system is bigger than the sanctioned load.
Outstanding electricity arrears
A consumer account with unpaid electricity arrears can be blocked from net metering and the subsidy until the dues are cleared.
Fix: Confirm the customer’s electricity account is clear of arrears before applying. A quick check of the latest bill at the lead stage avoids a late surprise.
Missing commissioning certificate
The commissioning certificate is the document that triggers the subsidy. Without it issued by the DISCOM after net-meter installation, no DBT is released.
Fix: Drive the job to commissioning — net meter, inspection, then certificate. Track the certificate as the real finish line, and do not consider a job done until it is issued.
Missing net-metering certificate or required photos
A missing net-metering certificate, or site photos that are absent or shot from the wrong angles, holds the file at inspection and blocks the claim.
Fix: Capture photos from the specified angles on install day (panels, inverter, meter board, wide shot) and ensure the net-metering certificate is on file before claiming.
Invoices without ALMM certificate numbers
Invoices and documents that do not carry the ALMM model and certificate numbers fail verification, even when the right equipment was actually installed.
Fix: Ensure every invoice lists the ALMM model and certificate numbers and the serials match what was installed. Reconcile invoice, serials and photos before submission.
Notice the pattern: the costliest rejections — name mismatch, Aadhaar seeding, non-ALMM equipment — are decided before the claim is ever submitted. They are procurement and onboarding decisions, not paperwork at the end. See ALMM and DCR modules for the equipment side and subsidy claim tracking for what happens after a clean submission.
The two front-loaded checks that prevent most rejections
If you only fix two things, fix the identity checks. The name match across Aadhaar, electricity bill and bank, and the Aadhaar seeding of the bank account, together account for the bulk of failed DBTs — and both are invisible until the very end of the job, when the money should land but does not. Because NPCI matching is unforgiving about even small differences (an initial, a maiden name, a spelling on the bill), the only safe approach is to verify them before any equipment is ordered.
The reason this matters so much commercially is sequence: by the time a DBT fails, you have already installed the system, the customer expects their subsidy, and the correction (a bank KYC update or a bill name change) can itself take weeks. A two-minute check at the lead stage replaces a multi-week scramble after commissioning. Treat the customer's documents as part of your QC, not the customer's problem.
The pre-submission QC checklist
Run this checklist on every job before you submit the claim. It maps directly to the nine reasons above — if every box is ticked, the common rejections are closed off.
- ✓Name on Aadhaar, electricity bill and bank all match (NPCI-strict).
- ✓Customer's bank account is Aadhaar-seeded and active in the NPCI mapper.
- ✓Your firm is empanelled for this DISCOM; no self-installed parts.
- ✓Modules are ALMM List-I + DCR cells (List-II cells from 1 Jun 2026), verified as currently listed.
- ✓System capacity is within the sanctioned load (or load enhancement done).
- ✓Customer's electricity account has no outstanding arrears.
- ✓Commissioning certificate issued after net-meter installation.
- ✓Net-metering certificate on file and photos shot from the required angles.
- ✓Invoices carry the ALMM model and certificate numbers, matching the installed serials.
The first two boxes are the ones EPCs skip and regret. Verifying the name match and Aadhaar seeding at the lead stage — before a panel is ordered — is the single highest-value habit for a clean subsidy.
What to do if a claim is already rejected
If a claim has already been rejected or the DBT has failed, do not treat it as final — most causes are correctable, and the customer is counting on you to fix it. Start by identifying which of the nine reasons applies, because the remedy is specific to the cause.
Work the cause, then resubmit
For a name mismatch or unseeded account, the customer corrects their bank or bill details and the DBT is reattempted once the records align — this is the most common and most fixable case. For an equipment or documentation gap (missing ALMM numbers on an invoice, an absent certificate, wrong-angle photos), assemble the correct evidence and resubmit through the portal. A non-empanelled vendor or self-install is the hardest to recover, because it goes to eligibility rather than paperwork — which is exactly why empanelment must be confirmed before the job starts.
Throughout, keep the customer informed in plain language: tell them what failed, what you are doing, and a realistic new timeline. A rejection handled openly protects the relationship; a rejection the customer discovers on their own does not. Track the correction the same way you track the original subsidy claim so it does not stall a second time.
How SuryaHub stops rejections before they happen
SuryaHub builds this QC checklist into every job. It prompts for the name-match and Aadhaar-seeding check at onboarding, raises ALMM/DCR-aware procurement so non-compliant equipment never gets ordered, and holds the certificates, serials and angle-specific photos the claim needs — through the project management module — so the file is complete and clean before submission. SuryaHub is pre-revenue; real pilots are Suryantra Energy and RGESPL, and the scheme figures here are facts from government sources, not guarantees.
Catch every rejection before you submit
See how SuryaHub runs QC on every PM Surya Ghar job.
Related guides
Frequently asked questions
Why do PM Surya Ghar subsidy claims get rejected?+
PM Surya Ghar subsidy claims get rejected mostly for avoidable reasons: a name mismatch across Aadhaar, electricity bill and bank, a non-Aadhaar-seeded account, a non-empanelled vendor or self-install, non-ALMM equipment, a sanctioned-load mismatch, electricity arrears, or missing certificates and photos. Almost all are catchable before submission with a QC check.
What is the most common PM Surya Ghar subsidy rejection reason?+
A name mismatch across the Aadhaar, the electricity bill and the bank account is the most common PM Surya Ghar DBT failure. NPCI matching is strict, so the subsidy transfer fails if the names differ, even after commissioning. The fix is to pre-check all three names at the lead stage and align them before installation.
Does non-ALMM equipment cause PM Surya Ghar subsidy rejection?+
Yes. PM Surya Ghar requires ALMM List-I modules with DCR cells, and from 1 June 2026 cells from ALMM List-II manufacturers. Non-ALMM or non-DCR equipment is caught at the DISCOM inspection and rejects the subsidy. Verify a model is currently listed before buying, because the ALMM lists change.
Can a self-installed system get the PM Surya Ghar subsidy?+
No. A self-installation or a job done by a non-empanelled vendor auto-disqualifies the PM Surya Ghar subsidy at the technical-sanction gate. Only a vendor empanelled with the customer’s DISCOM can carry the subsidised work, and empanelment is per-DISCOM and not portable across states.
How can an EPC prevent PM Surya Ghar subsidy rejection?+
An EPC prevents PM Surya Ghar subsidy rejection by running a pre-submission QC checklist on every job: verify name match and Aadhaar seeding, confirm empanelment, use ALMM and DCR equipment, check sanctioned load and arrears, and ensure the commissioning and net-metering certificates, photos and invoice ALMM numbers are all in order.
How does SuryaHub help avoid PM Surya Ghar subsidy rejections?+
SuryaHub runs a pre-submission QC checklist on every job and holds the documents, serials, photos and certificates the claim needs, so the common rejection reasons are caught before submission. SuryaHub is pre-revenue; real pilots are Suryantra Energy and RGESPL, and scheme figures here are facts, not guarantees.
Sources & references
The rejection causes, ALMM/DCR requirement, empanelment rule and the DBT-to-customer structure come from primary government sources. Always confirm the current rules and required documents with your DISCOM and the National Portal before submitting a claim.
- National Portal for PM Surya Ghar ↗
The subsidy claim, DBT validation and the documents that gate a successful payout.
- Ministry of New & Renewable Energy (MNRE) ↗
Scheme guidelines, ALMM/DCR requirement and empanelment rules.
- Press Information Bureau (PIB) ↗
Official scheme announcements and the DBT subsidy structure.
Written by the SuryaHub team · reviewed against MNRE & National Portal sources · updated 19 June 2026.
Method: Rejection causes and rules are taken from the government sources above and re-checked every 30 days. The #1 DBT failure (name mismatch) reflects NPCI-strict matching. SuryaHub is pre-revenue; only Suryantra Energy and RGESPL are real pilots.
Change log: 19 Jun 2026 — first published.