BESS EPC and supply contracts: interfaces, acceptance and remedies
Allocate BESS battery, PCS, EMS and grid interfaces, distinguish FAT/SAT from market tests, and link acceptance evidence to warranties and practical remedies.
Jurisdiction: Ukraine. Sources reviewed . Periodic review required. Next scheduled editorial review: . Material rule changes require earlier review.
A battery supply contract can be performed while the complete project still fails to deliver its investment case. The gap often sits between cells, power conversion, controls, civil works, grid interfaces and the operating obligations assumed by the financial model. An acquisition review should therefore reconcile scope, test criteria and remedies across the whole contract package.
For a Ukrainian BESS, classify the relevant supply, works and construction relationships with counsel before applying a statutory rule to the entire package. Legal sources were checked through Mitralex on 31 October 2026. The proposed matrices below are diligence tools, not a standard EPC form or an engineering test specification.
Draw the responsibility boundary before comparing the price
Identify the party responsible for design integration, installation, software, communications, metering, grid compliance and the interfaces between them. "Turnkey" in a presentation is not enough: inspect definitions, exclusions, employer-supplied items and contract precedence. A separately priced external transformer or operator work package can remain critical to completion even where battery equipment is fully paid.
Table — scroll horizontally if needed
| Interface | Evidence to reconcile | Question that should have one accountable answer |
|---|---|---|
| Battery / power conversion | Compatible specifications, conditions, protections and performance boundaries | Who resolves a mismatch between component capability and system output? |
| PCS / EMS / dispatch | Control philosophy, software rights, communications and response requirements | Who demonstrates the intended operating mode end to end? |
| Equipment / civil works | Layout, foundations, safety design and installation conditions | Who bears redesign, rework and schedule consequences? |
| Plant / grid | Actual directional limits, protection and metering requirements | Who delivers each interface and which operator action remains external? |
| Completion / operation | Manuals, training, data access, spares and service handover | Can the owner operate and evidence compliance after the contractor leaves? |
| Existing solar / new BESS | Shared assets, dispatch priority and affected warranties | Who proves that one component does not undermine the other? |
Document any responsibility shared between contracts, the decision process and the commercial consequence of disagreement. An integration obligation should not disappear because two suppliers each satisfy a narrower component specification.
Separate factory tests, site tests and market qualification
Define what each test proves. A factory acceptance test (FAT) examines the contracted equipment/configuration before the relevant shipment or release. A site acceptance test (SAT) examines the installed system against the agreed site criteria. Commissioning and performance tests address defined operating conditions and interfaces. The exact sequence, safety prerequisites and witnessing need an engineer-approved plan; the labels alone do not establish a legal or technical standard.
Market-service qualification is a separate workstream under the applicable rules and TSO process. A factory report does not automatically qualify the plant for ancillary services, and a successful market test does not by itself settle every obligation under the EPC contract. Align the contractor's deliverables with the evidence needed for the actual revenue route without promising an award or market income.
For a relationship governed by Ukrainian construction-contract provisions, article 882 of the Civil Code addresses handover and acceptance, including preliminary testing where required by the contract or the nature of the works. Acceptance in that case follows a positive test result. The article also addresses acceptance records and refusal, so simply declining to sign a document is not a substitute for a properly evidenced position and contractual procedure.
Make the measurement boundary part of the bargain
Specify usable energy and power, AC/DC boundary, state-of-charge window, temperature, auxiliaries, efficiency, availability and the test conditions relevant to each guarantee. Fix the reference date and how the measurement is corrected, repeated or disputed. Avoid mixing a cell-level energy quote with export energy at the commercial meter.
Synthetic example: an OEM quotes 20 MWh nominal DC, while the integrated contract promises 18 MWh usable AC at the agreed meter and 10 MW sustained output under the stated conditions. The contracted full-power duration is 18 / 10 = 1.8 hours. A buyer modelling 20 MWh of AC delivery and two hours has changed the specification, not discovered another guaranteed service. If an agreed compliant test measures 17.5 MWh against an 18 MWh obligation, assess the test method, tolerances, remedy and evidence; do not jump from one reading to a conclusion of automatic rejection.
Table — scroll horizontally if needed
| Test entry | Minimum definition to negotiate | Investment consequence |
|---|---|---|
| Capability | MW/MWh boundary, duty and conditions | Feasible contracted service |
| Efficiency | Import/export boundary and auxiliary treatment | Charging cost and net revenue |
| Availability | Measurement period, exclusions and data | Operating/revenue downside |
| Pass or fail | Criteria, tolerances and permitted exceptions | Acceptance and payment readiness |
| Failed result | Correction, retest, time/cost and escalation | Exposure before the remedy works |
| Evidence | Witnesses, calibrated data, reports and access rights | Ability to prove the result later |
Read warranty, performance and acceptance together
Article 853 of the Civil Code addresses inspection and notification of defects for works; it distinguishes defects apparent on ordinary acceptance from hidden defects. Build the review and notice process into the handover plan rather than assume a later general warranty claim will cure every omission.
Where the relationship falls within the construction-contract regime, article 884 provides a ten-year warranty period from acceptance, or a longer period established by contract or law, and specifies contractor responsibility and relevant exclusions. This is not a statement that every battery supply contract carries a ten-year capacity-retention warranty. Construction quality, OEM retention/throughput, system performance and O&M availability can have different objects, conditions and remedies.
Map who responds to a claim, what is repaired/replaced or compensated, limits, exclusions, notice requirements and the effect of assignment/change of control. Lost revenue may sit outside a particular remedy. Test the counterparty's ability to perform and the delay before repair or payment; a contractual entitlement is not immediate liquidity.
Match payments to evidence and exposure
A payment schedule may distinguish design approval, manufacture, delivery, installation, defined acceptance and retained amounts. For each stage, identify title, risk, insurance, evidence, security and what happens after failure. Do not assume payment transfers all risks in the same way as technical acceptance or statutory commissioning.
The World Bank construction-contracts checklist is useful general context for reviewing design responsibility, testing and contractual remedies. It is not Ukrainian law or a requirement that a private BESS use a particular contract form. The actual package still needs coordinated legal and engineering review.
Before an acquisition offer, obtain the complete agreements and variations, outstanding payments, claims, test records, punch list, warranty/security documents and handover access. Identify missing permissions or interfaces and put their cost and delay into the completion budget. An EPC label or a Qualified Project status cannot replace that work.
Read the BESS lifecycle guide, BESS investment diligence and bankability framework. Discuss your mandate with the acceptance evidence and remaining interface risks your team can underwrite.