> 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/order-to-cash-process.md).

# Order-to-Cash Process

The order-to-cash process involves everything from receiving a customer order to collecting payment. It integrates several business functions, including sales, inventory, and finance, ensuring smooth and accurate operations.

**Steps in the Order-to-Cash Process:**

1. **Receive a Sales Order:** A sales order is entered into the ERP system, which checks for stock availability.
2. **Commit Stock:** The system allocates the necessary stock to fulfill the order.
3. **Dispatch Goods:** After the order is confirmed, goods are dispatched, and the order status is updated.
4. **Generate Invoice:** Once goods are dispatched, an invoice is generated and sent to the customer.
5. **Receive Payment:** Payment is tracked in accounts receivable, and once received, the financial records are updated.

<figure><img src="https://2730446929-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcGTthTPJX2LiOOtMQ0VH%2Fuploads%2FnIINpPU5ENd1CPEPBHc0%2FClipboard_10-18-2024_11.jpg?alt=media&amp;token=a881c92d-279e-4643-9fdb-bbc93ef849f7" alt=""><figcaption><p>Pakk has built-in views for handling Sales 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/order-to-cash-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.