> For the complete documentation index, see [llms.txt](https://docs.ezorderly.com/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ezorderly.com/guide/sheng-ji-yu-fu-kuan/fu-kuan-yu-fa-piao-ji-lu.md).

# 付款與發票紀錄

點選左上角縮放功能目錄，最下方的「升級與付款」中，點選「付款與發票」即可做相關的瀏覽。

![](/files/PNWOyjJpDagYAxP51Dpn)

### 系統費用

顯示購買、升級方案的資訊歷史紀錄。

* **狀態：**本筆訂單的付款狀態，是否已付款。
* **發票：**本筆訂單的發票編號。
* **付款日期：**本筆訂單的付款日期。
* **方案：**顯示購買的方案版本，以及購買期數。
* **到期日：**顯示方案截止日期。
* **額度：**顯示本筆訂單附贈的郵件和簡訊數量。
* **金額：**顯示本筆訂單的金額(含稅)。

### 加購儲值

顯示加購、儲值訊息點數的歷史紀錄。

* **狀態：**本筆訂單的付款狀態，是否已付款。
* **發票：**本筆訂單的發票編號。
* **付款日期：**本筆訂單的付款日期。
* **方案：**顯示儲值郵件或儲值簡訊。
* **到期日：**顯示儲值點數截止日期。
* **額度：**顯示本次儲值的郵件或簡訊數量。
* **金額：**顯示本筆訂單的金額(含稅)。

![](/files/lnKMojj4sr7AFkmL9dEs)

{% hint style="info" %}
郵件與簡訊儲值欄位旁，點擊連結前往線上儲值，說明請參閱 [郵件與簡訊儲值](/guide/sheng-ji-yu-fu-kuan/fu-kuan-yu-fa-piao-ji-lu/you-jian-yu-jian-xun-chu-zhi.md)
{% 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://docs.ezorderly.com/guide/sheng-ji-yu-fu-kuan/fu-kuan-yu-fa-piao-ji-lu.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.