Skip to main content
Aria Knowledge Central

Price Plan Setup

  1. Last updated
  2. Save as PDF
  1. Supported pricing models by transaction type
  2. To view existing price plans
  3. To view details of a specific price plan
  4. Filter options for price plans
  5. Sort options for price plans
  6. To add rates to a price offer
  7. Set flat pricing model
  8. Set recurring pricing model
  9. Set recurring tiered pricing model
  10. Set transaction attribute-based pricing model
  11. Set usage attribute-based pricing model
  12. Set usage progressive tier pricing model
  13. Set usage prospective tier pricing model
  14. Set usage volume tier pricing model
  15. Set usage composite pricing model
  16. Set high water mark pricing
  17. Set unique location pricing
  18. Set first usage pricing
  19. Set minimum commitment with true-up
    1. Core Aria setup for minimum commitment
    2. Aria Allegro setup for minimum commitment
  20. Add currency, accumulator, and allowance impacts
    1. To add a currency impact
    2. To add an allowance impact
    3. To add an accumulator impact

This section describes how to navigate the Aria Allegro UI to view, filter, and configure price plans by selecting pricing models and setting rates.

Note: Aria Allegro does not allow direct creation of new price plans. Price plan shells are created automatically for each unique combination of plan, plan rate schedule, and service when those combinations are saved in core Aria. You then associate pricing models with those shells and set rates accordingly.

Supported pricing models by transaction type

The following table shows which pricing models are available for each transaction type.

The following table shows the allowed combinations for composite pricing models by transaction type.

To view existing price plans

  1. Click the Usage toggle in the navigation pane.
  2. Click Monetization in the navigation pane to expand the submenu.
  3. Click Price Plans in the navigation pane. The list displays all price plans configured for the client.

When you open a price plan, the UI displays the drawer dynamically based on the selected pricing model and transaction type. Key points to note:

  • Key attributes appear at the top of the drawer. These are the fields you must set. The shell price offer is created automatically, minimizing data entry. You select the pricing model and add rates accordingly.
  • Additional attributes appear in a collapsible More Data section.
  • The lower section of the drawer is dynamic: it changes based on the pricing model and transaction type. For example, a TIERED pricing model displays a Tiered Pricing Model section.
  • Information notes on key attributes provide context. Hover over or click a note to read details.

Two read-only attributes appear in the price offer details:

  • Billing Reference Price: Shows the price set in core Aria. Use this value as a reference when setting allowances or accumulators for activation and recurring services.
  • Non-Subscription Offer: Indicates whether the service type is Order. Aria Allegro uses non-subscription offerings (NSOs) for minimum commitment true-ups. This value is TRUE for Order-type services and FALSE otherwise.

To view details of a specific price plan

  1. Navigate to the Price Plans list as described in "To view existing price plans."
  2. Click the price plan ID link to open the drawer and manage price plan data.

Filter options for price plans

The following fields are available to filter the price plans list:

  • Price Offer Id: Filter by price offer ID. This is a case-insensitive partial match search.
  • Name: Filter by price offer name. This is a case-insensitive partial match search.
  • Billable Service Id: Search by the exact billable service ID defined in the Aria catalog.
  • Billable Service Name: Search by billable service name. This is a case-insensitive partial match search.
  • Plan Rate Schedule Id: Search by the exact plan rate schedule ID from core Aria pricing catalog.
  • Plan Rate Schedule Name: Search by plan rate schedule name. This is a case-insensitive partial match search.
  • Plan No: Search by the exact plan number assigned in core Aria catalog.
  • Plan Name: Search by plan name. This is a case-insensitive partial match search.
  • Service Type: Filter by service type using the dropdown. This is an exact match search.
  • Pricing Model: Filter by pricing model using the dropdown. This is an exact match search.
  • Status: Filter by status using the dropdown. This is an exact match search.
  • Transaction Type: Filter by transaction type using the dropdown. This is an exact match search. For usage services, the transaction type is USAGE.
  • Pricing Setup Complete: Filter for price plans where shells exist but pricing models and rates have not yet been defined. Select a Boolean value from the dropdown. This is an exact match search.
  • Non-Subscription Offer: Filter for non-subscription offering price plans. Select a Boolean value from the dropdown. This is an exact match search.
  • High-Water Mark: Filter for high water mark price offers. Select a Boolean value from the dropdown. This is an exact match search.

Sort options for price plans

You can sort the price plans list ascending or descending by: Price Offer Id, Name, Billable Service Id, Billable Service Name, Plan Rate Schedule Id, Plan Rate Schedule Name, Plan No, Plan Name, Service Type, Pricing Model, Status, Transaction Type, and Pricing Setup Complete.

To add rates to a price offer

When plan, rate schedule, and service combinations are saved in core Aria, a shell for each unique combination is created automatically in Aria Allegro. You must define rates for each shell by selecting a pricing model and configuring rates.

  1. Navigate to the Price Plans list.
  2. Use the filter fields to locate the price plan by ID, name, rate schedule, or billable service. Alternatively, set Pricing Setup Complete to False to find shells with no rates defined.
  3. Click the price plan ID link to open the drawer.
  4. In the Pricing Model field, select the desired model from the dropdown.
  5. Verify the Transaction Type field reflects the correct type. For usage services, this should be USAGE. This value updates automatically if the billable service has the correct service type.
  6. If the service includes an allowance or accumulator, note the Billing Reference Price value to use as a reference when setting those impacts.
  7. Follow the procedure for the selected pricing model:
    • Flat pricing: see "Set flat pricing model."
    • Recurring pricing: see "Set recurring pricing model."
    • Recurring tiered pricing: see "Set recurring tiered pricing model."
    • Transaction attribute-based pricing: see "Set transaction attribute-based pricing model."
    • Usage attribute-based pricing: see "Set usage attribute-based pricing model."
    • Usage progressive tier pricing: see "Set usage progressive tier pricing model."
    • Usage prospective tier pricing: see "Set usage prospective tier pricing model."
    • Usage volume tier pricing: see "Set usage volume tier pricing model."
    • Usage composite pricing: see "Set usage composite pricing model."
    • High water mark pricing: see "Set high water mark pricing."
    • Unique location pricing: see "Set unique location pricing."
    • First usage pricing: see "Set first usage pricing."
    • Minimum commitment with true-up: see "Set minimum commitment with true-up."

Set flat pricing model

  1. In the Pricing Model field, select FLAT. The Flat Pricing section appears in the drawer.
  2. Add currency, accumulator, and allowance impacts as needed. See "Add currency, accumulator, and allowance impacts."
  3. Click Save.

Set recurring pricing model

The recurring pricing model applies to recurring services. A price plan shell is created automatically in Aria Allegro for recurring services configured with an allowance or accumulator in core Aria.

  1. In the Pricing Model field, select Recurring. The Recurring Pricing Model section appears.
  2. Verify the Transaction Type field: FORWARD_RECURRING for forward charges, ARREARS_RECURRING for arrear charges.
  3. In the Recurring Pricing Model section:
    1. Confirm Recurring Unit and Recurring Frequency match the charge duration. For example, a monthly recurring charge uses MONTHS and a frequency of 1.
    2. Set Purchase Proration for mid-cycle purchases. Options are PRORATE (prorate the charge), FULL (full charge), and NO_CHARGE (no charge for a partial cycle).
    3. Set Cancel Proration for mid-cycle cancellations.
    4. Set Upgrade Proration for mid-cycle upgrades.
    5. Set Downgrade Proration for mid-cycle downgrades.
    6. If the recurring charge depends on an accumulator (for example, minimum spend true-up charges), select a Rate Unit from the dropdown of preconfigured units.
    7. Select the Advanced Billing checkbox if you want the next cycle fee applied in advance. For example, a November 1–December 1 charge can be applied on October 20 (11 days early).
  4. Add currency, accumulator, and allowance impacts as needed. See "Add currency, accumulator, and allowance impacts."
  5. Click Save.

Set recurring tiered pricing model

The recurring tiered pricing model applies to recurring services. A price plan shell is created automatically in Aria Allegro for recurring services configured with an allowance or accumulator in core Aria.

  1. In the Pricing Model field, select Recurring. The Recurring Pricing Model section appears.
  2. Verify the Transaction Type field: FORWARD_RECURRING for forward charges, ARREARS_RECURRING for arrear charges.
  3. In the Recurring Pricing Model section, complete the proration and advanced billing fields as described in "Set recurring pricing model," steps 3a–3g.
  4. In the Tiered section:
    1. In Tier Reference, select BALANCE (based on accumulator balance) or QUANTITY (for quantity tiers).
    2. If Tier Reference is BALANCE, select the Accumulator Id from the dropdown.
    3. In Tier Type, select PROGRESSIVE or PROSPECTIVE.
    4. If you select PROSPECTIVE, complete the following fields:
      • Evaluation Start: Enter the start month. For quarterly tiers, 1 defines the fixed terms January–March, April–June, July–September, and October–December.
      • Offset Months: Enter an integer to defer the pricing term, allowing resellers time to apply markups.
      • Volume Treatment: Select AVERAGE, ANNUALIZE, or AS-IS.
      • Evaluation Term Unit: Select the evaluation unit, for example QUARTERS.
      • Pricing Term Unit: Select the pricing unit, for example QUARTERS.
      • Frequency: Enter the frequency for evaluation and pricing terms, for example 1 for quarterly tiers.
    5. Click Add Tier and configure each tier:
      • Set the minimum quantity. For the first tier, enter 0. The minimum quantity is inclusive.
      • Set the maximum quantity. For the last tier, leave this empty or enter 0 (no maximum). The maximum quantity is exclusive.
      • Add currency, accumulator, and allowance impacts. See "Add currency, accumulator, and allowance impacts."
      • Repeat to add additional tiers.
  5. Click Save.

Set transaction attribute-based pricing model

The transaction attribute-based pricing model rates usage transactions based on derived attributes such as time-of-day, day-of-week, holiday, and zone. All transaction attributes support an ANY value (for example, ANYTIME, ANYDAY, ANYHOLIDAY). Always include a default row where all attribute values are set to ANY to ensure all usage records match at minimum. The engine applies the best match first; the order in which you configure transaction attribute combinations affects matching when multiple rows produce the same match quality.

  1. In the Pricing Model field, select Transaction attribute-based. The Transaction Attribute-Based Pricing Model section appears.
  2. Verify the Transaction Type field is set to USAGE.
  3. In the Transaction Attribute-Based Pricing Model section:
    1. In Time of Day, select a preconfigured time-of-day value, or select ANYTIME to match any time.
    2. In Day of Week, select a preconfigured day-of-week value, or select ANYDAY.
    3. In Holiday Name, select a preconfigured holiday, or select ANYHOLIDAY.
    4. In Select Zone, select the zone from the configured zone model. If only one zone model exists for the service type, it is selected automatically.
    5. In Pricing Zone, select the pricing zone. Zone and pricing zone are mutually exclusive: use only one. Pricing zones are useful when thousands of originating zones map to a smaller number of pricing zones. For example, calls from Germany to any EU country may share a single pricing zone.
  1. In Select Zone Unit, select the zone unit from the dropdown. The dropdown populates automatically based on the selected zone model.
  2. Add currency, accumulator, and allowance impacts for this attribute combination. See "Add currency, accumulator, and allowance impacts."
  3. To add pricing for additional transaction attribute combinations, repeat step 3.
  4. Click Save.

Set usage attribute-based pricing model

The usage attribute-based pricing model rates usage transactions based on raw attributes in the usage record. During mediation setup and file mapping, raw attributes from all sources are mapped to the Aria Allegro Usage container. When you define usage attribute-based pricing, those mapped attributes are available for selection.

The engine finds the best matching combination. When more than one section matches a usage record, the order of sections determines which is applied: the first best match takes precedence. Add a catch-all section (all attributes set to wildcard) to provide default pricing for records that do not match any specific combination. Without a catch-all, unmatched usage records are suspended.

  1. In the Pricing Model field, select Usage attribute-based. The Usage Attribute-Based Pricing Model section appears.
  2. Verify the Transaction Type field is set to USAGE.
  3. Click Add new usage attribute-based Pricing. A section appears for selecting usage attributes, values, and pricing impacts.
  4. Optionally, select a Billable Service Id from the dropdown to associate with this attribute grouping.
  5. To add usage attributes to this section:
    1. In Select Record, choose the record from the dropdown. If only the DETAIL record exists, it is selected automatically.
    2. In Select Field, choose the field from the record.
    3. The third field displays the selected field in the format Record.Field (for example, DETAIL.direction).
    4. In Value, select the value for the chosen field. To match any value, select *.
    5. Repeat steps 5a–5d to add more usage attributes to this section.
  6. Add currency, accumulator, and allowance impacts for this attribute combination. See "Add currency, accumulator, and allowance impacts."
  7. Click Add new usage attribute-based Pricing again to add additional attribute sections. The following table illustrates how matching works when multiple sections are configured:
Usage attribute 1 Usage attribute 2 Usage attribute 3 Rate
UA1 UA2 * X1
UA1 * UA3 X2
* UA2 UA3 X3
* * * X4 (catch-all)
  1. Click Save.

Set usage progressive tier pricing model

The progressive tier pricing model applies to usage transactions. Multiple tier prices can apply to a single usage record within a cycle. Tiers start at 0 and reset when the tier term resets, which typically aligns with the usage billing cycle.

  1. In the Pricing Model field, select TIERED. The Tiered Pricing Model section appears.
  2. Verify the Transaction Type field is set to USAGE.
  3. In the Tiered section:
    1. In Tier Reference, select BALANCE (based on accumulator balance) or QUANTITY (for quantity tiers).
    2. If Tier Reference is BALANCE, select the Accumulator Id from the dropdown.
    3. In Tier Type, select PROGRESSIVE. The Evaluation Start, Offset Months, Volume Treatment, Evaluation Term Unit, Pricing Term Unit, and Frequency fields are disabled and are not required for progressive tiers.
    4. Click Add Tier and configure each tier:
      • Set the minimum quantity. For the first tier, enter 0. The minimum quantity is inclusive.
      • Set the maximum quantity. For the last tier, leave this empty or enter 0 (no maximum). The maximum quantity is exclusive.
      • Add currency, accumulator, and allowance impacts. See "Add currency, accumulator, and allowance impacts."
      • Repeat to add additional tiers.
  4. Click Save.

Set usage prospective tier pricing model

The prospective tier pricing model applies to usage transactions. All usage records within a cycle are rated at a single fixed tier price determined by quantity or accumulator balance. The prospective tier cycle typically matches the usage billing cycle but can differ.

  1. In the Pricing Model field, select TIERED. The Tiered Pricing Model section appears.
  2. Verify the Transaction Type field is set to USAGE.
  3. In the Tiered section:
    1. In Tier Reference, select BALANCE or QUANTITY.
    2. If Tier Reference is BALANCE, select the Accumulator Id from the dropdown.
    3. In Tier Type, select PROSPECTIVE and complete the following fields:
      • Evaluation Start: Enter the start month. For quarterly tiers, entering 1 defines January–March, April–June, July–September, and October–December.
      • Offset Months: Enter an integer to defer the pricing term, allowing time for reseller markups.
      • Volume Treatment: Select AVERAGE, ANNUALIZE, or AS-IS.
      • Evaluation Term Unit: Select the evaluation unit, for example QUARTERS.
      • Pricing Term Unit: Select the pricing unit, for example QUARTERS.
      • Frequency: Enter the frequency for evaluation and pricing terms, for example 1 for quarterly tiers.
    4. Click Add Tier and configure each tier:
      • Set the minimum quantity. For the first tier, enter 0. The minimum quantity is inclusive.
      • Set the maximum quantity. For the last tier, leave this empty or enter 0 (no maximum). The maximum quantity is exclusive.
      • Add currency, accumulator, and allowance impacts. See "Add currency, accumulator, and allowance impacts."
      • Repeat to add additional tiers.
  4. Click Save.

Set usage volume tier pricing model

Volume tier pricing (also called bill-time rating or two-pass rating) is a special case of prospective tier pricing. All usage records in a billing cycle are rated at the same tier based on total cumulative volume. Aria Allegro determines this tier using two-pass processing:

  • First pass: Accumulates usage records. At month end, the accumulator holds the total volume used to determine the tier.
  • Second pass: Rates all usage records using the tier determined by the accumulator value from the first pass.

Key characteristics of volume tier pricing:

  • The accumulator can combine multiple usage types within a master plan instance (MPI) vertical, enabling independent tier pricing based on the total combined value.
  • Multiple accumulators can operate within an MPI vertical, each covering subsets of usage types, allowing independent tier pricing for each subset.

The following table describes how resource types are applied across the two passes:

Resource type Applied in Notes
Tier reference accumulator First pass only Accumulates total quantity for tier resolution in the second pass. Only quantity-based accumulators are supported as tier references; amount-based accumulators are not eligible.
Other quantity accumulators First or second pass Can be configured to accumulate in either pass depending on the use case.
Amount-based accumulators Second pass only Applied after the rated amount is determined in the second pass.
Quantity allowance Second pass only Applied as an offset to the rated amount during the second pass.
Amount allowance Second pass only Applied as an offset to the rated amount during the second pass.

Note: Multiple price points are not supported for volume rating (two-pass rating).

To set up volume tier pricing:

  1. In the Pricing Model field, select TIERED. The Tiered Pricing Model section appears.
  2. Verify the Transaction Type field is set to USAGE.
  3. Select the Volume Rating checkbox. This signals the billing job to perform the second pass.
  4. Complete the tier setup following the steps in "Set usage prospective tier pricing model."
  5. Click Save.

Set usage composite pricing model

The composite pricing model lets you combine two or more pricing models into a single model. You can freely combine usage attribute-based, transaction attribute-based, and tiered pricing components. There is no limit to the number of combinations you can create.

  1. In the Pricing Model field, select Composite. The Composite Model section appears.
  2. Verify the Transaction Type field is set to USAGE.
  3. In the Composite Model section, select the components to include. A composite model requires at least two selections:
    • Add Usage Attributes: Includes usage attribute-based pricing.
    • Add Transaction Attributes: Includes transaction attribute-based pricing.
    • Add Tiers: Includes tiered pricing.
  4. After making your selections, the UI adds an Index-1 section for your pricing configuration.
  5. If you selected Add Usage Attributes, configure the usage attribute fields and impacts as described in "Set usage attribute-based pricing model."
  6. If you selected Add Transaction Attributes, configure the transaction attribute fields and impacts as described in "Set transaction attribute-based pricing model."
  7. If you selected Add Tiers, configure tier settings and impacts as described in the appropriate tiered pricing model procedure.
  8. Click Save.

Set high water mark pricing

High water mark pricing bills your customer only for the usage record with the highest quantity in the billing period.

  1. In the Pricing Model field, select Tiered. The Tiered Pricing Model section appears.
  2. Verify the Transaction Type field is set to USAGE.
  3. Select the High Water Mark checkbox. This instructs billing jobs to locate the usage record with the highest quantity and apply the configured pricing to that quantity.
  1. Set Tier Reference to BALANCE and Tier Type to PROSPECTIVE.
  2. Select the Accumulator Id that tracks the high water mark value accumulated in the first pass.
  3. Configure tier rates. The example below shows a sample tier configuration for high water mark pricing.
  1. Complete the remaining price offer setup.
  2. Click Save.

Set unique location pricing

Unique location pricing applies charges based on the count of distinct attribute values in usage records for the billing period. For example, if a subscriber generates 1,000 usage records across six unique locations, this model bills for the 1,000 usage records and for the six unique locations as a separate charge. The distinct attribute can be location or any other attribute mapped to the usage record.

  1. In the Pricing Model field, select Tiered. The Tiered Pricing Model section appears.
  2. Verify the Transaction Type field is set to USAGE.
  3. Select the Volume Rating checkbox. This tells the rating engine to perform rating at end of month during the second pass, after the first pass has accumulated the required values.
  4. Set Tier Reference to BALANCE and Tier Type to PROSPECTIVE.
  5. Select the Accumulator Id that tracks location counts accumulated in the first pass.
  6. In the custom database function field, enter the function name used to evaluate unique location counts. For example, get_distinct_flex_attr1_count counts distinct values for the attribute mapped to flex-attribute-1 of the Aria Allegro Usage container object model.
  1. Configure tier rates. The tier price applies for each unique location found. The example below shows a sample tier configuration.
  1. Complete the remaining price offer setup.
  2. Click Save.

Set first usage pricing

First usage pricing applies a special charge when your customer has at least one usage record in the billing period, separate from the charge for actual usage.

  1. In the Pricing Model field, select Tiered. The Tiered Pricing Model section appears.
  2. Verify the Transaction Type field is set to USAGE.
  3. Select the Volume Rating checkbox. This tells the rating engine to perform rating at month end during the second pass.
  4. Set Tier Reference to BALANCE and Tier Type to PROSPECTIVE.
  5. Select the Accumulator Id that tracks quantity accumulated in the first pass.
  1. Configure tier rates. In the second pass, only the first usage record is rated in the first tier. The example below shows a sample configuration.
  1. Complete the remaining price offer setup.
  2. Click Save.

Set minimum commitment with true-up

The minimum commitment model guarantees revenue for the service provider and gives your customer visibility into their service usage against a committed value. If actual usage falls below the commitment value at the end of the commitment term, Aria Allegro applies the difference as a true-up charge.

Setup spans both core Aria and Aria Allegro and involves the following areas.

Core Aria setup for minimum commitment

  1. Set up a non-subscription offering (NSO) service for Aria Allegro to send the true-up when usage is below the commitment value. This controls the true-up line on the invoice or statement.
  2. To exclude a specific account from contributing usage toward the commitment, add a product field at the plan level in core Aria. When purchasing a plan, populate this field to exclude that account. All accounts count toward commitment by default; set this field only for exceptions. Note the field name you use: it is needed during Aria Allegro setup.
  3. Add a recurring fee service with the correct unit and frequency to match the commitment term. Configure the plan service to include an accumulator with advanced pricing enabled. This service links the commitment value: either as a fixed catalog value or a customized contract value entered at plan purchase: to the accumulator. For a one-time commitment, use an activation service instead of a recurring service.

Aria Allegro setup for minimum commitment

Complete the following setup in Aria Allegro. For accumulator configuration details, see Allegro Configurations: Accumulator resources.

  1. Set up two accumulators for the commitment:
    • An accumulator to hold the commitment value for the period.
    • An accumulator to track the commitment counter (actual usage), linked to the commitment value accumulator.
  1. To configure the account-specific exclusion:
    1. Navigate to Configurations > System Properties > Subscriptions.
    2. Locate the Skip Commitment Field Name property and set its value to the exact field name added at the plan product level in core Aria.
    3. Click Save. This is a one-time configuration.
  1. Configure the commitment value price offer. For the recurring or activation service that sets the commitment value accumulator, open the price offer and select the correct Accumulator Id. Set up the catalog commitment value, or use the customized contract value entered at plan purchase.
  1. Configure the commitment counter for usage price offers. For each usage price offer that should count toward the commitment, add the commitment counter accumulator as an accumulator impact. The usage price offer can use any pricing model.
  2. Configure the true-up price offer (NSO). The shell price offer for the NSO service is created automatically and shows the Non-Subscription Offer flag as TRUE. Open the price offer and complete the following:
    1. In Commitment Accumulator, select the commitment value accumulator from the dropdown. This maps the NSO offer to the correct commitment value accumulator.
    2. Click Add Currency and select the currency resource.
    3. For a monetary commitment true-up: set the amount to 1. Aria Allegro calculates the shortfall and applies 1 monetary unit per shortfall unit. For example, a $50 shortfall results in a $50 charge. Use the FLAT pricing model.
    4. For a non-monetary commitment true-up: provide a blended rate using a FLAT or tiered pricing model. For example, if the commitment is one million tokens in a quarter and the shortfall is 100,000 tokens, set a unit or tier price for the true-up rate.

The true-up applies at the end of the commitment term. The billing job in Aria Allegro applies the true-up and syncs it to core Aria as an NSO order with the true-up amount.

Add currency, accumulator, and allowance impacts

This section applies to all pricing models. It covers the configuration of rates (currency impacts) and any associated allowances or accumulators.

To add a currency impact

  1. Click Add Currency. A row for currency impact appears.
  2. The Currency field auto-populates from the rate schedule. This is the currency for the price plan shell.
  3. In Amount, enter the rate to apply.
  4. Select Flat Rate if the amount applies as a fixed charge per usage record (regardless of quantity), or leave it unselected if the amount applies per unit of quantity. For example, for a 20-minute usage record:
    • If Flat Rate is not selected and the rate is P, the rated value is 20P.
    • If Flat Rate is selected and the rate is X, the rated value is X (flat charge for the entire record).
  5. Select Skip Allowance to prevent this price point from being offset by any configured allowances. Use this for price components that should always be charged regardless of available allowance balances: for example, a flat administrative fee that coexists with a per-minute rate covered by free-minute allowances.
  6. Select Skip Accumulator to exclude this price point from accumulator tracking. Use this for charges (for example, a surcharge or penalty) that should not count toward accumulator balances such as minimum spend or volume thresholds.
  7. Click Add Currency again to add a second independent price point if needed. When multiple currency rows are configured:
    • Each price point is rated independently; all amounts are summed to produce the total charge.
    • Each price point independently controls its own rate, Skip Allowance, and Skip Accumulator flags.
    • For QUANTITY or COUNT type allowances: allowance units are consumed against each eligible price point (Skip Allowance = false). Charge negation is applied proportionally.
    • For AMOUNT type allowances: each eligible price point draws from the shared allowance balance in sequence.
    • For accumulators: the engine computes the net post-allowance charge from all price points where Skip Accumulator is false and records that amount in the configured accumulators.

Note: Multiple price points are not supported for volume rating (two-pass rating).

To add an allowance impact

  1. Click Add Allowance.
  2. For a grant (for activation or recurring services):
    1. In Allowance Id, select the allowance resource from the dropdown.
    2. In Amount, enter the allowance amount. Use the Billing Reference Price as a reference.
    3. In Allowance Impact Type, select ALLOWANCE.
    4. Repeat to add additional allowance grants.
  3. For consumption (for usage services):
    1. In Allowance Id, select the allowance resource from the dropdown.
    2. The Allowance Impact Type field auto-selects CONSUME for usage transaction types.
    3. Repeat to consume additional allowances.

To add an accumulator impact

  1. Click Add Accumulator.
  2. In Accumulator Id, select the accumulator resource from the dropdown.
  3. The Accumulate Quantity flag and Expression fields are read-only and display values from the accumulator configuration.
  4. Repeat to add additional accumulators.
TOP
  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Page type
    Topic
  2. Tags
    1. allegro
    2. rating
    3. usage