> 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/carry-forward-upper-narration.md).
# Carry Forward Upper Narration
**YouTube:** [How to Transfer Header Narration to Line Item Narration in Cash / Bank Vouchers?](https://www.youtube.com/watch?v=JV0Ekmki8C8)
## How to Transfer Header Narration to Line Item Narration in Cash / Bank Vouchers?
This tutorial explains how to automatically carry forward the Upper Narration into the Voucher Narration while creating Payment and Receipt Vouchers in Logic ERP. This feature eliminates repetitive manual typing and helps maintain consistency in voucher narration.
***
### Objective of This Feature
* Automatically carry forward Upper Narration
* Reduce manual narration entry
* Improve voucher entry efficiency
* Maintain consistent narration across transactions
***
### Access to Cash/Bank Voucher Configuration
* Navigate to **Accounts** and then **Configurations**
* Open **Cash/Bank Voucher Configuration**
* Choose the required **Voucher Configuration**
* Example: **Bank Payment Voucher Configuration**
* Locate the option labeled as:
> **“Carry Forward Upper Narration”**
* Currently Disabled.
***
### Verify Default Behavior
* Open **Bank Payment Module.**
* Select Relevant Configuration.
* Proceed with Voucher Entry.
**Enter Narration**
* In the **Upper Narration Field.**
* Enter Required **Narration.**
**System Behavior**
* Proceed to Voucher Entry Window
Observation
* The Upper Narration:
* Is not carried forward to the Voucher Narration or Line Narration field
**Result**
* Users must manually enter:
* Voucher Narration
* Or Line Narration
***
### Enable Carry Forward Upper Narration
* Return to **Cash/Bank Voucher Configuration Window.**
* Enable **“Carry Forward Upper Narration”.**
* Save the changes
***
### Verify the Functionality
* Open **Bank Payment Module**
* Enter **Upper Narration** in the Header Section
* Proceed to Voucher Entry Window
**System Behavior**
* The Upper Narration:
* Is automatically carried forward to the Voucher Narration or Line Narration field
**Result**
* No manual retyping is required
* Voucher entry becomes faster and more efficient
***
### Key Benefits
* Eliminates repetitive narration entry
* Saves time during voucher posting
* Ensures narration consistency
* Improves user efficiency and accuracy
***
### Best Practice Tips
* Use meaningful and standardized Upper Narrations
* Enable this feature for frequently used voucher configurations
* Review narration formats periodically for consistency
***
### Final Outcome
* Upper Narration is automatically copied to Voucher Narration
* Manual narration entry is minimized
* Voucher processing becomes faster and more streamlined
* Better consistency is maintained in Payment and Receipt Vouchers 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 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://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/accounts/configuration/cash-bank-voucher-configuration/other-options-2/carry-forward-upper-narration.md?ask=&goal=
```
`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.