> For the complete documentation index, see [llms.txt](https://energy-web-foundation.gitbook.io/katalist/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://energy-web-foundation.gitbook.io/katalist/guidelines/how-to-use-katalist/accepting-smf-3-retired-on-your-behalf-ff-and-co.md).

# Accepting SMF-3 retired on your behalf (FF & CO)

An FF & CO who does not have a Katalist account can have an SC, FF or FA retire tokens on their behalf. They will receive the statement via e-mail and can accept it by following these steps.

**1)** The first time you have SMF-3 retired on your behalf from a specific company, you will receive an email asking to confirm that the information provided by your supplier is correct. Please review this information and click confirm if it is correct.

<figure><img src="https://757876471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrHs8pNWuI44XibDoughw%2Fuploads%2FUMQf5ttYV9yBmC7qdF8l%2Fimage.png?alt=media&amp;token=d0bf43c1-8040-4ba6-8562-3fa898026f36" alt=""><figcaption></figcaption></figure>

**2)** You will then receive an email with a draft retirement statement attached. Please review this statement to ensure it matches your agreement, and review the email text before clicking "Confirm." If you have asked your supplier to send the retirement statements to multiple email addresses, all recipients will receive this draft statement. However, only the employee listed as the final approver can confirm or reject the retirement.

<figure><img src="https://757876471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrHs8pNWuI44XibDoughw%2Fuploads%2FNggDIbfszbrRkNaEJGyh%2Fimage.png?alt=media&amp;token=70971704-4cfd-4343-ae39-a868a1417a18" alt=""><figcaption></figcaption></figure>

**3)** Once you have confirmed, the Registry Administrator will review this retirement. When approved by the Administrator you will receive an email containing the final retirement statement. If you have asked your supplier to send the retirement statements to multiple email addresses, all recipients will receive this final statement. No further action is needed from you.&#x20;

<figure><img src="https://757876471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrHs8pNWuI44XibDoughw%2Fuploads%2FtP9oak75NwEYdkFN5udk%2Fimage.png?alt=media&amp;token=69b881f9-a539-4ef5-9d6c-5d37c48c33a8" alt=""><figcaption></figcaption></figure>


---

# 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://energy-web-foundation.gitbook.io/katalist/guidelines/how-to-use-katalist/accepting-smf-3-retired-on-your-behalf-ff-and-co.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.