Dynamic Billing That Prices Every Event in Context

Dynamic billing is a billing approach where the price applied to a product, service, or billable event can change according to configured rules and context. Instead of assigning one fixed rate and using it in every situation, the billing engine can evaluate factors such as demand, time, customer attributes, service characteristics, quantities, formulas, and conditional triggers before it calculates the charge.

This is useful when the commercial value or cost of delivering a service changes depending on the circumstances. OneBill connects that pricing logic to the rating and invoicing flow so the rate that matches the event can be applied automatically and carried through to the customer bill.

Rule-based billing uses predefined business logic to decide which price, rate, discount, surcharge, or SKU charge should apply. A rule can be simple, such as charging a peak rate after 5 PM, or it can combine several conditions, such as customer segment, location, volume, service type, and contract term.

Once the relevant data is available, OneBill evaluates the rule and applies the matching pricing outcome without requiring a billing operator to select the rate manually. For a broader view of the structures that can sit alongside these rules, see OneBill’s pricing models.

OneBill supports demand-based, time-based, formula-based, attribute-based, and conditional pricing scenarios. Demand-based rules can react to utilization or capacity; time-based rules can change rates by day or time window; formulas can calculate a price from multiple variables; attribute-based pricing can use customer or service characteristics; and conditional pricing can trigger a new rate when defined criteria become true.

These approaches do not have to exist in isolation. They can work alongside recurring billing, usage-based billing, tiered pricing, one-time charges, and hybrid billing when a business needs multiple monetization methods in the same customer relationship.

Yes. OneBill can use day and time classifications to apply different rates during peak, off-peak, weekend, seasonal, or other defined periods. When a usage or billable event carries a timestamp, the rating process can evaluate which configured time window that event belongs to and apply the corresponding rate.

This model is useful for services where capacity, demand, or operating cost varies throughout the day, including communications, utilities, mobility, cloud infrastructure, and other metered services.

Yes. Attribute-based pricing can use information about the customer, product, service, contract, location, segment, quantity, or other custom fields to determine the applicable rate. For example, an enterprise customer in Australia on a 36-month agreement can qualify for a different rate from a small-business customer purchasing the same base service in another region.

The important distinction is that the attributes become part of the pricing decision. The billing system does not simply store them as descriptive data; it can use them to select or calculate the rate that should be billed.

Usage-based billing measures what a customer consumes, while dynamic billing determines which rule or rate should be applied to that consumption. Together, they allow each metered event to be evaluated according to time, demand, customer attributes, formulas, thresholds, or other conditions before the final charge is calculated.

For example, the same API call, network minute, kilowatt-hour, GPU minute, or data unit can have a different price depending on when it occurred or which customer consumed it. OneBill’s usage-based billing software provides more detail on usage ingestion, mediation, rating, and metered billing workflows.