Usage Events Reversal with Balance Management

In Subscription Management, usage events that are associated with a balance register can be corrected using a batch-based process from the Usage Events Dashboard. This approach is designed to handle scenarios where usage needs to be rated again, reversed, or replaced in a controlled and auditable way.

From the Usage Events Dashboard, you work with usage events by creating a batch. A batch acts as a container that groups one or more usage events so they can be processed together instead of individually. This is especially useful when multiple events need correction for the same subscription or balance impact.

When creating a batch, you select the type of processing required:

• Usage Rating, which is used to rate usage events that haven’t been rated yet.

• Re-rate, which is used when existing usage needs to be rated again, typically because balances or allowances have changed.

• Reverse and Replace, which is used when usage events were reported incorrectly and must be reversed and substituted with corrected events.

Usage events can be added to a batch in multiple ways. You can select them directly from the dashboard, add them based on defined selection criteria, import them, or include them through REST API integration. If usage events have parent-child relationships, those relationships can be preserved when reversing and replacing events.

After events are added, the batch supports several actions that control how and when processing happens. You can add more events, remove events that no longer belong in the batch, lock the batch for review so that the data can be inspected without further changes, revert the batch if edits are needed, and submit the batch for processing. Processing actions such as rating, rerating, or reversal run through background jobs, and their progress can be monitored.

The application enforces safeguards to prevent conflicts. Usage events that are already reversed, already processed, or locked in another batch can’t be added again. This ensures the same usage isn’t corrected more than once and helps maintain billing accuracy.

Operational visibility is supported through logging, status tracking, and system messages. These help you understand what’s happening during batch execution and assist with troubleshooting if issues occur.

There are some important constraints to be aware of. Usage events can’t be reversed if the related bill lines have already been integrated with Fusion Accounts Receivable. In those cases, attempting a reversal results in errors. Eligibility rules also apply, so only valid, unlocked events can be processed.

Depending on the batch type, some actions may or may not be available. Before submitting a batch, it’s important to review validation results and resolve any errors. If you rely on custom reporting for usage or billing analysis, you may need to account for batch-related data when interpreting results.

Overall, this batch-driven approach provides a structured way to correct usage events tied to balances, while maintaining control, traceability, and data integrity across rating and billing processes.