Financial Model Builder: Self-Service Cashflow Modeling

What FMB will be

The Financial Model Builder (FMB) is a Layer 3 tool on the EDMA roadmap. FMB is a self-service cashflow modeling environment for developers across all 12 protocol routes. The tool unifies the per-route economics work that developers currently piece together in spreadsheets.

Every route page on this site already includes the route's specific formulas (Saleable_t calculations, deductions and buffers, the 4% total fee structure, the seller-fee EDM-needed calculation, the admission-prefund formula). What FMB will do is consolidate those formulas into a single tool, pull live pricing from regional and registry feeds, run multi-scenario sensitivity analysis, and export reproducible dossiers.

FMB is also clearly roadmap status. The protocol pattern (locked inputs, route-specific math, reproducible outputs) applies; the specific UI, the pricing service integration, and the export formats are part of the design work for Phase 5 of the master plan (Weeks 14 to 20, target public launch August 1, 2026).

What problem FMB will solve

Developers on the EDMA platform today face a common workflow problem. A renewable-energy developer evaluating whether to enroll a project under Route 1 (compliance certificates), Route 2 (granular attributes plus flex), Route 4 (additionality carbon tonnes), or some combination needs to model each route's cashflow separately. Each route has its own pricing reality (regional REC prices vs voluntary attribute prices vs carbon tonne prices by methodology), its own deductions (uncertainty bands, permanence buffers, leakage budgets), and its own fee math.

Carbon-side developers face the same problem multiplied. An ARR project (Route 5) might also be a candidate for soils (Route 8) on adjacent fields, and the developer needs to model both lanes with route-specific accruals (2-8 tCO2/ha/yr for tropical ARR, 0.2-0.7 tCO2/ha/yr for practice-based SOC). Buffers differ (10-20% for forestry, higher for soils). Pricing differs ($20-60/t for high-integrity ARR, $10-30/t for SOC).

The current state: developers piece together spreadsheets per route, sometimes re-deriving formulas from the route docs, sometimes copy-pasting numbers from EDMA's published methodology references. The cashflow models are not reproducible across teams or across time (a developer who built the model six months ago can't easily re-run it against current pricing). FMB will fix this by being the single source of route-specific cashflow modeling on the platform.

FMB WORKFLOW · CONFIGURE TO EXPORT, ROADMAP STATUSFive stages from project configuration to dossier export. The Financial Model Builder is a Layer 3 tool on the EDMA roadmap. The workflow follows the EDMA pattern (locked inputs, route-specific math, reproducible outputs); the build is scheduled for Phase 5 of the master plan (Weeks 14 to 20).

S01CONFIGURE

Project parameters (roadmap)developer self-service inputs

EvidenceProject parameters are entered: jurisdiction, asset class (PV, BESS, HP, AD reactor, forest, etc), capacity or area, commissioning date, methodology preference, and the route or routes the developer wants to model. Multi-route portfolios are supported (a project might pursue Route 1 today and Route 4 later, or combine Route 5 ARR with Route 8 soils on different fields)

ActorDeveloper signs in to the tool; route selector populated from the protocol's current route registry; jurisdiction selector cross-references the live regulatory and registry availability

OutputConfigured project model ready for pricing and scenario inputs

S02PRICE

Pricing and fee structure (roadmap)live regional and registry feeds

EvidenceRegional and registry-specific pricing is pulled (REC and SREC prices by jurisdiction, voluntary carbon prices by methodology family, thermal-attribute prices by registry, avoided-diesel pricing bands). The 4% total fee structure is applied (2% seller in $EDM + 2% buyer with $EDM-discount option). The $0.50/EDM fee-denomination floor is the modelling baseline; live oracle prices are used when above the floor

ActorFMB internal pricing service pulls from the protocol's price-oracle feed and from publicly available registry rate cards; the developer can override with custom scenarios (downside, base, upside) where the live feed is illustrative

OutputPricing inputs locked into the project model; scenarios saved for later sensitivity analysis

S03COMPUTE

Route-specific math (roadmap)formulas from R1 through R11

EvidenceRoute-specific math runs: R1/R2: ETT to MWh aggregation, registry-native unit issuance, REC or GO pricing. R4: Saleable_t = MWh × EF_marginal × (1 − Losses) × (1 − Buffer). R5-R8 (carbon): Saleable_t = Area × Accrual × (1 − Deductions) × (1 − Buffer). R9 (diesel): fuel-based or kWh-based path. R10 (thermal): MWh_th × attribute price + thermal flex. R11 (methane): Flow, Biogas, or Rice path with rho_CH4 and GWP100. All routes apply the seller fee, EDM-needed-at-floor, net proceeds, and admission-prefund formula

ActorFMB compute service evaluates the formulas against the configured inputs and the locked pricing scenarios; results land in a project model object

OutputComputed cashflow projections per route, per scenario, with the full chain of deductions and fees broken out

S04REVIEW

Sensitivities and scenarios (roadmap)ranges, comparisons, exports

EvidenceSensitivity analysis is displayed: how the saleable tonnes shift if the deduction is 20% vs 25% vs 30%, how the net cashflow shifts across the three pricing scenarios (downside, base, upside), how the prefund changes with quarterly volume, how route selection affects total project NPV. Multi-route portfolio view shows the contribution of each route to total cashflow

ActorDeveloper reviews the model in the FMB UI; can adjust assumptions live and see the cashflows recompute

OutputReviewed cashflow projections ready for export

S05 · FINALEXPORT

Dossier output (roadmap)investor packs, lender decks, internal forecasts

EvidenceExport options are class-specific: Investor pack with executive summary, scenario comparison, sensitivity tables, and the route methodology references. Lender deck with cashflow waterfall, debt-service coverage projections under the three scenarios, and the protocol's audit-survivability discipline as the integrity story. Internal forecast with the raw cashflow tables for the developer's accounting system. All exports include the methodology version and the pricing scenario hash for reproducibility

ActorFMB export service generates the requested format (PDF, Excel, or JSON); the export references the locked methodology version and pricing scenarios so the model can be reproduced exactly later

OutputExported dossier in the developer's hands; the project model object remains in FMB for iteration and update as the project progresses

Five stages from project configuration to dossier export. Every stage uses forward-looking language because FMB is roadmap status. The workflow follows the EDMA pattern: locked inputs at S01 and S02, deterministic computation at S03, reviewable outputs at S04, reproducible export at S05 with the methodology version and pricing scenario hash recorded for later re-runs.

What FMB will compute

FMB will run the route-specific math that is already documented across the route pages on this site. The formulas are the same; FMB will execute them against the developer's configured inputs and the locked pricing scenarios.

Energy routes (R1, R2, R4). ETT aggregation from project capacity and capacity factor; Energy NFT aggregation from 100 ETT blocks; registry-native unit issuance with the regional pricing feed; the 4% fee structure with the EDM-needed-at-floor calculation; admission-prefund per the standard formula.

Carbon routes (R5-R8). Saleable_t = Area × Accrual × (1 − Deductions) × (1 − Buffer); voluntary market pricing by methodology family (CCP-eligible or otherwise); permanence-buffer reversal modeling over the crediting period.

Complex routes (R9-R11). Route-specific math: R9 fuel-based or kWh-based with 2.68 kg CO2/L diesel or 0.67-0.80 t/MWh EF; R10 thermal-attribute pricing in low-single-digit dollars per MWh-th plus thermal flex availability and event revenue; R11 methane sub-path math (Flow, Biogas, or Rice) with rho_CH4 = 0.000716 t/m3, GWP100 = 28, DE typically 98%.

R12 Tech Removals (roadmap-on-roadmap). FMB will support R12 once the route ships, with class-specific math for DAC, mineralization, enhanced weathering, and BECCS.

What FMB will export

Three export classes are designed:

Investor pack. Executive summary, scenario comparison (downside, base, upside), sensitivity tables, route methodology references, and the protocol's audit-survivability discipline as the integrity narrative. The pack format is investor-presentation ready (slide structure, executive-visible numbers).

Lender deck. Cashflow waterfall with the explicit chain of deductions and fees, debt-service coverage projections under the three pricing scenarios, sensitivity to key variables (capacity factor for energy projects, accrual rate for carbon projects, regional pricing assumptions), and the protocol's settlement record as the cash-flow timing reference. The deck is built for project-finance lenders who need to underwrite the cashflow.

Internal forecast. Raw cashflow tables in Excel, JSON, or CSV format for the developer's accounting system or business model. No formatting, no narrative; just the numbers with the methodology version and pricing scenario hash for reproducibility.

All exports include the locked inputs (project parameters, methodology version, pricing scenarios) and the computation timestamp, so the model can be reproduced exactly later. The FMB compute service is deterministic: same inputs and locked pricing produce the same outputs.

Where it stands

FMB is currently in design. The protocol-level architecture FMB depends on is mature: the PoV Gate produces the deterministic data foundation, the One-Claim Ledger enforces the discipline against double-counting (so the cashflow model can't accidentally count the same kWh or hectare twice), the Attestor Registry provides the pricing oracle integration points.

The FMB-specific build work scheduled for Phase 5 of the master plan (Weeks 14 to 20) covers four areas:

Pricing service integration. Live feeds from the major regional registries (PJM-EIS GATS for Mid-Atlantic SRECs, M-RETS for North American RECs and RTCs, the EU AIB hub for GOs, Verra VCS for voluntary carbon registry data) and from the EDMA marketplace itself (for CLE and external-registry-converted unit prices). Pricing snapshots are versioned for reproducibility.

Compute service. Route-specific formula execution as documented in the protocol specs; multi-scenario evaluation; sensitivity analysis with explicit ranges per variable; multi-route portfolio aggregation.

UI. Project configuration, scenario setup, review of computed cashflows with sensitivity sliders, export selection. Self-service for developers across the protocol's 12 routes.

Export pipeline. Investor-pack PDF generation, lender-deck PDF or PowerPoint, Excel and CSV and JSON formats for internal forecasts. All exports embed the methodology version, pricing scenario hash, and computation timestamp.

The companion tool on the master plan is the Presale Builder, also a Phase 5 deliverable, which serves the Launchpad surface rather than the route economics. FMB and the Presale Builder are independent tools that share the same protocol-level data foundation but serve different developer workflows.

For the protocol-level architecture FMB depends on, see Proof-of-Verification, One-Claim Ledger, and Attestor Registry. For the route economics FMB will consolidate, see the per-route pages under Energy Routes, Carbon Routes, and Complex Routes.