> 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/purchase/purchase-module/purchase-transactions/po-short-close.md).
# PO Short Close
The **PO Short Close** option is used to close Purchase Orders that are partially used, not used, or pending for a long period. This helps ensure that inactive or unnecessary Purchase Orders are properly closed in the system.
## Steps for PO Short Close
Step 1: Go to the **Purchase** main menu.
1. Click **Transaction**.
2. Select **PO Short Close**.
* The PO Short Close screen will appear.
Step 2: Click the **Open** button.
Step 3: Click the **Search icon** to view available Purchase Orders.
1. The list of Purchase Orders will appear.
2. Double-click on the required **PO** that needs to be short closed.
* The selected Purchase Order details will be loaded into the screen.
Step 4: After selecting the PO, click the **Save** button.
* Once saved, the Purchase Order will be marked as **Short Closed** 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/purchase/purchase-module/purchase-transactions/po-short-close.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.
