Tolling agreement vs merchant BESS: who owns the upside, risk and dispatch?

Four common commercial structures

A toll is not inherently “better” than merchant operation. It can improve cash-flow visibility and financing while transferring upside. Merchant can retain value and strategic control while increasing volatility. The decision depends on price, tenor, counterparty, lender requirements and confidence in the project’s operating capability.

Map risk explicitly

• Market risk: prices, spreads, activation and product saturation.
• Volume/performance risk: whether the battery can deliver committed MW and MWh.
• Availability risk: outages, derates and maintenance.
• Degradation risk: who pays for accelerated wear or augmentation.
• Imbalance risk: deviations between position and metered delivery.
• Regulatory/access risk: rule, qualification or product change.
• Credit risk: ability of the floor provider or toller to pay over the term.
• Basis risk: mismatch between contract index/benchmark and realizable asset value.

“Guaranteed revenue” is incomplete language. Identify guarantor, conditions, security, exclusions, cure rights, cap, termination and how availability or force majeure changes payment.

Who controls dispatch—and within which envelope?

In many tolls, the toller obtains defined dispatch rights while the owner keeps the plant available. But the right is never physically unlimited. The agreement should align with OEM warranty, usable SOC window, power/ramp capability, grid connection, maintenance and safety controls.

Questions include: Is there an annual throughput or equivalent-full-cycle budget? Are high C-rate or deep cycles restricted? Who chooses recovery SOC after activation? What happens if the BMS derates? Does non-delivery reduce the toll, create liquidated damages or consume an availability allowance?

In a merchant or optimization agreement, the owner may approve strategy while an optimizer proposes trades and setpoints. Define whether the optimizer, trader, aggregator, EMS or owner has final authority at each stage.

Revenue certainty and bankability

Contracted cash flow may support debt sizing when lenders accept the counterparty, payment terms and operating obligations. It can also cap the owner’s exposure to favorable future volatility. Merchant models require more downside analysis and may support different leverage. Floors sit between these only if their conditions and provider credit are robust.

Compare structures using the same physical model. A toll price should be evaluated after required availability, degradation, augmentation, O&M and performance risk. Merchant value should be forecast-driven and include fees, imbalance and cannibalization—not a perfect-foresight backtest.

Data and control rights are economic terms

The party carrying risk needs timely data. Contracts should cover telemetry granularity, meter hierarchy, forecasts, orders, positions, commands, acknowledgements, alarms, maintenance, settlement and audit access. Define ownership and permitted use after termination.

Control needs an interface specification: authorized command source, validity, priority, local limits, acknowledgement and fallback. A toller may have commercial dispatch rights while the BMS, PCS, EMS and operator retain safety and grid authority. VoltMage can sit in the optimization and execution chain without changing those legal allocations.

Questions for the term sheet

• What exact payment is fixed, indexed, floored, shared or capped?
• Is “revenue” gross or net of energy purchases, fees, imbalance and taxes?
• Who controls bids, positions, SOC target and physical setpoint?
• What operating envelope and cycle budget does the toller receive?
• How are availability, degradation and augmentation measured and paid?
• Who carries market-rule, qualification and change-in-law risk?
• What telemetry, settlement and audit data can each party access?
• What happens on a failed command, BMS derate or communications loss?
• How do exclusivity, termination and handback affect future optionality?
• Which liabilities and remedies survive—and are they financeable?

Model at least merchant, contracted and hybrid cases under the same downside scenarios before selecting a structure. Then have qualified legal, tax and financing advisers negotiate the actual agreement.

Compare structures on like-for-like economics

For merchant operation, model net market revenue after energy purchases, losses, fees, imbalance, optimizer/trader cost, degradation and availability. For a toll, start with contracted payments, then deduct owner-retained O&M, augmentation, insurance, connection and performance exposure. For a floor, model the exact calculation period, carry-forward, cap and upside waterfall.

Do not compare a gross merchant backtest with a net toll payment. Use the same inflation, tax, financing, capacity fade and residual-value assumptions. Include counterparty default and early termination scenarios. A lower expected return with a narrow distribution may support cheaper debt; the financing effect belongs in the comparison.

Illustrative risk allocation

A toller requests aggressive cycling within a stated annual throughput allowance. The battery reaches the allowance earlier than forecast because balancing activation is high. The agreement must say whether the toller loses dispatch rights, pays an excess-use charge, funds augmentation or can continue within an OEM-approved higher limit. Without that provision, market upside becomes a degradation dispute.

Now assume the BMS derates power during heat. If the owner guaranteed availability but the toller selected the SOC and duty cycle, causation matters. Telemetry, commands, temperatures and alarm history become contract evidence. The operating platform should therefore preserve an immutable event chain.

Hybrid structures need physical partitioning

Allocating “50% merchant, 50% toll” is not simply two 5 MW virtual batteries. Both shares use common energy and SOC. Define whether rights are partitioned by MW, MWh, interval, product or revenue; establish priority during activation; and use one coordinator to prevent contradictory dispatch. The contract abstraction must be feasible on the physical plant.