> 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-version-release-notes/january-2026/reports/po-date-and-po-no.-columns-added-to-ledger.md).
# PO Date & PO No. Columns Added to Ledger
**YouTube:** [Jan 2026 Release Notes: PO Date & PO No. Columns Added to Ledger](https://www.youtube.com/watch?v=PhTDnLfNaew)
## Jan 2026 Release Notes: PO Date & PO No. Columns Added to Ledger
In this tutorial, we will explore the **newly added PO Number column in the Bank Payment module**, along with the **PO Date and PO Number columns in the Ledger Report** in Logic ERP. Let’s get started.
***
### Enable PO Number in Bank Payment Module
* Navigate to the **Bank Payment** module.
* Proceed to record a payment **against a Purchase Order**.
* To enable the newly added column, open **Set Column Attributes**.
* Locate the **PO Number** column.
* Tick the checkbox to enable it and **save** the changes.
The PO Number column is now successfully added to the Bank Payment entry screen.
***
### Record Bank Payment Against a Purchase Order
* Enter the required payment details.
* Press the **Space bar** in the **PO Number** field.
* Select the relevant **Purchase Order** from the list.
Once selected, the corresponding **PO Number is automatically populated** in the field.
* Save the bank payment entry.
***
### Enable PO Columns in the Ledger Report
* Open the **Ledger Report**.
* Go to **Set Column Attributes**.
* Enable the newly introduced columns:
* **PO Date**
* **PO Number**
* Rearrange the columns if required.
* Save the configuration.
* Press **F2** to refresh the report.
**Result**
As shown, the **PO Date and PO Number columns** are now successfully displayed in the ledger report, accurately reflecting the linked purchase order details.
***
### Conclusion
This enhancement ensures:
* Better traceability between **bank payments and purchase orders**
* Improved audit visibility
* Clear and structured reporting in the **Ledger Report**
With this update, tracking PO-wise payments in Logic ERP becomes more transparent and efficient.
---
# 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-version-release-notes/january-2026/reports/po-date-and-po-no.-columns-added-to-ledger.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.
