> 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/bang-zhu/faq.md).

# 常见问题

## 账户余额和顶部汇总为什么不同？

账户行显示原币种余额；顶部会按统计货币换算并应用筛选。

| 检查项目         | 可能造成的差异          |
| ------------ | ---------------- |
| **账本筛选**     | 顶部只汇总当前筛选账本      |
| **账户组与父子账户** | 子账户会先换算为主账户货币再汇总 |
| **统计排除**     | 被排除的账户不计入顶部金额    |
| **汇率日期**     | 不同日期的换算结果可能不同    |

未来账单不会计入资产页面的当前余额和顶部汇总，到达账单时间后才会产生影响。

## 另一台设备为什么没有立即看到修改？

确认 Apple ID、iCloud Drive、Daak 的 iCloud 权限和网络状态。共享内容还需要确认邀请已经接受，然后在两台设备打开 Daak 等待同步。

## 为什么某笔账单不能编辑或删除？

它可能来自存钱、分期或定存等功能，或者受到共享权限限制。请从详情进入关联功能处理。

## 为什么市场价格不是今天的？

股票价格会受到休市、收盘数据发布时间、服务端队列或供应商异常影响。加密货币也可能因网络暂时显示上一条数据；已保存价格不会因一次失败被清空。

## 为什么归档后统计里仍有记录？

{% hint style="info" %}
归档只隐藏入口，不删除历史。这是为了保持过去的资产和收支统计完整。
{% 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/bang-zhu/faq.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.