When the spreadsheet stops scaling: the operational wall every BRP and supplier eventually hits

Advisory · Energy Operations

Walk into the operations team of almost any Dutch energy supplier or BRP and you'll find the same thing. A folder somewhere, on a shared drive, with a workbook called something like settlement_april_FINAL_v3.xlsx. Inside it, hundreds of tabs. Months of patched formulas. Macros nobody fully remembers writing.

The work that workbook does is sophisticated. The tooling is not.

This is not a competence problem. The teams running these spreadsheets are some of the sharpest commercial and analytical people in European energy. The problem is that the work they're being asked to do has outgrown the tool they're being asked to do it with.

What's actually living in the spreadsheet

Most BRPs and suppliers we speak to have at least five operational workflows still running through Excel as the primary tool:

PPA portfolio settlement. Twelve monthly settlements, plus an ex-post correction once government data publishes. Each one matches fixed and dynamic price components against actual delivery, customer by customer, contract by contract.

Quarter-hourly residual pricing. When portfolio products combine fixed base load and peak load with spot residuals, every customer needs pricing built up at quarter-hour resolution. That's tens of thousands of price points per customer per year.

Imbalance cost allocation. Imbalance costs land at portfolio level. Allocating them back across customers fairly, reproducibly, and audit-ready usually means opening last month's workbook and editing it.

EDSN message reconciliation. End-of-supply notices, switching messages, metering updates. When XML tracking lives in an inbox plus a side sheet plus a status column someone updates by hand, errors compound silently and surface at month end.

Forecasting and allocation reconciliation. Forecast versus realised, allocation versus settled, week by week. The reconciliation logic is genuinely complex and almost always lives in formulas.

None of these workflows is unsophisticated. All of them are, at some level, simulations of operational software running inside a spreadsheet.

Why it worked, and why it's stopping

Excel earned its place in energy operations honestly. It's flexible, fast to iterate, and every analyst knows it. When portfolios were smaller and product mixes simpler, a smart team with a well-maintained workbook could run the entire operational layer without breaking stride.

Three things have changed.

Portfolios have grown. Customer counts that were manageable five years ago are now two or three times larger. The same workbook that handled 5,000 customers does not gracefully handle 50,000. Calculation times stretch. File sizes balloon. Recovery from a single broken formula costs hours.

Product complexity has multiplied. Hybrid PPAs, dynamic pricing, profile matching for production sites, capacity tariffs, time-of-use components. Each new product type is another layer of logic the workbook has to absorb. The result is workbooks where the original author left two years ago and nobody fully understands the macros anymore.

Audit and compliance pressure has intensified. Regulators, auditors, and customers all expect reproducible, traceable calculations. A spreadsheet where last month's tab is overwritten with this month's data, and where formulas reference cells that may have moved, is increasingly hard to defend.

The work hasn't gotten easier. The tool has stopped keeping up.

The signs the spreadsheet is breaking

You usually know before you admit it. The signs look like this:

The workbook takes longer to open every month. Recalculations that used to take seconds take minutes. The team has informal rules about who is allowed to touch which sheets. Settlement runs that used to finish on day three now spill into day five. Errors that used to surface immediately now surface a month later, in places nobody thought to check.

The most telling sign is a cultural one. The operations team starts treating the workbook with the kind of careful, anxious respect usually reserved for legacy systems on the verge of failing. People talk about it the way they'd talk about an old server in the basement that nobody wants to touch.

That's the moment. The spreadsheet hasn't broken yet. It's about to.

What replaces it (and what doesn't)

The instinct, when the spreadsheet starts failing, is to build something internal. A small data team. A bespoke tool. A custom calculation engine. Something the operations team owns and controls.

This works for some teams. It also fails for many. The reasons are predictable: the build takes longer than planned, the original engineers move on, the tool covers 70 percent of the workflows but never quite the last 30, and five years later the team is having the same conversation about the in-house system that they once had about the spreadsheet.

The teams that solve this durably tend to do something different. They separate the work into two categories.

Work that differentiates them commercially. Pricing models, hedging strategy, customer experience, trading logic. This stays in-house, owned by the team, refined as the competitive edge.

Work every BRP and supplier does in roughly the same shape. Settlement, allocation, market messaging, billing mechanics, reconciliation, imbalance handling. This gets delivered as a service, configured to the team's portfolio and product mix, but not rebuilt from scratch.

The split matters because it changes what the operations team spends its time on. In a spreadsheet model, most of the team's energy goes to running the calculation. In a service model, most of it goes to interpreting the result and acting on it. Same people, same expertise, fundamentally different leverage.

The cost of waiting 

Most teams know the spreadsheet is becoming a liability before they act on it. The reasons for waiting are understandable: replacing operational tooling is disruptive, the current setup is at least working, and the team has more pressing priorities.

The cost shows up later, and it's almost always larger than expected. Errors that compound silently for months become regulatory issues. Audit findings drag on for quarters. Settlement disputes with customers stretch out because the calculation can't be reproduced cleanly. New product launches get delayed because the operational layer can't absorb them.

The teams that move early aren't the ones with the worst spreadsheets. They're the ones who recognise that operational tooling has stopped being a back-office concern and started being a commercial constraint.

The work hasn't changed. The leverage has.

The work of running a Dutch BRP or supplier hasn't fundamentally changed. Settlement still has to settle. Allocation still has to allocate. Imbalance still has to be reconciled against published data.

What's changed is that this work no longer has to live in a spreadsheet, and the teams that recognise this earliest are the ones who get to spend their next five years on commercial growth rather than operational firefighting.

Eneve runs that operational layer. Settlement, allocation, billing, balancing, market messaging, reconciliation. The full Dutch operating system for energy retail, delivered as a service, so the spreadsheet can finally retire. 

Explore how Eneve works here.