Oxaide
Australia Battery M&A

Independent Australia BESS due diligence for buyers who want the real asset story

Secondary-market battery deals in Australia reward technical clarity and penalise weak assumptions. Oxaide helps buyers test usable capacity, degradation mode, and operational risk before close.

What buyers need answered

How much usable battery is really there, what degradation is already in motion, and what that does to revenue, reserve assumptions, and downside protection.

Where standard DD falls short

Vendor data rooms often provide neat summaries but limited proof. BMS health estimates, availability charts, and warranty packs do not automatically reveal the physical condition of the cells.

Why this matters in Australia

Merchant upside and active secondary-market activity make battery condition more commercially material. The stronger the revenue case, the more expensive sloppy diligence becomes.

What a stronger diligence pass includes

Raw or near-raw BMS and operating logs
SCADA historian exports and dispatch history
Independent review of rack-level variance and imbalance
Cross-check of reported SoH against commercially usable capacity
Evidence for SPA protections, reserves, and pricing adjustments
A clear decision on whether post-close monitoring is justified

Decision-useful, not decorative

The point is not to kill deals. It is to stop buyers paying clean-asset multiples for messy-asset reality.

If the asset is still attractive after a proper review, great. The buyer moves forward with better pricing, better protections, and a more defendable operating plan.

Operating posture

Scope first

Defined review scope

Boundary, telemetry window, and mandate question are pinned down before conclusions move.

Encrypted handling

Protected review workflow

Review traffic and operating data are handled with encrypted transfer and controlled access.

Customer boundary

Customer-controlled deployment

Managed, private, and isolated deployment paths are available when the environment requires them.

Direct accountability

Principal sign-off

Technical accountability stays close to the method rather than disappearing into a generic workflow.