> For the complete documentation index, see [llms.txt](https://docs.datacake.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datacake.de/organization/billing/unused-time-and-remaining-time-in-invoices-prorations.md).

# Unused time and Remaining time in Invoices (Prorations)

The following documentation describes the meaning of "Remaining time on..." and "Unused time on..." inside Stripe generated invoices.

The subscriptions are billed in a cyclic way. This means that customers that created a subscription (created devices on the platform) will always be billed the same day of the creation.

However, changes to a subscription in the middle of the billing period, such as upgrading or downgrading can result in prorating charges. For example, if a customer upgrades from the Light subscription (1 € per month per device) to the Standard subscription (3 € per month per device), they’re charged prorated amounts for the time spent on each option.

Assuming the change occurred halfway through the billing period, the customer is billed an additional **1 €**: -0.5 € for unused time on the initial price, and 1.5 € for the remaining time on the new price.

The prorated amount is calculated as soon as the API updates the subscription. The current billing period’s start and end times are used to calculate the cost of the subscription before and after the change.


---

# 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.datacake.de/organization/billing/unused-time-and-remaining-time-in-invoices-prorations.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.