What this is A detailed guide to interpreting why your project submission was rejected.
Who this is for Developers who received a rejection and want to understand what went wrong.
What you can do - Decode rejection reason codes - Understand what each failure means - Determine if the issue is fixable - Plan your next steps
Rejection reason categories
Financial thresholds not met - Project IRR below minimum : The calculated return is lower than investor requires. Often fixable by reviewing costs. - Equity IRR insufficient : Return on equity is too low. Review leverage and debt terms. - Payback period exceeds maximum : Too long to recover investment. Improve cash flow or reduce costs.
Project characteristics - System size outside range : Project too small or large. Find different investor. - Country not accepted : Investor does not invest in this geography. Find investor active in your country. - Technology not accepted : Investor may not finance certain configurations.
Data quality issues - Missing required information : Critical fields empty. Complete and resubmit. - Values outside plausible range : Inputs seem unrealistic. Verify and correct data.
What to do next For fixable issues: Review feedback, update submission, resubmit. For fundamental mismatches: Find investors with different criteria.
Common mistakes - Assuming rejection means project is bad - Resubmitting without making changes
Related articles - Improving Submission Success Rate - Project Versioning Explained
--- Tip: A rejection is feedback, not a final verdict.