Definition
Billing mode is how data billing prices usage. The usual choices are by volume (allowance inside the plan, then overage), by time online, and by pool (the data pool is rated in total, then shared out to the SIMs). A data plan has to name its billing mode when it is designed.
The three modes
- By volume: The common case. The plan includes a fixed allowance, such as 10 GB a month. When that is used up, the SIM can be suspended, or overage billing can start and charge by the megabyte. It fits IoT uses where usage can be estimated in advance.
- By time: The charge follows days or months of use, not how much data moved. It fits devices that stay online and send little, such as a shared bike or a charging post.
- By data pool: Many SIMs share one data pool. The enterprise is charged on the pool’s total usage, and that charge is then split to each SIM by an even share, by actual usage, or by weight. It fits a project whose SIMs do not use data evenly.
Which mode fits which fleet
Connected vehicles and video surveillance move a lot of data, so volume billing fits. Shared devices and low-power sensors fit time billing. A project whose SIMs spike at different times fits a pool. One platform can run all three, and each data plan can pick its own mode.
What has to be filled in when the plan is packaged
The mode is chosen at plan packaging, and it drives the data billing engine. Volume mode needs the included amount and the overage unit price. Time mode needs the number of valid days. Pool mode needs the pool’s total allowance and the split rule. The mode has to follow the operator tariff, through operator mapping. It also changes the shape of the bill and how hard operator reconciliation will be, so it should be settled while the offer is still being designed.
How the mode shows up in day-to-day operations
Volume mode is the one most plans use. The data plan sets the allowance steps and the plan period. When the allowance is gone, the SIM can suspend or switch on overage billing. Time mode is for a device that stays online and sends little. Pool mode starts by creating a data pool that the SIMs share, then splits the charge by the pool’s rule. The mode also shapes how plan orders and plan changes are built, and it feeds settlement revenue share, the bill, and the e-invoice. Several modes can be live at once. Each plan simply carries the one it was packaged with.
Choosing before the plan is published
Pick from the fleet, not from a default. Heavy data, such as connected vehicles and video, points to volume. Shared devices and low-power sensors point to time. SIMs that swing widely against each other point to a pool. The choice is locked at plan packaging because it has to match the operator tariff through operator mapping. A wrong mode makes data billing and operator reconciliation disagree on what a megabyte, a day, or a pool total is supposed to mean.
Under volume billing, in-plan and overage are two ledger lines
Volume billing is not a question of whether there was any usage. It is whether the usage fell inside the plan’s included amount or outside it. The included amount, the measurement period, and the overage unit price have to be configured together. A monthly plan resets its included amount at the end of the cycle. A quarterly plan must not zero the data on calendar-month boundaries. If usage is collected with an hourly delay, the night the cycle ends may first decide the plan is exhausted and suspend the SIM, then the next day’s late records show it was not over. Both resume and the bill have to be able to recalculate from the late records. Units should be unified to bytes and then converted to the megabytes or gigabytes on the plan, so the platform is not counting in thousands while the operator counts in units of 1,024, leaving every SIM short at reconciliation. A SIM with an attach and zero traffic should not generate a traffic charge under volume billing. Whether a separate monthly rent applies has to be its own line. It cannot be folded into the traffic unit price. SimtoLink data billing should pick the algorithm from the billing mode on the plan. After a SIM changes plan, usage from the old cycle must not carry into the new mode.
Time-based billing still depends on whether attach is allowed
Time-based billing usually charges by activated days or by calendar month. It does not jump price by a traffic tier. It fits devices that report often and send very little each time. It does not mean usage can go uncollected. The operator may still bill by traffic. If the platform charges the customer only by the day, reconciliation shows a structural gap: the customer bill is in days and the operator bill is in megabytes. That needs a crosswalk. It should not be forced by multiplying days by an imaginary volume. Whether suspended days still count has to be written into the rule. If days of a nonpayment suspension are still billed, the customer reads it as rent continuing while the SIM is cut off. If suspension stops the day count, the rule has to say whether that stop begins when the suspend command succeeds or at the end of the calendar day. A test period or a silent period that is also billed by time should use its own zero or low time price. It should not share a product code with the formal monthly rent. If the device is removed but the SIM is not suspended, the time charge keeps running on a SIM whose user has left, so removal has to end with suspend or cancellation.
Which usage figure is the numerator when a pool is shared out
Pool billing charges the enterprise for the pool’s total usage, or for the pool’s bundle, and then decides how much each SIM bears. The share numerator can be the SIM’s actual usage, a weight, or a simple average. An average share puts a charge on a SIM that used nothing. Sharing by actual usage can put almost the whole charge on a few heavy SIMs. The pool’s included amount and a single SIM’s included amount must not both deduct the same megabyte, or the same traffic is billed twice. A SIM that joins or leaves the pool mid-cycle has to be sliced by day or by usage. It cannot be treated as in the pool for the whole month. After the pool is exceeded, whether the whole pool suspends, only the SIMs that went over suspend, or the pool itself takes overage billing, is a pool rule. It is not the overage switch on a single-SIM plan. At reconciliation, match the pool’s total usage first, then the share-out. If the total does not match, do not start by adjusting each SIM’s ratio. SIMs in the pool that belong to different operators usually cannot sit in the same physical pool. A “logical pool” on the platform only shares cost inside the enterprise. It cannot pretend the operator has already shared the allowance.