Demand for CAEs arises from energy-saving obligations, but no single number describes it. Obligated parties may use certificates, financial contributions to the FNEE and other routes permitted by the applicable rules. The published financial-equivalence rate supports regulatory compliance; it is neither a sale price nor a market quotation.
Where regulated demand comes from
Regulated demand begins with the annual energy-saving obligation allocated to each obligated party, not with a forecast of projects offered for sale. The annual order, the underlying national obligations framework and any current implementation rules establish the compliance perimeter and dates. A portfolio team should record the obligation in the prescribed energy unit, the period to which it belongs and the entity that bears it. Group estimates or press summaries cannot replace the individual figure used for compliance.
An obligated party may compare the permitted compliance routes, including obtaining valid CAEs and making the financial contribution to the FNEE, subject to the rules in force for that year. This creates potential demand for certificates, but it does not mean every unit of obligation will be purchased as a CAE. Internal demand estimates should therefore show route allocation, certificates already held, expected submissions, contingency capacity and the deadline by which each choice must become operational.
Separate CAEs, FNEE and equivalence
The financial-equivalence amount published for regulatory compliance gives a monetary reference for the relevant FNEE contribution. It is not an official CAE sale price, a mandatory offer to project owners or evidence of a market-wide quotation. A bilateral contract price reflects its own volume, maturity, documentation, timing, allocation of risk and bargaining conditions. Broader market conditions are a third concept and cannot be inferred reliably from one contract or from the regulated equivalence alone.
A useful compliance model starts with the confirmed obligation and deducts only CAEs that are valid, available to the correct party and usable within the applicable period. Candidate dossiers belong in a separate pipeline, weighted by their actual stage rather than counted as issued certificates. The model can then compare a conservative certificate case, a mixed-route case and a contribution-led fallback. These are planning scenarios, not predictions that an authority will recognise a stated volume.
Build a compliance scenario
Timing can be as important as nominal volume. Technical completion, document collection, verification, administrative processing and registry availability may all sit between a project estimate and usable CAEs. The team should map latest responsible dates backwards from the compliance deadline and apply buffers supported by its experience, without presenting those buffers as official service levels. A late dossier may still have technical merit while being unsuitable for the obligation currently under management.
Procurement decisions should identify the precise product and status being acquired. Terms need to say whether the subject is an existing certificate, rights over future savings or a conditional transfer linked to successful recognition. Quantity definitions, delivery evidence, long-stop dates, substitution rights and consequences of reduction or rejection should align. Paying an advance or signing exclusivity cannot turn estimated savings into issued CAEs or override the public rules governing compliance.
Contract without inventing an official price
The portfolio register should reconcile certificates by origin, holder, status, intended compliance year and any prior commitment. Separate controls are needed for duplicate allocation, affiliated entities and transfers still awaiting completion. Reconciliation with official records matters more than a spreadsheet label. Where information remains uncertain, the volume should be flagged rather than silently included. This preserves a credible view of uncovered obligation and prevents a commercial pipeline from being mistaken for regulatory fulfilment.
Sensitivity analysis should focus on variables that genuinely change the route decision: recognised volume, processing time, transaction costs, verification expense, contribution equivalence and contractual payment terms. It should not manufacture a single break-even price described as the market price. Tax, finance and accounting treatment may also differ between a FNEE contribution and acquisition under a private agreement, so the relevant specialists should confirm treatment for the entity and period concerned.
Refresh the decision with current data
Governance works best when the obligation owner, technical dossier team, procurement function, legal reviewers and treasury use one dated decision pack. The pack should identify official sources, current assumptions, committed CAEs, conditional pipeline, contribution fallback and unresolved legal or operational questions. Approval thresholds can respond to exposure and maturity. Any update to the annual order, a dossier or a contract should trigger a controlled refresh rather than an undocumented overwrite of the original case.
The final choice remains conditional until the compliance route has been completed and recorded as required. A prudent plan maintains alternatives and avoids promising that a particular project, seller or timetable will satisfy the obligation. CAEs may reduce the portion met through a FNEE contribution when the applicable framework allows and the certificates are successfully recognised and available. Neither that possibility nor the published equivalence guarantees issuance, delivery, remuneration or a particular commercial outcome.