> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/general-ledger/general-ledger-module/gl-transaction/post-dated-cheques.md).
# Post-Dated Cheques
**Post-Dated Cheques (PDCs)** are cheques issued with a future date. These cheques cannot be presented for payment until the date specified on the cheque.
The Post-Dated Cheques module enables users to record, manage, and monitor future-dated cheque transactions accurately. This helps organisations maintain proper control over upcoming payments and receipts while ensuring that transactions are processed according to the cheque date.
## Steps for Recording a Post-Dated Cheque
Step 1: Navigate to the **General Ledger** module.
1. Click **Transaction** from the menu.
2. Select **Post-Dated Cheques** option from the menu.
* The Post-Dated Cheques entry screen will be displayed.
Step 2: Click **Add** button. 
1. Select the Transaction Type and Transaction Date
Step 3: After selecting the transaction type and date, click the **Search** button available in the **Account Name** field.
1. Use the **Parties** list to locate the required account.
2. Search or browse through the available party records.
3. Select the appropriate account name.
Step 4: Enter the cheque amount in the appropriate field.
1. Specify whether the amount is a **Debit** or **Credit** transaction based on the nature of the cheque.
Step 5: Click the **Save** button.
* The post-dated cheque transaction is successfully saved in the system.
---
# 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://help.rbsgo.com/general-ledger/general-ledger-module/gl-transaction/post-dated-cheques.md?ask=&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.
