> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Managing Billing Packages

> Create, edit, activate, and delete volume and maintenance Billing Packages from the Midaz Console to set the periodic charges that Billing Runs calculate.

A **Billing Package** sets a periodic charge in the [Fees Engine](/en/products/midaz/fees/console/fees-engine-overview). A package has one of two types:

* **Volume**: charges per number of events in the period. It supports price tiers, a free quota, and discounts.
* **Maintenance**: charges a fixed amount from each target account every period.

<Note>
  Enable the Fees Engine in [Midaz module settings](/en/platform/console/plugin-settings) before you use this page.
</Note>

## Accessing the Billing Packages page

***

In the Midaz Module sidebar, expand **Fees Engine**. Select **Billing Packages**. The page lists the packages of the Ledger that you select in the organization switcher.

The list shows the **Name**, **Type**, **Asset**, and **Status** of each package. Use the **Type** filter to show Volume or Maintenance packages.

From the list, you can:

* Turn the **Status** switch on or off to activate or deactivate a package.
* Select **Details** in the row menu to see the package configuration.
* Select **Edit** in the row menu to change the package.
* Select **Delete** in the row menu to delete the package. The Console asks you to confirm.

## Creating a Billing Package

***

<Steps>
  <Step title="Choose the type">
    Click **New Package**. In **Choose the billing type**, select **Volume Package (Tiered)** or **Maintenance Package (Flat Fee)**.
  </Step>

  <Step title="Fill in the basic information">
    In **Type & Information**, enter the **Package Name** and an optional **Description**. Select the **Asset Code**. The package uses the Ledger that you select in the organization switcher.
  </Step>

  <Step title="Configure the package">
    In **Configuration**, set the fields for the package type. The next two sections describe these fields.
  </Step>

  <Step title="Review and save">
    In **Review**, check the summary. To change a section, use its edit button to go back to that step. Then select **Save**.
  </Step>
</Steps>

A new package is active when you create it. The next billing run includes it.

You can change the type until you save the package. If you change it after you fill in **Configuration**, the Console discards the **Configuration** data.

## Volume package fields

***

| Section | What you set |
| - | - |
| **Event Filter** | The **Transaction Route** that defines which transactions the package counts, and the **Transaction Status** to count: **Approved** or **Pending**. |
| **Pricing Model** | **Tiered**: events fill the tiers in order, and each tier has its own unit price. **Flat Tier**: one unit price applies to every event. |
| **Price Tiers** | For **Tiered**, each row has **From (min)**, **To (max)**, and **Unit Price**. Each tier starts at the quantity after the maximum of the previous tier. The last tier has no maximum. For **Flat Tier**, you set one unit price. |
| **Free Quota** | For **Tiered**. The package does not charge the first N events in the period, where N is the quota. |
| **Progressive Discounts (optional)** | For **Tiered**. Each discount sets a percentage that applies from a starting quantity. Enter the discounts in ascending order. |
| **Debit and Credit Accounts** | The **Debit Account (alias)** and the **Credit Account (alias)**. Both are required. |
| **Calculation Preview** | The charge for sample event counts, from the tiers, the free quota, and the discounts. |

## Maintenance package fields

***

* **Fee Amount**: the amount that the package charges from each target account every period.
* **Target Accounts**: the accounts to charge.
  * **By Segment**: the accounts in the selected segment.
  * **By Portfolio**: the accounts in the selected portfolio.
  * **Account List**: account aliases that you type, or that you upload in a UTF-8 CSV file with an `accountAlias` column.
* **Credit Account (alias)**: the account that receives the charged amounts.

An account list can have at most 100 aliases. When you create the package, Midaz checks that each alias exists in the Ledger. If an alias does not exist, Midaz refuses the package.

## Editing a Billing Package

***

Select **Edit** in the row menu. You can change the **Package Name** and the **Description**. The type, the asset, and the **Configuration** fields do not change after creation.

To stop a package from charging, turn its **Status** switch off. Billing runs use active packages only.

## Where to go next

***

<Columns cols={2}>
  <Card title="Billing Runs" icon="receipt" horizontal href="/en/products/midaz/fees/console/billing-runs">
    Preview the fees for a period before you apply them.
  </Card>

  <Card title="Fees Engine overview" icon="gauge" horizontal href="/en/products/midaz/fees/console/fees-engine-overview">
    Understand how the Fees Engine, packages, and rules fit together.
  </Card>
</Columns>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.