> For the complete documentation index, see [llms.txt](https://docs.rtkdata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rtkdata.com/reseller-hub/billing.md).

# Reseller Billing: Monthly Collective Invoice

How RTKdata bills resellers: one bill per month, tier discounts, the upcoming bill, payment status, online payment, PDF and CSV exports, price snapshots and what happens when a bill is overdue.

RTKdata bills you, not your customers. However many licenses you provision and whatever terms they run on, you receive **one bill per month**.

![The billing page](https://3957820804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJflLSSoC9TU9MkwT5lbC%2Fuploads%2Fgit-blob-e43beff49625d0f9896a67efa810368846c3a151%2Freseller-hub-billing.png?alt=media)

***

## The four numbers at the top

| Card                    | What it means                                                                                                                                                                     |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Current Month**       | New licenses, renewals and upgrades from this month that are not on a bill yet, before VAT. If you are billed in another currency, an estimate in that currency is shown under it |
| **Most Recent Bill**    | The last billing period issued, with its amount                                                                                                                                   |
| **Next Payment Due**    | The due date and amount of your oldest unpaid bill. Bills are due 30 days after issue, and the card turns red once one is overdue                                                 |
| **Outstanding Balance** | Everything issued and not yet paid                                                                                                                                                |

***

## The upcoming bill

The **Upcoming bill** card (marked **Draft**) shows this month's charges before the bill is issued: every license, what the charge is for, the customer, the period, the list price and the amount after your discount. Its footer gives the **Net total, before VAT** and an estimate in your billing currency.

What lands on a bill:

* A **new license** is charged in full in the month it goes live.
* A **trial** costs nothing, and is charged in full in the month it converts to a paid license.
* A **renewal** is charged in the month it renews.
* An **upgrade** is charged in the month you make it, see [How an upgrade is charged](/reseller-hub/licenses.md#how-an-upgrade-is-charged).

The month closes on its last day, and the bill is issued on the first of the next month.

***

## Tier discounts

Every bill applies the discount of the tier your **active paid licenses** reach on the day the bill is issued. The more licenses you have running, the higher the tier. The **Conditions** card on the dashboard shows your current tier, your discount, your base price, and how many more licenses take you to the next tier.

Because the discount is worked out when the bill is issued, the Upcoming bill card always shows it as an estimate.

***

## History

Each row is one billing month. The table shows the period (**Bill**), **Issued On**, **Payment Received** and **Status**, and a row expands to show its charges. Overdue bills sort to the top. Search covers period, customer and mountpoint, and **Status** filters the list.

| Status      | Meaning                                                                  |
| ----------- | ------------------------------------------------------------------------ |
| **Paid**    | Payment received                                                         |
| **Open**    | Issued, not yet due                                                      |
| **Overdue** | Past the due date, see [When a bill is overdue](#when-a-bill-is-overdue) |

Three actions sit on every row:

* **Pay online** - opens the secure hosted payment page for that bill. It is greyed out once the bill is paid
* **Download invoice** - the PDF
* **Export CSV** - the charges, for your own bookkeeping

Tick several rows and use **Export N as CSV** to export them together in one file. If RTKdata has set you up for bank transfer, the bank details are printed on the invoice PDF.

Invoices from the previous RTKdata reseller portal are listed in their own card below the history, with **Pay online** for any that are still open.

***

## An individual bill

![An invoice detail page](https://3957820804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJflLSSoC9TU9MkwT5lbC%2Fuploads%2Fgit-blob-d24af4cf101e43b045939fd95af7a39c0a92691f%2Freseller-hub-invoice-detail.png?alt=media)

**Invoice Information** gives the period, the status, the issue and payment dates, the net amount, the discount applied, the VAT and the total. If you are charged in a currency other than US dollars, it also shows the amount charged in your currency and the exchange rate used: bills are kept in US dollars and converted at the European Central Bank rate of the day before issue.

**Charges** lists every line on the bill: the license, what the charge is for, the customer, the period, the list price and the amount.

**Contact support** on the same page raises a question about that specific bill, so you do not have to restate which one you mean.

***

## Price snapshots

> A price list change never affects a bill you already have.

Each license keeps the **list price** it was sold at as a snapshot. Price list versions are effective dated, and once a version is activated it cannot be edited.

In practice this means:

* A running license keeps its list price for its whole term. Your tier discount is applied on top on each bill.
* A new price list applies to licenses provisioned after it takes effect, and to renewals that change the data streams or the term, and to upgrades. These become the license's new snapshot.
* Re-downloading an old invoice always produces the same figures.

***

## When a bill is overdue

An unpaid bill moves your account along a fixed reminder ladder, counted from the due date:

| Days overdue | What happens                                                                                                   |
| ------------ | -------------------------------------------------------------------------------------------------------------- |
| **7**        | **Payment reminder**. Nothing is blocked yet                                                                   |
| **14**       | **Credit hold**. No new licenses and no new trials                                                             |
| **30**       | **Renewals blocked**. Renewals and auto renew stop as well                                                     |
| **60**       | **Service cut pending**. RTKdata reviews the account and may suspend running licenses. This is never automatic |

Each stage shows as a banner on your dashboard and arrives as a notification. Paying the outstanding bill lifts every restriction.

***

## Billing issues on a customer

The **Billing** column on the customer list, and the **Billing Issues** tile above it, flag customers with at least one suspended or expired license. Opening the customer shows which one.

***

## Next

* [Licenses & Provisioning](/reseller-hub/licenses.md) - what gets billed and when
* [Procurement & Invoicing](/commercial/procurement-and-invoicing.md) - VAT and billing on the commercial side


---

# 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.rtkdata.com/reseller-hub/billing.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.
