> For the complete documentation index, see [llms.txt](https://docs.altitude.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.altitude.fi/general/yield-generation-process/how-are-yields-recognised.md).

# How are yields recognised?

Yields are recognised through the harvest process. During this process, we:

* Claim and swap any reward tokens received from the Yield Farm
* Recognise any balance changes (positive or negative)

These changes in the farm balance are logged in a harvest snapshot that can be used for distribution to users at a later date.

In case of earnings, these are either used to decrease the users loan or give the user access to claimable rewards. When there are farm earnings, we also reserve a certain percentage as vault reserve as displayed on the vault information page.

Should the farm have suffered a loss, this is distributed to users in the form of an increase in their loan value. The harvest process is run periodically.

{% hint style="info" %}
Each harvest is captured in a snapshot that stores key details about yields recognised and the state of the vault at the time.
{% endhint %}

## When do harvests happen?

Harvests happen weekly, usually on Wednesdays between 8am UTC and 11am UTC.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.altitude.fi/general/yield-generation-process/how-are-yields-recognised.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.