> For the complete documentation index, see [llms.txt](https://docs.kasu.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kasu.finance/lending-with-kasu/understanding-epochs-and-clearing-periods/clearing-periods.md).

# Clearing Periods

A Clearing Period occurs at the end of each epoch during a 48-hour period at which certain lending activities, and related transactions, are processed

### 🧤 Lending & Withdrawal Request Processing <a href="#lending-and-wtihdrawal-request-processing" id="lending-and-wtihdrawal-request-processing"></a>

All queued Lending and Withdrawal requests are processed during the final 48 hours of each epoch, based on Lender Loyalty Levels. Recall that loan Tranche allocations may be adjusted to accommodate submitted requests if a Lending Strategy is oversubscribed.

### 💵 Interest Accrual <a href="#interest-accrual" id="interest-accrual"></a>

Interest is accrued every epoch (7 days) and is reflected in your loan balance(s) at the start of each new epoch.

### 📊 Loan Balance Updates <a href="#loan-balance-updates" id="loan-balance-updates"></a>

After clearing, at the start of each new epoch, your loan balance(s) is updated to reflect increases (associated with Accepted Lending Requests and/or interest earned) or decreases (associate with Accepted Withdrawal Requests and/or losses).

### 🧮 Loyalty Level Recalculation <a href="#loyalty-level-recalculation" id="loyalty-level-recalculation"></a>

Lender Loyalty Levels are recalculated based on current $KASU holdings and lending activity, thereby concluding clearing.\\


---

# 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://docs.kasu.finance/lending-with-kasu/understanding-epochs-and-clearing-periods/clearing-periods.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.