> 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/dokumentation/controlling/cost-management.md).

# Cost management

Cost management: recurring and one-time costs, forecast, analysis per service and per cost center, export of cost center changes.

**Path:** sidebar → **"Controlling" → "Cost management"**

## "By resource" tab

At the top, there are two tiles:

* **"One-time costs"** with "Recurring" and "Forecast"
* **"Recurring costs"** with "Recurring" and "Forecast"

**"Recurring"** shows the costs in the current period, **"Forecast"** the expected costs including changes that have already been requested or are upcoming.

Below is a table of all services with search, filters and **Excel export**. Columns include: "Asset ID", "Supplier", "Invoice issuer", "Service name", "Location", "Employee", departments, category, "Options", **"Cost center"**, inventory number, **"Current costs"**, **"One-time costs"**, "Offer type", **"Remaining term"**, "Extension period", "Activation date", "Status" and "Add-ons". Clicking a row opens the service's detail page.

**Typical analyses:**

* Costs of a location, department or category: via column filter.
* Expiring contracts: sort by "Remaining term". You set up email reminders under [Email notifications](/dokumentation/settings/email-notifications.md) ("Expiring services", "Upcoming contract renewal").
* Costs per supplier: "Supplier" filter.

## "By cost center" tab

(For users with company-wide access.)

For each cost center, the table shows "Description", "Manager", "Billing address", "One-time costs" and "Current costs".

### Exporting cost center changes

**"Export changes"** creates an Excel file of all cost center changes within a period (preset: start of the month to today; without a period, all changes). Columns: "Asset ID", "Inventory number", "Service name", "Change date", "Original cost center", "New cost center" (each with description), "Employee name", "Employee email", "Current costs", "One-time costs", "Service removed".

This is useful, for example, for monthly reallocation postings in financial accounting.

{% hint style="info" %}
The export shows the **current** costs of the services, not the costs at the time of the change.
{% endhint %}

**"Administration"** takes you to cost center maintenance (see [Cost centers and billing addresses](/dokumentation/organization/cost-centers-and-billing-addresses.md)).

## How do costs arise?

* A service incurs costs from its **activation** (status "Active") according to the selected offer.
* **One-time costs** are incurred once, **recurring** costs in the offer's billing cycle.
* Recorded or imported existing devices are not charged retroactively; monthly costs count from the next billing interval.
* Canceled services incur costs until the end of the contract.

## Frequently asked questions

**Why don't I see any costs?**

Your role is not allowed to see prices.

**Why does the forecast differ from the recurring costs?**

The forecast already takes into account requested orders, changes and cancellations.


---

# 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/dokumentation/controlling/cost-management.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.