Skip to content

    Sherpa is now Navorda. Read the announcement

    Navorda
    For CFO / Finance

    Bring governed project information into financial forecasts and capital decisions.

    Better financial decisions start with a clearer view of project reality.

    Connect milestones, permits, risks and project commitments to your financial forecasts. Anticipate capital requirements, understand financial exposure and make investment and financing decisions with greater confidence.

    Last updated

    Explore Navorda Finance
    The problem

    Your project moved. Did your financial forecast?

    A renewable energy developer can have carefully maintained financial forecasts and still lack a reliable connection between those forecasts and what is happening across its projects.

    Development teams maintain permits, milestones, land readiness, construction schedules and operational risks.

    Finance maintains cash forecasts, procurement commitments, funding requirements and investment models.

    Both teams may be doing their jobs correctly.

    But when a project milestone changes, its financial consequences do not necessarily travel with it.

    1. A permit slips.
    2. NtP moves.
    3. Equipment procurement is rescheduled.
    4. The funding requirement changes.

    And somebody must identify every affected assumption, contact the relevant teams and reconcile the financial forecast.

    By the time the information reaches the CFO, the business may already be operating from different versions of reality.

    The problem is not the financial model. It is the distance between the financial model and the project reality it represents.

    What changes with Navorda

    From operational changes to better-informed financial decisions.

    Six ways the same governed project reality supports Finance. Navorda provides the operational context; the forecast, the model and the decision stay with you.

    1. 01

      Forecast from project reality

      Understand the operational assumptions behind project costs, revenues, commitments and timing. Link financial context to the project record rather than relying exclusively on periodic status collection.

    2. 02

      Anticipate procurement commitments

      Connect procurement planning to project milestones and readiness. Understand how a delayed NtP or construction milestone may affect expected orders, procurement schedules and payments.

    3. 03

      Understand future capital requirements

      Make funding requirements easier to forecast from expected project progress. Support more informed capital-call planning and liquidity allocation across SPVs, countries and portfolios.

    4. 04

      Support financing readiness

      Bring permits, project milestones, land readiness, contractual commitments and change history into a traceable operational record that can support lender due diligence, financing conditions and drawdown preparation. The due diligence itself, and the lender's decision, stay with the parties who run them.

    5. 05

      Improve investment risk visibility

      Help Finance and investment teams understand which operational changes threaten forecast assumptions, delivery dates and capital efficiency. Maintain visibility of baselines, deviations and historical project decisions.

    6. 06

      Govern financial models without replacing Excel

      Keep sophisticated financial models in Excel. Link critical outputs to governed project information, retain provenance and version history, and see when model assumptions no longer match project reality.

      External Models Governance
    An illustrative example

    When NtP moves, see what moves with it.

    Initial assumptions

    • Expected NtP: January
    • Major procurement activity dependent on NtP
    • Equipment payment and funding requirements reflected in the financial forecast
    • Construction and COD assumptions used by Finance

    New situation

    NtP moves from January to April because a prerequisite has not been completed.

    Consequences requiring review

    1. Procurement ordering dates may change.
    2. Expected supplier payments may be rephased.
    3. Capital-call timing may need adjustment.
    4. Debt drawdown planning may need revision.
    5. COD and project return assumptions may need reassessment.

    Illustrative example. Notice to Proceed moves from January to April because a prerequisite has not been completed. In Navorda, the items linked to that milestone stay connected: the EPC payment forecast linked to NtP can follow it when its owner chooses; the Funding Status of the amount, from Forecast through Capital Call and Purchase Order to Payment, is tracked on the record; the risk recorded against the milestone carries its time-at-risk; the monthly close preserves the previous version read-only; and the financial model that still assumes NtP in January is flagged as outdated, with its outputs marked as possibly stale. Finance then reviews, in its own systems, the procurement ordering dates, the supplier payments to rephase, the capital-call timing, the debt drawdown planning and the COD and return assumptions. Navorda shows what is linked and what may be stale; the recalculations, the cash position and the lender reporting stay in the ERP, the treasury system and the financial model.

    Illustrative example.

    One operational change. Several financial consequences. One governed context to understand them.

    Your financial systems

    Keep your ERP. Keep your financial models. Connect them to execution.

    Navorda does not need to replace the financial tools your organization already uses.

    Accounting remains in the ERP. Treasury and payments remain in the systems responsible for them. Complex financial calculations remain in the specialist models Finance trusts.

    Navorda contributes the governed project and portfolio context that those systems need. It connects financial figures and assumptions to the operational events, dependencies, responsibilities and versions that give them meaning.

    When project reality changes, Finance can identify the assumptions and commitments that may require attention.

    Questions, not reports

    Questions Finance can answer with project context.

    The questions a finance team asks about a development portfolio are rarely accounting questions. They are questions about what the projects are going to do — and when.

    With milestones, permits, dependencies, risks, versions and the linked financial context on one governed record, those questions can be answered from the record instead of being rebuilt for every committee.

    Seven questions

    • Which projects are likely to require capital in the next two quarters?
    • Which permits or milestones are threatening our financial forecast?
    • What procurement commitments may move if NtP is delayed?
    • Which financial assumptions have changed since our last investment committee?
    • Which projects may need revised debt drawdown planning?
    • Which forecast changes come from project execution rather than financial modelling?
    • Which financial-model version supports the committed project IRR or CapEx?

    Target business questions, answered from the governed record and the linked finance and model outputs. Not every answer is natively calculated without configuration or integration.

    Frequently asked questions

    Bring governed project information into financial forecasts and capital decisions. Navorda connects governed project information with financial context, helping CFOs understand the operational events behind forecasts, procurement commitments, funding requirements and investment decisions. Your financial systems keep the numbers; Navorda keeps the operational reality behind them connected to the project, the milestone and the version that explain them — so Finance exercises its judgment on better information, not on a reconstructed status.

    No. Accounting remains in the ERP. Navorda provides project and portfolio financial governance connected to the operating model, complementing the ERP rather than replacing it. General ledger, invoicing, payments, tax, treasury and consolidation stay where they are; Navorda Finance records project-level forecasts, commitments and postings with their project context and exports the exact set for reconciliation.

    No. Complex models remain in Excel. Navorda can govern selected outputs, assumptions, workbook versions and links to project data without rebuilding the financial calculation engine. It reads results and flags when an assumption no longer matches the governed project; it never computes them.

    Navorda can improve the operational visibility supporting capital planning, lender due diligence and financing workflows: a Funding Status that follows an amount from Forecast through Capital Call to Payment, forecast dates linked to the milestones that drive them, versioned closes and a traceable record of permits, milestones and commitments. The extent of automation depends on the deployed modules, data, configuration and integrations. Lenders and financing counterparties retain their own approval processes.

    Navorda preserves governed project dates, dependencies, versions and related context. Where financial commitments and forecasts are linked through the appropriate capabilities, Finance can see which linked amounts and model assumptions the change touches, assess the consequences and update or rephase affected forecasts according to the configured workflow. Nothing is recalculated for you: the decision stays with Finance.

    One operational change. Several financial consequences. One governed context to understand them.

    Bring one project. Start from your reality.

    Take one representative project, its financial forecast and the operational assumptions behind it. Let's examine how changes move between Development and Finance — and where a governed operating model could reduce reconciliation effort and improve decision-making.

    Explore the platform