> For the complete documentation index, see [llms.txt](https://docs.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pakk.io/suppliers-and-purchasing/purchase-orders/invoicing-and-payment.md).
# Invoicing and Payment
### Invoicing
Invoicing works in an identical way to *Sales Orders*: there is no concept of `Partially Invoiced`; Purchase Orders are either `Fully Invoiced` or `Not Invoiced`. A Purchase Order is invoiced as soon as an 'Invoic' date is set. There are many more fields on the 'Billing' tab of a Purchase Order than on a Sales Order to reflect the larger number of pieces of information that one normally needs to log on a supplier invoice: like 'invoice ref', the supplier's legal billing details and payment terms.
Invoicing a Purchase Order will make your balance with that Supplier **go up**.
#### Payments
Again, these work pretty much exactly in the same way as *Sales Orders*. You can either manually create Payments from internal *Accounts* or you can quickly record a payment for the whole invoiced amount (or remaining amount if some payments have already been made) by using the *Payment* action button. Purchase Orders can have the status `Not Paid`, `Partially Paid` and `Fully Paid`.
Recording payments on a Purchase Order will make your balance with that Supplier **go down**.
---
# 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://docs.pakk.io/suppliers-and-purchasing/purchase-orders/invoicing-and-payment.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.