How to track PM Surya Ghar subsidy for 100+ customers

PM Surya Ghar subsidy tracking is the practice an EPC uses to follow every customer’s subsidy claim through the scheme’s fixed stages — from portal registration to the money reaching the customer by DBT — so no claim goes quiet and no customer is left wondering. At one or two jobs it lives in your head. At fifty or a hundred live claims, all at different stages, it needs a shared status model — or the where-is-my-subsidy calls will bury you.

This post is for the high-volume rooftop EPC running dozens of PM Surya Ghar jobs at once. The hard truth up front: the subsidy is never your money, yet its delay is squarely your reputation. We will give you a simple eight-stage tracker model, the exact fields to record per customer, the five reasons claims stall, and a follow-up rhythm to unstick them. It builds on our PM Surya Ghar guide for EPC contractors.

Why track subsidy that is not even your money?

Because the customer does not see the DISCOM or MNRE — they see you. Under PM Surya Ghar, the Central Financial Assistance is paid straight to the homeowner’s bank account by direct benefit transfer, after the system is commissioned and the net meter is installed. The money never passes through the EPC. And yet, when it is late, there is only one phone number the customer calls: yours.

This is the trap of high-volume rooftop work. You have already installed the plant, raised your invoice and moved your crew to the next roof. To you the job feels done. To the customer, the job is not done until the promised ₹78,000 lands in their account. Every day it does not, they wonder if you filed something wrong — and they hold back your final payment or withhold the referral you were counting on.

So subsidy tracking is not accounting — it is reputation management at scale. A customer whose subsidy is stuck at “inspection pending” is fine if you call them first and explain. The same customer becomes a one-star review if they call you and you have to say “let me check and call back.” The tracking exists so you always know the answer before they ask. These steps live inside your broader government workflows, on the same job record as the build.

The 8 stages every subsidy claim sits in

Every PM Surya Ghar subsidy claim, for every customer, sits in exactly one of eight stages at any moment. This is the original asset of this post: a status model you can adopt today. Give each customer’s claim a single current stage, and your hundred-claim pipeline becomes a list you can filter, not a memory you have to search.

Notice where control shifts. In stages 1 and 2 you are waiting on the customer and the DISCOM. In stages 3 to 6 the work is yours. In stages 7 and 8 you are waiting again — but this is where most claims silently rot, because the crew has left and no one owns the payout. A claim parked at stage 5 or 7 with no follow-up date is the single most common cause of an angry call. The status model exists to make that stall visible.

What to track for each customer (copy this)

For every customer, track a fixed set of fields so any claim can be answered in seconds, not phone calls. The stage tells you where a claim is; these fields tell you everything else you need when the customer — or the DISCOM — asks. Copy this table into whatever you use today, even a spreadsheet, and standardise it across your team.

The two columns that do the heavy lifting are current stage and owner plus next follow-up. Stage lets you filter your whole pipeline — “show me every claim stuck at inspection for 10+ days.” Owner and follow-up mean each of those stuck claims has a human and a date attached, so nothing waits on “someone should probably check that.” A live analytics dashboard turns these fields from a spreadsheet you maintain into a screen you glance at.

Why claims stall — and the follow-up cadence to fix them

Subsidy claims stall at five predictable points, and each one has a fix — if you catch it before the customer does. None of these are exotic. They are the same five problems on every high-volume EPC’s desk, which is exactly why a tracker that surfaces them early is worth more than any amount of chasing after the fact.

The cadence that unsticks them is boring and it works: a fixed follow-up rhythm on every claim past stage 4. A weekly sweep of everything sitting in “net-meter applied” or “inspected,” a call to the DISCOM with the reference number, and a proactive note to the customer that you are on it. Most delay is not a hard block — it is a queue that moves when someone keeps asking. For the module-eligibility side of this, keep our PM Surya Ghar hub handy for the current scheme rules.

How long does the subsidy DBT really take?

The scheme targets roughly 30 working days for DBT after commissioning and net-meter details are uploaded — but real timelines vary widely by state and DISCOM. Treat 30 days as the target on the poster, not a promise you can bank. In practice, claims clear anywhere from a couple of weeks to a couple of months, depending on inspection backlogs, portal processing and how clean the paperwork was.

Why does this matter for tracking? Because a target of 30 days means you should flag any claim that has sat in “commissioned” or “bank details submitted” for longer than that. The tracker is not just a record — it is an alarm. When a claim crosses its expected window, it should surface at the top of someone’s list, not disappear into the pile.

Set the expectation in writing at quote stage

The single best way to cut subsidy-chasing calls is to set the DBT expectation in writing, at the quote stage, before the customer has paid a rupee. Most anger about a “late” subsidy is really anger about a broken assumption. The customer assumed the ₹78,000 would arrive the day the plant switched on. You never said that — but you never said otherwise either.

Put three plain lines in every quote and handover document:

• The subsidy is paid by the government to you, not to us. It reaches your bank account by DBT; it never passes through our company.
• It arrives after commissioning and net metering, not at installation. The clock starts once the meter is in and details are uploaded.
• Targeted around 30 working days, but it varies by state. We will track your claim and update you at each stage.

That last promise — “we will track your claim and update you” — is only credible if you actually have the tracker behind it. This is where the status model earns its keep: it lets you make a confident promise at the quote stage and keep it across a hundred customers. For the installer-specific playbook around this, see our PM Surya Ghar installers solution.

Tracking every claim on one record with SuryaHub

SuryaHub keeps the subsidy claim on the same job record as the install, so every customer has one live stage, one owner and one next follow-up date — and nothing goes quiet. The eight-stage model and the tracker fields in this post are not a separate tool you bolt on. They sit on the job file you already run, next to the survey, the quote and the payment milestones.

On a live PM Surya Ghar job, SuryaHub ties the subsidy claim to the delivery:

• One record per customer — the subsidy stage lives on the same job file as the install, so status is never in a second place.
• Stage-based pipeline — filter every claim by its current stage to see who is stuck at feasibility, inspection or DBT.
• Owner and follow-up dates — each claim has a person and a next action, so stalls surface instead of hiding.
• Compliance details on file — ALMM, DCR and net-meter references sit with the claim, ready for any portal check or audit.

Here is the honest part. SuryaHub is pre-revenue and building alongside two pilot EPCs, Suryantra Energy and RGESPL. We will not show you invented claim-clearance rates or fake testimonials. And to be clear about what the tool does not do: it does not read the DBT amount from the National Portal automatically — your team marks a claim “DBT released” once the customer confirms the money landed. What SuryaHub gives you is the one thing high-volume EPCs lack: a single, filterable view of where every customer’s subsidy stands, so you call them before they call you.

Frequently asked questions

How do you track PM Surya Ghar subsidy for many customers at once?

Give every customer a subsidy-claim record that sits on the same job file as the install. Move each record through the eight scheme stages — registered, feasibility approved, installed, net-meter applied, inspected, commissioned, bank details submitted, DBT released. Then filter by stage to see who is stuck. Tracking one claim is memory; tracking a hundred needs a status model everyone can read.

If the subsidy goes to the customer by DBT, why is tracking the EPC job?

Because the customer blames the EPC for any delay, even though the money never touches you. MNRE pays the Central Financial Assistance straight to the homeowner bank account after commissioning and net metering. But the customer only knows their subsidy has not arrived, and they call you. Tracking it protects your reputation, your referrals and your final payment.

How long does the PM Surya Ghar subsidy take to reach the customer?

The scheme targets roughly 30 working days after the commissioning and net-meter details are uploaded and the customer submits bank details. In practice it varies a lot by state and DISCOM, from a few weeks to a few months, depending on inspection backlogs and portal processing. Tell customers it is targeted, not guaranteed, and confirm the current position for their state.

Why do PM Surya Ghar subsidy claims get stuck?

Claims stall most often at five points: DISCOM feasibility rejection, net-meter delays, document mismatch on the portal, non-ALMM modules on a subsidised job, or wrong customer bank details. Each has a fix, but only if you catch it early. A claim with no owner and no follow-up date sits silent until the customer calls angry.

What details should an EPC record for each subsidy claim?

Record the customer and site, the DISCOM and consumer number, the sanctioned load, the current claim stage with its date, the application and net-meter reference numbers, the ALMM and DCR module details, and whether bank details are submitted. Add an owner and a next follow-up date. These fields let you answer any where-is-my-subsidy call in seconds.

Can SuryaHub track PM Surya Ghar subsidy DBT status?

Yes. SuryaHub keeps the subsidy claim on the same job record as the install, so each customer has one live stage and follow-up date. It is honest to say SuryaHub is pre-revenue and building with two pilot EPCs, so we do not read the DBT amount from the portal automatically — your team updates the released status, and the dashboard shows who is still pending.

Keep reading

Want every subsidy claim tracked to DBT, so no customer ever goes quiet?

Book a demo →