> For the complete documentation index, see [llms.txt](https://doc.moze.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.moze.app/record/postpone.md).

# 延後入帳

信用卡支付常常會遇到消費日跟入帳日不同的狀況，因為店家會分批彙整消費資料後才向銀行請款，所以入帳日通常會比消費日晚個幾天。

如果對帳時發現某筆交易沒有算進這一期帳單，很可能是結算日當下店家還沒向銀行請款，所以延到下一期帳單。這時你可以把入帳方式改成延後入帳，並填上實際入帳的日期，信用卡帳單就會自動略過尚未入帳的交易。

<img src="https://1006683-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MCbsscJsS02Gvb4-1bD%2F-MGviMMums3mgZZmdPvg%2F-MGvnFLj6qMeFI5gDE8D%2F%E5%BB%B6%E5%BE%8C%E5%85%A5%E5%B8%B31.png?alt=media&amp;token=ce995cae-fe83-4eae-8265-050c42340bf5" alt="" width="375">

&#x20;

<img src="https://1006683-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MCbsscJsS02Gvb4-1bD%2F-MGviMMums3mgZZmdPvg%2F-MGvnH4tJYj0ph-aJHGo%2F%E5%BB%B6%E5%BE%8C%E5%85%A5%E5%B8%B32.png?alt=media&amp;token=ca0c743b-ca1e-4492-9765-64ab50553ae1" alt="" width="375">

&#x20;

<img src="https://1006683-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MCbsscJsS02Gvb4-1bD%2F-MGvnMkbFXUbGgObsW0e%2F-MGvnqlo0WyA257me6X5%2F%E5%BB%B6%E5%BE%8C%E5%85%A5%E5%B8%B33.png?alt=media&amp;token=99f76a90-7d85-4512-86ea-900ac4b25db7" alt="延後入帳到下一期帳單" width="375">

通常你不需要把每一筆刷卡記錄都調整成延後入帳，只要在**對帳模式**裡，把不屬於這一期帳單的交易左滑延後入帳即可，詳情可參考：

{% content-ref url="/pages/-MCe5ZqyeobvB\_Mye52V" %}
[對帳模式](https://doc.moze.app/reconciliation/statement-mode.md)
{% endcontent-ref %}


---

# 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://doc.moze.app/record/postpone.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.
