1. Scenario Overview
The figure finance finally settles on is usually the operator's monthly bill, the usage detail, and the feature-fee list. The platform already has usage billing and settlement and revenue sharing. A systematic gap against the operator bill still misstates gross margin, starts a dispute over channel share, and can become a compliance issue. Operator bill reconciliation is the finance close on the operator integration side of the SimtoLink IoT Cloud Platform. A standard or custom billing file comes in, and the engine compares it automatically with platform charges by ICCID, billing period, and fee item. The output is a discrepancy list, an adjustment approval, and a trail.
The three major operators do not share field definitions or period boundaries — a calendar month is not always the billing month. Usage units and rounding differ. Back-billing, reversals, and waivers often sit on their own rows. The reconciliation engine maps the operator's labels onto the platform's, so finance spends less time matching rows in a spreadsheet.
2. Core capabilities
Parse the billing file
A template per operator or per customer sets the delimiter, the encoding, the header row, and which summary rows to skip. Large files load in chunks and are checked as they arrive. Bad rows are reported on their own, so the operator can fix them and send the file again.
What gets compared
Amount and usage can be matched by ICCID, project, customer, or fee type. A threshold can treat a gap below a set amount as a rounding remainder. Usage fees are also checked against the totals in usage statistics and analysis.
Working a discrepancy
A gap can be assigned to operations or to finance. The conclusion might be an operator billing error, a platform rule change, or a customer-specific waiver. The decision and the attachments stay on the record, which is the audit chain.
Reports
You get a summary, the line-level gaps, what is closed, and what is still open. Export reaches an ERP or a finance system, which is what a listed company or a group internal audit asks for.
3. Reconciliation and revenue sharing
Settlement and revenue sharing is how money is split with channels, agents, and end users. Operator bill reconciliation is how cost between you and the operator is confirmed. Gross margin and the channel policy are only reliable once those two agree.
4. Where finance uses it
- China Mobile's monthly bill: Each month the usage detail and the monthly bill come in automatically and are compared with platform charges at ICCID level. Finance reviews the gap list. The close moves from 5 days of manual checking to 1 day of automated matching.
- A project on all three networks: The same project uses China Mobile, China Unicom, and China Telecom SIMs. The engine normalizes the three field sets and produces one gap report, which is the basis for channel share and for cost-center allocation.
- Back-billing and reversals: When an operator posts a back-charge or a reversal against an earlier period, the unusual fee item is flagged on its own. Finance does not miss it, and the profit figure does not drift into a dispute.
5. How to put it in place
Put the file format and the delivery time in the operator contract. The first cycles should make every gap visible, then tighten the threshold. A standing bias, such as a cutoff-time difference, belongs in the rule engine as a standing adjustment, not as a note someone rewrites each month.
6. What a matched bill changes
Operator bill reconciliation makes the finance numbers something you can stand behind, shortens the monthly close, and gives pricing and channel policy a cost figure you can trace.