Definition
Operator reconciliation compares the platform’s own charges with the operator bill, so SIM purchase fees, traffic fees, and monthly rent agree. The comparison can be by SIM, by batch, or by time range. A difference can be marked and followed until it is closed. A match is the basis for payment.
What is compared
- SIM purchase fee: Quantity and unit price of SIMs the platform bought, checked against the operator bill, so the purchase cost is right.
- Traffic fee: The platform’s data billing checked against operator usage and overage billing, by SIM or by batch.
- Monthly rent and plan fee: Fixed charges such as plan rent, checked against the operator tariff plan.
How a cycle is closed
The operator usually supplies a bill file or an API query on the settlement cycle. The platform matches its own bill to the operator bill line by line or in total, and marks what is missing, what is extra, and where the amount differs. After that, the platform adjusts its data or confirms the line with the operator. A passed reconciliation is what payment to the operator is based on. See reconciliation for the general term.
Dimensions and differences
The match can run by ICCID, by batch, or by time range. SIM purchase fees compare the platform’s purchase records with the operator’s outbound records. Traffic fees compare data billing with the operator usage bill, including overage billing and data pool sharing. Differences often come from delayed usage collection, billing rules that do not match, or a wrong operator mapping. Each difference is analyzed and tracked until it is closed. Payment to the operator waits for that pass, so cost stays accurate.
Reconciliation and settlement
Operator reconciliation follows the settlement cycle. It is not an agent settlement statement. It is the cost check before the enterprise pays the operator. After it passes, the enterprise pays the operator bill. Platform bills, data billing, and agent settlement and revenue sharing all depend on that operator cost. It is a core step in finance on the IoT Cloud Platform, and it sits beside the general term reconciliation.
Reading a difference
Differences often come from delayed usage collection, billing rules that do not match, a wrong operator mapping, or a different data pool share. Each line is analyzed and tracked until it is closed. Payment to the operator waits for the pass. The platform should export a reconciliation report, mark differences, and keep the adjustment record. This check is how the IoT Cloud Platform controls cost. The result is what payment to the operator and a financial audit both use.
When the usage day and the bill period are a day apart, which side to align first
Operator reconciliation compares the card fees, plan fees, usage, and overage the platform holds with the bill the operator issues, line by line. Only after they match is the result a basis for payment. Before comparing, align the bill period. If the operator uses a calendar month but cuts the day at 08:00, and the platform cuts the day at midnight, one day’s usage lands in the neighboring period every month. Recompute a version of platform usage on the other party’s day cut first, and only then talk about differences. Do not edit the unit price directly. Card purchase fees are the quantity shipped or accounts opened, times the agreed unit price, and they are a separate line from traffic fees. A traffic difference cannot offset a difference in SIM-card quantity. SimtoLink operator billing reconciliation keeps both original files and the platform’s recomputed result. Adjustments are recorded only on the difference document. They do not overwrite the original usage records.
When a difference row is allowed to close
Differences fall into at least three kinds: the platform has it and the operator does not, the operator has it and the platform does not, and both have it but the amount or the usage does not match. Closing a difference row requires a written reason, for example a mapping that used an expired code, a late catch-up record, a test SIM that was not excluded, or a different pool-sharing basis. A row with no reason cannot be marked handled. If the contract says test SIMs and gift SIMs are not charged traffic by the operator, exclude them from the reconciliation scope and attach the contract clause number. Do not delete the rows by hand every month. An amount difference inside an agreed rounding tolerance can be cleared by rule. The tolerance is written as an absolute value or as a ratio, and the clearance is logged. A row past the tolerance goes to appeal or to an adjustment. While it is under appeal, that item does not enter the “payable” total. A payment request can cite only a bill version that is closed or accepted, so finance does not pay from the first draft while operations book from the final draft.
A matched operator bill does not mean the channel settlement can be paid
The operator bill is the enterprise’s cost. Channel settlement is the enterprise’s sales revenue and revenue share. The two books meet only on usage and on the SIM list. A matched cost does not imply that a given agent’s share is correct, because share also depends on the purchase order and the retail price. The other way around, share already paid to a channel does not replace approval to pay the operator. Reconciliation results are filed by operator account and by bill period. If a SIM changed plan during the period, split it into two stretches that correspond to the operator’s detail. Do not multiply the whole month’s usage by the plan in force at month end. If a whole stretch of usage is missing, trigger a catch-up sync first, then recalculate that bill period. Recalculation produces a new version, and the old version stays for audit. With several operators, reconcile by account. Do not add the three amounts and look only at one total. The account, the bill period, and the bill version number on the payment document have to trace back to the closed difference version. When finance re-imports a file, the version number refuses to overwrite the version that has already been paid.