← Full guide: PM Surya Ghar Subsidy: Eligibility, Application, and Payment Checklist

Treat the subsidy as a workflow with evidence at every handoff

PM Surya Ghar applications involve the national portal, the consumer’s electricity connection/DISCOM process, a registered vendor, installation…

Start here

PM Surya Ghar applications involve the national portal, the consumer’s electricity connection/DISCOM process, a registered vendor, installation and verification steps before subsidy payment. Do not hand full control to an installer and assume the government portal will correct every mistake later.

What applies to this exact problem

PM Surya Ghar applications involve the national portal, the consumer’s electricity connection/DISCOM process, a registered vendor, installation and verification steps before subsidy payment. Do not hand full control to an installer and assume the government portal will correct every mistake later.

Keep one case file from registration to subsidy credit

StageEvidence to keep
Portal registrationConsumer details and application/reference number
DISCOM/technical stepApproval/status messages required in your state
Vendor selectionRegistered-vendor details, quotation and scope
InstallationInvoice, module/inverter serials, photos and commissioning records
Meter/inspectionNet-metering/inspection status where applicable
Subsidy claimPortal status and verified bank details

Use the live official portal for subsidy amounts and eligibility

Scheme values and implementation details can change. Check the live PM Surya Ghar portal and MNRE before committing to a system size based on an old subsidy graphic. State/DISCOM procedures can also differ.

Choose system size from consumption and roof reality

Subsidy is not a reason to oversize. Review 12 months of electricity consumption, sanctioned load, usable unshaded roof area, orientation, structural condition and expected future demand. Ask the vendor for generation assumptions and compare them with your actual daytime/load pattern.

Separate the vendor price from the subsidy

Write the gross installed price, what you pay to the vendor, any loan amount, and the expected subsidy as separate lines. Do not pay an inflated price merely because a subsidy is expected later. Finance affordability should survive a delay in subsidy credit.

When status stalls

Identify the exact pending actor: portal data, vendor upload, DISCOM inspection/metering, bank validation or another step. Escalate that step with the reference number and evidence. A generic “subsidy not received” complaint is slower to solve.

Decision rule: proceed only when you can audit the system economics without the subsidy, then treat the confirmed scheme benefit as a reduction after the official workflow is satisfied.

Check these first

  • Stage: Evidence to keep.
  • Portal registration: Consumer details and application/reference number.
  • DISCOM/technical step: Approval/status messages required in your state.

Fix it in this order

  1. Stage: Evidence to keep.
  2. Portal registration: Consumer details and application/reference number.
  3. DISCOM/technical step: Approval/status messages required in your state.
  4. Vendor selection: Registered-vendor details, quotation and scope.
  5. Installation: Invoice, module/inverter serials, photos and commissioning records.
  6. Meter/inspection: Net-metering/inspection status where applicable.
  7. Subsidy claim: Portal status and verified bank details.

Evidence to keep

  • Signed quote and scope — keep it with the evidence for “Treat the subsidy as a workflow with evidence at every handoff”.
  • Module/inverter serials and warranty — keep it with the evidence for “Treat the subsidy as a workflow with evidence at every handoff”.
  • DISCOM/portal application IDs — keep it with the evidence for “Treat the subsidy as a workflow with evidence at every handoff”.
  • Generation data, photos, and installer tickets — keep it with the evidence for “Treat the subsidy as a workflow with evidence at every handoff”.

Do not make it harder

  • Paying the final amount before checking agreed milestones For “Treat the subsidy as a workflow with evidence at every handoff”, that can hide whether the underlying issue is actually resolved.
  • Assuming low generation is automatically a bad panel For “Treat the subsidy as a workflow with evidence at every handoff”, that can hide whether the underlying issue is actually resolved.
  • Treating installer completion as DISCOM/subsidy completion For “Treat the subsidy as a workflow with evidence at every handoff”, that can hide whether the underlying issue is actually resolved.

How you know it is fixed

  • The official record and your real-world result agree for “Treat the subsidy as a workflow with evidence at every handoff”.
  • You have enough written evidence to prove the issue is finished if it returns later for “Treat the subsidy as a workflow with evidence at every handoff”.

If this still isn't resolved

  1. Installer/vendor grievance State the unresolved issue explicitly: “Treat the subsidy as a workflow with evidence at every handoff”.
  2. DISCOM/portal grievance route State the unresolved issue explicitly: “Treat the subsidy as a workflow with evidence at every handoff”.
  3. Consumer forum or other official remedy where appropriate State the unresolved issue explicitly: “Treat the subsidy as a workflow with evidence at every handoff”.

Sources for this path

Use these references to confirm provider-, model-, policy-, or jurisdiction-specific details before an irreversible step.

Need the complete context?

This page solves one branch. The parent guide covers the full decision, edge cases, alternatives, and related checks.

Open the full guide