What long-horizon projections are for
Most bank loans run for five to fifteen years, so a projection horizon of twenty-five years is longer than a single facility. The value of a long horizon is not that every loan needs twenty-five years. It is that the same model can cover a long-lived asset, a phased expansion, or a business plan that the borrower and the bank review year after year without rebuilding the file.
Finxora's project report software supports projections up to twenty-five report years. That range lets a promoter model a full asset life, a multi-phase project, or a long repayment schedule in one place.
Where the 25-year capability lives
The twenty-five-year projection horizon is a feature of the project report module, not of the CMA data module. CMA data covers the borrower as a going concern and is usually prepared for a shorter span: a few audited years, the current provisional year and a small number of projected years. Project reports cover a specific investment and need a longer view.
Using the two together is common: CMA data shows the existing business, and the project report shows the new investment and its repayment. Finxora shares data between the balance sheet, CMA and project report modules, so the historical years do not need to be re-entered.
What the projection engine builds
Everything in the project report is projected: operating statement, balance sheet, cash flow, depreciation and debt service for each report year, up to the twenty-five years the project master allows. The calculation engine derives them from your inputs rather than asking you to type each statement, so the balance sheet tallies and the ratios follow from the figures shown.
- DSCR: receipts (net profit plus depreciation plus term-loan interest) divided by repayments (principal plus interest), computed for every projected year, with an average DSCR row alongside.
- Ratio analysis: current ratio, quick ratio, gross profit percentage, net profit percentage, EBDIT margin, return on capital employed, return on equity, debt-equity, debt to total assets, interest coverage, proprietary ratio, solvency ratio, TOL to TNW, fixed asset coverage, debt to EBITDA and promoter contribution.
- Break-even: the sales value at which the unit covers its fixed and variable costs, as a value and a percentage of sales, with the margin of safety above it.
- Repayment: EMI or fixed-principal repayment, a moratorium if the term loan starts later, a repayment frequency of your choosing, and multiple term loans, each amortised on its own schedule.
- Subsidy: a capital subsidy entered as a flat amount or as a percentage of the loan, released upfront or after a delay, adjusting either the EMI or the tenure, plus interest subvention handled the same way.
- Working capital: the turnover method and MPBF working, so the borrowing proposed against the project can be checked the way a credit officer would.
- Seasonality: revenue and expense rows can be spread only over their active months instead of twelve, so a seasonal business does not show a flat monthly average it never earns.
How to set up a long-horizon project
- Create the project master: enter the firm and promoter profile, choose the report years to project, and tag the loan type as Mudra, PMEGP, Normal MSME or another scheme.
- Enter the project cost and means of finance: list cost lines such as land, building and plant and machinery, then fund them with own contribution, one or more term loans, the working capital loan and any subsidy.
- Enter revenue and expense assumptions: capacity, utilisation, selling price and direct and indirect expense rows for each year, month-wise and seasonal where needed.
- Review the statements the engine builds: profit and loss, projected balance sheet, cash flow, depreciation chart, EMI schedules, DSCR, ratio analysis, break-even, turnover method and MPBF all calculate from those inputs.
- Export the finished report: pick the sections to include, add the cover page, index and narrative, choose PDF, Word or Excel, and download.
Change an assumption and everything recalculates, so the long horizon stays internally consistent instead of being rebuilt by hand.
When a shorter horizon is enough
Not every file needs twenty-five years. A straightforward term loan for equipment may need only the loan tenure plus a couple of years. A longer horizon adds value when the asset life is long, when the project has phases, or when the bank wants to see the full repayment and post-repayment position.
The project master lets you choose the report years to project, so you are not forced to use the full twenty-five. Use the horizon that matches the asset and the loan, and document the basis for the choice.
CMA data alongside the project report
CMA data presents the borrower as a going concern and is usually shorter in span. When both are needed, Finxora lets the balance sheet figures seed the historical years of a CMA report or a project report directly, keeping the audited figures identical across documents and removing a full round of re-entry and the reconciliation differences it usually creates.
Before deciding, open the samples collection to see a finished project report in the order a bank expects to read it. Plans and pricing are on the project report pricing page. Our tools section lists free calculators you can use alongside.
Reviewing a long-horizon model
A long projection is only useful if it is reviewed critically. Check the early years against realistic capacity ramp-up, the middle years against market saturation, and the later years against asset replacement and maintenance costs. Verify that debt is fully repaid within the horizon and that the DSCR stays above the bank's comfort level in every year, not just on average.
Sensitivity analysis and break-even analysis for the projected years help test how much revenue is needed to cover fixed costs. If a small change in utilisation or price breaks the DSCR, the model needs stronger assumptions or a shorter loan tenure.
Common mistakes to avoid
- Using a twenty-five-year horizon when the asset and loan need only a few years.
- Projecting without documenting the assumptions behind growth, margins and utilisation.
- Ignoring seasonality, which flatters or depresses the monthly picture.
- Re-entering the same figures into separate documents instead of reusing them.
- Claiming outcomes the bank has not approved.
A long horizon is a tool, not a requirement. Match it to the asset, keep the assumptions defensible, and let the software keep the figures consistent.
