> For the complete documentation index, see [llms.txt](https://academy.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.pakk.io/school-of-erp/practical-erp-workflow-examples/purchase-to-pay-process.md).

# Purchase-to-Pay Process

The purchase-to-pay process in an ERP system covers the entire procurement cycle, from placing a purchase order to receiving goods and paying suppliers. This process ensures that businesses manage their procurement activities efficiently and maintain good relationships with suppliers.

**Steps in the Purchase-to-Pay Process:**

1. **Create a Purchase Order:** A purchase order is generated based on demand planning and sent to the supplier.
2. **Receive Goods:** The supplier delivers the goods, and the ERP system updates inventory based on the goods received.
3. **Invoice Matching:** The supplier’s invoice is matched with the purchase order and goods receipt to ensure accuracy.
4. **Make Payment:** The invoice is processed for payment, and accounts payable is updated to reflect the payment made.

<figure><img src="https://2730446929-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcGTthTPJX2LiOOtMQ0VH%2Fuploads%2FpRSWxpB5vCbPI6XMd2gX%2FClipboard_10-18-2024_10.jpg?alt=media&amp;token=aa68d512-e118-4909-8c75-d76c039284f4" alt=""><figcaption><p>Pakk has built-in views for handling Purchase Order at different stages. They are fully customisable, and you can create your own too!</p></figcaption></figure>


---

# 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://academy.pakk.io/school-of-erp/practical-erp-workflow-examples/purchase-to-pay-process.md?ask=<question>&goal=<user_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.
