> 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/setups/configurations/purchase-voucher-configurations/other-settings-1/prompt-for-po-close-hold-in-case-of-po-retrieval.md).
# Prompt for PO Close/Hold in case of PO Retrieval
**YouTube:** [How to Mark a Purchase Order as Complete Despite Pending Items ?](https://www.youtube.com/watch?v=tbtXvc94wBk)
## How to Mark a Purchase Order as Complete Despite Pending Items?
This feature allows users to receive a **prompt to mark a Purchase Order (PO) as closed or on hold** during its retrieval in a purchase voucher. This ensures cleaner tracking and prevents accidental Re-Use of partially retrieved Purchase Orders.
***
### **Step-by-Step Guide:**
* Navigate to **Purchase Configuration**.
* Locate and enable the option: **“Prompt for PO Close/Hold in case of PO Retrieval.”**
***
### **Create a New Purchase Voucher**
* Navigate to the **Purchase** and click on **"Purchase Voucher".**
* Select the **supplier account**.
* Click on **Retrieve Purchase Order**.
* Choose a PO and **partially retrieve** the order.
* Enter required details and **save the voucher**.
* Upon saving, the system will display a **prompt**:
* *“Do you want to mark this PO as complete?”*
* Select **“Yes”** to mark the Purchase Order as completed.
***
### **Attempt to Retrieve the Same PO Again**
* Try retrieving the **same Purchase Order** again.
* Notice that the PO **does not appear** in the list.
* Even though there was **pending quantity**, it is no longer retrievable.
***
### **Key Notes**
* Once a PO is marked as **complete**, it cannot be retrieved again.
* This avoids duplicate or unintentional order processing.
* Use this feature to maintain **accurate procurement records** and track pending POs effectively.
---
# 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/setups/configurations/purchase-voucher-configurations/other-settings-1/prompt-for-po-close-hold-in-case-of-po-retrieval.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.