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–2032)? 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 — all percentages on this page are the wiki’s own judgement, not figures from any source.

eSett has three layers, with three different futures

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%, wiki judgement) — eSett is owned by the Nordic TSOs 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–2029: 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; Svk delegates BSP settlement to eSett, Source - Svk BSP Avtal 5937-2 (2025))
• 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.

~2030–2035 — the inflection (conditional on DHV; the date moves with the start and the reuse choice)

• Ei and Svk’s September 2026 report (Ei R2026:08) gives an indicative schedule in months from the start of implementation, not calendar dates: first go-live in months 36–42 if the old Elmarknadshubb material is reused, 90–96 if the solution is built from scratch (procured or in-house). The government has not yet decided or set a start. On the wiki’s own arithmetic a 2027 start means ~2030–2031 (reuse) or ~2034–2035 (from scratch). (Source - Ei R2026-08 Förslag Centralt Datahanteringsverktyg (2026))
• When DHV lands it takes over nätavräkning (grid settlement/reconciliation), in effect becoming Sweden’s MDA (the wiki’s reading of DHV’s role) — 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, Source - NC DR Amended Text (ACER Recommendation 01-2025 Annex 1))

The two uncertainties, as a decision tree

Q1 — Is DHV operational by end-2032 (the end of the realistic NC DR full-implementation window)? Probabilities below are the wiki’s own; the structure follows the report’s schedule, which runs in months from a start that has no date. Three things decide it:

• Start by end-2028: ~75%. A government decision and the set-up of the Svk subsidiary come first; no source gives a date.
• Reuse-based development (the report’s option A): ~75%. The report says a substantial element of reuse is both possible and appropriate whichever route is chosen; from-scratch builds (options B1, B2) cannot be operational before ~2034 even on a 2027 start.
• Plan holds within about two years of slack, given both: ~70%. The report itself lists regulatory decisions, market actors’ readiness, IT complexity and staffing as external dependencies, and the elmarknadshubb has a 2015 → 2020-pause → 2025-restart history, so betting against Swedish data-infrastructure timelines has been the correct base rate.

Combined: 0.75 × 0.75 × 0.70 ≈ 39%, so ~40% operational by end-2032 and ~60% not.

Q2 — If DHV is operational, 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 Compensation route (route the cross-BRP transfer through eSett’s already-built, day-ahead-priced Compensation mechanism): ~30% — the NBS Handbook already defines Compensation as a settled financial transaction and says eSett is ready to settle these; building four national flex-settlement systems is wasteful, and the TSO owners could in principle direct eSett to do it (the wiki’s inference; no source states this is planned).

End-state scenarios at NC DR full implementation (by end-2032)

(Wiki-derived arithmetic: 0.39 × 0.70 ≈ 27% ≈ 30% A; 0.39 × 0.30 ≈ 12% ≈ 10% B; 0.61 ≈ 60% C. The bars are drawn at 5 px per percentage point.)

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–2029: stable and lightly deepening (free-standing BSP settlement activates).
• By end-2032, ~40% 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.
• ~60%: DHV is not operational by end-2032 (a late start, or the from-scratch path, which cannot land before ~2034) and eSett looks much as it does today.

The highest-information events to watch are (1) the government’s decision on the September 2026 DHV proposal (Ei R2026:08) — the start date and the reuse-versus-scratch choice move Q1 from near 0% (from scratch) to roughly 50–70% (reuse, early start) — and (2) any statement on where aggregation compensation settles, which would move ~20 points between A and B. The report provides verified flexibility volumes for imbalance adjustment and supplier compensation basis but leaves financial settlement outside the tool.

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–2029 free-standing BSP and a DHV window that opens ~2030–2031 at the earliest (later without reuse), 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

• Government decision on the September 2026 DHV proposal: start date, reuse-versus-scratch choice, and whether it fixes the aggregation-compensation money-flow route (domestic vs eSett’s Compensation mechanism); Ei R2026:08 leaves financial settlement outside the tool
• 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

Related pages

• eSett — the entity page (ownership, NBS model, roles)
• Independent Aggregation in Sweden — The Implementation Gap — the Model 3/4 compensation architecture; the “paper construction”; DHV as critical dependency
• Elmarknadshubb — DHV/FIS; why Sweden lacks a hub; nätavräkning migration
• Balancing Markets / BSP and BRP Roles — the settlement context
• The Regulatory Architecture for Swedish Flexibility 2026–2028 — DHV as the system-wide critical path
• Network Code on Demand Response — FIS/SPG as the registration layer distinct from settlement