# Billing

Billing administration tasks.

# Tenants Dashboard

Review tenant balances, usage exposure, and billing state.

Use **Admin > Tenants Dashboard** to manage tenants dashboard.

This page is a starting point for administrators: review existing records, add only the objects needed by the deployment, and keep names consistent across tenants, routing, and provisioning.

## Typical Workflow

1. Open the menu entry and confirm whether the record already exists.
2. Create or edit the record with a descriptive name and only the required options first.
3. Save the record and reopen it to verify the stored values.
4. Check dependent objects before deleting anything that may be used by routing, billing, provisioning, or reporting.

## Documentation Example

For documentation and testing, use names prefixed with **Docs Demo**. Existing PBX nodes should be reused as examples; do not create additional nodes unless the deployment actually requires them.

# Providers Dashboard

Review provider balance and traffic indicators.

Use **Admin > Providers Dashboard** to manage providers dashboard.

This page is a starting point for administrators: review existing records, add only the objects needed by the deployment, and keep names consistent across tenants, routing, and provisioning. The source form exposes these main blocks or fields: From, To.

## Typical Workflow

1. Open the menu entry and confirm whether the record already exists.
2. Create or edit the record with a descriptive name and only the required options first.
3. Save the record and reopen it to verify the stored values.
4. Check dependent objects before deleting anything that may be used by routing, billing, provisioning, or reporting.

## Documentation Example

For documentation and testing, use names prefixed with **Docs Demo**. Existing PBX nodes should be reused as examples; do not create additional nodes unless the deployment actually requires them.

## Main Fields

<table id="bkmrk-field-or-blockpurpos"><thead><tr><th>Field or block</th><th>Purpose</th></tr></thead><tbody><tr><td>From</td><td>Review this value in relation to the object being configured and the tenant or system scope where it is used.</td></tr><tr><td>To</td><td>Review this value in relation to the object being configured and the tenant or system scope where it is used.</td></tr></tbody></table>

# Outbound Call Rates

Maintain outbound rate tables used to price calls.

Use **Admin &gt; Outbound Call Rates** to manage outbound call rates.

This page is a starting point for administrators: review existing records, add only the objects needed by the deployment, and keep names consistent across tenants, routing, and provisioning.

## Typical Workflow

1. Open the menu entry and confirm whether the record already exists.
2. Create or edit the record with a descriptive name and only the required options first.
3. Save the record and reopen it to verify the stored values.
4. Check dependent objects before deleting anything that may be used by routing, billing, provisioning, or reporting.

## Documentation Example

For documentation and testing, use names prefixed with **Docs Demo**. Existing PBX nodes should be reused as examples; do not create additional nodes unless the deployment actually requires them.

# Inbound Call Rates

Maintain inbound rate tables used for DID and inbound traffic billing.

Use **Admin &gt; Inbound Call Rates** to manage inbound call rates.

This page is a starting point for administrators: review existing records, add only the objects needed by the deployment, and keep names consistent across tenants, routing, and provisioning.

## Typical Workflow

1. Open the menu entry and confirm whether the record already exists.
2. Create or edit the record with a descriptive name and only the required options first.
3. Save the record and reopen it to verify the stored values.
4. Check dependent objects before deleting anything that may be used by routing, billing, provisioning, or reporting.

## Documentation Example

For documentation and testing, use names prefixed with **Docs Demo**. Existing PBX nodes should be reused as examples; do not create additional nodes unless the deployment actually requires them.

# Conference Rooms Rates

Maintain rates applied to hosted conference-room usage.

Use **Admin &gt; Conference Rooms Rates** to manage conference rooms rates.

This page is a starting point for administrators: review existing records, add only the objects needed by the deployment, and keep names consistent across tenants, routing, and provisioning.

## Typical Workflow

1. Open the menu entry and confirm whether the record already exists.
2. Create or edit the record with a descriptive name and only the required options first.
3. Save the record and reopen it to verify the stored values.
4. Check dependent objects before deleting anything that may be used by routing, billing, provisioning, or reporting.

## Documentation Example

For documentation and testing, use names prefixed with **Docs Demo**. Existing PBX nodes should be reused as examples; do not create additional nodes unless the deployment actually requires them.