> For the complete documentation index, see [llms.txt](https://docs.maitredpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maitredpos.com/maitred/maitred-online-help-contents-by-module/accounting-interface/account/expenses.md).

# Expenses

### Expenses General

This option allows to set the Expenses. For each Inventory location, you have to link an account to every inventory categories. When you select this option, for each location,

**Delivery Fees**

If you are charging delivery fees in your Delivery configuration, select from the drop-down menu the appropriate account.

**Misc**

Select from the drop-down menu, the account the miscellaneous charges will be entered into.

***

### Expenses **Category**

![Button - Modify](https://documentation.payfacto.com/POS/MaitreD/Fulldoc/assets/images/MaitreDCommon/Buttons/MDButton-Modify.jpg)

Select for each inventory category used in this inventory location an account number. To configure a category, highlight it and click on the MODIFY key. Then you are allowed from the drop-down menu the account number wanted.  

**Account Number**

Select from the drop down menu the account number that represent this inventory category in the accounting package.


---

# 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.maitredpos.com/maitred/maitred-online-help-contents-by-module/accounting-interface/account/expenses.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.