> 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/transfers/before-you-transfer-batches-and-conversion.md).

# Before You Transfer: Batches and Conversion

{% hint style="danger" %}
**Read this before your first transfer.** How you transfer batches decides who receives the first ECUs when PRUs convert. Misunderstanding it can cause problems at the first PRU-to-ECU conversion.
{% endhint %}

{% hint style="info" %}
**ECU and VRU are the same unit type.** Converted units are now called ECUs. Units issued under the former name may still show **VRU** in the Registry; they are treated exactly like ECUs.
{% endhint %}

## How batches are identified

PRUs are held in batches: an account holder owns batches of PRUs. Each batch is a volume of PRUs identified by a serial number with this structure:

```
EQE-[project type]-[project ID]-[country]-[unit type]-[issuance date or vintage]-[batch]-[block start]-[block end]
```

| Part                     | Meaning                                                                                    |
| ------------------------ | ------------------------------------------------------------------------------------------ |
| `EQE`                    | Equitable Earth registry prefix                                                            |
| Project type             | Number for the project type: `1` for Terrestrial Forest Restoration, `0` for Reforestation |
| Project ID               | Identifier of the project                                                                  |
| Country                  | Two-letter ISO country code                                                                |
| Unit type                | `PRU` or `ECU` (`VRU` for units issued under the former name)                              |
| Issuance date or vintage | Issuance date (for a PRU) or vintage (for an ECU/VRU)                                      |
| Batch                    | Batch number                                                                               |
| Block start / Block end  | First and last unit numbers in the batch                                                   |

For example, `EQE-1-123-FR-PRU-2025-3-1-100` is batch 3 of PRUs issued in 2025 for Terrestrial Forest Restoration project 123 in France, containing units 1 to 100.

## Transfers take units from the end of a batch

When you transfer part of a batch, the **last** units of the batch are transferred.

Take the batch `EQE-1-123-FR-PRU-2025-3-1-100` (100 PRUs, units 1 to 100). If account 1 transfers 25 PRUs from it to account 2, the batch is split in two:

| New batch                        | Units  | Held by   |
| -------------------------------- | ------ | --------- |
| `EQE-1-123-FR-PRU-2025-3-1-75`   | 1–75   | Account 1 |
| `EQE-1-123-FR-PRU-2025-3-76-100` | 76–100 | Account 2 |

Account 2 now holds the last PRUs in the sequence.

## Conversion takes units from the start of a batch

PRUs convert to ECUs in sequential order: the **first** PRUs convert first.

In the example above, conversion starts with account 1's batch, because it holds the first PRUs. Account 2's batch only starts converting once account 1's batch has fully converted to ECUs.

{% hint style="warning" %}
**Transfer with care.** Because transfers take the last units and conversion starts with the first, the way you transfer decides who receives ECUs first.

If you need to transfer the **first** PRUs of a batch, split the batch with a subaccount first: see [Split a Batch Using a Subaccount](/registry/transfers/split-a-batch-using-a-subaccount.md).
{% endhint %}


---

# 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/transfers/before-you-transfer-batches-and-conversion.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.