Every euro, on the project it belongs to.
Development happens in days and euros. Navorda governs both.
Navorda Finance is the project and portfolio financial management add-on to Navorda Platform. It connects project costs, revenues, forecasts and financial commitments to the same projects, milestones, permits, versions and responsibilities used to manage development — so development schedule and development money operate from one model, while your ERP remains the accounting system of record.
Same project reality. More specialist depth: keep financial reality connected to project events.
Last updated
Sound familiar?
The project moved. The forecast didn't.
NtP slips three months, but the forecast payments tied to NtP keep their old dates until somebody finds and updates them by hand.
The spreadsheet knows the number, not why it exists
A forecast says €850,000 in June. It does not say the payment exists because NtP is expected in April — so when April moves, June stays.
Financial status disappears between systems
A cost moves from forecast to capital call, purchase order, goods receipt and payment — and that lifecycle is split across trackers, ERP records and email.
Development and finance should not be two versions of reality.
Development knows why the project changed. Finance knows what has been spent and what is forecast. Management receives two reporting processes and reconstructs the relationship between them by hand — usually after the date has already moved. The problem is not that finance lacks data. The problem is that project reality and financial reality live in systems that cannot reference each other, so every schedule change becomes a reconciliation exercise instead of a number.
One financial record. Connected to its context.
Every Finance entry in Navorda is a posting against a project: a finance figure, a ledger account, an amount and a date — with a counterpart, a comment, a source-system reference and the business fields your organization needs. It belongs to a Navorda version, like the milestones and permits beside it.
That is what makes the number explainable: the record carries the project it belongs to, the account it hits and the version it was reported in, instead of a cell reference.
Navorda does not replace the accounting entry in your ERP. It gives the amount its project context.
An illustrative Finance entry in Navorda: project Solar Alpha (48 MWp), finance figure CapEx EPC contract, ledger account 2310 Plant under construction, amount 850,000 euros dated 14 April 2028, counterpart EPC contractor, source-system reference ERP 4500123, business field Funding Status set to Forecast, recorded in the locked version Aug close.
Illustrative example.
When the project moves, the money can move with it.
A payment date is not always an independent date. Sometimes it exists because another project event happens first — an EPC payment due 30 days after NtP, a fee triggered by a permit. Navorda models that dependency instead of storing two unrelated dates: a financial amount can be linked to the milestone or permit that drives it.
Users decide whether the linked financial date should follow the milestone or remain fixed. When it follows, a schedule change reaches the forecast the moment it is recorded. When it is fixed, the link still shows what the amount depends on.
Two illustrative timelines. Baseline: NtP on 15 March 2028, with an EPC forecast payment of 850 thousand euros due 30 days later, on 14 April 2028. When NtP moves 60 days to 15 May 2028, the linked forecast payment moves with it to 14 June 2028. The link is user-controlled: the payment date can follow the milestone or stay fixed.
Illustrative example.
Follow money from forecast to payment.
Finance records carry configurable business fields, so a record can reflect the financial process your organization actually runs rather than a fixed workflow. Funding Status is one example: it can follow an amount from Forecast through Capital Call, Purchase Order and Goods Receipt to Payment.
The status is tracked on the record, beside the project and the milestone it depends on. Executing the payment itself stays in your ERP and banking stack.
Funding Status, a configurable business field, follows an amount through five example stages: Forecast, Capital call, Purchase order, Goods receipt and Payment. The status is tracked on the financial record; executing the payment stays in the ERP and the bank.
Everything you need
Every posting on the project it belongs to
Every financial record carries a project, a finance figure and a ledger account, so an amount is never a loose row in a tracker.
Your chart of accounts, not ours
A configurable seven-level ledger-account hierarchy, from root accounts to leaves, with source-system IDs and reporting tags.
Your finance structure and budget codes
Organize finance figures through a configurable three-level hierarchy — income, costs, CapEx or the structure your organization uses — with budget codes.
Forecasts that follow the schedule when you choose
Link amounts to milestones or permits and decide whether their dates follow project schedule changes.
A lifecycle that matches your process
Add business fields such as Funding Status and follow amounts through the stages your organization actually uses.
Monthly closes that keep the money with the project
Postings belong to Navorda versions. Locked versions are read-only, so a close preserves financial and project reality together.
Filter the portfolio, total exactly what you selected
Filter by project, figure, ledger account, counterpart, date or amount and read the total of the selected set.
Finance inside every project
Each project has its own Finance view, using the same records as the portfolio-level ledger.
Fast entry with guardrails
Create and edit records quickly while accounts, figures, archived projects and locked versions stay protected.
Export the exact set for reconciliation
Excel export of the selected records, including finance hierarchy and ledger-account paths, for reconciliation with the ERP.
Financial access that does not have to match project access
Independent view, edit and export permissions for Finance, so financial access is granted on its own terms.
Counterparts and references you already use
Postings reuse the counterpart records your land contracts, SPAs and offtake agreements use, and carry the source-system ID that ties them back to the ERP.
Close the money with the project.
Navorda already preserves development reality through versions and approved reporting periods. Finance participates in the same model: when a reporting version closes, financial postings are preserved beside the milestones, permits, risks and project figures management saw at that point in time.
A locked version cannot silently change later.
Project history and financial history remain explainable together.
Navorda reporting versions: June close, July close and August close are locked and read-only; the working draft is the open version where the current month moves.
What teams can now answer
- How much has been spent and forecast on Project Alpha — by finance figure and by ledger account?
- What happens to the payment forecast if NtP moves by three months?
- Which forecast payments are linked to milestones that currently carry an open risk?
- How much of next quarter's forecast is still at Forecast, versus Purchase Order or Payment?
- Which counterparties account for the largest forecast commitments?
- What did the financial forecast look like at the previous monthly close?
- Can Finance export the exact filtered project set for reconciliation with the ERP?
How it works
Set up your structure
Configure finance figures, ledger accounts and budget codes, and add the business fields your process uses, such as Funding Status.
Post against projects
Record costs, revenues, forecasts and commitments per project, with counterpart and source-system references where relevant, and link amounts to the milestones or permits that drive them.
Close and reconcile
Close reporting versions so money and milestones are preserved together, then filter, total and export the exact set the ERP reconciliation needs.
Works seamlessly with the rest of Navorda
Navorda Finance complements your ERP and finance stack — SAP, IFS or whichever system holds the ledger. It governs project-level financial context — costs, revenues, forecasts and commitments against projects, milestones, permits and versions — while accounting, invoicing, payments, tax, treasury, consolidation and statutory reporting stay where they already work.
Built on the same operating model
Navorda Platform governs what the project is expected to achieve and when. Navorda Finance connects the money to those same commitments — same project, same milestones, same reporting versions.
Platform governs project reality. Navorda Finance connects the money to that reality.
Navorda Platform governs: Project, then Permit, then Milestone, then Risk. Navorda Finance connects: Forecast, then Commitment, then PO, then Payment. NtP moves → the milestone changes in Navorda Platform → the forecast payment linked to NtP can move with it, on the same project and the same version.
Navorda Finance complements your ERP. It does not replace it.
Two different questions, two different systems. Navorda answers which project an amount belongs to and what has to happen for it to move. The ERP keeps the books.
Navorda Finance governs
- Project-level costs and revenues
- Development financial forecasts
- Financial commitments
- Connection to projects
- Connection to milestones and permits
- Finance figures and budget codes
- Project-linked chart-of-account references
- Counterpart relationships
- Financial lifecycle and status
- Versioned project-financial snapshots
- Project and portfolio filtering
- Governed export and integration context
ERP and finance systems continue to govern
- General ledger accounting
- Accounts payable and receivable
- Invoicing
- Actual bank payments
- Tax
- Treasury
- Statutory accounting
- Financial consolidation
- Corporate P&L
- Balance sheet
- Cash-flow statements
- Formal FP&A where performed elsewhere
The ERP records the accounting truth. Navorda connects financial reality to the project reality that explains it.
Frequently asked questions
Your project schedule already explains when money should move.
Put both in the same governed operating model.