> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/classes/admin/costs-and-controlling.md).

# Costs and controlling

{% hint style="info" %}
Walkthrough goes here.
{% endhint %}

Cost management adds up what your active services actually cost and sorts it by cost center, so you can answer what a department or a site spends without exporting anything first.

The chain behind it is worth understanding. A service carries a cost center, the cost center carries a billing address. Order a printer for your site in Czechia and it lands on that location's cost center, which is attached to the billing address used for invoicing there.

Which cost center applies depends on the primary context. Assigned to an employee, the employee's applies. Booked on a location, the location's applies. It is a default, not a rule, and you can always override it.

For accounting, the useful export is not the full list but the changes. Resources move between cost centers when devices are stored and handed out again, and the change export gives finance only that delta.

### Read more

{% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/08BySRpPiMBfb88YR04F" %}
[Cost Management](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/controlling/cost-management)
{% endcontent-ref %}

{% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/IOtTeRAOu37YoBiDvbLk" %}
[Billing adresses & Cost Centers](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/controlling/billing-adresses-and-cost-centers)
{% endcontent-ref %}

### Next

The last step of the lifecycle is getting equipment back: [Offboarding employees](/classes/admin/offboarding-employees.md).


---

# 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://hub.equipme.io/classes/admin/costs-and-controlling.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.