> For the complete documentation index, see [llms.txt](https://help.daak2.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.daak2.com/zh-cn/cun-qian-guan/savings.md).

# 存钱罐

## 创建存钱计划

1. 打开 **存钱罐**，点击右上角 **+**。
2. 输入计划名称，选择计划类型和货币。
3. 按类型设置目标、存入金额、频率、开始日期或递增金额。
4. 需要协作时，在编辑页设置共享。
5. 点击 **保存**。

| 计划类型  | 设置内容         |
| ----- | ------------ |
| 固定    | 每期金额、执行频率和目标 |
| 灵活    | 自由存入，不固定每期金额 |
| 52 周  | 首期金额和每周递增金额  |
| 365 天 | 按每日计划记录      |

## 记录存钱

1. 点击计划进入详情。
2. 选择要记录的期数，或点击存入操作。
3. 选择账本、转出账户和存钱账户。
4. 确认金额和日期后保存。

计划详情会显示已完成期数、累计金额和记录历史。

## 取钱、结束与删除

| 操作       | 结果                |
| -------- | ----------------- |
| **取钱**   | 记录从存钱账户转出的金额      |
| **取消记录** | 恢复计划进度，并删除该期关联账单  |
| **编辑计划** | 修改计划名称和后续设置       |
| **结束**   | 停止计划继续进行，已有记录保留   |
| **已结束**  | 在存钱罐页面底部查看已经结束的计划 |
| **删除计划** | 删除计划及全部关联账单       |

{% hint style="danger" %}
删除存钱计划及关联账单，不可撤销。共享中的计划需要先结束共享。
{% endhint %}


---

# 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://help.daak2.com/zh-cn/cun-qian-guan/savings.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.