> For the complete documentation index, see [llms.txt](https://documentation.opencollective.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencollective.com/collectives/managing-money/tagging-expenses.md).

# Tagging expenses

Tagging your expenses can be a useful way to show how your money is being spent:

To add a tag, go to your expense, and find the “Add Tag” button next to your expense’s invoice number (underneath the title).

You can add and edit tags when the expense is created, or at any time afterwards. This means you can create your own consistent categories, such as:

* Employees (wages and benefits)
* Contractors (invoices from suppliers/freelancers)
* Accounting (invoices, auditor fees)
* Software (subscriptions to software and SaaS products)
* Meals and Entertainment (Team lunches and client meetings, etc)
* Workspace (Home office costs or coworking expenses)
* Travel (Transportation and associated costs)
* Donations (contributions to other entities)

Decide on the best ones for you, and refine them as you go.


---

# 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://documentation.opencollective.com/collectives/managing-money/tagging-expenses.md?ask=<question>&goal=<endgoal>
```

`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.