> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/accounts/configuration/cash-bank-voucher-configuration/other-options-2/transfer-voucher-date-to-date-of-occur.md).
# Transfer Voucher Date to Date of Occur
**YouTube:** [How to Transfer Voucher Date to Date of Occurrence in Cash / Bank Vouchers?](https://www.youtube.com/watch?v=kOrVzVBP1H8)
## How to Transfer Voucher Date to Date of Occurrence in Cash / Bank Vouchers?
This tutorial explains how to automatically transfer the Voucher Date to the Date of Occurrence while generating Payment and Receipt Vouchers in Logic ERP. This feature helps reduce manual date entry and ensures consistency between voucher dates and occurrence dates.
***
### Objective of This Feature
* Automatically transfer Voucher Date to Date of Occurrence
* Reduce manual date entry
* Improve voucher entry accuracy
* Maintain date consistency in transactions
* Speed up Payment and Receipt Voucher processing
***
### Access to Cash/Bank Voucher Configuration
* Navigate to **Accounts** and then **Configurations.**
* Open **Cash/Bank Voucher Configuration.**
* Choose the required **Voucher Configuration.**
* Example: **Bank Receipt Voucher Configuration.**
* Locate the option labeled as:
> **“Transfer Voucher Date to Date of Occur”**
**Default Status:**
* The feature is disabled
***
### Observe Behavior in Disabled State
**Transaction Process**
* Open **Bank Receipt Module.**
* Select Relevant Voucher Configuration.
* Proceed with Voucher Entry.
**System Behavior**
* The system automatically picks the current date in the Voucher Date field.
* Users can also Modify the Voucher Date manually.
**Important**
* The **Date of Occurrence** column can be enabled through:
* **Setup Column Attributes**
**System Behavior**
* Since the feature is disabled:
* The Voucher Date is not transferred automatically to the Date of Occurrence column.
* Users must:
* Manually enter the Date of Occurrence if required
***
### Observe Functionality After Enabling
**Action**
* Return to **Cash/Bank Voucher Configuration Module**
* Enable **Transfer Voucher Date to Date of Occur**
* Save the Configuration
**Process**
* Again, proceed with Voucher Entry
* Select Voucher Date.
**System Behavior**
* Upon enabling the feature:
* The Voucher Date is automatically transferred to the Date of Occurrence column.
* Manual entry becomes unnecessary
***
### Key Benefits
* Faster voucher entry process
* Reduces manual date entry effort
* Ensures date consistency
* Improves transaction accuracy
* Simplifies Payment and Receipt Voucher management
***
### Best Practice Tips
* Keep Date of Occurrence column enabled for visibility
* Verify voucher dates before saving transactions
* Use this feature to standardize transaction date management
* Review date settings periodically for accuracy
***
### Final Outcome
* Voucher Date is automatically copied to the Date of Occurrence field
* Manual date entry is minimized
* Payment and Receipt Voucher processing becomes faster and more accurate in Logic ERP
---
# 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://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/accounts/configuration/cash-bank-voucher-configuration/other-options-2/transfer-voucher-date-to-date-of-occur.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.
