Part 018 — Charge Types, Billing Periods, Usage Rates, Tiers, and Allowances

Positioning

Enterprise and telecom products rarely have one simple price.

A commercial offer may combine:

• installation fee;
• recurring subscription;
• per-site charge;
• usage rate;
• included allowance;
• overage;
• tiered volume;
• minimum commitment;
• deposit;
• and early termination charge.

Jika seluruhnya dimodelkan sebagai generic amount, downstream akan kehilangan:

• billing period;
• rate unit;
• tier behavior;
• allowance semantics;
• effective dates;
• and customer explanation.

Core thesis: charge types must preserve temporal, quantity, and rating semantics. One-time, recurring, usage, allowance, and tiered charges are not interchangeable representations of money.

1. Charge Model Overview

A charge model should answer:

What event or period causes the charge?
What quantity is measured?
What unit applies?
What rate or amount applies?
How often?
For how long?
What allowance or tier modifies it?

2. One-Time Charge

A one-time charge applies once for a defined trigger.

Examples:

• installation;
• activation;
• equipment;
• setup;
• migration;
• and expedited service.

3. One-Time Trigger

Possible triggers:

• quote acceptance;
• order creation;
• shipment;
• installation;
• activation;
• or contract start.

Quote may state commercial charge, while billing decides activation trigger.

4. One-Time Charge Timing

Need to distinguish:

• quoted applicability;
• ordered charge;
• charge activation date;
• and invoice date.

5. Recurring Charge

A recurring charge applies repeatedly over a period.

Examples:

• monthly subscription;
• annual license;
• per-site recurring fee;
• managed service charge.

6. Recurrence Period

Common periods:

• daily;
• weekly;
• monthly;
• quarterly;
• annually.

7. Calendar Period

A monthly charge usually follows calendar/billing period semantics, not fixed 30-day duration.

8. Billing Frequency

Billing frequency is how often invoiced.

It may differ from charge period.

Example:

• annual service price;
• billed monthly.

9. Charge Frequency versus Billing Frequency

Charge frequency

Economic recurrence.

Billing frequency

Invoice schedule.

Do not conflate.

10. Usage Charge

Usage charge depends on measured consumption.

Examples:

• GB;
• minute;
• message;
• API call;
• transaction;
• device-hour.

11. Usage Measure

A usage measure should define:

• metric;
• unit;
• aggregation;
• time window;
• and source.

12. Usage Event

A usage event may include:

• customer/account;
• product;
• quantity;
• unit;
• event time;
• source;
• and correlation.

CPQ usually does not rate actual future usage but may quote rates and estimates.

13. Usage Rate

Example:

0.05 USD per GB

Needs:

• currency;
• unit;
• validity;
• and tier/allowance context.

14. Included Allowance

An allowance grants consumption before overage.

Example:

• 100 GB/month included.

15. Shared Allowance

An allowance can be shared across:

• sites;
• users;
• products;
• or account.

This changes rating and billing semantics.

16. Per-Item Allowance

Each product instance receives its own allowance.

17. Rollover Allowance

Unused allowance may:

• expire;
• roll over;
• or accumulate with cap.

18. Allowance Period

Allowance usually resets by:

• billing period;
• calendar period;
• or contract-defined cycle.

19. Overage

Usage beyond allowance is charged by rate or tier.

20. Minimum Commitment

Customer commits to minimum:

• spend;
• quantity;
• usage;
• or term.

21. Minimum Spend

If actual charge is below threshold, charge minimum amount.

22. Minimum Usage

Customer commits to purchase or consume at least a quantity.

23. Take-or-Pay

Customer pays committed amount regardless of actual usage.

This has important contract and billing implications.

24. Maximum Charge

A cap limits charge.

Examples:

• monthly spend cap;
• overage cap;
• and bill shock protection.

25. Price Tier

A tier maps quantity range to:

• rate;
• amount;
• discount;
• or rule.

26. Tier Boundaries

Define:

• lower bound;
• upper bound;
• inclusivity;
• and unit.

27. Volume Pricing

A single rate applies to all units based on total quantity.

Example:

1–9 sites: 50/site
10–19 sites: 45/site
20+: 40/site

For 20 sites:

20 × 40 = 800

28. Graduated Pricing

Different portions use different rates.

Example:

First 10 sites: 50/site
Next 10 sites: 45/site
Above 20: 40/site

For 20 sites:

10 × 50 + 10 × 45 = 950

29. Block Pricing

A fixed amount applies per block.

Example:

• 100 USD per block of 10 users.

Need rounding-up/down policy.

30. Package Pricing

A fixed amount covers a quantity band.

Example:

• up to 100 users for 1000/month.

31. Step Pricing

Rate changes at discrete configuration values.

Example:

• 100 Mbps;
• 500 Mbps;
• 1 Gbps.

32. Slab Pricing

Term often used similarly to graduated/tiered pricing.

Define local meaning.

33. Tier Selection

Inputs may include:

• total quote quantity;
• per-item quantity;
• account portfolio;
• committed quantity;
• or expected usage.

34. Tier Scope

Possible scopes:

• one item;
• one bundle;
• one quote;
• one account;
• one contract;
• or one billing period.

35. Tier Aggregation Window

For usage, quantity may aggregate by:

• hour;
• day;
• month;
• billing cycle;
• or contract term.

36. Cross-Item Tier

Total quantity across multiple items determines rate.

37. Cross-Site Tier

Site count across quote determines volume rate.

38. Portfolio Tier

Existing installed products plus new products determine tier.

39. Tier Rounding

Quantity conversion may require rounding before tier selection.

40. Tier Boundary Example

At exactly 10 units, decide whether range is:

[1,10]
or
[1,10)

Avoid ambiguity.

41. Tier Gap

Tiers should not leave unpriced quantity ranges.

42. Tier Overlap

Overlapping tiers require precedence or should be rejected.

43. Infinite Upper Bound

Use explicit open-ended range.

44. Negative Quantity

Usually invalid except special correction/reversal contexts.

45. Zero Quantity

Can mean:

• no charge;
• invalid configuration;
• or free allowance.

Define behavior.

46. Fractional Quantity

Valid for:

• GB;
• hours;
• and measured usage.

May be invalid for devices or sites.

47. Unit Conversion

Tier quantity must use canonical unit.

Example:

• 1 TB = 1000 GB or 1024 GB depending on policy.

48. One-Time + Recurring Composition

Example:

Installation: 500 once
Subscription: 100/month

Customer-facing summary should keep them separate.

49. Recurring + Usage Composition

Example:

Base subscription: 100/month
Included usage: 100 GB/month
Overage: 0.05/GB

50. Recurring + Tiered Site Price

Example:

1–9 sites: 50/site/month
10–19 sites: 45/site/month
20+: 40/site/month

51. One-Time Waiver

Waive installation fee under promotion or approval.

Keep base charge plus waiver adjustment.

52. Recurring Discount

Discount may apply:

• indefinitely;
• for first N periods;
• or until contract end.

53. Free Period

Example:

• first three months free.

Model as limited-duration recurring discount, not base rate zero forever.

54. Trial

A trial may have:

• zero recurring charge;
• limited feature;
• automatic conversion;
• and expiry.

55. Introductory Rate

Lower rate for initial period, then standard rate.

Need two temporal phases.

56. Step-Up Price

Rate increases at scheduled milestones.

Example:

• year 1: 100/month;
• year 2: 110/month;
• year 3: 120/month.

57. Step-Down Price

Rate decreases over time.

58. Price Schedule

A price schedule defines multiple temporal charge phases.

59. Schedule Segment

Each segment should include:

• start;
• end;
• rate/amount;
• and conditions.

60. Schedule Overlap

Reject overlapping segments unless precedence explicit.

61. Schedule Gap

A gap may mean:

• free period;
• or missing price.

Represent explicitly.

62. Effective Date

Charge definition may become effective at:

• contract start;
• product activation;
• order completion;
• or fixed date.

63. Relative Date

Example:

• starts 30 days after activation.

Need event reference.

64. Absolute Date

Example:

• starts 2026-08-01.

65. Trigger-Based Start

A charge begins when event occurs.

Examples:

• activation;
• shipment;
• installation.

66. Trigger-Based End

Charge ends when:

• termination;
• contract expiry;
• or replacement.

67. Charge Duration

Possible:

• one period;
• N periods;
• until date;
• until event;
• or indefinite.

68. Contract Term Dependency

Rate may depend on 12/24/36-month term.

69. Co-Termination

Multiple products may align end date to one contract date.

70. Anniversary Billing

Charge may renew on contract anniversary.

71. Billing Cycle Alignment

Activation may be aligned to billing cycle.

72. Proration

Proration calculates partial-period amount.

Possible methods:

• daily;
• actual days;
• fixed 30-day;
• calendar fraction;
• no proration.

73. Proration Basis

Need:

• period start/end;
• activation date;
• calendar;
• and rounding.

74. First-Period Proration

Example:

• activate on 15th;
• monthly billing cycle starts 1st.

75. Last-Period Proration

Termination mid-cycle may create credit or full-period charge depending on policy.

76. Mid-Cycle Upgrade

May generate:

• credit for old product;
• charge for new product;
• and prorated difference.

77. Proration and Discounts

Define whether discount applies:

• before;
• after;
• or proportionally to prorated amount.

78. Tax and Proration

Tax basis follows prorated charge according to jurisdiction.

79. Usage Window

Usage may be rated in:

• real-time;
• near-real-time;
• daily batch;
• or billing-cycle batch.

80. Usage Aggregation

Possible aggregation:

• sum;
• maximum;
• average;
• percentile;
• distinct count.

81. Peak Usage

A charge may depend on peak usage.

82. Concurrent Usage

Charge may depend on concurrent users or sessions.

83. Time-of-Day Rate

Different rates by:

• peak;
• off-peak;
• weekend;
• or holiday.

84. Location-Based Usage

Rate may depend on:

• origin;
• destination;
• roaming zone;
• or region.

85. Usage Classification

Usage event may map to rating category.

86. Rating

Rating converts usage quantity into monetary charge.

CPQ may only model rate plan, while charging/billing performs actual rating.

87. Rate Plan

A Rate Plan groups:

• rates;
• tiers;
• allowances;
• and time windows.

88. Rate Card

A Rate Card may define rates by dimension.

Example:

• destination zone;
• usage type;
• volume tier.

89. Multi-Dimensional Rating

Rate depends on multiple dimensions:

• quantity;
• time;
• location;
• customer tier;
• and product.

Complexity grows rapidly.

90. Rating Key

A rating key may identify:

• product;
• event type;
• zone;
• and unit.

91. Quoted Usage Rate

Quote should show:

• rate;
• unit;
• tier;
• allowance;
• and assumptions.

92. Estimated Usage

An estimate should state:

• assumed quantity;
• period;
• and non-binding status.

93. Committed Usage

Contract may bind minimum or included quantity.

94. Burst Pricing

Usage beyond committed capacity may incur different rate.

95. Overage Tier

Overage itself can be tiered.

96. Allowance Hierarchy

Possible order:

1. promotional allowance;
2. product allowance;
3. shared account allowance;
4. paid usage.

Precedence must be explicit.

97. Allowance Consumption Order

Different allowances may expire at different times.

Use deterministic consumption policy.

98. Shared Pool

A shared pool requires:

• member set;
• priority;
• reset period;
• and allocation semantics.

99. Rollover

Need:

• maximum rollover;
• expiry;
• and consumption order.

100. Unlimited

“Unlimited” may still include:

• fair-use policy;
• speed throttling;
• or cap.

Model actual policy.

101. Fair Use

Fair-use threshold may trigger:

• throttle;
• surcharge;
• or review.

This is not necessarily price only.

102. Cap and Floor

Usage charge can have:

• minimum charge;
• maximum charge;
• and zero-charge threshold.

103. Threshold Charge

Charge applies after quantity exceeds threshold.

104. Activation Fee per Site

One-time charge multiplied by site count.

105. Recurring Fee per Device

Recurring amount multiplied by active devices.

106. Charge Quantity Source

Quantity can come from:

• quote selection;
• inventory count;
• measured usage;
• billing account;
• or external system.

107. Quoted Quantity versus Billed Quantity

Quoted quantity may be expected/committed.

Billed quantity may be actual.

Preserve distinction.

108. Charge Scope

Possible scopes:

• quote;
• item;
• site;
• device;
• account;
• contract;
• and usage pool.

109. Charge Identity

Each charge instance should have identity for:

• adjustment;
• activation;
• reversal;
• and reconciliation.

110. Charge Definition Identity

Reusable definition.

111. Charge Result Identity

Transaction-specific calculated result.

112. Billing Charge Identity

Downstream billing-specific charge.

Lineage should connect all three.

113. Charge Provenance

Store:

• source definition;
• tier;
• quantity;
• allowance;
• schedule;
• and calculation version.

114. Tier Provenance

For graduated pricing, record each tier segment used.

115. Allowance Provenance

Record which allowance reduced charge.

116. Schedule Provenance

Record which temporal segment applied.

117. Quote Representation

Customer-facing quote should explain:

• one-time charges;
• recurring charges;
• usage rates;
• allowances;
• and variable assumptions.

118. Order Representation

Order should preserve accepted commercial charge structure.

119. Billing Representation

Billing may need:

• charge type;
• rate plan;
• activation trigger;
• period;
• quantity source;
• and schedule.

120. Charge Transformation

One quoted charge may map to multiple billing instructions.

121. Many-to-One Charge Mapping

Multiple commercial components may become one billing charge.

Preserve aggregation lineage.

122. One-to-Many Charge Mapping

A commercial charge may create:

• base recurring charge;
• discount schedule;
• and usage allowance.

123. Charge Activation

Activation event must be explicit.

124. Activation Failure

If product activates but charge does not:

• revenue leakage.

125. Deactivation

Termination should stop future recurring and usage charges.

126. Retroactive Activation

Backdated activation may require:

• catch-up billing;
• proration;
• and audit.

127. Suspended Product

Suspension may:

• continue charge;
• reduce charge;
• or pause charge.

Policy-specific.

128. Resume

Resume may restart charge with or without proration.

129. Partial Fulfillment

Some site charges may activate while others remain pending.

130. Partial Billing

Need per-site/item charge lineage.

131. Cancellation Before Activation

One-time cancellation fee may still apply.

132. Early Termination Fee

Can depend on:

• remaining term;
• subsidy;
• and contract policy.

133. Refund

Refund may be:

• negative charge;
• credit;
• or payment reversal.

Define downstream semantics.

134. Charge Reversal

Links to original charge and reason.

135. Correction

Corrects rate or quantity error while preserving history.

136. Repricing Existing Subscription

Changing rate for active customer may require:

• notice;
• agreement;
• effective-date schedule;
• and grandfathering.

137. Grandfathered Rate

Preserve old rate for eligible installed product.

138. Renewal Rate

At renewal, rate may:

• remain;
• update;
• or require new quote.

139. Charge Compatibility

Changing charge model can break:

• quote;
• order;
• billing;
• and reporting.

140. Schema Evolution

Adding a new charge type may require consumer compatibility.

141. Enum Evolution

Consumers must handle unknown charge types safely.

142. Unit Evolution

Changing usage unit requires conversion.

143. Tier Evolution

New tiers should not reinterpret accepted quotes.

144. Schedule Evolution

New schedule applies only according to lifecycle policy.

145. Charge Validation

Validate:

• amount/rate;
• currency;
• unit;
• period;
• tier coverage;
• allowance;
• and schedule.

146. Tier Validation

Check:

• no gaps;
• no overlaps;
• correct bounds;
• and valid rates.

147. Allowance Validation

Check:

• unit compatibility;
• reset period;
• sharing scope;
• and non-negative quantity.

148. Schedule Validation

Check:

• ordered segments;
• no overlap;
• and complete intended coverage.

149. Proration Validation

Check:

• basis;
• dates;
• rounding;
• and amount reconciliation.

150. Charge Invariants

Representative invariants:

• every recurring charge has period;
• every usage rate has unit;
• tier ranges do not overlap unintentionally;
• allowance unit matches usage unit;
• one-time charge trigger is explicit;
• and accepted charge schedule is immutable.

151. Property-Based Testing

Properties:

• graduated tier sum equals quantity;
• volume rate selection deterministic;
• no tier leaves quantity unpriced;
• allowance never creates negative billable usage;
• schedule segments do not overlap;
• and proration remains within full-period amount.

152. Boundary Testing

Test tier boundaries exactly.

153. Large Quantity Testing

Test maximum realistic site/user/usage volumes.

154. Precision Testing

Usage quantity and rates may need high precision.

155. Time Testing

Test:

• month length;
• leap year;
• timezone;
• and daylight-saving where relevant.

156. Proration Testing

Test first/last day, mid-cycle, and zero-day edge cases.

157. Usage Replay Testing

Same usage events and rate plan should reproduce same charge.

158. Charge Reconciliation

Compare:

• quoted charge definition;
• ordered charge instruction;
• activated billing charge;
• and invoiced amount.

159. Revenue Leakage Detection

Examples:

• active product with no recurring charge;
• usage without rate plan;
• missing overage;
• and fee waiver not authorized.

160. Overbilling Detection

Examples:

• duplicate recurring charge;
• allowance not applied;
• wrong tier;
• and charge not stopped after termination.

161. Observability

Metrics:

• charge activation lag;
• missing charge;
• duplicate charge;
• tier usage;
• allowance exhaustion;
• and quote-to-bill variance.

162. Business Metrics

• recurring revenue;
• one-time revenue;
• usage revenue;
• discount/free-period cost;
• and minimum commitment attainment.

163. Charge Incident

Examples:

• monthly charge modeled as one-time;
• wrong tier boundary;
• free period never ends;
• and shared allowance applied per item.

164. Incident Diagnosis

Ask:

Which charge definition?
Which quantity source?
Which tier?
Which allowance?
Which schedule?
Which activation event?

165. Charge Smells

• one generic charge type;
• period stored in description;
• no unit;
• tier rules in code only;
• and free period represented as zero base rate.

166. Tier Smells

• overlapping ranges;
• ambiguous boundaries;
• first-match selection;
• and volume/graduated semantics not distinguished.

167. Usage Smells

• no event time;
• no unit;
• no source;
• and estimated usage treated as actual.

168. Allowance Smells

• allowance represented as negative price;
• reset period missing;
• shared scope undefined;
• and rollover implicit.

169. Anti-Patterns

One Price Fits All

All charge semantics collapsed into amount.

Monthly as 30 Days

Calendar semantics lost.

Tier by UI Label

No machine-readable boundaries.

Unlimited Means Infinite

Fair-use policy hidden.

Charge Activation by Order Completion Only

Partial fulfillment ignored.

Billing Reconstructs Quote Rules

Historical commitment lost.

170. Charge Definition Template

## Charge Definition ID and Version

## Charge Type

## Trigger

## Amount or Rate

## Currency

## Quantity Unit

## Charge Period

## Billing Frequency

## Scope

## Tier Model

## Allowance

## Schedule

## Effective Period

## Tax Class

## Activation / Deactivation

## Mapping to Billing

171. Tier Template

Tier ID:
Model: volume / graduated / block / package
Lower bound:
Upper bound:
Inclusivity:
Unit:
Rate/amount:
Currency:
Priority:

172. Allowance Template

Allowance ID:
Quantity:
Unit:
Reset period:
Scope:
Shared pool:
Rollover:
Expiry:
Consumption order:

173. Charge Schedule Template

Schedule ID:
Start trigger/date:
End trigger/date:
Segments:
- period
- amount/rate
- condition
Proration:
Renewal:

174. Usage Rate Template

Usage type:
Unit:
Aggregation:
Time window:
Allowance:
Tiers:
Rate:
Currency:
Minimum:
Maximum:
Source:

175. Worked Example: Connectivity Subscription

Charges:

• installation 500 once;
• recurring 100/site/month;
• 20 sites;
• one-time total 500;
• recurring total 2000/month.

176. Worked Example: Volume Site Pricing

Tiers:

• 1–9: 50/site;
• 10–19: 45/site;
• 20+: 40/site.

For 20 sites:

• recurring = 800/month.

177. Worked Example: Graduated Site Pricing

For 20 sites:

• first 10 × 50 = 500;
• next 10 × 45 = 450;
• total = 950/month.

178. Worked Example: Usage Allowance

Subscription:

• 100/month.

Allowance:

• 100 GB/month.

Overage:

• 0.05/GB.

At 130 GB:

• billable usage = 30 GB;
• overage = 1.50.

179. Worked Example: Shared Allowance

Five sites share 500 GB/month.

Need:

• pool identity;
• member sites;
• reset period;
• and allocation/consumption trace.

180. Worked Example: First Three Months Free

Base recurring:

• 100/month.

Schedule:

• months 1–3: 100% discount;
• month 4 onward: standard rate.

181. Worked Example: Step-Up Contract

• year 1: 100/month;
• year 2: 110/month;
• year 3: 120/month.

Quote and billing mapping preserve schedule segments.

182. Worked Example: Mid-Cycle Upgrade

Old product:

• 100/month.

New product:

• 160/month.

Upgrade on day 15.

Billing policy may create:

• old credit;
• new prorated charge;
• and new recurring schedule.

183. Worked Example: Early Termination Fee

Fee:

• remaining months × subsidy recovery rate;
• capped at defined maximum.

Requires contract and remaining-term context.

184. Worked Example: Partial Site Activation

20 sites ordered.

12 active this month.

Only those 12 recurring site charges activate if policy is activation-based.

185. Senior Engineer Operating Model

Model charge semantics explicitly

Type, trigger, unit, period, and scope.

Separate charge and invoice timing

Commercial and billing lifecycles differ.

Distinguish volume and graduated tiers

They produce different results.

Preserve allowance semantics

Do not model as negative amount.

Treat time as first-class

Schedules, free periods, and proration.

Preserve quantity source

Quoted, measured, or installed.

Design billing lineage

Charge definition -> quote -> order -> billing.

Test boundaries aggressively

Tier and temporal bugs are expensive.

Reconcile revenue

Detect missing and duplicate charges.

186. Internal Verification Checklist

Charge types

• Which one-time, recurring, usage, fee, credit, deposit, and allowance types exist?
• Are charge types first-class or encoded in descriptions?
• Are triggers explicit?

Periods and timing

• What is charge period versus billing frequency?
• What starts/stops charges?
• Is proration supported?
• How are free and step-up periods modeled?

Usage

• What usage units and event sources exist?
• Is actual usage rated outside Q&O?
• How are allowances and overage represented?
• Are estimated and actual usage distinguished?

Tiers

• Which models exist: volume, graduated, block, package?
• How are boundaries represented?
• Are gaps/overlaps validated?
• What is the aggregation scope?

Lifecycle

• How do ADD/MODIFY/SUSPEND/RESUME/TERMINATE affect charges?
• How are grandfathered rates handled?
• How are accepted charge schedules protected?

Integration

• How do quoted charges map to billing?
• What event activates charge?
• Can one commercial charge map to multiple billing charges?
• How is quote-to-bill variance reconciled?

Operations

• What charge incidents are common?
• Are missing/duplicate charges monitored?
• Can support trace tier, allowance, and activation?
• Are revenue leakage controls automated?

187. Practical Exercises

Exercise 1 — Charge taxonomy

Model one product with one-time, recurring, and usage charges.

Exercise 2 — Tier comparison

Calculate volume and graduated outcomes for the same quantities.

Exercise 3 — Allowance model

Design individual, shared, and rollover allowance behavior.

Exercise 4 — Schedule

Model first-three-months-free and step-up pricing.

Exercise 5 — Proration

Define mid-cycle activation and termination calculations.

Exercise 6 — Billing lineage

Trace one recurring charge from quote to invoice.

188. Part Completion Checklist

You are done if you can:

• distinguish one-time, recurring, and usage charges;
• model charge trigger and period;
• separate charge frequency from billing frequency;
• model allowances and overage;
• distinguish volume and graduated tiers;
• define tier boundaries and scope;
• model schedules and free periods;
• define proration inputs;
• preserve charge lineage into billing;
• and create an internal charge-model verification backlog.

189. Key Takeaways

1. Charge type is domain semantics.
2. One-time and recurring charges are not interchangeable.
3. Usage rates need unit and aggregation window.
4. Allowance is not merely a negative price.
5. Volume and graduated tiers differ materially.
6. Tier boundaries must be explicit.
7. Billing frequency and charge period may differ.
8. Free periods and step-ups require schedules.
9. Charge activation must align with fulfillment policy.
10. Internal CSG charge and billing semantics must be verified.

190. References

Conceptual baseline:

• General telecom and enterprise one-time, recurring, usage, allowance, and tiered-pricing practices.
• Billing-period, rating, proration, rate-plan, and charge-activation concepts.
• Domain-Driven Design value objects, temporal modeling, and transaction lineage.
• Quote-to-order and billing reconciliation practices.

These references do not define internal CSG charging or billing implementation.