# Subscriptions

Subscriptions enable users to manage one-off and recurring transactions for charging non-metered services.  

* ***One-off***  Subscriptions may be used for managing server setup fees or applying a one-off correction.
* ***Recurring*** Subscriptions are typically used to charge a specific service for a certain quantity every month or every year.

Subscriptions are always applied to a leaf account on the deepest level of a [**Report** ](/3.5.4/data-pipelines/reports.md)definition.

### Creating a Subscription

To create a subscription, first, browse to the *Accounts > Subscriptions* menu. In the *Subscriptions* menu, it is now first required to select a *'leaf account'* (meaning: an account at the deepest level of a report definition). Once this account has been selected, a new *Subscription* can be created:

![Creating a new Subscription for a leaf account](/files/-M4nXWlrDe9ZjrVN1qNO)

When creating a new subscription, it is mandatory to first give it a name and select the **Service Category** and **Service** where this *Subscription* applies to:

![Selecting the Service](/files/-M4nYHLhKZnoDmA2WZRI)

Once a *Service* has been selected, depending on the type of *Service*, you are either free to fill in a customer *Subscription* **Rate** and optional **Cost**. If this service has already rates configured in Exivity, it will automatically show and use those:

![Providing custom rates for a Subscription](/files/-M4nYpIDDJyasab_YAog)

Next the Interval section will be required to fill in. First provide the *Subscription Type*, which can be either a **Recurring** subscription or a **One-off** transaction. In the case of a **Recurring** subscription, it is required to provide an **Interval** of *Daily, Monthly* or *Yearly.* This determines how often the Subscription is being charged.  Then the Subscription **Start date** needs to be set, which determines the initial charge date. Also an optional **End date** be configured. If none is provided, it will be charged until the Subscription is removed, or changed later to include an **End date**.

![](/files/-M4nZuVucIJtiFnFW-gr)

{% hint style="warning" %}
When subscribing to a *Service* which has *Manual* rates configured, the *Subscription* inheretes the rate from the Global rate revision of the subscribed *Service.* It is therefore required to have the start date of the Subscription set to an **equal or more recent date** than the oldest configured *Global Rate Revision* of the subscribed *Service.*
{% endhint %}

When creating a *Monthly* or *Yearly* Subscription, it is also required to select a **Charge day**. This determines the day of the month when the Subscription is being charged. In case of a *Yearly* subscription, it will also be required to specify a **Charge month**, to indicate which month of the year the Subscription will be charged:

![Depending on the Interval, a Chage month and/or day are required](/files/-M4nbx_w-g-80uhVEb5-)

The last step in creating the subscription is specifying a consumed **Quantity**, which should reflect the number of units being charged per interval. Optionally an [Instance](/3.5.4/reports/instances.md) **Identifier** may be specified. If none provided, it will fall back to the name of the *Subscription*. 

Click the **Create** button to create this subscription. In case you are creating a *Subscription* with a historical **Start date**, it will then be required to use the **Create - *****with preparing*** button:

![](/files/-M4nddNMCeinlncMxBt5)

In case you are creating multiple Subscriptions,  it is advisable to stack these creations to avoid having to execute **Create** - ***With preparing*** multiple times in a row.

 


---

# Agent Instructions: 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://olddocs.exivity.io/3.5.4/services/subscriptions.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.