> 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-tw/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-tw/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.