Government subsidy budgets go unspent every year while businesses complain schemes are 'sirf kagaz pe'. Both things are true, and the gap between them is application quality: the majority of rejections are self-inflicted — sequencing errors, paper defects and abandonment — not policy stinginess. Having seen the pattern across hundreds of files, here are the actual rejection reasons, ranked, and the system that prevents each.
Reason 1: The sequencing sin
The single largest killer: spending before applying. Most schemes fund proposed investments — machinery ordered, land registered or production started before the application (or before in-principle approval) becomes ineligible expenditure. Stamp-duty exemptions claimed after registration, capital subsidies on machines bought last year, PMEGP for units already running: all dead on arrival. Prevention: entitlement mapping happens at DPR stage, applications file before financial commitments, and where genuine urgency exists, get the scheme's written position on interim spending first.
Reason 2: DPR and viability defects
- Template project reports with copied financials — committees and bankers pattern-match them instantly
- Fantasy revenue against no demand evidence; missing working capital (the all-machinery DPR); costs without quotations
- The promoter can't explain their own numbers at interview/task-force stage — fatal in PMEGP/Stand-Up settings
- Prevention: bottom-up DPRs from real quotations and local data, working capital honestly sized, and the promoter rehearsed on every figure — it's their business plan, not the consultant's
Reason 3: Eligibility misreads
- Ineligible activity (negative lists), ineligible costs (land/building where only P&M qualifies, second-hand machinery), wrong category (turnover/investment bands misjudged)
- Family dedupe hits (PMEGP's one-per-family rule), prior-subsidy conflicts (same cost claimed under another scheme)
- Entity mismatches: scheme requires company/SHG/SPV forms the applicant doesn't have; Udyam details stale
- Prevention: read the current guidelines (schemes amend — last year's slabs mislead), run the dedupe honestly, and fix entity/registration hygiene before filing
A growing share of rejections are digital: wrong documents uploaded (unreadable scans, mismatched names), Aadhaar/PAN/bank-detail mismatches that fail auto-validation, deadlines missed inside application windows, and — the classic — queries raised on the portal that nobody saw until the lapse date. Prevention: one owner for every application with portal credentials, calendar alerts, and a weekly check of every pending application's query tab.
Reason 5: Bank-stage failures
Scheme approval ≠ money: bank-linked schemes (PMEGP, Stand-Up, Mudra-routed, AIF) die at credit appraisal — CIBIL defects discovered late, margin money unavailable, security disputes, or branch-level indifference. Prevention: pre-clear credit reports before applying, keep margin evidenced, choose branches where your conduct is known, obtain the DIC/scheme recommendation letters that move branch files, and escalate stalled files formally (portals, LDMs, nodal officers) — tracked applications get decisions; verbal enquiries get sympathy.
Reason 6: Abandonment
The quiet epidemic: applications that fail because the applicant stopped — didn't attend the EDP training, missed the inspection date, never resubmitted after a curable deficiency, or gave up at the second follow-up. Government process rewards persistence mechanically: files with complete responses and polite, written, referenced follow-ups clear; files without them age out. Prevention: treat each application as a 6–18 month project with an owner, a milestone tracker and a follow-up cadence — because that is what it is.
The prevention system, summarised
One page, five disciplines: (1) entitlement mapping before any money moves; (2) guidelines read in current version, eligibility tested honestly; (3) DPRs built bottom-up and owned by the promoter; (4) one named owner per application with portal, calendar and query vigilance; (5) bank and department relationships worked in parallel with written escalation paths. Run this and your hit-rate flips from the ambient 30–40% to the 80%+ that professional files achieve — on the same schemes everyone else calls fictional.
How Aidwish helps
Aidwish's subsidy practice is this system industrialised — entitlement mapping, defect-proof files, portal and query management, bank/task-force preparation and follow-through to disbursal — because the scheme money is real, and it goes to the best-prepared file in the queue.