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

# Scheduled Price Adjustments

***

## 1. Overview

Scheduled price adjustments let you decide today how a subscription's prices will change on a future date, and leave Younium to make the change when that date arrives. A typical use is an annual indexation or a contractual price increase: you agree the percentage, choose the date it takes effect, and attach it to the orders it applies to. Younium then raises the prices on those orders automatically through a daily scheduled job, without anyone having to remember to do it.

A price adjustment is defined once as a **template** — a named percentage — and then scheduled on orders. Each order carries one schedule: the date the new prices take effect, how many days before that date Younium should make the change, a note to record against the change, and whether the adjustment happens once or repeats. Within an order, every charge either receives the adjustment or is excluded from it.

When a schedule falls due, Younium applies it the same way an amendment made by hand is applied. The order gets a new version with the higher prices from the effective date, its metrics are recalculated, and a booking classified as a price adjustment is recorded. Invoicing, revenue recognition and reporting all follow from that new version. For a one-off change made immediately across many orders, see [Adjusting many orders at once](https://docs.younium.com/platform/orders.md#adjusting-many-orders-at-once) in Orders.

***

## 2. Core Concepts

### Price adjustment template

A template names a percentage change, such as *Annual indexation 2027* at 3.5%. Templates belong to the legal entity and are chosen when a price adjustment is scheduled. The percentage is read from the template at the moment the adjustment is applied, not when it is scheduled.

### Schedule

The schedule is the price adjustment set up on one order. It holds the effective date, the offset, the booking notes and the recurrence, and it applies to every charge on the order that is scheduled. An order has at most one schedule at a time, so scheduling an order again replaces the schedule it already had.

### Effective date

The date the adjusted prices apply from. The new order version that Younium creates when it applies the adjustment takes this date as its effective change date, so charges are invoiced at the old price up to it and at the new price from it.

### Offset days

How many days before the effective date Younium applies the adjustment. An offset of 30 means the new order version is created 30 days ahead of the effective date. An offset of 0 applies the adjustment on the effective date itself.

### Recurrence

A schedule is either **one-time**, applied once and then finished, or **monthly**, in which case Younium schedules the next adjustment each time one is applied. A recurring schedule has an interval in months, so an interval of 12 repeats the adjustment every year.

### Scheduling status

Every charge on a scheduled order carries a status showing where it stands, and the order carries a status summarising its charges. Both are described in [Statuses](#5-statuses).

***

## 3. Templates

A template is the reusable part of a price adjustment: a name and a percentage. The same template can be scheduled on any number of orders, and one order can use several templates when templates are set per charge.

When Younium applies an adjustment, it takes the template's percentage at that moment. Changing the percentage on a template therefore changes every adjustment that is scheduled with it and has not yet been applied. Adjustments that have already been applied are not recalculated.

| Field          | Description                                                                      |
| -------------- | -------------------------------------------------------------------------------- |
| **Name**       | Required. Up to 100 characters                                                   |
| **Percentage** | Required. The change applied to the list price of each charge it is scheduled on |
| **Is active**  | Whether the template is active                                                   |

> **Note on deleting templates:** A template cannot be deleted while any charge is scheduled with it or has been adjusted with it. A template that is the **Default Template** in the settings can be deleted, and the default is then cleared.

### Settings

| Setting              | Description                                                            | Default |
| -------------------- | ---------------------------------------------------------------------- | ------- |
| **Offset Days**      | The default offset, in days, for scheduled price adjustments. 0 to 365 | 30      |
| **Default Template** | The default template for scheduled price adjustments                   | None    |

***

## 4. Scheduling a Price Adjustment

A price adjustment is scheduled on an order in one of three ways.

| Choice                         | What happens                                                                                                            |
| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------- |
| **One template for the order** | Every eligible charge on the order is scheduled with the same template                                                  |
| **Template per charge**        | Each eligible charge is either given its own template or excluded. Every eligible charge must be given one or the other |
| **Exclude the order**          | Every charge on the order is excluded, and no adjustment is scheduled                                                   |

Whichever way it is set, an order that is scheduled needs a template, an effective date and an offset. Booking notes are optional. An excluded order carries none of these: excluding an order clears any schedule it had.

**Which orders can be scheduled.** A price adjustment is scheduled on the current version of an order, and the order must have at least one charge. Cancelled and deleted orders cannot be scheduled. Draft orders can be scheduled once they have been saved, because they may be activated before the adjustment falls due. A draft that is open for editing cannot be scheduled until the edit is saved. A draft must have been activated by the time the adjustment falls due for it to be applied.

**Which charges take part.** Four kinds of charge never receive a scheduled price adjustment, and Younium leaves them out without reporting an error: one-off charges, charges on stock products, usage charges priced with the **Rated** model, and charges that end on or before the effective date.

A charge counts as ending when it has a specific end date, or when it ends on a milestone that has already been activated. A charge that ends on a milestone not yet activated always takes part.

**Scheduling many orders at once.** The same schedule can be set on up to 100 orders in one go. Each order is scheduled on its own, so an order that cannot be scheduled reports its own error and does not stop the others. Individual charges can also be scheduled or excluded across many orders in one go, up to 500 charges on up to 100 orders. This works only on orders that already have a pending schedule: each charge is given a template or excluded, and the order's effective date, offset, booking notes and recurrence stay as they are. The schedule can also be set from a file, through the Data Management Tool's order Edit. See [Scheduling from a file](#scheduling-from-a-file) below.

**Removing a schedule.** Removing the price adjustment from an order returns every charge on it to *Not scheduled*, including charges that have already been adjusted. The prices already changed by an applied adjustment stay as they are.

### Settings

These fields are set when the price adjustment is scheduled. The labels below are the ones Younium gives them on the order, and the names of the price adjustment columns in the Data Management Tool.

| Setting                                           | Description                                                                                        | Default   |
| ------------------------------------------------- | -------------------------------------------------------------------------------------------------- | --------- |
| **Price adjustment template**                     | The template scheduled on the order                                                                | —         |
| **Price adjustment template per charge**          | If checked, the template is set per charge instead of one for the whole order                      | Unchecked |
| **Price adjustment effective date**               | The date the adjusted prices apply from                                                            | —         |
| **Price adjustment offset days**                  | Days before the effective date when the adjustment is applied. 0 to 365                            | —         |
| **Price adjustment booking notes**                | Recorded on the booking when the adjustment is applied. Up to 2,000 characters                     | Empty     |
| **Price adjustment recurrence**                   | Whether the adjustment is applied once or rescheduled after every application                      | One-time  |
| **Price adjustment recurrence interval (months)** | Months between two applications of a recurring adjustment. 1 to 60. Empty for one-time adjustments | Empty     |
| **Exclude order from price adjustment**           | If checked, all charges on the order are excluded                                                  | Unchecked |

On each charge, **Scheduled price adjustment template** shows the template the charge is scheduled with, and **Excluded from price adjustment** shows whether it is excluded.

### Scheduling from a file

The Data Management Tool's order **Edit** offers the order fields above as columns, and two more at charge level, so a schedule can be set, changed or narrowed on many orders from one file, down to individual charges. See [Data Management Tool](https://docs.younium.com/platform/data-management-tool.md) for how a file is mapped and run.

| Column                             | Level  | Effect                                                                                                                                                    |
| ---------------------------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Excluded from price adjustment** | Charge | *true* excludes the charge from the order's price adjustment. *false* schedules it                                                                        |
| **Price adjustment template**      | Charge | Schedules the charge with this template, which overrides the order's template for that charge. Using it turns on **Price adjustment template per charge** |

A charge is identified by its **Order Product Charge** reference on the row, and each charge can appear on only one row per order. A row refers only to charges on that order.

**Columns left out keep their current value.** A file does not have to repeat the whole schedule. A row that gives only a new **Price adjustment effective date** keeps the order's template, offset days, booking notes, recurrence and per-charge exclusions. A row that carries none of the price adjustment columns leaves the order's schedule unchanged.

**Charges not listed on the row.** Charges that the file does not mention keep the status they have: a charge already excluded stays excluded, and a charge already scheduled stays scheduled. When the row also gives an order-level **Price adjustment template**, charges with no status yet are scheduled with it, and charges already scheduled take it, unless the row gives them a charge-level template of their own.

**What a row must add up to.** Once the file's values are combined with the order's current schedule, every charge that ends up scheduled needs a template, and the order needs an effective date and offset days. If any is missing, the row is refused. **Price adjustment recurrence interval (months)** can only be given when **Price adjustment recurrence** is *Monthly*, and a monthly recurrence needs an interval. **Exclude order from price adjustment** set to *true* excludes the whole order and overrides every other price adjustment column on the row.

The price adjustment columns cannot be cleared from a file. To remove a schedule, remove it from the order.

***

## 5. Statuses

Each charge on an order that has been scheduled carries a status, shown as **Scheduled price adjustment status**.

| Status            | Meaning                                                                                              |
| ----------------- | ---------------------------------------------------------------------------------------------------- |
| **Not scheduled** | The charge has no adjustment waiting. A charge that has never been scheduled counts as not scheduled |
| **Scheduled**     | The charge will be adjusted with its template when the schedule falls due                            |
| **Applied**       | The adjustment has been made to the charge                                                           |
| **Excluded**      | The charge has been deliberately left out of price adjustments                                       |
| **Cancelled**     | The order was cancelled, and its adjustment with it                                                  |

The order's own status summarises its charges, and follows these rules in order:

| Order status      | When                                                               |
| ----------------- | ------------------------------------------------------------------ |
| **Scheduled**     | At least one charge is scheduled                                   |
| **Applied**       | No charge is scheduled and at least one has been adjusted          |
| **Cancelled**     | Every charge is cancelled                                          |
| **Excluded**      | Every charge is excluded                                           |
| **Not scheduled** | Anything else, including an order with no scheduled charges at all |

When an order's status becomes *Excluded*, *Not scheduled* or *Cancelled*, its effective date, offset, booking notes and recurrence are cleared. An applied order keeps them, so it remains visible what was applied and when.

The **Not scheduled price adjustments** field on charges is checked for every charge that is not scheduled, including charges that have never had a schedule. It is the simplest way to find charges that an adjustment has not yet been planned for.

***

## 6. Applying the Adjustment

### When it is applied

Due adjustments are applied by the scheduled job **Apply Scheduled Price Adjustments**, which each legal entity sets up for itself and runs once a day. A schedule falls due when the date is on or after its effective date less its offset days, with dates evaluated in UTC. A schedule whose effective date is already in the past is applied the next time the job runs.

> **Note on the scheduled job:** Without the **Apply Scheduled Price Adjustments** job, no price adjustment is ever applied automatically. Schedules stay *Scheduled* indefinitely, however far past their effective date. Every legal entity that uses scheduled price adjustments needs the job set up and active, repeating once a day.

An adjustment can also be applied at once, without waiting for the scheduled job. This can be done on one order, or on up to 1,000 orders together. A bulk application runs in the background, order by order, and records each failure against the order that caused it.

### What it changes

Applying a schedule adjusts every scheduled charge on the order together, in one change.

| What               | Effect                                                                                                                   |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------ |
| **Order**          | A new version is created, with the effective date as its effective change date                                           |
| **List price**     | The list price of every price tier on each scheduled charge rises by the template's percentage of its current list price |
| **Price**          | Recalculated from the new list price. Each tier keeps its discount percentage, so the price moves by the same percentage |
| **Price adjusted** | The charge's **Price adjusted** date is set to the date the adjustment was applied                                       |
| **Booking**        | Recorded with the change type *Price adjustment*, carrying the schedule's booking notes                                  |
| **Status**         | Each adjusted charge becomes *Applied*                                                                                   |

Charges that are not scheduled, are excluded or no longer take part are carried to the new version unchanged. A tier whose list price is zero stays at zero.

> **Note on the effective date and the application date:** The **Price adjusted** date on a charge is the day Younium made the change, not the effective date. With an offset of 30 days, a schedule whose new prices apply from 1 January falls due on 2 December, and that is the date its charges show as **Price adjusted** when the scheduled job applies it.

Once the new version exists, it behaves like any other order version. It is invoiced, recognised and reported from the effective date, and it can be reverted. See [Orders](https://docs.younium.com/platform/orders.md) for how versions and change orders work.

### When it cannot be applied

An adjustment that falls due is not applied when:

| Situation                                                 | Outcome                                        |
| --------------------------------------------------------- | ---------------------------------------------- |
| The order is a draft                                      | Not applied. The order must be activated first |
| The order has been cancelled or deleted                   | Not applied                                    |
| No charge on the order is still scheduled and taking part | Not applied                                    |

Every automatic and bulk application is written to the order's log, as *Automatic scheduled price adjustment application* or *Bulk scheduled price adjustment application*. A failed attempt is logged as *Failed automatic scheduled price adjustment application* or *Failed bulk scheduled price adjustment application*, together with the reason. A schedule that could not be applied stays scheduled.

***

## 7. Recurring Adjustments

A monthly schedule repeats itself. Each time Younium applies it, it schedules the next adjustment on the new order version, with:

| Carried forward                                             | Value                                                              |
| ----------------------------------------------------------- | ------------------------------------------------------------------ |
| **Effective date**                                          | The previous effective date plus the recurrence interval in months |
| **Offset days**, **booking notes**, **recurrence interval** | Unchanged                                                          |
| **Template**                                                | Each charge keeps the template it was adjusted with                |

Because each adjustment is a percentage of the list price at that moment, a recurring adjustment compounds. A 3% yearly adjustment on a list price of 100 gives 103 after the first year and 106.09 after the second.

Only charges that were adjusted continue into the next occurrence, and only if they still take part on the next effective date. A charge that ends before that date stays *Applied* and drops out of the recurrence. When no charge on the order takes part any longer, the recurrence ends. Charges that were excluded stay excluded.

***

## 8. When the Order Changes

A schedule follows the order through its life. When an order gets a new version for another reason, Younium carries the schedule across.

| Change to the order                                   | Effect on the schedule                                                                                                                                                                                               |
| ----------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Amendment**                                         | The schedule moves to the new version. Charges that were changed keep their status. Charges that were removed lose theirs. New charges are added as *Not scheduled*, or as *Excluded* if the whole order is excluded |
| **A charge now ends on or before the effective date** | The charge is dropped from the schedule. A charge that has already been adjusted is kept as *Applied*                                                                                                                |
| **Cancellation of the whole order**                   | Every charge becomes *Cancelled* and the schedule's dates are cleared                                                                                                                                                |
| **Reactivation of a cancelled order**                 | Every charge returns to *Not scheduled*. The adjustment must be scheduled again                                                                                                                                      |
| **Revert to the previous version**                    | The schedule moves back to the previous version. Charges with no counterpart there are dropped                                                                                                                       |
| **Deletion of the order**                             | The schedule is deleted                                                                                                                                                                                              |

> **Note on charges added after scheduling:** A charge added to an order that already has a schedule is not scheduled automatically, even if every other charge on the order is. To include it, schedule the order again.

***

## 9. Permissions

Access to scheduled price adjustments is controlled by the **Schedule Price Adjustment** permission group in role settings, together with the existing order permissions. The System administrator role receives the new permissions automatically. Other roles receive them only when they are granted in role settings.

| Permission                                    | What it allows                                                                                             |
| --------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| **View schedule price adjustment settings**   | View the settings and open templates                                                                       |
| **Update schedule price adjustment settings** | Change the settings, and create, edit and delete templates                                                 |
| **Access schedule price adjustment overview** | Use the overview to schedule, exclude, update templates for and apply price adjustments across many orders |

On an individual order, the order permissions apply as follows.

| Action                                                                                                   | Required permissions                                            |
| -------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- |
| View an order's schedule, and read the default settings shown on the order and in the scheduling dialogs | View orders                                                     |
| Schedule, remove or apply a price adjustment on one order, or schedule individual charges                | Update orders                                                   |
| Schedule, exclude, update templates for or apply price adjustments across many orders                    | Update orders **and** Access schedule price adjustment overview |

> **Note on default settings:** The order and the scheduling dialogs read their defaults, such as the offset and default template, with the View orders permission alone. Users who schedule adjustments therefore do not need permission to view the settings.


---

# 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.younium.com/platform/scheduled-price-adjustments.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.
