PPA certificate management: from forecast to customer evidence

Does a PPA include the renewable attributes?

Read the agreement. Under the published GHG Protocol Scope 2 Guidance, a power purchaser cannot claim the generator’s attributes when the associated certificates are sold separately. The commercial arrangement needs to establish what the purchaser receives. See section 6.11.2 of the guidance.

Certificate attributes can be traded separately from physical electricity. That makes the power invoice, certificate movement and customer evidence related records rather than a single event. I-TRACK explains this separation.

For operations, the question is concrete: which certificate product is due, in what quantity, to which account or beneficiary, and by when? Capture the answer before the first delivery rather than relying on a colleague to interpret the agreement each month.

Six questions to settle at onboarding

1. Rights: who is entitled to the certificates, and may any attributes be sold separately?
2. Specification: what scheme, facility, technology, geography and production period must be delivered?
3. Volume: is the obligation linked to actual generation, a fixed quantity or another agreed formula?
4. Timing: what are the delivery dates, evidence deadlines and steps when issuance is delayed?
5. Shortfalls: who handles a shortfall, and what replacement attributes or approvals does the contract allow?
6. End use: is the obligation a transfer, or does it include cancellation or redemption for a named beneficiary?

These are questions for the contract and operating process, not suggested legal terms. Keep the agreed answers in structured records linked to the signed agreement.

Keep forecasts, issued certificates and commitments distinct

A production forecast is an expectation. An issued certificate is an existing instrument. A customer commitment is an obligation. Showing all three as one balance can hide both timing risk and a short position.

Use a view with separate quantities for forecast production, verified generation awaiting issuance, issued holdings, committed supply and completed delivery. Record the date and owner of each forecast update, and make the calculation basis visible.

A follow-up to the issuer may resolve the first issue. It cannot create the generation missing from the second. A single “500 MWh pending” label would conceal that distinction.

Connect each allocation to its evidence

Allocate certificates to customer obligations using the agreed specification and a traceable identifier. If one issuance serves several customers, retain the quantity assigned to each. If an allocation changes, record who changed it and preserve the earlier state.

Then reconcile the expected delivery to the registry movement. A completed transfer may close a transfer obligation; it does not by itself prove that customer-use evidence has been completed. Our reconciliation checklist covers the separate checks.

For reporting, make the trail navigable: agreement → obligation → issuance → allocation → movement → final evidence. This sequence is our suggested operating framework; the precise steps depend on the scheme and service agreed.

Prepare for changing reporting requirements without confusing them

Keep production timestamps, consumption periods and geographic attributes in a form that can be retrieved and checked. This helps teams answer customer questions without reconstructing their book later.

The GHG Protocol is revising its Scope 2 guidance. The sources reviewed on 9 October 2026 distinguish the published 2015 guidance from proposals on hourly matching and deliverability. Treat proposals as proposals when evaluating a present obligation. See the guidance and revision process.

Record the reporting framework and version relevant to each customer. A change in a reporting standard, registry rule or customer contract should trigger a review of the affected obligations, rather than a blanket relabelling of the entire portfolio.

What should a PPA workflow demo show?

Ask to follow a single agreement through a forecast change, delayed issuance, partial customer allocation and final delivery. Include an exception, such as a production-period mismatch, and ask how the team sees and resolves it.

That makes the evaluation about the work the desk will actually perform. Book a demo around your PPA and certificate workflow.