You did everything you were told. You got a project report made. You submitted it to the bank with all your documents. And then—rejection. Or worse, a vague “please revise and resubmit” with no clear explanation of what’s actually wrong.
This specific situation — where the report exists but the loan still doesn’t come through — is more common than most people realize, and the reasons behind it are almost never the ones banks openly explain.
After working with thousands of loan applicants across India, Sharda Associates has seen the same hidden patterns show up repeatedly. Here’s what’s actually happening when a bank rejects a loan even after a project report has been submitted.
Hidden Reason 1: Your Report Was Prepared Without Anyone Checking If the Numbers Make Sense
A project report can look complete—cover page, financial tables, balance sheet, P&L—and still contain assumptions that no banker familiar with your industry would accept for a moment. The most common version: Year 1 revenue projections that assume 80-90% capacity utilization right from launch, when banks typically expect 40-60% for new businesses.
When a credit officer sees a first-year manufacturing unit projecting near-full capacity without any explanation of how those sales will be achieved, the entire report loses credibility in their eyes—not just that one section. They begin to question every other number in the document.
This is the specific risk of reports generated through online tools or prepared by someone unfamiliar with how banks evaluate projections: the report is complete, but the assumptions behind it haven’t been tested against industry reality. A CA reviewing your report before it goes anywhere will catch this. An automated tool won’t.
Hidden Reason 2: The Financial Statements Don’t Actually Tie Together
Banks don’t just read your P&L. They cross-check it against your balance sheet, your cash flow statement, and your CMA data. If these documents aren’t internally consistent — if the net profit in your P&L doesn’t reconcile correctly with retained earnings in your balance sheet, or if your cash flow statement shows a different picture than your P&L suggests — it’s a significant red flag.
This particular problem happens frequently in reports where different sections were prepared separately or where one number was manually adjusted after the fact without updating the figures that depended on it. The report looks fine when you read any one section in isolation. But the cross-check reveals inconsistency, and that inconsistency is what triggers the revision request or rejection.
A CA who prepares all sections of the report as an integrated document — rather than generating each one independently—is the only reliable way to prevent this.
Get Your Detailed Project Report
Hidden Reason 3: Your DSCR Is Technically Above 1 But Not Convincingly Above It
This is subtler than most people expect. Most businesses applying for loans know they need a positive DSCR — they know it needs to be above 1. What they often don’t know is that a DSCR of 1.05 or 1.10 creates as much concern for a bank as a DSCR below 1 would.
Banks don’t just want to see that your projected income covers your EMI. They want to see meaningful headroom — enough that if your actual revenue comes in 15-20% below projection (which is common for new businesses in early years), the loan can still be serviced. A DSCR of 1.5 or above gives banks that comfort. A DSCR barely above 1 tells them one bad quarter puts you in default.
If your report shows a DSCR that’s technically passing but not convincingly so, banks will either reject the application or ask for additional security to compensate for the thin margin. Often, this is fixable — not by inflating numbers, but by restructuring the loan tenure, revisiting the EMI schedule, or adjusting the loan-to-own-contribution ratio to produce a more comfortable ratio.
Hidden Reason 4: The Report Doesn’t Match Your Bank Account Reality
This one catches a lot of applicants off guard. When banks appraise your loan application, they don’t only read your project report—they also look at your bank statements for the last 6 to 12 months. If your bank statements show transaction patterns, income flows, or balances that are significantly inconsistent with what your project report claims about your business, the mismatch raises questions.
For an existing business applying for a loan, this is particularly relevant: if your financial projections show strong profitability but your bank statements suggest thin or irregular cash flow, the credit officer will weight the bank statement evidence more heavily than the report’s projections. For a new business, the issue is different: if your own contribution to the project cost isn’t verifiably sitting in your bank account, the bank will flag it regardless of what your project report says.
This isn’t a documentation problem that can be fixed by revising the report. It’s a gap between the report and the verifiable reality behind it — which is why understanding your specific situation before preparing the report matters more than just filling in a template.
Hidden Reason 5: The Wrong Section Was Skipped or Left Generic
Banks have a standard sequence for how they review project reports, and credit officers — especially at public sector banks — often work through the same checklist for every application. If a specific section that’s normally present is thin, generic, or missing entirely, it gets flagged automatically.
The most commonly skipped or underprepared sections:
Working capital justification — Many reports state a working capital requirement as a single number without explaining the calculation. Banks want to see the logic: inventory holding days, debtor days, creditor days, and minimum cash requirement all itemized, not just a final figure.
Technical and operational plan — Particularly for manufacturing businesses, banks want specific details about machinery specifications, production process, and raw material sourcing. A vague description of “manufacturing operations” doesn’t satisfy this requirement.
Market and competition section — Generic statements about “growing demand” for a product without any data, local market sizing, or competitive context are one of the fastest ways to weaken an otherwise solid application.
Each of these sections sounds minor in isolation. Collectively, if several are thin or templated, the report reads as if the applicant hasn’t genuinely thought through their business — which is exactly the impression you don’t want to create with a bank.
What To Do If You’ve Already Been Rejected
The first step — before anything else — is getting the actual written rejection or revision note from your bank and understanding what specific issue was cited. Banks are required to provide a reason, and while the language is sometimes vague, it usually points to one of the five issues above.
From there, the report can typically be revised and resubmitted rather than started from scratch. At Sharda Associates, we review existing reports that have been rejected or flagged, identify the specific issues, and prepare a corrected, CA-certified version—delivered within 24 to 48 hours and built to address the exact concerns raised rather than just reformatting the same document.
Conclusion
A rejected loan application — even with a project report attached — is almost never about your business idea being fundamentally unviable. It’s almost always about something specific in how the report was prepared with an assumption that doesn’t hold up, an inconsistency between financial statements, a DSCR that’s technically passing but not convincing, or a section that was left too thin.
These are fixable problems. The faster you identify which one applies to your situation, the sooner your application can move forward—and that process starts with understanding exactly what your bank is actually looking at when they review what you’ve submitted. Get Your Feasibility Report →
Call or WhatsApp +91 89899 77769
Frequently Asked Questions
1. Why did my bank reject my loan even though I submitted a project report?
The most common hidden reasons include unrealistic financial projections, inconsistencies between financial statements, a DSCR that’s technically above 1 but too thin for bank comfort, a mismatch between your report and bank statements, and underprepared sections like working capital justification or market analysis.
2. What does it mean when a bank says “please revise and resubmit” my project report?
It typically means something specific in your report raised a concern during credit appraisal—often an assumption that doesn’t match industry norms, an inconsistency between sections, or a section that was insufficiently detailed for the bank’s evaluation criteria.
3. Can a project report be fixed after rejection, or do I need a new one?
In most cases, the report can be revised and corrected rather than prepared from scratch. The key is identifying the specific issue raised during appraisal and addressing it directly in the revision.
4. What DSCR does my project report need to show for bank loan approval?
Most banks want to see a DSCR of 1.25 or above, with 1.50 considered comfortably bankable. A DSCR barely above 1.0 raises almost as many concerns as a DSCR below 1 because it leaves no headroom for revenue shortfalls in early operating years.
5. Why do financial statements need to be “internally consistent” in a project report?
Banks cross-check your P&L against your balance sheet and cash flow statement. If the net profit in your P&L doesn’t reconcile with retained earnings in your balance sheet, or if cash flow doesn’t match your stated profitability, it creates a red flag that suggests the report was assembled carelessly or contains errors.
6. How does my bank account affect my project report approval?
Banks review your bank statements alongside your project report. Significant inconsistencies between what your report claims and what your bank statements show — in terms of income, transactions, or cash balances — will weigh against your application regardless of how well the report is written.
7. How quickly can Sharda Associates fix a rejected project report?
A revised, CA-certified project report addressing specific bank rejection reasons is typically delivered within 24 to 48 hours of sharing the rejection details and your business information.