> For the complete documentation index, see [llms.txt](https://help.eq-earth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.eq-earth.com/registry/retirements/retire-ecus.md).

# Retire ECUs

Retiring ECUs takes them out of circulation so their impact can be claimed by the beneficial owner.

{% hint style="warning" %}
An ECU can only be retired once. Retired ECUs can no longer be transferred or cancelled. Check the beneficial owner, reason and quantity before you submit.
{% endhint %}

{% hint style="info" %}
**Retirements are public.** The retirement reason and the beneficial owner are disclosed on the Equitable Earth Registry.
{% endhint %}

{% hint style="info" %}
**Before you start:**

* You need at least one beneficial owner: see [Create a Beneficial Owner](/registry/retirements/create-a-beneficial-owner.md).
* Units still labelled **VRU** are the same unit type as ECUs and are retired the same way.
  {% endhint %}

{% stepper %}
{% step %}

### Log in

Log in to the Equitable Earth Registry.
{% endstep %}

{% step %}

### Initiate the transfer

Open the **Operations** drop-down at the top of your homepage and select **Initiate Transfer**.

![](https://2569783243-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FED6lPsyoF2iHXq92LOvD%2Fuploads%2FDnx0KuTCDDO2jA7oFYQX%2Fretirement-04-initiate-transfer.png?alt=media)
{% endstep %}

{% step %}

### Choose Retirement and the beneficial owner

In the **Select Batch Criteria** section on the left pane, select **Retirement** from the Transfer Type drop-down, then select the Beneficial Owner from the drop-down.

![](https://2569783243-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FED6lPsyoF2iHXq92LOvD%2Fuploads%2FhnQMdLD82NEy4Q91CIud%2Fretirement-05-type-owner.png?alt=media)
{% endstep %}

{% step %}

### Select a retirement reason

Select the reason that matches the claim the beneficial owner will make:

* **Compensation claim**: the ECUs are retired to offset GHG emissions attributable to the retiring party.
* **Contribution claim**: the ECUs are retired to represent a financial contribution to mitigating climate change and supporting ecological conditions and livelihoods, without offsetting emissions.

![](https://2569783243-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FED6lPsyoF2iHXq92LOvD%2Fuploads%2FqaYz6GFKSjIVKXtUzU3c%2Fretirement-06-reason.png?alt=media)
{% endstep %}

{% step %}

### Select the subaccount

Select the subaccount holding the ECUs to retire, then select **View Assets**.

![](https://2569783243-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FED6lPsyoF2iHXq92LOvD%2Fuploads%2FfdXNzHqN8lZrBHtm01Tq%2Fretirement-07-subaccount.png?alt=media)
{% endstep %}

{% step %}

### Select your ECUs

On the **Select Your Assets** screen, use **Select All** or **Clear All**, or enter the number of ECUs to retire in the **Transfer Quantity** field.

![](https://2569783243-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FED6lPsyoF2iHXq92LOvD%2Fuploads%2FClfaAooxVDFEMNyJf4XV%2Fretirement-08-select-assets.png?alt=media)
{% endstep %}

{% step %}

### Submit

The number of ECUs ready for retirement is shown at the bottom left. Select **Submit** at the bottom right to complete the retirement.

![](https://2569783243-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FED6lPsyoF2iHXq92LOvD%2Fuploads%2Fdf3GWoUJzQVer41JAAl7%2Fretirement-09-submit.png?alt=media)
{% endstep %}
{% endstepper %}

## Your retirement record and certificate

Every retirement is recorded in the Registry with the account holder that requested it, the beneficial owner and the retirement reason.

Retirement details and a PDF certificate are emailed to the Account Manager. You can also download the PDF at any time from the **My Retirements** report.

## Making claims with ECUs

Each ECU represents one tonne of CO₂ equivalent verified by an independent VVB as reduced or removed, together with the project's benefits for biodiversity and livelihoods. ECUs are not biodiversity credits.

* Equitable Earth encourages organizations claiming ECUs to use them alongside a credible 1.5°C- or 2°C-aligned pathway, and to follow market best practice on claims, such as the VCMI Code of Practice.
* Equitable Earth does not condone using ECUs for carbon neutrality claims, or bundling them into the sale of net-zero products.

## Compliance and international uses

Besides voluntary pledges in the voluntary carbon market, ECUs can be used for compliance schemes (for example, carbon tax regimes such as those in Singapore, Colombia and South Africa), for CORSIA, and towards a purchasing country's NDC under Article 6 of the Paris Agreement.

For CORSIA and Article 6, only ECUs from projects that have obtained the corresponding eligibility can be used. These ECUs carry the corresponding label in the Registry, and the host country's Letters of Authorisation are published on the Registry. See the [Avoiding Double Claiming Procedure](https://docs.eq-earth.com/avoiding-double-claiming-v1.3.pdf) for details.

## If a project is suspended or fails

* **Suspended project:** ECUs issued before the suspension remain valid and can still be transferred and retired, unless Equitable Earth specifies otherwise.
* **Failed project:** ECU holders must retire the project's issued ECUs within **12 months** of the project failure notification. ECUs not retired within that time are automatically cancelled. If the failure materially compromises the integrity of the ECUs, Equitable Earth may cancel them immediately. Retired ECUs are never cancelled.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.eq-earth.com/registry/retirements/retire-ecus.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.