Usage Billing Data

View Balance Group for an account

To view a balance group's details, navigate as follows:

• Refer to the Usage Billing Data
• The Balances tab is the default tab in the activity pane.
• Click on the ID Link for the balance group. This expands the balance group details in a drawer.

The following screenshot illustrates this:

Balance Group detail in drawer is shown in the following screenshot:

Allegro Balance Group characteristics

Key characteristics of a Balance Group are:

• Currency balance is a running balance for usage in Allegro. The balance is not reset with post invoicing activities like payments, adjustments and more.
• Allowance balance:
  • Activation service can grant a one-time allowance, such as 10 free movies for Prime Movies with an Amazon Prime subscription.
  • An allowance can be granted for recurring service every recurring term. The Aria Allegro billing job ensures recurring grants are available as scheduled.
  • Each service can grant one or more allowance types. For example, a recurring service may give 5000 AI tokens and $50 for AI usage in outcome-based monetization.
  • An allowance bucket is created for each grant.
  • Each bucket has a validity period with start and end date/time. Only usage records within this period can consume the allowance.
  • Allowances can be pooled across a Master Plan Instance hierarchy by configuring consumption for specific usage types in Aria Allegro price plans.
  • Each usage price plan can consume multiple allowance types in the configured order. A single usage record may consume more than one allowance if the first lacks sufficient balance.
  • Each allowance consumption in a monetized usage record shows units consumed and creates an equivalent currency offset reflecting the net transaction amount.
  • In the future, usage or other Allegro term-end activities may grant allowances under specific conditions, such as converting an accumulator over a term to an allowance for the next period.
  • Rollover of allowances is also in the roadmap, and we look to prioritize it with a client requirement.
• Accumulator balance: 
  • Accumulators are configured as Quantity accumulators (record quantity), Amount accumulators (record amount), or using expressions (e.g., 75% of the amount or quantity)
  • Add accumulators to price plans for activation services (e.g., one-time commitment value for the first year or contract term), recurring services (e.g., recurring commitment value per cycle), or usage services.
  • The Aria Allegro billing job adds recurring accumulator values to balances per the recurring cycle.
  • Each service can link to multiple accumulators configured in its price plan.
  • An accumulator bucket is created for each period.
  • Each bucket has a validity period with start and end date/time. Only usage records within this period accumulate in that bucket.
  • Accumulator values can pool across a Master Plan Instance hierarchy by configuring Accumulator impacts for specific usage types in Aria Allegro price plans.
  • Each usage price plan can have multiple accumulators in the configured order.
  • Each accumulator impact in a monetized usage record shows units accumulated based on the accumulator resource configuration.
  • In the future, usage or other Allegro term-end activities will allow accumulator conversions, such as converting an accumulator into an allowance or loyalty points. 

View a Billing Profile For an Account

To view a billing profile detail, navigate as follows:

• Refer to the View Billing profile
• The Balances tab is the default tab in the activity pane.
• Click on the ID Link for the billing profile in the table. This expands the billing profile details in a drawer.

The following screenshot illustrates this:

Key attributes of a billing profile 

Some of the object attributes are for future considerations. Key attributes of a billing profile are:

• Attributes from core Aria flow from core Aria to Aria Allegro with plan instance activities.
  • Anniversary date or Billing DOM (Day or month). This is the anniversary date for the billing profile.
  • Billing Frequency, specified in 'n' units where units can be days, weeks, months, quarters, or years.
• Allegro attributes
  • Status: Allegro manages billing profile status by propagating the related plan instance status from core Aria.
  • Cycle data updates dynamically with each recurring billing cycle execution, including:
    • Last Cycle data: Tracks previous billing cycle data via last accounting date, last bill object, and last bill date.
    • Next Cycle data: Tracks current billing cycle data via next accounting date, next bill object, and next bill date.
    • Future Cycle data: Tracks future billing cycle data via future accounting date, future bill object, and future bill date. Currently unused but planned for Delayed Billing, a roadmap item for a client, or known as Positive lag days in core Aria. Allegro will implement a concept of 
      • Open Billing cycle: Executed on the anniversary date to trigger next cycle activities, such as granting allowances for next cycle usage.
      • Close Billing cycle: Executed on anniversary date plus lag days to complete current cycle activities.
  • With each billing cycle execution,
    • Next cycle data becomes last cycle data.
    • A new current cycle data set is created if positive lag days are not used; otherwise, future cycle data becomes next cycle data.
    • With Open Billing cycle for positive lag days, a new future billing cycle data set is created.
  • Accounting and Billing dates: These dates are always set but apply when the billing cycle exceeds one month.
    • Accounting cycles are always monthly.
    • Billing cycles follow the multi-month billing frequency.

View a Bill Unit For an Account

To view a bill unit details, navigate as follows:

• Refer to the View Bill Units
• Click on the ID Link for the billing profile in the table. This expands the billing profile details in a drawer.

The following screenshot illustrates this:

Screenshot for a bill unit detail:

Key Attributes of a Bill Unit

Some object attributes are reserved for future use. Key attributes of a bill unit include:

• Start date: Inclusive start date for monetized records (monetized records ≥ start date 00:00:00).
• End date: Exclusive end date for monetized records (monetized records < end date 00:00:00).
• Billing profile: Reference to the billing profile for which the bill unit is created.