Storage (BESS) Contracts: What Business Owners Need to Know
By Clarence Tan
Rising electricity costs and decarbonisation pressures are pushing many commercial and industrial businesses in Singapore to look more closely at on-site energy solutions. Battery energy storage systems (BESS) offered on an Energy-as-a-Service (EaaS) model can appear to solve several problems at once – reducing peak-demand charges, avoiding upfront capital expenditure, and outsourcing operational risk to a specialist developer. But the Energy Services Agreement (ESA) that underpins an EaaS arrangement is a long-term, multi-layered contract, and its detailed terms will determine whether the project delivers the expected benefits over time.
1. Introduction: Why BESS EaaS Is on the Agenda
(a) Battery energy storage systems – commonly known as BESS – are increasingly being installed at commercial and industrial premises across Singapore, particularly at sites with significant peak-demand profiles such as manufacturing plants, data centres and logistics hubs.
(b) Under the Singapore Green Plan 2030, the government has been actively encouraging more efficient and sustainable energy use, and the Energy Market Authority (EMA) has introduced regulatory pathways that make BESS deployments more commercially viable than in the past.
(c) Against this backdrop, many site owners are being approached by energy developers offering to install a battery system at no upfront cost, in exchange for a long-term contract under which the developer shares in the electricity cost savings that the system generates.
(d) This model – often described as Energy-as-a-Service, or EaaS – can be attractive: lower electricity costs, no capital expenditure, and a developer that takes on the technical and operational risk of owning and operating the BESS.
(e) However, the contract that governs the arrangement – usually called an Energy Services Agreement, or ESA – is not a simple services contract; it is a long-term commitment that combines elements of property, performance and financing, and the commercial implications of those elements deserve careful scrutiny before signing.
(f) This article highlights key issues that business owners may wish to consider when reviewing a BESS EaaS agreement; it is intended to help you ask more focused questions of the developer and your advisers, and to understand how the contract will operate over its life.
2. What You Are Actually Signing: Land, Performance and Upside
(a) An EaaS agreement for BESS installations typically bundles three distinct arrangements into a single document: a licence relating to the land and premises, a performance commitment, and a mechanism for sharing upside.
(b)Land – The site licence governs how the developer may install, access and operate the BESS on your premises; it determines who owns the equipment, what third-party consents are needed (for example from a landlord or mortgagee), and what reinstatement obligations apply at the end of the term.
(c)Performance – The performance commitment is the heart of the commercial deal; it defines the minimum level of savings or performance that the developer is contractually obliged to deliver, and sets the baseline against which under-performance is measured.
(d)Upside – The upside-sharing mechanism determines how financial benefits above the guaranteed level are allocated, including whether any additional savings or ancillary revenues (such as grid-programme participation) are shared with you or retained by the developer.
(e) Many ESAs are drafted primarily from the developer's perspective, which is understandable given that the developer is often using the contract to support project financing; however, this means that the allocation of rights and obligations around land, performance and upside warrants close attention from the site owner's perspective.
(f) When reading an ESA, it can be helpful to keep this "land, performance, upside" framework in mind and ask, for each provision, which of the three it affects and whether that aligns with your commercial expectations.
3. Understanding Your Guaranteed Saving – Fixed Amount or Floor?
(a) One of the most important concepts in any BESS EaaS agreement is the "guaranteed saving" – the minimum reduction in electricity costs that you are promised under the contract.
(b) In many structures, the developer offers a fixed guaranteed saving, typically expressed as a defined reduction in your electricity charges per month or per year, and retains all savings generated by the BESS in excess of that amount as its upside.
(c) By contrast, some agreements describe the site owner's entitlement as a "floor", suggesting that the site owner will receive at least a certain level of savings, with the possibility of more if the system outperforms; this can be attractive in principle but may not align with the developer's financing or revenue model.
(d) A simple example illustrates why the language matters: if the ESA states that you are entitled to a "floor" saving of, say, 100 units, and the BESS ultimately delivers 140 units, you may reasonably view the additional 40 units as something to be shared, whereas the developer may have modelled those 40 units as its exclusive upside.
(e) This type of ambiguity can be fertile ground for disputes, particularly if the project performs better than expected and stakeholders have differing views on whether and how the additional value should be shared.
(f) Before signing, it is prudent to confirm exactly how your guaranteed saving is defined – as a fixed amount with no sharing above that level, as a floor with sharing of uplift, or in some other way – and to ensure that the drafting of the ESA clearly reflects the commercial understanding.
4. The Administrative Steps That Actually Unlock Your Savings
(a) A point that often surprises site owners is that achieving the projected savings from a BESS EaaS arrangement may depend not only on the system's technical performance but also on administrative steps that the site owner must take with the network operator or the retailer.
(b) One of the most commercially significant of these steps is the need, in many cases, to apply to reduce your contracted or registered demand level with Singapore's network operator once the BESS has demonstrated that it can reliably keep your actual demand below a certain threshold.
(c) This matters because maximum demand charges – a major component of many large-site electricity bills – are often calculated with reference to the registered demand level; if this level is not reduced when the BESS begins to perform, the technical benefit of peak shaving may not translate into a corresponding tariff reduction.
(d) If the ESA does not set out a clear obligation and process for you to make the necessary application, the developer may in fact deliver the physical performance it has promised, yet the full saving may never materialise because the administrative step to "unlock" the tariff benefit has not been taken.
(e) It is therefore useful to check whether the ESA specifies when the reduction application should be made, who within your organisation is responsible for it, what information the developer must provide to support it, and what happens if it is delayed or not made at all.
(f) These provisions sit at the intersection of legal, technical and internal governance issues, and it may be helpful to involve your facilities, finance and procurement teams in confirming that the proposed process is workable in practice.
5. When the System Fails Permanently – Rights, Remedies and Exit
(a) Most EaaS agreements include a performance guarantee under which the developer must pay the guaranteed saving even if the BESS underperforms against the agreed metrics, which is an important feature of the model from the site owner's perspective.
(b) A more challenging scenario arises if the BESS suffers a catastrophic failure – for example, a major battery defect or fire – and cannot realistically be repaired or economically replaced, so that the system is no longer capable of delivering any savings.
(c) In some ESAs, the developer's obligation to pay the guaranteed saving continues for the full remaining term even in a total-failure scenario, which may appear to provide strong protection but raises practical questions about whether the developer can in fact sustain those payments without operating revenue from the system.
(d) An alternative approach, seen in more robust structures, is to give the developer a clearly defined right to exit the agreement in a genuine permanent-failure scenario in exchange for a pre-agreed compensation payment, such as a lump sum designed to approximate the economic value of the remaining term.
(e) A simple way to think about this is to compare two outcomes: in one, the developer remains formally bound to pay annual guarantees for several years without a functioning asset; in the other, the contract provides for a one-off compensation amount and an orderly de-installation of the BESS, allowing both parties to move on with clarity.
(f) When reviewing an ESA, it is therefore useful to ask how "permanent system failure" is defined, what evidence is required, what rights each party has in that scenario, and whether the compensation or exit mechanism is clearly specified and commercially acceptable.
6. Grid Programmes and Peak-Shaving Priorities
(a) Some BESS developers register their installations under EMA's Demand Response or other grid support programmes, enabling the battery to earn additional revenue by responding to signals from the national grid; this secondary revenue stream can improve project economics but introduces potential conflicts of priority.
(b) The primary reason the BESS is at your site is usually to manage your peak demand and reduce your electricity bills, whereas grid programmes may require the battery to charge or discharge at times that are driven by system-wide needs rather than your site's profile.
(c) Consider a simple scenario: your site's demand is approaching its threshold on a hot weekday afternoon just as a grid dispatch signal is issued; if the BESS responds to the grid call in a way that leaves less capacity available to shave your peak, the result could be a missed saving or even a higher demand charge than without the BESS.
(d) To manage this risk, the ESA should clearly state that managing your peak demand takes priority over participation in grid programmes, and should address how guaranteed savings are treated if a grid dispatch event causes the system to miss a peak-shaving window.
(e) The agreement should also specify who bears the cost if the BESS needs to recharge from your supply after responding to a grid call, and how the rules in the legal document align with the technical operating protocols agreed between you and the developer.
(f) If the developer intends to participate in demand response or similar programmes, it is prudent to review both the ESA and any operating procedures to ensure that the allocation of priority, cost and risk is clearly documented and understood.
7. When the Developer Raises Project Finance
(a) Many BESS developers do not fund projects entirely from their own balance sheets; instead, they raise project financing, often on a limited-recourse basis, secured against the BESS assets and the revenue stream under the ESA.
(b) Because your ESA is the primary revenue contract, lenders will scrutinise it closely and may require additional provisions that go beyond what would appear in a straightforward services agreement.
(c) Common lender-driven requirements include step-in rights that allow the lender or a replacement operator to take over the developer's obligations if the developer defaults, rights to assign the ESA as security, and a separate direct agreement under which you acknowledge the lender's interests and agree to certain notices and cure periods.
(d) These features are standard in project-financed transactions and are not, in themselves, unfavourable to the site owner; they are often what allows the developer to secure long-term, non-recourse funding and proceed with the project in the first place.
(e) However, they do affect who you may ultimately be dealing with if the developer runs into difficulty, and they may impose additional obligations – such as signing direct agreements or consent letters – that should ideally be anticipated and agreed at the term-sheet stage.
(f) If a developer indicates that project finance will be used, it can be helpful to request an outline of the expected lender requirements early in the process, so that these can be factored into internal approvals and negotiations around the ESA.
8. How Your Savings Are Calculated – Why Definitions Matter
(a) The payment mechanics in an EaaS agreement – the formulae that determine how your guaranteed saving is calculated, measured and verified – are often set out in a technical schedule at the back of the contract, and it is tempting to treat these as boilerplate; in practice, they are central to the commercial outcome.
(b) Typically, the calculation relies on a series of defined terms, such as your actual peak demand, your baseline demand (what your demand would have been without the BESS), and the difference between them, and on how these values are measured using specific meters over defined time intervals.
(c) Inconsistencies – for example, where one variable is measured in half-hourly intervals and another is based on monthly averages, or where different meters are used for different purposes without clear tie-breakers – can produce calculated savings that do not reflect either party's expectations.
(d) Where a site has multiple meters, which is common in BESS installations, the ESA should specify which meter governs each calculation, how discrepancies between meters are resolved, and how data is accessed and shared.
(e) It is often worthwhile to have the measurement and verification methodology reviewed alongside the main payment provisions, ideally by advisers who can reconcile the legal drafting with the technical model and ensure that the two are aligned.
(f) This is a technical exercise, but the stakes are commercial, because over the life of a long-term ESA, small definitional asymmetries can translate into meaningful differences in the savings you actually receive.
9. Questions to Ask Before You Sign
The following questions are intended as a practical checklist when reviewing a BESS EaaS agreement; they do not replace legal advice but are designed to help you engage more effectively with your advisers and with the developer.
(a)Guaranteed saving – What exactly am I guaranteed? Is my saving described as a fixed amount or a floor, and does the drafting clearly reflect the commercial understanding between me and the developer?
(b)Your obligations – Beyond paying invoices, what are my ongoing obligations? Am I required to apply to reduce contracted capacity or take other steps with the network operator or retailer, when is this triggered, and what happens if I do not comply?
(c)System failure – How does the contract deal with permanent system failure? How is "permanent" or "total" failure defined, what compensation or exit mechanism applies, and is it clear and workable in practice?
(d)Grid programmes – Does the developer intend to participate in demand response or other grid programmes, and if so, does the ESA clearly state that managing my peak demand takes priority and explain who bears any costs if grid dispatch events affect my savings?
(e)Financing and counterparties – Is the developer raising project finance, and will I be asked to sign direct agreements or consent letters with lenders? If so, on what broad terms and at what stage in the process?
(f)Measurement methodology – How is my saving calculated in practice? Are the defined terms and formulas in the technical schedules consistent with the commercial provisions in the main contract, and have they been tested against realistic operating scenarios?
(g)End-of-term outcomes – What happens at the end of the ESA term? Who owns the BESS equipment, what reinstatement obligations apply to the site, and who bears the cost of removal and reinstatement?
(h)Landlord and security interests – If I am a tenant or if the property is mortgaged, what consents or acknowledgments are required from the landlord or mortgagee, and how are these reflected in the ESA and related documents?
10. Practical Considerations and Next Steps
(a) A BESS EaaS arrangement can be a genuinely attractive proposition for business owners in Singapore, offering potential reductions in electricity costs without upfront capital outlay and with operational risk borne by a specialist developer.
(b) At the same time, the ESA governing the arrangement is a long-term, multi-party contract whose detailed terms will shape your rights and obligations for years, and the issues highlighted above are not theoretical but arise regularly in practice.
(c) Many of these points – particularly around guaranteed savings, grid-programme priorities, landlord and lender requirements, and measurement methodologies – are considerably easier to address before the agreement is signed than after the BESS has been installed and the project has been financed.
(d) For that reason, site owners may find it useful to seek advice at an early stage, including when heads of terms are being discussed or before lender requirements are finalised, so that there is more room to align the commercial and legal structure with their operational needs.
(e) Clarence & Co LLC regularly advises on BESS transactions and related energy-infrastructure projects in Singapore, including landlord consent processes, project-finance structures and regulatory engagement with EMA and other stakeholders, and is available to assist businesses considering or negotiating BESS EaaS arrangements.
This article is intended for general informational purposes only and does not constitute legal advice. Readers should seek professional legal advice in respect of their specific circumstances.
© 2026 Clarence & Co LLC. All rights reserved.
