Definition
Overage billing charges the usage that continues after the allowance inside a data plan is used up. It can use a stepped unit price, a different price in each usage band, a cap, or unlimited stacking. In data billing, the plan fee and the overage fee are calculated apart. The overage line has to be checked in operator reconciliation.
How it is priced
- By MB or GB: Overage is actual usage times the unit price, for example 0.1 CNY/MB.
- Stepped price: Each band has its own price. For example, 0–1 GB at 0.1 CNY/MB, and above 1 GB at 0.05 CNY/MB, which leaves room for a moderate overage.
- Cap: A ceiling on overage fees per SIM or per month. Past the ceiling, the SIM is suspended or slowed, which limits the user’s exposure.
Suspend, or keep billing
When the allowance is gone, the enterprise can set overage billing or an immediate suspend. Overage billing fits usage that swings, where frequent suspend and resume would get in the way. An immediate suspend fits a hard cost limit. Some operators let each SIM turn overage on or off. The platform has to follow that through operator mapping.
Overage and the operator bill
The overage charge needs usage collected correctly and the unit price applied correctly. On operator reconciliation, the overage fee is a main line to check. The operator may use a different usage cycle or a different rating rule, so the mapping and the difference analysis have to cover it. The overage unit price is usually higher than the price inside the plan. A sensible price covers cost and leaves a margin. A cap limits the user’s exposure and avoids a dispute over an abnormally high bill.
Where the rule is set
Overage can be set on the data plan or during plan packaging, and it can be turned on or off by plan, by SIM, or by project. With overage on, using up the allowance does not suspend the SIM at once. Usage keeps being rated. With overage off, the SIM suspends when the allowance is gone, and resume waits for a renewal. The unit price, the steps, and the cap have to line up with operator mapping and the data billing engine so the bill is right. The pattern fits usage that swings and a wish to suspend and resume less often, such as connected vehicles and shared devices.
Overage on the bill
Rating the overage still depends on collecting usage correctly and applying the unit price correctly. In operator reconciliation, the overage fee is a main line to check. The overage unit price is usually higher than the in-plan price, and a sensible price can cover cost. A cap limits the user’s exposure and avoids an abnormally high bill. Overage billing is part of data billing, and it is tied to the billing mode and the plan cycle.
After the cap: suspend, or keep rating at the capped price
Overage billing, after the included amount is used up, records the excess as a separate charge by usage and unit price, and the SIM can stay online. It and “suspend when exhausted” are alternatives on the plan, or a conditional combination. Both cannot be left vaguely on. The unit price can be one price per megabyte, or it can step by how far the usage has gone past the allowance. A step has to say whether the top of the band is included, and whether usage is accumulated for the cycle or by the day. If the cap means the SIM suspends once the fee reaches the top, send suspend at that moment and stop accumulating. If the cap means the price stops rising and traffic keeps flowing, do not also send suspend, or the user believes they still have “unlimited data” and finds the line cut. SimtoLink data overage rules are bound to the plan cycle. When the cycle resets, the overage total resets. Before the reset, do not open another tier on the calendar month.
Where the platform overage price and the operator overage price diverge
The overage unit price the operator charges the enterprise, and the overage unit price the enterprise charges the user or the project, can differ, but they are configured separately. Reconciliation checks only the tier between the enterprise and the operator. The retail bill uses the tier sold to the customer. Reconciling the operator bill at the retail price produces a false difference every month. Which side’s usage is authoritative has to be agreed in advance. Collection delay can under-record overage when the cycle ends, then a catch-up record adds another stretch. The bill has to allow the overage fee to be recalculated from the catch-up record, and it has to write an adjustment line. A SIM inside a traffic pool should not also take single-SIM overage, unless the pool rule explicitly says “overage inside the pool is shared out by SIM again.” A plan billed by time, if it has no notion of included traffic, should not grow an overage line, or the charge duplicates the monthly rent.
Which usage must stay out of the overage total
A test allowlist, a directed address that the billing rule treats as free, and a previous cycle’s usage record that arrives late should not enter this cycle’s overage. If a previous cycle’s record is stored only in this cycle, write it back to the previous cycle and keep it under that cycle’s cap. Do not pile it into this month and break the cap early. Negative usage or a rolled-back record has to be able to reduce the total. If the fee has already been billed, create a credit. Do not show the user a negative usage figure. Usage generated in the window before a suspend command has taken effect is included in overage or not according to a cut at the receipt time, and that window rule is written into the billing note. The overage amount the user sees should expand to usage and unit price. With only a total, support cannot explain why it differs from the price printed on the plan. A SIM that has not opened overage should suspend when the allowance is used up. If usage is still growing, first check whether suspension really took effect, rather than automatically switching the SIM to overage billing. If the contract allows overage to be opened after the fact, that also needs its own approval record and an effective time. Whether usage from before that time is billed retroactively has to be written down. It must not default to a recalculation from the start of the month.