What is Ex-Domain Cancellation of Guarantees of Origin? Comprehensive Guide to Ex-Domain Cancellation in 2026

AIB Guarantee of Origin certificates are governed by the EECS ruleset which are operationalised by the national registries underpinning the system. When an end user claims renewable electricity consumption, their claim only occurs when they cancel their GO in the national registry that corresponds with their physical energy consumption. The often overlooked detail that matters is which cancellations actually end up counting due to where they occur. This brings us to the tricky and highly misunderstood concept of “Ex-Domain Cancellation” (EDC).

Is Ex-Domain Cancellation Allowed Under RE100 and EECS Rules?

EECS:

Within the AIB context, ex-domain cancellation means cancelling an EECS GO in the country where it was issued while making a renewable electricity claim in a different EECS country, without transferring the certificate first. The Association of Issuing Bodies doesn't allow this as a conventional mechanism under EECS rules: as certificates must be exported to the registry where local consumption occurred, before they're cancelled (cancelled certificates are exited from circulation and therefore not transferable). Cancellation is permitted solely as follows:

• Own Domain (C7.1.1(a))
• Cross-Domain via agreement (C7.1.1(b))
• Non-Domain export scenarios (EDC) (C7.1.1(c)): Only if energy is physically exported there, automated transfer is "temporarily impossible due to technical difficulties", and the local Issuing Body is notified.
• Conversion Issuance restricted to the "same geographical area" (C7.1.4)
• Only to demonstrate origin of energy "consumed before the date of cancellation" (C7.1.6(b)).

RE100:‍

RE100 takes the same position in their 2025 Technical FAQ: claims that skip this registry transfer aren't recognised. That means a certificate cancelled in Finland can't support a claim against German consumption - “it does not observe the RE100 market boundary definition”. That’s a highly important detail that, if missed, will be troublesome from a watertight reporting perspective.

Auditors sometimes miss this fact, presumably due to the very apparent interoperability of the system overall, assuming that cancellation can replace a transfer, and the end-result is the same. They mistakenly treat cancellation as a yes/no event rather than explicitly checking which registry was used.

There are some edge-cases, though...

Is Ex-Domain Cancellation Impossible Everywhere?

At the time of writing, there are very few legitimate ways to perform EDC that are allowed under the EECS rules and outlined as per AIB domain protocols and the imposed conditions for trade, expiry and cancellation. This is the full list, for clarity:

The pattern is very clear: most countries that allow it treat it as a fallback for when Hub transfer isn't possible - the "technical difficulties" clause (C7.1.1(c)(ii))., not as a routine or best-practice mechanism.

‍

‍

How Do Companies Manage GO Cancellations Across Multiple EAC Registries?

Cross-border renewable procurement and cancellation means dealing with transfer mechanics across 30-plus national registries, each running their own export and cancellation procedures. On top of this, you’re dealing with private standards like RE100 that explicitly prohibit Ex-Domain cancellation. It’s a lot to manually balance, leading to intense periods of administrative busywork.

A multinational with consumption in Germany, Sweden, and the Netherlands ultimately needs to have their certificates cancelled in three separate registries, properly transferred and documented before each cancellation event. Working through intermediaries who don't have direct registry access introduces delays and documentation gaps. You need a platform that integrates with every registry and allows you to download the source documentation: the export-ready cancellation statements - these are the only documents that actually proves compliant consumption.

Soldera integrates directly into registries across Europe from a single account, running export, transfer, and cancellation as one automatically-compliant workflow. The platform is designed for corporates that require verified cancellation statements across any multi-jurisdiction portfolio - build a compliance position that holds up.