Skip to content
ALMM & DCR hub · troubleshooting

Why DCR certificate numbers get rejected on PM Surya Ghar

A back-office fix list for EPCs — the real reasons a DCR number is sent back on the PM Surya Ghar portal, from duplicate serials to format typos, and the exact fix for each.

By the SuryaHub team Updated 20 June 2026 12 min read
TL;DR for the back office
  • A DCR number is rejected when it does not match the NISE record.
  • The top cause is a serial already used on another application.
  • Format typos — extra spaces or O-for-zero — break the 16-digit check (verify length).
  • An ALMM List-I panel is not DCR; rooftop subsidy needs a true DCR module.
  • Always verify the serial on the NISE DCR portal before you upload.
  • The old vendor-undertaking route is reported discontinued — verify against MNRE notices.

A rejected DCR number stops a subsidy claim cold. The good news is that almost every rejection comes from a short list of fixable causes. Match the error message on the PM Surya Ghar portal to the cause below, apply the fix, and most claims go through on the next try.

What a DCR rejection actually means

A DCR rejection means the DCR number you entered did not match a valid record in the NISE register when the PM Surya Ghar portal checked it. The portal now validates the serial live against NISE, so any gap — a typo, a used serial, a missing record — sends the number back.

DCR is about the cells, not just the panel

DCR stands for Domestic Content Requirement. A DCR module is built with solar cells made in India. PM Surya Ghar rooftop subsidy needs DCR modules, so the portal does not just check that your panel is approved — it checks that this exact serial is a recorded DCR cell-and-module unit on the NISE side.

Why the back office sees most of these errors

The installer fits the panels, but the back office keys the serials and uploads the certificate. That is where a clean serial becomes a rejected one — a wrong PDF, a fat-fingered digit, or a serial already claimed on another job. The rest of this guide is built around that moment.

Why does a "DCR number already used" error appear?

A "DCR number already used" error appears because that serial is already claimed against another PM Surya Ghar application, or it was entered twice on the same job. Each DCR serial can back only one subsidy claim, so the portal blocks any repeat use.

The honest mistakes

Most duplicates are simple. The same panel serial got pasted into two consumer applications, or a batch of serials was copied across jobs without editing. Check whether the serial truly belongs to this rooftop and whether anyone on your team already submitted it.

The fix

Verify the serial on the NISE DCR portal and confirm it maps to this job. If the serial was wrongly reused inside your firm, correct the entry. If it looks cloned by someone else, raise a ticket with NISE and your module maker, and keep the purchase invoice ready as proof of ownership.

Why does the portal reject the 16-digit DCR number format?

The portal rejects the DCR number format when the serial is the wrong length, carries spaces, or contains a letter typed as a number. The DCR number is commonly a 16-character serial, though you should verify the exact format against your own NISE certificate.

The usual format traps

  • Letter-for-number — the letter O typed as zero, or I typed as 1.
  • Hidden spaces — a leading or trailing space copied from a PDF.
  • Wrong length — a digit dropped or doubled while keying by hand.
  • Wrong field — the model code pasted where the serial belongs.

The fix

Copy the serial straight from the NISE DCR certificate rather than retyping it. Paste it into a plain text box first to strip hidden spaces, then enter it. Re-check the character count against the format on your certificate before you submit.

What if the DCR number is not found in the NISE record?

If the DCR number is not found, the serial is most likely not yet in the NISE register, or the module maker has not uploaded it. The PM Surya Ghar portal can only confirm serials that already exist on the NISE DCR side, so a missing record reads as "not found".

Check NISE before you blame the portal

Search the serial on the NISE DCR portal first. If it is missing there too, the problem is upstream, not on PM Surya Ghar. A scan that will not read at all is a different issue — see our serial-not-found RFID and QR fix.

The fix

Ask the module maker to push the serial to the NISE register, since only the maker can do that. Get a confirmation, then retry on the PM Surya Ghar portal. Build a habit of verifying serials at goods-inward, not at claim time, so a missing record never surprises you mid-claim.

Why does the portal say the module is "not DCR"?

The portal says a module is "not DCR" when the panel is on the ALMM List-I but not on the DCR List-II. List-I means the model is an approved module; DCR means the cells inside it were made in India. PM Surya Ghar rooftop subsidy needs the second, stricter status.

List-I and List-II are not the same

Many installers assume any ALMM-approved panel qualifies. It does not. An imported-cell module can sit on List-I and still fail the DCR check, because the subsidy rule is about Indian cells, not just an approved model. Our PM Surya Ghar DCR requirement guide explains this split in full.

The fix

Order true DCR (List-II) modules for any PM Surya Ghar rooftop job and confirm the DCR status on the purchase order, not just the model name. If a List-I panel was already fitted, the subsidy under DCR rules cannot stand — you will need a compliant module to claim.

Can a portal or integration timing lag cause a rejection?

Yes, a timing lag can cause a temporary rejection when a freshly issued DCR serial has not yet synced from NISE to the PM Surya Ghar portal. The two systems talk to each other, and a brand-new record can take time to appear on the subsidy side.

How to tell a lag from a real error

A lag usually shows as "validation pending" or a serial that verifies on NISE but is "not found" on PM Surya Ghar. If the serial is clearly present and correct on the NISE DCR portal, the gap is likely timing, not data. The exact sync window is a point-in-time rule — verify it.

The fix

Wait, then retry rather than re-keying the serial or assuming it is wrong. If it still fails after a reasonable wait, treat it as a data problem and re-verify on NISE. Schedule claims a little after the panels are recorded so the systems have time to sync.

What if the wrong certificate was uploaded?

If the wrong certificate was uploaded, the portal reports a mismatch because the document does not list the serials being claimed. The most common slip is uploading the ALMM certificate instead of the NISE DCR certificate, since both exist for the same module.

ALMM and DCR certificates are different documents

An ALMM certificate proves the model is approved. A DCR certificate proves these specific cells and modules are Indian-made and recorded with NISE. The subsidy claim needs the DCR certificate that carries your exact serials, not the general ALMM listing.

The fix

Open the PDF before uploading and confirm it is the NISE DCR certificate that lists the serials on this job. File certificates per job, not per supplier, so the back office never grabs a generic document by mistake. Our DCR verification guide shows what a valid certificate should contain.

Why does a name or capacity mismatch get flagged?

A name or capacity mismatch gets flagged when the maker name, model, or wattage you enter does not match the NISE record for that serial. The portal cross-checks these fields, so even a small difference in spelling or rating can stop the claim.

The fields that trip people up

  • Maker name — a short name or abbreviation instead of the registered name.
  • Model code — a near-match model number from the same family.
  • Wattage — the project capacity entered instead of the per-module rating.

The fix

Copy the maker name, model and wattage from the NISE DCR record, letter for letter and watt for watt. Do not paraphrase the maker name or round the rating. If the project has mixed modules, enter each serial with its own matching details rather than one blanket entry.

Has the DCR vendor-undertaking route changed?

Yes, the earlier vendor-undertaking route for DCR is reported to be discontinued in favour of live NISE DCR-number validation — but this is a point-in-time rule you should verify against the latest MNRE and portal notices before you rely on it.

What this means in practice

In the past, a vendor could in some cases declare DCR compliance by undertaking. The shift to live serial validation means the portal now checks the actual DCR number against NISE, so a paper declaration no longer substitutes for a recorded serial. Plan your process around real, verifiable serials.

Always confirm the current rule

DCR and ALMM rules move often, and notices can change the validation method or the DCR portal address. Treat the NISE DCR portal URL solardcrportal.nise.res.in as a verify-URL, and confirm the current method on the ALMM & DCR hub and the official sources before each claim cycle.

DCR rejection cheat sheet — symptom, cause, fix

Use this as a quick lookup at the moment of rejection. Match the portal message to the likely cause, then apply the fix.

"DCR number already used" / duplicate
Cause: Serial claimed against another application, or entered twice
Fix: Confirm the serial belongs to this job on NISE; raise a ticket if cloned
"Invalid DCR number" / format error
Cause: Wrong length, extra spaces, or letter-for-number typo (O vs 0)
Fix: Re-key exactly 16 characters, no spaces; copy from the NISE certificate
"DCR number not found"
Cause: Serial not yet in the NISE register, or maker has not uploaded it
Fix: Verify on the NISE DCR portal; ask the maker to push the serial
"Module not DCR / not eligible"
Cause: Panel is ALMM List-I only, made with imported cells
Fix: Use a true DCR (List-II) module; List-I alone fails rooftop subsidy
"Validation pending" / no response
Cause: Portal-to-NISE integration lag right after issue
Fix: Wait, then retry; a fresh serial can take time to sync (verify timing)
"Certificate does not match"
Cause: Wrong PDF uploaded — ALMM cert instead of the DCR cert
Fix: Upload the NISE DCR certificate that lists these exact serials
"Details mismatch" on submit
Cause: Maker name, model or capacity differs from the NISE record
Fix: Match maker, model and wattage to the NISE entry letter for letter

Caption: Common DCR-number rejection errors on the PM Surya Ghar portal and the back-office fix for each. Source: PM Surya Ghar portal behaviour and NISE DCR records (point-in-time — verify the exact messages and the DCR portal URL against current MNRE / NISE notices).

How SuryaHub helps you stop DCR rejections

Most DCR rejections trace back to a serial that was wrong, reused, or paired with the wrong certificate. SuryaHub keeps every DCR serial, NISE certificate and module record tied to the right job and the right consumer, and runs the work through government workflows and procurement and inventory so the back office uploads the correct DCR number the first time. It flags duplicate or mismatched serials before submission. SuryaHub is pre-revenue; real pilots are Suryantra Energy and RGESPL, and figures here are scheme facts, not guarantees.

Catch DCR errors before the portal does

See how SuryaHub ties serials, certificates and claims to one job.

Book a Demo

Frequently asked questions

Why is my DCR certificate rejected on the PM Surya Ghar portal?+

A DCR certificate is rejected on the PM Surya Ghar portal when the DCR number does not match the NISE record. The usual causes are an already-used serial, a 16-digit format typo, a serial not yet in the NISE register, or a module that is ALMM List-I but not DCR.

How do I fix a duplicate DCR number error?+

To fix a duplicate DCR number error, first confirm the serial belongs to this job on the NISE DCR portal. If the serial was already claimed on another application or entered twice, correct your entry. If a serial appears cloned by someone else, raise a ticket with NISE and your maker.

Is a 16-digit DCR number the correct format?+

The DCR number is commonly a 16-character serial, but the exact format should be verified against your NISE certificate. Most format rejections come from extra spaces, a wrong length, or a letter typed as a number, such as the letter O instead of zero. Copy the serial directly from the certificate.

Why does the portal say my module is not DCR?+

The portal says a module is not DCR when the panel is on the ALMM List-I but not List-II. List-I covers approved modules, while DCR means the cells were made in India. PM Surya Ghar rooftop subsidy needs a true DCR module, so an ALMM List-I panel alone is rejected.

What if my DCR number is not found on the portal?+

If your DCR number is not found, the serial is likely not yet in the NISE register or the maker has not uploaded it. Verify the serial on the NISE DCR portal first. If it is missing there, ask the module maker to push the serial, then retry on the PM Surya Ghar portal.

Does the vendor undertaking still work for DCR claims?+

The earlier vendor-undertaking route for DCR is reported to be discontinued in favour of live NISE DCR-number validation, but this is a point-in-time rule you should verify against the latest MNRE and portal notices. Always confirm the current DCR validation method before you submit a claim.

How does SuryaHub help with DCR rejections?+

SuryaHub keeps every DCR serial, NISE certificate and module record tied to the right job, so the back office uploads the correct number the first time. It flags duplicate or mismatched serials before submission. SuryaHub is pre-revenue; real pilots are Suryantra Energy and RGESPL.

Sources & references

Error behaviour, DCR rules and the NISE register come from primary government sources. Validation methods and the DCR portal address can change, so confirm the current rule and the DCR portal URL before each claim cycle.

Written by the SuryaHub team · reviewed against MNRE, NISE & PM Surya Ghar sources · updated 20 June 2026.

Method: Rejection causes and fixes are taken from the government sources above and field reports, and re-checked every 30 days. DCR validation rules, the discontinued vendor-undertaking change and the NISE DCR portal URL are point-in-time — verify before relying on them. SuryaHub is pre-revenue; only Suryantra Energy and RGESPL are real pilots.

Change log: 20 Jun 2026 — first published.

The decision · now onboarding pilot EPCs

Run your whole solar business
on one platform.

Stop stitching together Tally, Excel, Sheets and WhatsApp. See the operating system built for India's solar EPCs — on your real projects.

India-first · PM Surya Ghar ready · Cloud or on-prem

Run your solar business on one OS.
Book a Demo