Certificate delivery reconciliation: from trade to audit trail

What should a certificate desk reconcile?

Start with three records: what was agreed, what the registry recorded, and what your portfolio says has been fulfilled. These records answer different questions. A trade confirmation describes the obligation. The registry provides evidence of the movement. The portfolio allocation connects that movement to the obligation.

Keep the distinction between movement and use. In EECS, transfer changes the registered holder; cancellation removes the certificate from further transfer. Expiry is a separate event. AIB explains the certificate lifecycle.

Our recommended approach is to mark an obligation complete only when the required evidence is present. If the contract requires transfer, a completed transfer may satisfy it. If it requires cancellation or redemption for a customer, receipt into your own account is an intermediate step.

The seven checks before closing a delivery

1. Obligation: link the movement to a trade, PPA allocation or customer instruction. Record the agreed delivery method and deadline.
2. Scheme and attributes: compare the scheme, country, energy source, technology, production period and any contractual eligibility conditions.
3. Quantity: compare in a consistent unit. Keep partial fulfilments and any remaining balance visible.
4. Accounts and parties: verify the sending and receiving accounts, legal entities and customer allocation.
5. Registry status: distinguish requested, pending, completed, rejected and reversed movements where those states exist.
6. Use evidence: where required, connect cancellation or redemption evidence to the beneficiary and relevant period.
7. Decision history: retain the original record, who approved an exception and the reason for any reassignment.

This is an operational checklist, not a universal scheme rule. Agree which fields are mandatory for each product and delivery method before enabling automatic matching.

Worked example: 1,000 MWh received, only 800 MWh matched

Consider an illustrative purchase of 1,000 MWh of Spanish solar GOs from 2026 production. Two completed registry deliveries arrive before the contractual deadline.

The registry receipt totals 1,000 MWh, but only 800 MWh matches the specified obligation. Keep the remaining 200 MWh open while the counterparty supplies the correct vintage or an authorised person agrees and records a contractual amendment. Do not silently change the purchase specification to make the totals agree.

If those 800 MWh are also allocated to a customer sale, preserve that link. A later correction to the purchase should make its downstream consequence visible instead of leaving an apparently complete customer delivery.

Make exceptions a queue with an owner

A useful exception record answers: what failed, who owns the next step, when is it due, and what evidence will close it? Use a small, consistent set of reasons: missing reference, quantity difference, attribute difference, incorrect account, incomplete status or missing use evidence.

Separate a missing registry update from a failed delivery. A stale import can make a correct movement look absent; retrying the movement without checking the source can create a second problem. Show the last successful data refresh beside the exception.

Set escalation around the delivery deadline and the size of the unresolved obligation. A small mismatch due today may deserve attention before a larger delivery scheduled next month.

What belongs in the audit trail?

Retain the commercial reference, original registry transaction identifier, certificate identifiers or ranges, attributes, quantity, accounts, timestamps and evidence of final status. Add the allocation history and any approved changes. Where cancellation or redemption is part of the service, preserve the resulting statement too.

The key test is reproducibility: can another team member follow the record from the agreed obligation to its final evidence without relying on someone’s inbox? Set retention and access controls around your organisation’s requirements.

Eco-Insights brings trades, positions and delivery matching into the certificate workflow. In a demo, bring one clean delivery and one difficult exception so the discussion covers both. Explore your reconciliation workflow.

Can matching be fully automated?

Only where the available data and agreed rules support a reliable match. Ambiguous allocations, contractual changes and missing evidence need an explicit decision. A sensible first step is to automate exact matches and give the team a clear queue for the rest.

Is a registry balance enough for an audit?

A balance tells you what is held at a point in time. It does not, by itself, explain which obligation each holding fulfils, what changed or why. Preserve transaction and allocation history alongside the balance.