> For the complete documentation index, see [llms.txt](https://docs.glesys.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.glesys.com/platform/control-panel/billing/understanding-your-invoice.md).

# Understanding your invoice

Our billing system is designed to be flexible and transparent, especially for virtual servers that may change over time. This guide explains how our billing works, how changes are calculated, and what to expect on your invoice.

### How billing works

We use a hybrid model:

**Advance billing:** You pay in advance for the coming month, based on each server’s configuration at the time of invoicing.

**Adjustments in arrears:** Any changes made after billing (upgrades, downgrades, new or deleted servers) are calculated and adjusted on your next invoice.

This ensures you're always paying fairly for the exact resources you use.

### What you’ll see on your invoice

Each invoice has two key sections:

#### **New billing period**

* Cost for all active servers and services for the coming month.
* Billed in advance.
* Example: If you’re billed monthly, you pay one month in advance for all services.

#### **Changes since last invoice**

* Adjustments for any changes during the previous month.
* Examples:

  * **Added server mid-month:** pay only for the days it was active.
  * **Deleted server mid-month:** receive a credit for unused time.
  * **Upgrades/downgrades:** billed or credited for the difference for the rest of the prepaid period.

### Example: how changes are billed

Here’s how adjustments work in practice.

#### Scenario

* A server costs 100 SEK/month when created.
* Billing is monthly.
* The customer adds, upgrades, downgrades, and deletes the server at various times.

#### February Invoice (issued February 1st)

**Includes:**

* New server created mid-January → 50 SEK (half month).
* February in advance → 100 SEK.
* **Total:** 150 SEK.

#### March Invoice (issued March 1st)

**Includes:**

* No changes in February → no adjustments.
* March in advance → 100 SEK.
* **Total:** 100 SEK.

During March, the customer makes three changes:

|            |                     |                |
| ---------- | ------------------- | -------------- |
| **Action** | **Timing in month** | **Adjustment** |
| Upgrade    | 1/4 into March      | +30 SEK        |
| Downgrade  | 2/4 into March      | -40 SEK        |
| Deletion   | 3/4 into March      | -15 SEK        |

#### April invoice (issued April 1st)

**Includes:**

* Adjustments for March:
  * +30 SEK (upgrade)
  * -40 SEK (downgrade)
  * -15 SEK (deletion)
  * **Total adjustment:** -25 SEK (credit)
* No advance charges (server was deleted in March).
* **Total:** -25 SEK (credit balance).

### Checking your billing in the control panel

In the control panel, you can view all issued invoices, see an estimate of your next invoice based on current usage and configuration, and track pending changes that will be billed or credited, with all estimates updating automatically as you make changes to servers or services.

### Need Help?

If you have questions about your invoice or need help understanding charges, contact our support team. We’re happy to assist.


---

# 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:

```
GET https://docs.glesys.com/platform/control-panel/billing/understanding-your-invoice.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.