> For the complete documentation index, see [llms.txt](https://docs.adminremix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adminremix.com/core/fines/creating-invoices-for-fines.md).
# Creating Invoices for Fines
You can now create an invoice for your fines.
1. Set up your Header for your invoices. You will do this under "Settings > Core", it only needs to be completed once.
2. Select the person or people who you want to create an invoice for (all fines will go into one invoice. Only use multiple people if creating a family invoice). You can create an invoice for 1 person with multiple fines as well. Once you've selected all of the fines, click the "+ > Create Invoice".
3. If you've selected multiple people, chose the person you want to create an invoice for.
4. You can choose to add customer details if you would like. **\*You will have to manually do this each as we do not keep student addresses in our system.**
5. If you would like to add a due date the date will automatically be put in the footer of the invoice. You can add a note if desired.
6. Click "Create" you will be automatically directed to the "Invoice" page.
7. Click on the "Download" button under "Actions" to download the invoice and send or print.
---
# 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://docs.adminremix.com/core/fines/creating-invoices-for-fines.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.
