Quick Answer
Solar subsidy calculator software should confirm residential route, consumer identity, geography, prior capacity, prior CFA, module capacity, and technical evidence before estimating support. Every result needs a dated authority rule, input snapshot, formula steps, warnings, reviewer, and audit trail. Estimated CFA is not eligibility, approval, sanction, invoice reduction, or payment.
Solar subsidy calculator installers need software that stops before arithmetic when eligibility facts, authority versions, or prior-benefit evidence remain unresolved.
An installer needs a reproducible estimate, not a persuasive number. Every output should identify its rule, inputs, formula, warnings, reviewer, proposal, and later authority decision.
Quick Answer
Solar subsidy calculator software should confirm residential route, consumer identity, geography, prior capacity, prior CFA, module capacity, and technical evidence before estimating support. Every result needs a dated authority rule, input snapshot, formula steps, warnings, reviewer, and audit trail. Estimated CFA is not eligibility, approval, sanction, invoice reduction, or payment.
This guide publishes no ranking, approval rate, payment time, customer count, accuracy, price, saving, return, conversion, update-speed, coverage, or outcome claim.
Solar subsidy calculator installers: 18 acceptance gates
Use these gates before trusting a calculator result or placing it in a proposal. A correct formula can still process the wrong person, connection, site, route, or rule.
| Gate | Required evidence | Block or pause when |
|---|---|---|
| Authority | Publisher, document, identifier, URL, dates, component, geography, and amendment relationship | A blog or software page supplies the rule |
| Rule version | Stable ID, effective date, retirement date, formula, tests, approval, and rollback | The displayed rate has no active version |
| Applicant | Legal name, identity source, role, record ID, status, date, and conflict check | Applicant and beneficiary are assumed identical |
| Consumer | Consumer number, category, connection, DISCOM, state, meter, and evidence | Residential status is inferred from the building |
| Site | Address, pincode, property, permission, roof route, and connection relationship | The site does not reconcile with the consumer |
| Project route | Individual residential, society, addition, replacement, relocation, or non-residential | One formula covers every route |
| Prior benefit | Prior plant, capacity, scheme, CFA, application, sanction, and payment evidence | Missing prior CFA defaults to zero |
| Capacity | Proposed, approved, module DC, inverter AC, installed, commissioned, portal, and claimed | Inverter size or roof area becomes eligible capacity |
| Technical state | DCR, equipment, approval, metering, inspection, commissioning, and portal evidence | A product choice proves eligibility |
| Benefit state | Estimate, review, sanction, disbursement, refund, reversal, and final state | An estimate is called approved subsidy |
| Money state | Gross price, support, contribution, invoice, tax, finance, payment, and accounting | Estimated support is silently deducted as cash |
| Formula | Variables, units, order, branches, rounding, caps, missing data, and conflict behavior | Hidden defaults produce a result |
| Explainability | Applied rule, capacity, prior treatment, exclusions, warnings, and next check | Users see only one amount |
| Change control | Source monitoring, impact, test, review, activation, rollback, and reissue | A rate changes without preserved history |
| Regression | Boundary, prior-benefit, route, unit, evidence, state, and channel cases | A happy-path demo replaces test evidence |
| Proposal handoff | Calculation ID, rule, snapshot, reviewer, caveat, validity, and supersession | A proposal copies an editable amount |
| Security and audit | Roles, access, logs, encryption, retention, restore, deletion, and incidents | Sensitive applicant or bank data lacks controls |
| Contract and exit | Data, rules, history, export, archive, deletion, transition, and assistance | Renewal is required to recover evidence |
Record pass, conditional pass, hold, narrow scope, or reject. Name the evidence, reviewer, expiry, unresolved risk, and approving authority for every gate.
Put official authority above the calculator
The MNRE June 2024 operational-guidelines notice is dated evidence for the residential CFA component.
MNRE states that this component concerns eligible residential consumers under capex mode. The document also states an implementation period through 31 March 2027.
The February 2025 clarification notice shows why rule versioning matters. Later official material can modify how an earlier section applies.
Use the PM Surya Ghar National Portal for the official application route and case records. Software does not replace portal or authority decisions.
Build an authority ledger
Record publisher, title, URL, document identifier, publication date, effective date, accessed date, component, geography, consumer category, capacity basis, and version.
Add amendment relationship, reviewer, legal or scheme owner, current status, last check, next check, and unresolved conflict. Retain inaccessible or withdrawn source evidence where lawful.
Published date, effective date, application date, installation date, inspection date, commissioning date, claim date, sanction date, and payment date answer different questions.
Block conflicting rules
Never select the most favorable source when official documents disagree. Mark the affected field, stop the calculation, and route the conflict to a qualified reviewer.
A portal screen, vendor badge, installer statement, old proposal, screenshot, search snippet, or product page does not amend an official rule.
The subsidy installer guide owns scheme-aware installer selection. This page owns calculator evidence and acceptance tests.
Separate every person, account, and site object
Applicant, beneficiary, consumer, household, society, legal entity, bank recipient, property owner, tenant, vendor, reviewer, and portal user may differ.
Consumer number, connection, meter, address, pincode, property, roof, DISCOM, state or UT, portal application, project, system, inspection, claim, sanction, and payment also differ.
Give every object an immutable ID. Record source, owner, date, status, verification, expiry, conflict, limitation, and related-object IDs.
Resolve duplicates and relationships
Check duplicate applicant, consumer, connection, site, household, project, application, bank account, and prior-benefit relationships before calculation.
One applicant may have several sites. One household may relate to several people. One society route may include individual plants and a common-facility connection.
Merge, split, restore, and correction events must retain previous IDs and source evidence. Never erase the relationship that produced an earlier estimate.
Confirm the route
Distinguish individual residential capex, GHS or RWA common facilities, capacity addition, replacement, relocation, non-residential, and another official programme.
The June 2024 guidelines exclude non-residential segments from this residential CFA component. A commercial lead should receive an ineligible-route result, not a capped residential amount.
The nearby vendor guide owns local vendor discovery and serviceability. Portal registration is not calculator accuracy evidence.
Keep capacity states separate
Proposed capacity is not approved capacity. Approved capacity is not installed capacity. Installed capacity is not commissioned or portal-recorded capacity.
Store module nameplate direct-current capacity, inverter alternating-current capacity, proposed, sanctioned, installed, commissioned, portal, prior, subsidized, incremental, and claimed capacity separately.
Every capacity needs a unit, precision, source, date, revision, equipment reference, status, reviewer, and limitation.
Use the authority-defined basis
The June 2024 guideline bases CFA on rated DC module capacity, irrespective of inverter size. It also addresses fractional capacity and caps additional support beyond its stated boundary.
Do not infer eligible capacity from inverter rating, roof area, electricity bill, customer preference, proposal, price, sanctioned load, or finance request.
If installed capacity differs from the accepted proposal, create a new calculation. Compare outputs, review eligibility, supersede the old proposal, and notify the recipient.
Treat prior systems as a calculation branch
Capture prior installation date, module capacity, connection, location, scheme, application, sanction, CFA, payment, relocation, and later addition.
The June 2024 guideline contains examples for additions after prior CFA. Those examples must become versioned regression fixtures, not memory-based sales rules.
Missing, stale, or conflicting prior-benefit evidence should block the estimate. A blank field must never mean no prior benefit.
Separate technical conditions
DCR status, module evidence, inverter evidence, vendor registration, feasibility, metering, inspection, commissioning, and portal acceptance are separate facts.
The cited guideline makes DCR a condition for CFA under its scope. A product brand, invoice line, certificate label, or salesperson statement does not prove project compliance.
Record exact equipment, evidence identifier, issuer, model, manufacturer, date, validity, project relationship, reviewer, and unresolved mismatch.
Separate estimates, sanctions, and money states
Gross system price, eligible basis, estimated central support, estimated state support, finance amount, customer contribution, invoice value, tax, discount, advance, and balance differ.
Sanctioned CFA, disbursed CFA, refund, reversal, final cost, bank credit, portal status, and accounting entry also differ.
Every amount needs currency, gross or net basis, tax inclusion, formula version, capacity basis, slab, rounding, cap, source, date, state, recipient, and limitation.
Do not net unverified support into price
Show gross price first. Show estimated central support separately. Show state support only after current official verification.
Customer contribution may be a scenario, not an invoice or cash requirement. Keep finance, payment timing, sanction, disbursement, refund, and accounting outside the estimated calculation.
The pricing calculator guide owns cost, price, markup, margin, discount, tax, and commercial-rule controls.
Treat state support as another authority layer
Require an official state or UT source, eligible geography, consumer category, capacity rule, amount rule, budget, availability, effective date, and application process.
Record stacking treatment, recipient, payment route, conflict state, reviewer, last check, and next check. Never infer a top-up from another state or an old announcement.
If sources conflict or availability cannot be confirmed, preserve the central result and block the state-support amount. Explain the exact missing verification.
Make each calculation reproducible
Create an immutable calculation ID linked to applicant, consumer, site, project, route, state, DISCOM, rule version, proposal version, reviewer, and audit record.
Store calculation timestamp, timezone, input snapshot, formula trace, output, warning, block, override, source links, and superseded calculation IDs.
Define every input
Each field needs a stable ID, label, type, unit, allowed range, source, required state, validation, default rule, dependency, error, privacy class, and retention rule.
Defaults for consumer category, prior CFA, state, DISCOM, capacity unit, DCR, and eligibility are unsafe. Require evidence or return an unresolved state.
Reject negative capacity, mixed units, impossible dates, unsupported categories, stale sources, mismatched connections, and conflicting application IDs.
Define every formula branch
Document variables, order, units, precision, rounding, slabs, caps, geography branches, route branches, prior-benefit treatment, exceptions, and missing-data behavior.
Version the formula independently from display text. Record effective and retired dates, source, reviewer, tests, activation, rollback, and affected calculations.
For the ordinary residential route, the June 2024 guideline states ₹30,000 per kWp for the first 2 kWp. It states ₹18,000 per additional kWp up to 3 kWp.
That dated rule gives ₹45,000 for 1.5 kWp and ₹69,000 for 2.5 kWp. Apply it only when the active authority version and case facts support it.
Explain the result
Show route, capacity basis, prior-capacity treatment, prior-CFA treatment, applied rule, formula steps, rounding, cap, exclusions, warnings, and unresolved facts.
Add authority caveat, reviewer, calculation time, validity, source links, and next verification step. Avoid a single green amount without context.
An ineligible, blocked, or review-required result is valid software behavior. It is safer than a guessed amount.
Control overrides
Record old value, new value, reason, source, requester, approver, timestamp, expiry, affected output, affected proposals, and audit link.
Do not permit overrides for missing authority, wrong consumer route, conflicting prior benefit, or unverified state support unless policy expressly allows review.
Govern rule updates and releases
Monitor named MNRE, National Portal, state, UT, regulator, and DISCOM sources. Record owner, frequency, last check, next check, availability, change signal, and escalation.
An automatic-update marketing claim does not prove source coverage, interpretation, review, testing, deployment, channel parity, or historical correctness.
Use controlled rule states
Distinguish draft, reviewed, approved, scheduled, active, deprecated, retired, rolled back, and emergency-rule states.
Only one authorized version should serve a defined route, geography, and effective period. Block calculation when active versions overlap or leave a gap.
Preserve old calculations under their original versions. Prevent new use of retired rules unless an approved exception records the reason and recipient impact.
Review affected proposals
A change request should identify source, effective date, affected applicants, fields, formulas, calculations, proposals, quotes, channels, integrations, and archived outputs.
Test expected results before activation. Define migration, backward compatibility, communication, reapproval, reissue, supersession, rollback, and incident handling.
The PM Surya Ghar proposal guide owns the full proposal workflow. This page owns the controlled calculation snapshot that feeds it.
Run 17 authority-derived regression cases
Build expected results independently from current official documents. Do not copy the software output into the expected-result column.
The examples below use the June 2024 guideline and February 2025 clarification as dated source fixtures. Revalidate them against later official material before each release.
| Case | Controlled input | Expected branch or result |
|---|---|---|
| REG-01 | New ordinary residential route, verified 1 kWp DC, no prior system | ₹30,000 estimated central CFA under the cited dated rule |
| REG-02 | New ordinary residential route, exact 2 kWp DC boundary | ₹60,000 estimated central CFA |
| REG-03 | New ordinary residential route, 2.5 kWp DC | ₹69,000 with visible 2 kWp and 0.5 kWp steps |
| REG-04 | New ordinary residential route, exact 3 kWp DC boundary | ₹78,000 estimated central CFA |
| REG-05 | New ordinary residential route, 6 kWp DC | ₹78,000 under the cited cap, with unsupported capacity visible |
| REG-06 | Verified special-category geography, 1 kWp DC | Apply the separately versioned special-category rate only after geography review |
| REG-07 | Ordinary GHS common facility, 20 households, 100 kWp | Test lower 60 kWp basis and ₹10,80,000 dated example result |
| REG-08 | Ordinary GHS common facility, 50 households, 100 kWp | Test 100 kWp basis and ₹18,00,000 dated example result |
| REG-09 | Prior 1 kWp Phase II system with CFA, total expands to 4 kWp | Test the guideline’s ₹48,000 additional-CFA example and retained prior evidence |
| REG-10 | Prior 1 kWp PM Surya Ghar system with CFA, total expands to 4 kWp | Test the guideline’s ₹48,000 additional-CFA example and no double count |
| REG-11 | Prior system or CFA facts missing or conflicting | Block calculation and request authority evidence |
| REG-12 | Commercial or industrial consumer | Return ineligible for this residential CFA component, with no amount |
| REG-13 | Capacity entered as watts but labelled kWp, or AC used as DC | Reject unit or basis and require correction |
| REG-14 | DCR or required technical evidence unresolved | Block eligibility estimate and identify missing evidence |
| REG-15 | Current official state support verified for the exact case | Calculate and label state support separately from central CFA |
| REG-16 | State sources conflict, expire, or lack budget availability | Preserve central result and block the state amount |
| REG-17 | Authority rule changes after proposal issue | Recalculate, compare, approve, reissue, communicate, and supersede |
Every case needs source, source date, rule version, inputs, expected branch, expected amount or block, warning, tolerance, reviewer, app version, and channel.
Retain actual result, timestamp, output file, pass or fail, defect, fix, retest, approval, and release. Test browser, mobile, offline, API, import, PDF, and customer view.
Add failure cases around the boundaries
Test zero, negative, blank, excessive, fractional, and over-precision capacity. Include wrong state, DISCOM, category, consumer, connection, timezone, currency, and unit.
Test duplicate applications, merged consumers, split sites, several meters, several systems, relocation, replacement, repower, stale rules, deleted evidence, and restored records.
Test late source changes, cached rules, failed proposal generation, repeated events, out-of-order updates, partial writes, and accepted stale documents.
Control proposal and quotation handoff
A proposal should receive an immutable calculation snapshot. Include calculation ID, rule version, capacity, gross price, estimated central support, state-support state, and contribution scenario.
Add inputs, assumptions, warnings, reviewer, source links, issue date, validity, recipient, proposal version, and supersession state.
Never pass one editable amount without its evidence. The quote generator guide owns controlled quote output and acceptance evidence.
The quotation app guide owns mobile, device, offline, permissions, synchronization, and field execution.
Map systems of record
Calculator, CRM, proposal, quote, contract, invoice, accounting, portal, DISCOM, bank, messaging, signature, and project systems serve different authorities.
Define object, ID, field owner, direction, event, timing, authentication, rule version, rate limit, retry, idempotency, conflict, error queue, alert, replay, and deletion behavior.
Reconcile calculation, proposal, accepted contract, invoice, portal record, sanction, bank payment, and accounting. Do not make the calculator authoritative for all states.
Test channel parity
Web, mobile, offline, spreadsheet, API, import, template, PDF, email, WhatsApp, and customer view should show the same calculation version.
Compare capacity, rule, steps, rounding, central estimate, state status, warnings, caveat, validity, reviewer, and source links across every output.
The proposal template guide owns reusable field, schema, variant, rendering, and template governance.
Protect applicant and payment data
Separate intake, document verification, technical input, rule administration, formula change, calculation, override, review, proposal issue, export, deletion, and audit roles.
Apply least privilege by legal entity, branch, team, applicant, record, field, action, rule, formula, output, export, integration, and audit.
Set privacy boundaries
Applicant identity, consumer number, bill, address, property, bank, portal, technical, support, and payment records need a defined purpose and owner.
The MeitY DPDP material shows phased, date-specific implementation. Qualified review must determine duties for the exact processing.
Document notice, consent or other basis, minimization, access, encryption, logs, sharing, subprocessors, hosting, transfer, backup, retention, deletion, grievance, and incident handling.
Use synthetic applicant and bank data during evaluation. Do not upload real records before privacy, security, contract, access, retention, and deletion approval.
Preserve an audit trail
Log actor, account, role, action, old value, new value, reason, source, timestamp, timezone, channel, approval, result, correlation ID, and affected documents.
Protect audit access and retention. Test export and restore of rules, formulas, versions, inputs, outputs, attachments, overrides, approvals, and superseded links.
Pilot, cost, contract, and exit
Pilot the exact legal entity, plan, account, role, region, channel, rule version, workflow, and production-like data pattern.
Test users, calculations, proposals, records, storage, templates, messages, mobile, offline, automation, integrations, API, security, backup, support, export, and deletion limits.
Normalize three-year cost
Include plan, seats, calculation volume, proposals, records, storage, messages, templates, rule updates, integrations, API, setup, migration, and configuration.
Add training, administration, support, backup, security, overages, taxes, renewal, export, archive, deletion, transition, and replacement work.
Mark every amount as quoted, contracted, estimated, assumed, or unknown. Do not infer value from a feature list.
The CRM pricing guide owns broad suite price and TCO comparison.
Contract the calculation boundary
Define data, document, rule, formula, source-update, interpretation, test, approval, availability, change, support, security, and privacy responsibilities.
Cover subprocessors, intellectual property, export, termination, retention, deletion, audit, liability, incident support, transition, and exit assistance.
Test export before purchase and renewal. Require applicant, consumer, site, evidence, rule, formula, version, input, output, warning, audit, proposal, and relationship data.
Evaluate QuickEstimate under identical gates
Disclosure: SurgePV and QuickEstimate have a commercial relationship. QuickEstimate receives the same authority, formula, regression, privacy, pilot, contract, and exit checks as every provider.
The QuickEstimate home and calculator page makes dated first-party PM Surya Ghar, state-support, proposal, CRM, update, and output claims.
Its 24-hour update, accuracy, eligibility, net-cost, state-support, DISCOM, integration, and outcome language is not accepted as proof.
The pricing page lists plan and feature claims. Verify exact calculator, rule, channel, limit, migration, support, renewal, export, and exit scope.
The security page, privacy page, and terms page remain vendor evidence.
Reconcile product and entity names, roles, hosting, subprocessors, backup, retention, residency, transfers, calculator data, exports, support, termination, and document priority.
QuickEstimate receives no rank here. Run all 17 regression cases and every acceptance gate in the purchased plan before relying on an output.
Keep SurgePV inside its verified scope
SurgePV’s current design page, shadow page, and generation tool support their stated technical and modelling scope.
Its current proposal page supports design-linked BOM, visuals, production, financial, PDF, and responsive-web proposal statements.
Those pages do not establish scheme authority, CFA eligibility, calculator logic, portal status, DISCOM approval, bank payment, or QuickEstimate integration.
Apply the same evidence, version, permission, export, history, and reconciliation standard to technical inputs passed into a scheme estimate.
Keep adjacent decisions separate
The PM Surya Ghar proposal guide owns the full proposal process. The vendor guide owns local discovery.
The subsidy installer guide owns provider selection. The pricing calculator guide owns commercial rules.
Broad proposal, quotation, CRM, design, portal, DISCOM, bank, accounting, and project decisions remain with their controlling systems and dedicated reviews.
Frequently asked questions
What should a solar subsidy calculator check first?
Check the dated scheme component, residential consumer route, applicant, connection, site, state or UT, DISCOM, prior system, prior CFA, proposed module capacity, and unresolved technical evidence. Calculation begins only after required facts pass validation.
Can subsidy calculator software confirm PM Surya Ghar eligibility?
No. Software can apply a dated rule to documented inputs and show an estimate. It cannot verify legal identity, approve feasibility, inspect equipment, commission a system, decide portal status, sanction CFA, or release payment.
Which capacity should a PM Surya Ghar calculator use?
The June 2024 operational guidelines base CFA on rated direct-current module capacity, not inverter size. Keep proposed, approved, installed, commissioned, portal, prior, subsidized, incremental, and claimed capacities separate and recheck later official changes.
How should a calculator handle prior rooftop capacity and CFA?
Capture prior system, capacity, scheme, CFA, date, consumer, connection, and portal evidence separately. Apply the current authority rule for additions. Missing or conflicting prior-benefit facts should block the estimate instead of defaulting to zero.
Can installers calculate residential CFA for commercial customers?
No. The June 2024 residential CFA guidelines exclude non-residential segments, including commercial and industrial consumers. Route those projects outside this calculator unless a separate current official programme and calculation have been verified.
Should estimated subsidy be deducted from the invoice price?
Do not treat estimated support as sanctioned or received cash. Show gross price, estimated central support, separately verified state support, customer contribution scenario, invoice, sanction, disbursement, refund, and accounting states independently.
How should a calculator handle a state subsidy?
Use only current official state or UT evidence with eligibility, geography, capacity, amount, budget, availability, effective date, process, stacking, and payment rules. Keep it separate from central CFA. Block stale or conflicting sources.
How should subsidy rules be updated in software?
Record the official source, effective date, affected cases, formula change, tests, reviewer, approval, activation, rollback, and reissue policy. Preserve old calculations under their original version while preventing unauthorized new use of retired rules.
How should QuickEstimate be evaluated as a subsidy calculator?
Treat its pages as related-party first-party claims. Apply identical authority, formula, version, regression, proposal, channel, privacy, security, pilot, cost, contract, support, export, archive, deletion, and exit gates without ranking.
