- Most rejections trace to one thing: the exact model number is not on ALMM List-I.
- A brand on the list does not mean that model variant is — match the full string.
- DCR-mandated jobs (like PM Surya Ghar residential) fail without a valid DCR certificate.
- Catch a serial/RFID-QR not in ALMM or a missing BIS before bulk dispatch.
- Re-check the live list before commissioning — a model can be delisted mid-project.
- Fix the catch point: verify before PO and commissioning, never at the claim stage.
A rejected project is not usually a quality problem. It is a paperwork-and-list problem that was easy to catch weeks earlier. The same handful of ALMM and DCR mistakes send EPC claims back at subsidy, net-metering and inspection — and each one has a simple early check.
Why do ALMM and DCR projects get rejected?
Projects get rejected when the installed module fails a compliance check the scheme runs at subsidy, net-metering or inspection. The checker matches your model against the ALMM list, scans the serial, looks for BIS, and — on DCR jobs — wants a valid DCR certificate. Miss any one and the file bounces.
The painful part is timing. These checks run at the end — after install, when the panel is on the roof and the money is spent. So the goal of this guide is to move every check to the front, before you raise a purchase order and before you commission. The mistakes below are listed with the same structure each time: why it fails, how to catch it early, and the fix.
Mistake 1: Using a module not on ALMM List-I by exact model number
This is the single most common rejection: the exact model you installed is not on the live ALMM List-I. ALMM List-I is the Approved List of Models and Manufacturers that MNRE keeps, and most government-linked jobs — subsidy and net-metering — require an enlisted model.
Why it fails
The checker does not approve "a 540 W mono panel." It approves a specific maker and a specific model number. If the model you bought is not on the list, there is nothing to match, and the claim is rejected even if the panel is perfectly good.
How to catch it before PO
Look up the precise model number on the live ALMM list before you raise the purchase order. Do not trust a quote line or a brochure. Use our guide on keeping the BOM compliant so the model on the PO is the one that is actually enlisted. The fix is simple: order only an enlisted model number, and reject "almost the same" near-matches.
Mistake 2: Brand is on the list, but the model is not
A trusted brand on ALMM does not mean every one of its models is enlisted. Makers enlist specific variants, and the one your supplier has in stock may not be among them. This trips up even careful buyers because the brand name passes a quick glance.
Why it fails
The inspector finds the manufacturer on the list, then looks for the exact model string — and it is not there. A different wattage, a newer variant, or an OEM-rebadged version can all sit outside the enlisted set. The claim fails on the model line, not the brand.
How to catch it early
Match the full model string, character for character, not just the brand. When in doubt, ask the maker for the exact ALMM entry that covers the variant they are shipping. The fix is to choose a model variant that is genuinely enlisted, and to put that exact string on the PO.
Mistake 3: A non-DCR module on a DCR-mandated job
Installing a non-DCR module on a job that requires DCR is a clean rejection. DCR stands for Domestic Content Requirement, and it is mandatory where the scheme requires it — most notably PM Surya Ghar residential subsidy.
Why it fails
On a DCR-mandated job you must attach a valid DCR certificate for the module. A non-DCR module has none, so there is nothing to submit and the subsidy is denied. The work can be flawless and the claim still dies on the content rule.
How to catch it at quoting
Confirm the DCR rule for the scheme at the quoting stage, before procurement, not after. If the project is PM Surya Ghar residential, treat DCR as mandatory unless the current order says otherwise. Our companion guide on the DCR vs non-DCR decision walks the choice for PM Surya Ghar. The fix: source DCR cells and modules for DCR-mandated jobs from the start, and verify against the current MNRE order.
Mistake 4: Missing or invalid DCR certificate
Even on a DCR job with the right module, the claim fails if the DCR certificate is missing, expired, or does not match the installed panel. The certificate is the proof, and the proof has to be valid and tied to the exact module.
Why it fails
A DCR certificate that names a different model, a different batch, or carries a bad reference is treated as no certificate at all. The subsidy is held until a valid, matching certificate is produced — which can stall a job for weeks.
How to catch it before commissioning
Verify the DCR certificate on the NISE process before you commission, and confirm it matches the serial you installed. Our DCR certificate verification guide shows the checks, and why DCR certificates get rejected covers the PM Surya Ghar fixes. The fix is to get a valid, matching certificate from the maker before money moves.
Mistake 5: Serial or RFID-QR not found in ALMM
A module can carry an enlisted model number and still fail when its serial or RFID-QR is not found in the ALMM database. The field scan is a second, independent check, and it catches relabelled, duplicated or unregistered panels.
Why it fails
At inspection the team scans the QR or RFID and looks the serial up against ALMM. If it is not there — wrong batch, maker upload pending, or a fake — the module is flagged and the claim stalls. The number on the box is not enough; the database has to agree.
How to catch it before bulk dispatch
Scan a sample serial against ALMM before the supplier ships in bulk. If a sample fails, do not accept the lot. Our serial-not-found RFID/QR fix walks the escalation. The fix is to replace the affected stock or push the maker to correct the ALMM record before you install.
Mistake 6: BIS registration is not present
A module without BIS registration can fail inspection even if it looks compliant. BIS registration shows the model meets the required Indian standard, and the registration number is part of what an inspector expects to see.
Why it fails
No BIS number on the nameplate, or a number that does not check out, reads as a non-standard module. That is enough to fail an inspection and hold the approval, regardless of the ALMM status.
How to catch it early
Check the BIS registration number on the nameplate and datasheet when you evaluate the model, not on commissioning day. Pair it with the ALMM model check so both pass together. The fix is to use only BIS-registered modules from enlisted makers, and to record the number with the project.
Mistake 7: The module was delisted from ALMM mid-project
A model that was on the list when you bought it can be delisted before you commission, putting the approval at risk. ALMM is a living list, and entries are added and removed over time.
Why it fails
If the model is off the list at the moment the checker looks, the match fails — even though it was enlisted at PO. Whether stock bought while listed is still acceptable depends on the cut-off rules in the current MNRE order, which you must confirm.
How to catch it before commissioning
Re-check the live list before each commissioning batch, not just once at PO. Our module delisted mid-project guide covers the options. The fix is to use stock bought while listed where the order allows it, or swap to a currently enlisted model to protect the claim.
Mistake 8: Mapping the wrong requirement to the project type
Applying the wrong rule to a project gets a good module rejected on the wrong job. ALMM and DCR do not apply the same way to every project type, and a mismatch means you met the wrong requirement.
Why it fails
Treat a DCR-mandated residential job as non-DCR, or assume ALMM does not apply when it does, and the file bounces on a requirement you never planned for. The module might be fine; the rule applied to it was wrong.
How to catch it at intake
Map each project to its ALMM and DCR rule at intake, before you quote. Our which projects ALMM applies to guide is the reference. For net-metering specifics, the net-metering hub covers the DISCOM side. The fix is to apply the correct rule per scheme and project type from day one.
Mistake 9: Paperwork that does not match the installed module
The last common failure is a paperwork mismatch: the serial, the invoice and the certificate do not all describe the same module. The file is technically complete but internally inconsistent, so it gets bounced.
Why it fails
A serial on the panel that does not match the invoice, or a DCR certificate for a different batch, signals a discrepancy. The checker cannot confirm what was actually installed, so the claim is sent back for correction.
How to catch it before submission
Cross-check the serial, the invoice and the certificate against each other before you submit. They must all point to the exact module on the roof. The fix is to align every document to the installed serial, and to record them together rather than chasing them at claim time.
The mistake → why it fails → how to catch it → the fix
Here is the whole list in one view. Use it as a pre-PO and pre-commissioning checklist. Verify each row against the current MNRE order, the live ALMM list, NISE and BIS for your project.
Source: SuryaHub field synthesis of MNRE ALMM orders, the PM Surya Ghar DCR requirement, NISE certification and BIS registration. Point-in-time as of 20 June 2026 — verify each rule against the current MNRE order, the live ALMM list, NISE and BIS before you rely on it.
How SuryaHub helps you avoid these rejections
Every mistake above is a check that should happen before the panel goes up. SuryaHub aims to tie the ALMM model, the DCR certificate, the BIS number and the serials to each project, so a gap shows up at PO and pre-commissioning rather than at the claim. That work lives in procurement & inventory, where the BOM, the compliance evidence and the stock for a job sit together. SuryaHub is pre-revenue and the automated compliance checks are on the roadmap; the only real pilots are Suryantra Energy and RGESPL, so treat this as where we are heading, not a guarantee.
Catch compliance gaps before the PO
See how SuryaHub ties model, DCR, BIS and serials to each job.
Related guides
Frequently asked questions
What is the most common ALMM DCR compliance mistake?+
The most common ALMM DCR compliance mistake is using a module whose exact model number is not on the live ALMM List-I. The brand may be enlisted while that specific model variant is not, so the subsidy or net-metering claim gets rejected. Always match the full model string on the current MNRE list before raising a purchase order.
Why does a solar subsidy get rejected for ALMM reasons?+
A solar subsidy gets rejected when the installed module is not enlisted on ALMM List-I by its exact model number, when the serial or RFID-QR is not found in the ALMM database, or when BIS registration is missing. For DCR-mandated jobs like PM Surya Ghar residential, a missing or invalid DCR certificate also triggers rejection.
Can a non-ALMM module fail net metering?+
Yes. Net metering can be rejected when a non-ALMM module is used on a job where the DISCOM requires an enlisted module. The DISCOM checks the model against ALMM and the serial against the database during approval. Confirm the net-metering rule with your DISCOM, because requirements vary and change over time.
When is DCR mandatory and what happens if I skip it?+
DCR is mandatory where the scheme requires it, notably PM Surya Ghar residential subsidy. If you install a non-DCR module on a DCR-mandated job, the subsidy claim is denied because there is no valid DCR certificate to attach. Confirm the DCR rule for each scheme against the current MNRE order before you procure.
What do I do if a module is delisted from ALMM mid-project?+
If a module is delisted mid-project, re-check the live ALMM list before your next commissioning batch and confirm the cut-off rules in the current MNRE order. You may be able to use stock that was purchased while the model was listed, or you may need to swap to a currently enlisted model to protect the approval.
How does SuryaHub help avoid ALMM DCR rejection?+
SuryaHub aims to keep the ALMM model, DCR certificate, BIS number and serials tied to each project so a compliance gap is caught before PO and commissioning, not at the claim stage. SuryaHub is pre-revenue and AI checks are on the roadmap; the only real pilots are Suryantra Energy and RGESPL.
Sources & references
The compliance rules here come from primary government sources. ALMM, DCR and BIS requirements change, so confirm the current order and the live lists before you rely on any point on this page.
- Ministry of New & Renewable Energy (MNRE) ↗
ALMM orders, List-I and List-II rules and DCR policy. Confirm the current order.
- National Portal for PM Surya Ghar ↗
Residential subsidy and the DCR requirement for rooftop jobs.
- National Institute of Solar Energy (NISE) ↗
DCR certification and the verification process for modules.
Written by the SuryaHub team · reviewed against MNRE, National Portal, NISE & BIS sources · updated 20 June 2026.
Method: Rejection patterns are synthesised from MNRE ALMM orders, the PM Surya Ghar DCR requirement, NISE certification and BIS registration, and re-checked regularly. The List-II cell mandate (around 1 June 2026) has been litigated — confirm whether it was deferred in the latest MNRE order; status as of 20 Jun 2026 is unsettled. SuryaHub is pre-revenue with AI checks on the roadmap; only Suryantra Energy and RGESPL are real pilots.
Change log: 20 Jun 2026 — first published.