> For the complete documentation index, see [llms.txt](https://klassdocs.gitbook.io/klassapp-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://klassdocs.gitbook.io/klassapp-documentation/docs-site/help/bursars/index.md).

# KlassApp for bursars

## KlassApp for bursars

You record fees and run payroll for one school. The account card says **Bursar**.

### Where you land

Sign in at the KlassApp login page. You open the bursar dashboard.

### Menu

In order:

* **Dashboard**
* **Fees & Payments**
* **Data Exports**
* **Holidays**
* **Payroll** — **Templates**, **Salaries**, **Payslips**, **Batch Run**

You do not see **Students**, **WhatsApp**, or **Settings**. Those stay with the [school admin](https://github.com/KlassApp-Foundation/KlassApp/tree/main/help/admins/README.md).

### Common tasks

* See payments and what the school is still owed: **Fees & Payments**.
* Record a payment: + Record Payment. The form heading is **Record Payment**. Choose Record Payment to save.
* Download figures: **Data Exports**.
* School holidays: **Holidays**.
* Pay: open **Payroll**, then the template, the salaries, the payslips, or a **Batch Run**.

Fee reminders that parents get from the school admin **Fees** page are not a separate bursar menu item. Parents can still ask **Fee Balance** on WhatsApp. See [Use KlassApp on WhatsApp](https://github.com/KlassApp-Foundation/KlassApp/tree/main/help/parents/whatsapp/README.md).

### Get help

Ask the school admin for a student who is missing from the fee list. Product questions: <community@klassapp.xyz>


---

# 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://klassdocs.gitbook.io/klassapp-documentation/docs-site/help/bursars/index.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.