> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/settings/document-processing/module/po-shipment-order-setting.md).
# PO Shipment Order Setting
## **Overview**
The **PO Shipment Order** section provides a breakdown of delivery and invoicing status for matched Purchase Order items. This section appears within the **Purchase Order Matching** screen when the feature is enabled.
## **How to Enable**
To activate this feature:
1. Go to **Settings** → **Document Processing** → **Module**.
2. Select **Purchase Order**.
3. Enable the **PO Shipment Order** option.\
\\
## **Where It Appears**
Once enabled, the PO Shipment Order section becomes visible in the Purchase Order Matching interface.
### **PO Shipment Order – Field Descriptions**
* **Item ID**\
Identifies the specific item in the purchase order.
* **Delivery Number**\
Reference number for the shipment or delivery.
* **Shipped Quantity**\
Quantity that has been delivered or received.
* **Invoiced Quantity**\
Quantity that has already been invoiced.
* **Invoice Open Quantity**\
Quantity still open for invoicing (calculated as *Shipped Quantity – Invoiced Quantity*).
* **Progress Bar and Percentage**
* Shows how much of the shipped quantity has been matched with invoices.
* Starts at 0% for new POs.
* Updates cumulatively across multiple invoices.
* Reflects total progress of invoiced vs. shipped items.
* **Promised Delivery Date**\
The expected delivery date for the PO item.
* **Late Indicator**
Displays the number of days the delivery is late based on the **Promised Delivery Date**.
---
# 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://docs.docbits.com/administration-and-setup/settings/document-processing/module/po-shipment-order-setting.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.
