> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/order-intake-cockpit/cockpit-views/upload-document.md).
# Upload Document
Upload purchase order PDF files in the Order Intake Cockpit to start extraction, validation, and order-intake processing.
Use **Upload Document** when you receive an order in a PDF file and want the system to extract data from the document and process it. You can drag and drop or browse files in the upload area. There are two things validated: the file format and the maximum file size.
After the upload, processing is triggered and the **Order Intake** value stream starts. You can track progress and outcomes under [Documents](/order-intake-cockpit/cockpit-views/documents.md) and in the [Value Stream Modeller](https://developer.emporix.io/vsm-guides/) by checking the related value stream status.
Upload document
---
# 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://developer.emporix.io/order-intake-cockpit/cockpit-views/upload-document.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.
