Last verified with: 10.8.6.0
Summary #
LogiSense Billing provides a usage rating and mediation capability that can process high-volume event data in either batch or near-real-time scenarios. Usage records are normalized into billable structures, matched to the correct customer and service context, rated using configured logic, and then passed forward for downstream billing and invoicing.
Why It Matters #
Usage-based billing is often one of the most operationally complex parts of a monetization platform. Businesses need to convert raw operational or network activity into accurate customer charges while preserving flexibility for different data formats, rating models, and customer agreements.
Business Problem It Solves #
Businesses that monetize usage need to answer a few critical questions consistently:
- what happened
- who should be billed for it
- which product, service, or contract terms apply
- what rate should be used
- how should exceptions or missing mappings be handled
LogiSense addresses this through a combination of mediation, identifiers, rate groups, rate plans, and usage processing rules.
Core Concepts #
Mediation #
Incoming data often arrives in a source-specific format. Mediation transforms those records into billable usage data structures that can be interpreted by the LogiSense rating engine.
UDRs And Usage Identifiers #
Usage data is processed as normalized billable records. The platform then determines which account and service context should own the usage by matching configured identifiers and ownership history.
Rating #
Once a usage event is associated to the correct billable context, the rating engine determines the applicable rate based on configured rate groups, plans, timing, geography, and other characteristics.
Exceptions #
Not every usage event will map cleanly. Exception handling is important for data quality, operational monitoring, and revenue protection.
How LogiSense Supports It #
LogiSense supports usage billing through an end-to-end flow that includes:
- intake of usage data through supported ingestion patterns
- mediation and transformation into billable usage structures
- identifier matching to determine ownership
- rate determination using configured pricing structures
- downstream delivery of rated usage into billing and invoicing processes
This allows businesses to monetize complex usage models without embedding rating logic in multiple disconnected systems.
Common Use Cases #
Usage-Based Subscription Billing #
A business bills customers based on usage volume, events, or units consumed rather than only on recurring subscription charges.
Tiered Or Variable Usage Pricing #
Different usage thresholds, locations, or service contexts apply different rates as volume grows or as specific rating conditions are met.
Shared Usage Constructs #
Businesses can support pooled or shared usage scenarios where usage behavior and entitlement are coordinated across multiple services or relationships.
Exception Monitoring #
Operations teams monitor unmatched or invalid usage activity so missing configuration or source-data issues can be corrected before they create revenue leakage.
Important Considerations #
- Usage billing depends heavily on clean upstream data and clear identifier ownership.
- Product, pricing, and mediation design need to be aligned; changing one area often affects the others.
- Exception handling is part of the business process, not just a technical afterthought.
- Rating design should be reviewed whenever new usage-based offers are introduced.