Flex›eSett's Swedish Role Through NC DR Implementation

eSett's Swedish Role Through NC DR Implementation

What happens to eSett — the Nordic imbalance settlement company — in Sweden between now and full NC DR implementation (~2031)? The short answer is that the question is mostly a non-event for eSett’s core and a genuinely open one for a thin slice at the edge. NC DR does not replace imbalance settlement; it builds a flexibility registration layer on top of it. The real uncertainty is what happens to eSett’s Sweden-specific functions as the DHV is built, and where the cross-BRP aggregation-compensation transfer ultimately settles. This page separates the certain from the contested and assigns probabilities.

eSett has three layers, with three different futures

LayerWhat it isExposure to the 2026–2031 changes
1 — Settlement backbone (ISR)Daily imbalance settlement, invoicing, collateral for every BRP/BSP; 15-min ISP since Mar 2025None. EU-mandated under EB GL; NC DR does not touch imbalance settlement
2 — Sweden-specific bolt-oneSett runs Sweden’s reconciliation/profiling because Sweden has no national datahubShrinks — migrates to DHV when DHV lands
3 — Aggregation-compensation settlementThe VoAA + Incentivizing Component machinery for cross-BRP independent-aggregation transfersThe open question

The single most important clarification: NC DR is not a threat to eSett’s core. NC DR’s deliverables — FIS, SPG qualification, baselines, register-once — are a registration and qualification layer owned by Svk/Ei/DHV, not a settlement layer. eSett is the settlement spine underneath all of it. Probability eSett remains Sweden’s ISR throughout this period and beyond: >95%. Sweden leaving the Nordic settlement model is a tail risk (~1–2%) — eSett is TSO-owned and the EU direction is harmonisation, not fragmentation. (Source - Nordic Imbalance Settlement Handbook v5.2 (2025), Source - EB GL (Regulation 2017-2195))

So “what will eSett’s role be” reduces to: what happens to layers 2 and 3 as DHV is built and NC DR lands.

Timeline

Now → ~2028 — unchanged backbone, marginal deepening

  • eSett keeps settling all Swedish BRP/BSP imbalances; Sweden still feeds it via Ediel (no national hub), and eSett still runs Swedish reconciliation itself.
  • ~2028: free-standing BSP arrives (the “+300 MW unlock”), activating eSett’s standalone Balancing Service Settlement Agreement — a real but modest deepening, not a new role. (Independent Aggregation in Sweden — The Implementation Gap)
  • Model 3 aggregation (multiple delivery points, ≥1 MW) is already settled through eSett’s ordinary imbalance settlement via the second BRP — eSett already settles the imbalance consequences of aggregation today. MARI (2027) and PICASSO (2027/28) add cross-border balancing-energy volume but do not change eSett’s function.

~2029–2031 — the inflection (conditional on DHV)

  • DHV proposal due 30 Sept 2026 → government decision likely not before 2027 → 4–6 year build → operational ~2029–2031. (Source - Ei Förslag Centralt Datahanteringsverktyg (2026))
  • When DHV lands it becomes Sweden’s MDA and takes over nätavräkning (grid settlement/reconciliation) — i.e. layer 2. eSett’s Sweden-specific reconciliation migrates to DHV, and Sweden normalises to the FI/NO/DK hub → eSett pattern. eSett’s Swedish footprint gets narrower and cleaner: pure ISR, fed by a hub like everywhere else.
  • DHV also produces the “centralized settlement basis for each flexibility delivery” → this is where Model 4 (korrigerad faktura) and the layer-3 fork are decided.

~2030–2032 — NC DR “fully implemented” (full FIS interoperability ≈ 4 years after entry into force, ~2030; realistically 2031–32). The end-state crystallises here. (Source - ACER Recommendation 01-2025 on NC DR)

The two uncertainties, as a decision tree

Q1 — Does DHV land by ~2031?

  • On time (~2029–31): ~55–60%
  • Slips past 2031: ~40–45%

Slippage is weighted heavily on the evidence: DHV is repeatedly flagged as the load-bearing constraint, the build is 4–6 years from a decision not before 2027, and the elmarknadshubb has a 2015 → 2020-pause → 2025-restart history — a 10-year governance gap. Betting against Swedish data-infrastructure timelines has been the correct base rate.

Q2 — If DHV lands, where does aggregation compensation settle?

  • Domestic route (korrigerad faktura, spotpris-based, DHV verifies volumes, “no money flows through Svk”): ~70% — this is Svk’s own stated Model-4 recommendation, and DHV is explicitly named in the government mandate as the compensation infrastructure. (Source - Svk Kompensationsmodell Delrapport 1 (2024), Source - Uppdrag Centralt Datahanteringsverktyg (2025))
  • eSett’s Nordic VoAA/IC route (route the cross-BRP transfer through eSett’s already-built compensation architecture): ~30% — the NBS Handbook already defines Compensation/VoAA/IC and says eSett is ready to settle these; building four national flex-settlement systems is wasteful, and the TSO owners can direct eSett to do it.

End-state scenarios at NC DR full implementation (~2031)

#ScenarioeSett’s roleProbability
ABackbone fed by DHV — DHV lands on time, absorbs reconciliation/MDA, aggregation compensation handled domestically (korrigerad faktura). eSett = clean ISR spine, fed by the hub.Narrows & standardises~40%
BNordic flexibility-settlement layer — DHV lands, but cross-BRP aggregation compensation is routed through eSett’s VoAA/IC. eSett becomes the Nordic settlement layer for independent aggregation, not just imbalance.Expands~20%
CStatus quo frozen — DHV slips past 2031. eSett unchanged from today: ISR fed via Ediel, still running Swedish reconciliation, aggregation stuck on Model 3 + BRP workarounds. NC DR’s settlement-dependent pieces (Model 4, sub-1 MW household flex) do not operate in the window.Unchanged~40%

(0.58 × 0.70 ≈ 40% A; 0.58 × 0.30 ≈ 18% ≈ 20% B; ~42% ≈ 40% C.)

Nuance that prevents over-reading B: eSett is never bypassed for the imbalance side — an aggregator activation always creates a BRP imbalance that eSett settles, in every scenario. The A-vs-B fork is narrowly about who runs the cross-BRP compensation transfer, not whether eSett is “in” flexibility (it already settles Model 3’s imbalance consequences). A realistic hybrid — eSett settles the imbalance leg while DHV verifies volumes and drives the korrigerad-faktura leg — sits inside scenario A and is arguably the single most likely concrete outcome.

Bottom line

  • Through ~2028: stable and lightly deepening (free-standing BSP settlement activates).
  • ~2029–2031, likely path (~60% combined A+B): eSett’s core is unchanged but its Swedish footprint shifts — it sheds the reconciliation bolt-on to DHV and is fed by a proper hub for the first time. Whether it also gains the flexibility-compensation layer (B) or that stays domestic (A) is the real open question.
  • ~40%: the build slips and eSett looks identical in 2032 to today.

The highest-information event to watch is the 30 September 2026 DHV architecture proposal — it should reveal whether the compensation money-flow runs domestically or through eSett, moving ~20 points of probability between A and B.

What this means for participants

  • Aggregators: eSett-level settlement is not your blocker today and won’t be — the constraints are national (the BSP “paper construction”, the missing DHV). Plan around the 2028 free-standing BSP and the ~2029–31 DHV window, not around eSett.
  • DSOs: the metering/reconciliation relationship you have (indirectly, via Ediel → eSett) is what DHV restructures; the imbalance-settlement layer above it is stable.
  • Platform/data businesses: the contested layer-3 settlement basis (volume verification for aggregation compensation) is a DHV-era opportunity, distinct from anything eSett does.

Data gaps

  • DHV architecture proposal (30 Sep 2026) — does it specify the aggregation-compensation money-flow route (domestic vs eSett VoAA/IC)?
  • How reconciliation/nätavräkning labour is divided between DHV and eSett once DHV is live
  • Any Nordic-level (TSO-owner) signal on whether eSett should operate flexibility-compensation settlement region-wide