> For the complete documentation index, see [llms.txt](https://docs.enzyme.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enzyme.finance/onyx-user-documentation/enzyme-vault/subscription/deposits/asynchronous-deposits.md).

# Asynchronous Deposits

The default deposit mechanism is asynchronous and relies on a queue.

**Deposit Requests** can :

* Be arbitrarily processed by Vault Owners or Managers
* Be executed in batch
* Be cancelled by the depositor after a waiting period defined by the Vault Owner or Admins

**Deposit Requests cannot** be cancelled by Vault Owner and Admins (*Subscriptions are on-chain transactions and only the initiator can revoke them*). However, Vault Owners and Admins may choose to ignore pending requests.

{% stepper %}
{% step %}

### Investor deposit funds

The investor submits a deposit request, which enters a dedicated queue.
{% endstep %}

{% step %}

### Deposit Processing - NAV Calculation and Reporting

Before new Vault Shares can be issued, the Vault Owner or Admin must evaluate the portfolio's underlying assets and positions, and report the ***Portofolio Value*** in the Administration App. 
{% endstep %}

{% step %}

### Deposit Processing - Deposit Request Execution

The Vault Owner or Admin approves pending deposit requests. This action triggers the issuance of Vault Shares, proportionally to the stake held in the Vault, which are then transferred  to the depositor’s wallet.
{% endstep %}

{% step %}

### Funds consolidation in the Vault

Once approved, the deposited funds are transferred into and consolidated within the Vault smart contract.
{% endstep %}

{% step %}

### Transfer to Management Wallet

After processing, Vault Owners or Admins may withdraw funds from the Vault smart contract to the Management Wallet.
{% endstep %}

{% step %}

### Strategy execution

From the ***Management Wallet***, managers are free to deploy funds across any system, protocol, or asset in line with their strategy.
{% endstep %}
{% endstepper %}


---

# 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.enzyme.finance/onyx-user-documentation/enzyme-vault/subscription/deposits/asynchronous-deposits.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.