Skip to main content
Aria Knowledge Central

Manage Monetized Non-usage Data

Aria Allegro supports augmenting the Activation and Recurring services with one or more allowances and/or accumulators. As a result, you have corresponding records created in Aria Allegro. If it is for recurring services, then Aria Allegro adds the record at every billing frequency. These records are referred to as monetized non-usage records. Each billing cycle will create additional records for granting recurring allowances that will be available for consumption for the usage records in the next billing cycle.

Types of Monetized Non-Usage Record

Monetized non-usage records include:

  • One-time—created for activation services.
  • Forward-recurring—created for forward recurring charges applied at the start of the billing cycle. Each charge associates with a frequency specified in 'n' units, which can be days, weeks, months, quarters, or years.
  • Arrears-recurring—created for arrear recurring charges applied at the end of the billing cycle. Each charge associates with a frequency specified in 'n' units, which can be days, weeks, months, quarters, or years.
  • Volume discounts—future use (based on one or more accumulators).
  • Rollover—future use (for allowance rollovers).
  • True-up—future use (for unused allowance rollovers)

Dates and validity period

There are a few date/time attributes that apply for non-usage records. Key attributes are:

  1. Created date/time—Date/time when the non-usage record is created.
  2. Start and End date/time—Period covered by the non-usage record.
    1. For activation services, the start and end date/time are identical.
    2. For recurring services, they indicate the period for granting allowances or accumulators.
    3. If backdating applies, these dates reflect the backdated period.
  3. Validity period for allowances and accumulators—When an activation or recurring service associates with accumulators or allowances, each impact has a validity period defined by
    1. Valid Start date—The date from which the allowance or accumulator bucket is valid.
    2. Valid To date—The date until which the allowance or accumulator bucket is valid.
  4. For allowances or accumulators linked to a recurring service, the system creates a bucket for each cycle. Usage records with start and end dates within the bucket (≥ valid start date/time and < valid end date/time) can consume or accumulate to that bucket.
    1. If multiple allowances apply to usage records, the bucket with the earlier end date is used. If buckets share the same validity, consumption follows the pricing plan order. Note that allowances offset amounts only up to the rated amount.
    2. If multiple accumulators are configured in the price plan, the system creates a bucket for each accumulator.

View Monetized Non-usage Data

To view raw usage data and details for a file with suspended usage records, follow these steps:

  1. Click the Usage switch (Usage/Account toggle) in the navigation pane.
  2. Click the Usage Activity option to expand its sub-menu in the navigation pane.
  3. Click the Usage Data option in the navigation pane.
  4. Click the Monetized Non-Usage Data option in the activity pane.
  5. The system displays the most recent monetized usage records (one page).

This is shown in the following screenshot:

MMN-01.png

View Monetized Non-Usage Record Details

To view monetized non-usage data and details, follow these steps:

  1. Refer to “View Monetized Non-Usage Data” to access the monetized usage page.
  2. Click the Id Link for a monetized non-usage record in the field. This opens a drawer showing the record's details.
  3. The drawer displays these data sections:
    1. Header attributes—key attributes shown at the top of the drawer by default.
    2. Recurring data—This applies only to Forward/Arrears recurring transactions. By default, the recurring data bar is minimized. Key attributes include:
      1. Cycle start & end date/time—Reflects the actual cycle for the recurring charge. For example, a monthly charge for January 2025 with anniversary date 1 has cycle start date/time 2025-01-01 00:00:00 (inclusive) and cycle end date/time 2025-02-01 00:00:00 (exclusive).
      2. Applied start & end date/time—Reflects the subset of the cycle when the charge applies, e.g., for mid-cycle purchase, cancellation, suspense, or re-activation. For a mid-cycle purchase on Jan 15, 2025, applied start is 2025-01-15 00:00:00 and applied end is 2025-02-01 00:00:00.
      3. Scale—the scale applied for the recurring charge. Key points:
        1. Scale = (Applied End date/time—Applied Start date/time) / (Cycle End date/time—Cycle Start date/time)
        2. Pro-ration setting on the recurring plan adjusts the scale value as follows:
          1. NO CHARGE—scale resets to 0
          2. FULL CHARGE—scale resets to 1
          3. PRORATE—use the calculated scale value
      4. Cycle unit and duration—Reflect the recurring charge frequency. For example, a monthly forward recurring charge uses cycle unit MONTHS and cycle duration 1.
      5. Proration—The actual pro-ration setting used for scale calculation.
    3. Currency—Currently, activation and recurring charges have no currency impact in Aria Allegro, as these charges apply during invoicing in core Aria.
    4. Allowance—Displayed as a minimize/maximize bar only when an allowance is granted for activation or recurring service. Multiple allowances may appear if granted. The bar defaults to maximized.
    5. Accumulators—Displayed as a minimize/maximize bar only when one or more accumulators are added for the recurring or activation charge. For example, a minimum commitment accumulator. The bar defaults to minimized.

This is shown in the following screenshot:

MMN-02.png

Filter Attributes For The Monetized Usage Data

  1. Account Number: Filter the monetized non-usage data using the account number. This is an exact search. Alternatively, you can use the Account Switch at the top and select the account to see the monetized usage only for the account.
  2. Bill Unit Id: Filter the monetized non-usage data using the bill unit id. Allegro creates a bill unit to keep track of all the usage records for a given billing cycle. This is an exact search.
  3. Start date: Enter or select the start date to search monetized non-usage. The start date is inclusive (>= 00:00:00 hours). This is a greater than or equal to filter.
  4. End date: Enter or select the end date to search monetized non-usage. The end date is exclusive (< 00:00:00 hours). This is a less than filter.
  5. Invoice Unit Id: This is for future use if and when we can capture the invoice id from the billing application back in the monetized non-usage record.
  6. Service Type: Select the service type from the drop-down list to search monetized non-usage for that service type. This is an exact match filter.
  7. Source: Select the value from the drop-down list. Monetized non-usage records can be triggered from various sources. For example, plan instance purchased with recurring or activation services, billing job in Aria Allegro (for recurring grants), and more.

Sort Attributes for the Monetized Non-Usage Data

  • Id—Sort ascending or descending by the monetized usage record's id, not the usage id.
  • Description—Sort ascending or descending by the monetized usage record's description, shown as the service name on the invoice.
  • Start Date—Sort ascending or descending by the monetized usage record's start date.
  • End Date—Sort ascending or descending by the monetized usage record's end date.
  • Net Amount—Sort ascending or descending by the monetized usage record's net amount.
  • Service Type—Sort ascending or descending by the service type linked to the monetized usage record.
  • Bill Unit Id—Sort ascending or descending by the bill unit id linked to the monetized usage record. Allegro assigns a bill unit id for each usage billing cycle, associating monetized usage accordingly.
  • Created date—Sort ascending or descending by the created date/time of the record.
  • Item Id—Reserved for future use.
  • Service Id—Sort ascending or descending by the service id linked to the usage record, also known as client plan instance id, provisioning id, or fulfillment id.
  • Source—Sort ascending or descending by the source that created the record.
  • Type—Sort ascending or descending by the type of the monetized non-usage record.

Export Monetized Non-Usage Data

Aria Allegro allows exporting monetized usage data as XML or PDF files. To export, follow these steps:

  1. Use “View Monetized non-usage data” to access the monetized usage data.
  2. Apply mandatory and optional filters to narrow the data for export. Large files may take longer or fail to process. For large files, use other methods.
  3. Scroll right in the search results using the horizontal scroll bar.
  4. Locate the 3 vertical dots in the table header on the right and click them to open a sub-menu.
    1. Use the Select columns option to choose columns and drag/drop them to arrange the sequence. The UI updates the table view automatically. This sequence and selection is saved for future access.
    2. Click the Export option to export the file as PDF or EXCEL. The UI creates and downloads the file automatically. The view paginates rows, but the download includes all data.
  5. Locate the file in the Download folder.
TOP
  • Was this article helpful?