Skip to main content
Aria Knowledge Central

Manage Billing Aggregate Usage Data

This section explains how to view and review aggregated usage data sent to core Aria for invoicing and statement generation. The data aggregates according to the “Aggregate Billing Usage”  configuration. For clients with large usage volumes, this reduces data size before sending it to core Aria. If the configuration aggregates usage data, the quantity, unit price, and amount attributes display blended rates and amounts. Otherwise, these attributes appear for each usage record. The attributes in the Billing Aggregate usage data correspond to those mapped for the bulk_record_usage_m core API. Note that 

  • a unique aggregated ID is generated for each aggregation batch and
  • a unique record ID is generated for each aggregated usage line.
  • Each monetized usage record links to the aggregated ID for backward reference.

View Billing Aggregate 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 Billing Aggregated Usage option in the activity pane.
  5. The system displays the most recent aggregated usage records (one page).

This is shown in the following screenshot:

MBA-01.png

View Billing Aggregate Usage Detail

To view billing aggregated usage data, follow these steps:

  1. Refer to “View Billing Aggregated Usage” to access the billing aggregated usage page.
  2. Click the Id Link for an aggregated usage record. This opens a drawer showing the record's details.
  3. The drawer displays these sections:
    1. Header attributes—key attributes shown atop the drawer by default, part of the “Aggregate for Billing” configuration.
    2. More data—a minimize/maximize bar to view remaining attributes from the “Aggregate for Billing” configuration. It is minimized by default.
    3. View Transactions—Click the View Transactions button to see a table of individual usage records aggregated into the single record.
      1. The table view matches the “View Monetized Usage data” display.
      2. Each table row has an ID link showing details as in “View Monetized Usage data detail”.
      3. For large volumes of usage records aggregated into one record, use pagination or filters as described in “Filters for Monetized usage record”.

This is shown in the following screenshot:

MBA-02.png

The View Transactions screenshot:

MBA-03.png

Status And Error Codes For Billing Aggregated Usage Records

Allegro uses core Aria’s ‘bulk_record_usage_m’ API, which supports batch sizes of records sent in a single call, such as 5K or 10K. Allegro uses the batch size system property to group billing aggregated usage records before making synchronous API calls. For each failed usage record in the batch, the API returns:

  • an error code and description 
  • a status value of ERROR

Aria Allegro updates the billing aggregated usage records accordingly. For other lines in the batch, the status is set to COMPLETE, and the error code and description are null.

These attributes are available in the billing aggregated usage record for viewing and filtering by error code or sync status.

The status values for billing aggregated usage records are:

  1. COMPLETE—The record was successfully processed by core Aria.
  2. ERROR—The record failed processing on core Aria. ERROR status includes the error code and description from the API.
  3. IGNORED—Core Aria ignored the record. Check core Aria for reasons.
  4. INCOMPLETE—Core Aria returned the record as incomplete. Check core Aria for reasons.
  5. PENDING—Aria Allegro has not yet sent the record. Note that
    1. Aria Allegro makes parallel API calls for processing. 
    2. Depending on batch size, synchronous API calls can take time. 
    3. Remaining aggregated usage records may be pending processing. 
    4. The Allegro consumer might not pick the aggregated usage record batch for synchronization, usually due to KAFKA topic consumer setup issues during initial deployment. The deployment team can assist with configuration.
    5. If the record remains pending, the “Reprocessing for Billing aggregate transaction” section in the product user guide explains how to reprocess records.

Filter Attributes for Billing Aggregated Usage

  1. Account Number: Filter Billing aggregated usage by account number using an exact search. Alternatively, use the Account Switch at the top to select the account and view its Billing aggregated usage.
  2. Billable Service Id: Search by the service ID generating the aggregated usage record. This matches the ID in the core Aria Catalog for the service. Use an exact search.
  3. Billable Service Name: Search by the service name generating the aggregated usage transaction. This matches the name in the core Aria Catalog. Use a case-insensitive partial search.
  4. Start date: Enter or select the inclusive start date to search billing aggregated usage data (aggregated usage record start date ≥ 00:00:00 hours). This is a greater than or equal to filter.
  5. End date: Enter or select the exclusive end date to search monetized usage (aggregated usage record start date < 00:00:00 hours). This is a less than filter.
  6. Sync Error Code: Enter the error code to search billing aggregated usage records with a specific error code. This code is returned by the ‘bulk_record_usage_m’ core Aria API. Use an exact search.
  7. Sync status: Select the status from the drop-down list to search by the sync status returned by the ‘bulk_record_usage_m’ core Aria API. Use an exact search.
  8. Usage Type Number: Enter the usage type number to search billing aggregated usage records. Use an exact search.

Sort Attributes for the Billing Aggregated Usage

  • Id—Sort ascending or descending by the billing aggregated usage ID, not the usage ID.
  • Account Id—Sort ascending or descending by the account linked to the billing aggregated usage records.
  • Billable Service Id—Sort ascending or descending by the billable service ID linked to the billing aggregated usage record.
  • Sync Error Code—Sort ascending or descending by the sync error code returned by the core Aria API ‘bulk_record_usage_m’ for the billing aggregated usage record.
  • Sync Status—Sort ascending or descending by the sync status returned by the core Aria API ‘bulk_record_usage_m’ for the billing aggregated usage record.
  • Usage Type Number—Sort ascending or descending by the usage type number of the billing aggregated usage record.
TOP
  • Was this article helpful?