> 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.

Pakk has built-in views for handling Purchase Order at different stages. They are fully customisable, and you can create your own too!

--- # 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://academy.pakk.io/school-of-erp/practical-erp-workflow-examples/purchase-to-pay-process.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.