> For the complete documentation index, see [llms.txt](https://csigma-asset-tokenization.gitbook.io/atlas/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://csigma-asset-tokenization.gitbook.io/atlas/pool-manager/reserve-management/move-funds-to-reserve.md).

# Move Funds to Reserve

### Overview

The **Move Funds to Reserve** function allows the Pool Manager to transfer funds from the **Available Balance** to the **Reserve Balance** of the Tokenized Pool.

The Reserve Balance acts as a **liquidity buffer** that helps the pool process lender withdrawals without waiting for capital to be returned from underlying investments.

If there are **pending withdrawal requests in the queue**, the transferred funds will first be used to **fulfill those requests automatically** before the remaining amount is added to the Reserve Balance.

### Where to Access

The **Move Funds to Reserve** function is available inside the **Vault widget** of the Tokenized Pool.

To access it:

1. Navigate to the **Asset Tokenization** tab.
2. Select the desired **Tokenized Pool**.
3. Locate the **Vault widget** on the pool dashboard.

The Vault widget displays:

* **Reserve Balance**
* **Available Balance**
* Amount input field
* **To Reserve** button

### Process

#### Step 1 — Enter Amount

In the Vault widget, the Pool Manager enters the amount that should be transferred from **Available Balance** to the pool reserve.

#### Step 2 — Click "To Reserve"

After entering the amount, the Pool Manager clicks the **To Reserve** button.

<figure><img src="https://3125893853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ffmxk4zctrz092V9PoVdO%2Fuploads%2FSFUAZWjaXJBPQRt8pDBs%2Fimage.png?alt=media&amp;token=3ac07855-b327-4d45-aa89-cb517f2d96e9" alt=""><figcaption></figcaption></figure>

#### Step 3 — Confirm Transaction

The Pool Manager confirms the transaction through their connected wallet.

<figure><img src="https://3125893853-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ffmxk4zctrz092V9PoVdO%2Fuploads%2Fcb0PxRNqbArsnr4GX7Ao%2Fimage.png?alt=media&amp;token=c01c7daf-8abd-4e14-bb9c-21fa8a6e92cc" alt="" width="319"><figcaption></figcaption></figure>

Once the transaction is completed:

1. Funds are moved from **Available Balance**
2. If there are **pending withdrawal requests**, those are fulfilled first
3. Any remaining amount is added to the **Reserve Balance**

### Example

Assume the following situation:

| Category          | Amount     |
| ----------------- | ---------- |
| Available Balance | 1,500 USDC |
| Reserve Balance   | 100 USDC   |
| Withdrawal Queue  | 200 USDC   |

The Pool Manager transfers **1,000 USDC** to reserve.

The funds are processed as follows:

1. **200 USDC** is automatically used to fulfill the withdrawal queue
2. The remaining **800 USDC** is added to the **Reserve Balance**

Final balances:

| Category          | Amount                |
| ----------------- | --------------------- |
| Withdrawal Queue  | 0 USDC                |
| Reserve Balance   | 900 USDC              |
| Available Balance | Reduced by 1,000 USDC |

### Important Notes

* Funds transferred to reserve are **first used to satisfy pending withdrawal requests**, if any exist.
* Only the **remaining amount after fulfilling the queue** is added to the Reserve Balance.
* This mechanism helps ensure that withdrawal requests are processed as soon as liquidity becomes available.
* Only funds from **Available Balance** can be moved to reserve.

### Role Responsibility

**Pool Manager Responsibilities**

* Maintain adequate reserve liquidity
* Move funds to reserve when withdrawal demand is expected
* Monitor withdrawal queues and pool liquidity

**cSigma Platform Responsibilities**

* Track reserve balances and withdrawal queues

This mechanism ensures that pools maintain **sufficient liquidity while prioritizing pending lender withdrawals whenever new liquidity is added to the reserve.**