- A net-metering rejection over ALMM/DCR is almost always a module-proof gap, not a grid issue.
- The top trigger is a serial or RFID not found in the live ALMM list — re-scan and fix the typo first.
- Next is a model not on List-I by exact model number — swap to an enlisted model.
- For DCR-mandated jobs, attach a valid NISE DCR certificate with matching serials.
- Escalate only when your module is genuinely compliant and documented. Cite your state regulation.
- DISCOM enforcement varies — verify your state net-metering regulation, not a generic rule.
A net-metering rejection over ALMM or DCR is one of the most stressful blocks an EPC faces. The install is done, the customer is waiting, and the DISCOM will not energise the connection. The good news: almost every ALMM/DCR rejection comes from a fixable proof gap, not a problem with the panels on the roof.
Why ALMM/DCR blocks net metering at all
A DISCOM blocks net metering when it cannot verify that your module meets the rules its state regulation requires. Before the DISCOM sanctions a net-metering connection on a government-linked or subsidy-linked job, it checks that the module is on the ALMM list and, where the scheme demands it, that the job is DCR-compliant. If that check fails, the file stalls.
ALMM (the Approved List of Models and Manufacturers) is set by MNRE. A module model must be enlisted by its exact model number, not just its brand, to count. DCR (Domestic Content Requirement) means the module and its cells are made in India and proven by a certificate from the NISE DCR portal. These are point-in-time rules — confirm the current ALMM order and your state net-metering regulation before you act.
The module is fine — the proof is the problem
In most rejections, the panels themselves are compliant. What fails is the evidence: a mistyped serial, a missing certificate, a model that the brand sells but never enlisted, or a datasheet that does not match the application. Fix the evidence and the file moves.
Read the exact rejection reason first
Always start by reading the DISCOM's written rejection reason word for word, because the fix depends entirely on which trigger it is. EPCs lose days swapping modules when the real problem was a one-character typo in a serial. Open the portal, copy the exact text, and match it to one of the common triggers below.
Source: common DISCOM net-metering rejection patterns, mapped to MNRE ALMM rules. DISCOM enforcement is not uniformly documented — verify your state regulation.
Serial or RFID not found in ALMM
The most common ALMM net-metering rejection is "serial not found", and it is usually a data error, not a panel problem. Each module carries an RFID or QR code with a serial that should trace back to the live ALMM record. When the DISCOM scans or looks up your uploaded serial and gets no match, it rejects the file.
Work through these checks in order
- Re-scan the code. A blurry photo or a manual typo is the top cause. Re-scan the RFID/QR on the actual installed module.
- Compare character by character. Zeros and the letter O, ones and the letter I, are easy to swap. Match the serial exactly.
- Confirm the model is enlisted. A serial cannot resolve if the model was never on List-I. Check the model number, not the brand.
- Check you installed what you filed. If a different batch went up than the one on the application, the serials will not match.
Our deeper guide on fixing an RFID or QR mismatch walks through each of these in detail.
The model is not on ALMM List-I
If the rejection says the model is not approved, the exact model number is not on the live ALMM List-I — even if the brand sells other enlisted models. ALMM enlists specific model numbers, not whole brands. A manufacturer can have ten models enlisted and three that are not.
How to confirm and fix it
Download the current List-I from the MNRE portal and search for your exact model number. If it is genuinely missing, the module cannot be used on this job and you must swap to an enlisted model, then update the serials, datasheet and photos before you re-file. Treat any List-I status as point-in-time and verify against the live MNRE list, because models are added and removed over time.
DCR certificate missing, invalid or mismatched
On a DCR-mandated job, the DISCOM rejects the file when there is no valid DCR certificate or the certificate serials do not match the installed modules. DCR is required where the scheme demands domestic content — most notably PM Surya Ghar residential subsidy. Being on ALMM List-I is not the same as being DCR; a module can be List-I but not DCR.
Fixing a DCR rejection
- Confirm the job actually needs DCR. Many C&I and open-access net-metering jobs do not. Check the scheme rule before you panic.
- Generate or re-pull the certificate from the NISE DCR portal for the exact modules installed.
- Match every serial. The DCR certificate serials must line up with the modules on the roof and on the application.
- Check the certificate is current and not rejected on the portal itself before you re-upload.
If your DCR certificate keeps bouncing, see why DCR certificates get rejected and the fixes.
List-II cell-origin questions
A newer trigger is the DISCOM asking for proof of cell origin under ALMM List-II. List-II enlists approved solar cells, and the 2026 mandate is intended to require that the cells inside the module come from an enlisted Indian maker. The exact effective date around 1 June 2026 faced deferment requests and court proceedings, so confirm whether it was deferred in the latest MNRE order — status as of 20 June 2026.
What to provide
If your DISCOM raises a List-II query, ask your module supplier for the cell-maker declaration and a chain-of-custody document linking the module serials to enlisted cells. Our guide on proving List-II cell compliance covers the paper trail. Treat List-II dates and enlisted-maker lists as point-in-time and verify on the MNRE portal.
How to re-file cleanly so it clears
A clean re-file fixes the root cause once and submits one consistent set of documents, so the DISCOM has nothing to bounce. Mismatched figures across the photo, nameplate, datasheet and application are the top cause of a second rejection. Follow these steps in order.
Pull the exact rejection text
Open the DISCOM portal and copy the written reason word for word. Do not guess — the fix depends on which of the six triggers it is.
Verify against the live source
Check the model on the live ALMM List-I and, for DCR jobs, the NISE portal. Confirm whether the problem is the module or the paperwork.
Fix the root cause
Correct the serial, swap to an enlisted model, regenerate the DCR certificate, or attach the missing BIS/cell proof — whatever the reason demands.
Re-upload a clean file
Submit corrected serials, certificates and photos in one consistent set. Mismatched figures across documents cause a second rejection.
Escalate only if the data is right
If your module is genuinely enlisted and documented but still rejected, raise a written grievance citing the state net-metering regulation.
When to escalate to a grievance
Escalate only when your module is genuinely enlisted and fully documented but the DISCOM still rejects it. Escalating a real compliance gap just wastes time and annoys the officer who will eventually approve you. If your data is right, raise a written grievance.
What a strong grievance includes
- The screenshot of the module on the live ALMM List-I, showing the exact model number.
- The serials, matched between the application, the certificate and the installed modules.
- The DCR certificate or BIS registration, where the job requires it.
- A citation of the relevant clause in your state net-metering regulation.
State enforcement practices differ, so the escalation route, timeline and authority vary by DISCOM and SERC. Use the net metering hub for your state's process and confirm the rule that applies to your connection.
Prevent the next rejection
The cheapest rejection is the one you never file. Most ALMM/DCR net-metering rejections trace back to a sourcing or data decision made weeks earlier, at the BOM stage. Catch the module problem before procurement, not at the DISCOM counter.
- Check the model on List-I before you buy, by exact model number — see BOM compliance.
- Confirm whether the job needs DCR using which projects need ALMM/DCR.
- Capture serials at goods-in, not at commissioning, so the data is clean and complete.
- Store the DCR certificate and BIS proof on the job the day the modules arrive.
How SuryaHub helps you clear DISCOM approval
SuryaHub closes the gap that causes these rejections by checking each module against compliance rules at the procurement and BOM stage, then carrying the serials, DCR certificate and BIS proof through to the DISCOM and net-metering file. By the time you submit, the proof the DISCOM needs is already attached and consistent. SuryaHub is pre-revenue; real pilots are Suryantra Energy and RGESPL, and the rules here are scheme facts to verify, not guarantees.
Stop net-metering rejections at the source
See how SuryaHub keeps every module compliant from BOM to DISCOM approval.
Related guides
Frequently asked questions
Why was my net-metering application rejected for ALMM or DCR?+
Net-metering applications get rejected when the module serial is not found in the live ALMM list, the exact model is not on List-I, or a DCR-mandated job has no valid NISE certificate. The DISCOM verifies the module before it sanctions net metering, so any gap in that proof blocks approval.
The DISCOM says my module serial is not in ALMM — what do I do?+
First re-scan the QR or RFID and fix any typo in the serial you uploaded. Then confirm the exact model is enlisted on the live ALMM List-I. If the serial is correct and the model is enlisted, raise a written grievance with the proof; if the model is not enlisted, swap it.
Does every net-metering job need a DCR certificate?+
No. DCR proof is required only where the scheme mandates domestic content, such as PM Surya Ghar residential subsidy. Many C&I and open-access net-metering jobs need ALMM List-I but not DCR. Check your state net-metering regulation and the scheme rule before filing.
Can I change the module after a net-metering rejection?+
Yes. If the rejection is because the model is not on ALMM List-I or is not DCR where required, you can swap to a compliant module, update the serials and datasheet, and re-file. Keep the new module consistent across the photo, nameplate and application to avoid a second rejection.
When should I escalate an ALMM net-metering rejection?+
Escalate only when your module is genuinely enlisted and fully documented but the DISCOM still rejects it. Raise a written grievance that cites your state net-metering regulation and attaches the ALMM record, serials and certificate. Escalating a real compliance gap only wastes time.
How does SuryaHub help unblock net-metering rejections?+
SuryaHub checks each module against compliance rules at the BOM stage and stores the serials, DCR certificate and BIS proof on the job, so the net-metering file is complete before you submit. SuryaHub is pre-revenue; real pilots are Suryantra Energy and RGESPL.
Sources & references
The module-compliance rules a DISCOM applies come from MNRE and NISE, but the exact net-metering check is set by your state regulation. DISCOM enforcement is not uniformly documented, so verify any state-specific claim before you act.
- Ministry of New & Renewable Energy (MNRE) ↗
ALMM orders and List-I/List-II rules that DISCOMs apply at approval.
- NISE DCR portal ↗
Generate and verify the DCR certificate a DISCOM may demand.
- Your state DISCOM / SERC ↗
State net-metering regulations set the exact module checks — verify your state.
Written by the SuryaHub team · reviewed against MNRE, NISE & state DISCOM/SERC sources · updated 20 June 2026.
Method: Rejection patterns are mapped to MNRE ALMM and NISE DCR rules and re-checked every 30 days. DISCOM enforcement varies by state — cite your SERC net-metering regulation. SuryaHub is pre-revenue; only Suryantra Energy and RGESPL are real pilots.
Change log: 20 Jun 2026 — first published.