Definition
Cross-Border Billing is ICMP's billing capability for cross-border IoT scenarios. It supports billing by country/region, Unified Invoice, Multi-Currency Settlement, and CDR-level usage attribution. For enterprise customers with devices spread across multiple countries, cross-border billing needs to consolidate dispersed usage and costs, generating clear invoices by customer, project, and region to support financial accounting and cost control.
Core Capabilities
The core capabilities of cross-border billing include: Billing by Country — attributing usage by country/region based on fields in the CDR such as MCC/MNC and PLMN and supporting Geo-Based Pricing; Unified Invoice — consolidating usage from multiple countries, multiple SIM cards, and multiple operators into a single Unified Invoice; Multi-Currency — supporting settlement in USD, EUR, CNY, etc., according to agreed currency or customer preference; Usage Attribution — CDR-level details are traceable, supporting statistics grouped by ICCID, IMEI, and project.
Technical challenges
Cross-border billing faces: multiple operators in different countries CDR formats are inconsistent, time zones differ, currencies differ, requiring normalization; distinguishing roaming and local usage, Roaming Partner settlement data integration; FX Management exchange rate fluctuations and locking; tax compliance—different countries have different invoice, tax rate, and VAT requirements. The platform needs to have Reconciliation capabilities to ensure consistency with operator bills.
Practice in ICMP
SimtoLink ICMP's Cross-Border Billing covers over 200 countries/regions worldwide, supporting Rate Card configuration by country, Usage Aggregation usage aggregation, Unified Invoice unified billing, Multi-Currency Settlement multi-currency settlement. Customers can obtain usage details, bills, and invoices through the Portal or API to meet finance and audit requirements.
How usage is assigned to the country where it was generated
Cross-border billing first answers where usage happened, then who is charged and in which currency. Attribution comes from the mobile country code, the network identifier, and the visited network on the detail record. It is not the country where the customer company is registered, and it is not where someone signed in to the platform. The same SIM can appear in several countries within one month. Each stretch of usage should match the geographic rate in force while that stretch happened, and then roll up to the SIM and the customer. The roll-up can be one invoice, but the detail must still split back to country, network, and SIM identifier.
When attribution fails, do not silently use the contracted-country price. A record missing the country field should stay in a pending queue until it is completed, or until it is confirmed that the country cannot be identified, and only then decide whether to use a default price written in the contract. The default price is itself a rule, and it has to be visible in the invoice notes. Treating every unrecognized flow as domestic traffic systematically under-bills high-price roaming.
Currency and tax that must be locked before a unified invoice
Four items must be locked before invoicing, and not changed again during that period: the settlement currency, the exchange rate at the conversion point, the billing period the usage belongs to, and whether this contract includes tax and who files it. Indirect-tax rules differ widely by country. The platform should not pick a tax rate on its own when the contract does not give a basis. What it can do is list the amount before tax, tax added on top, and the total including tax in separate columns, and name which customer-confirmed rule version the tax came from. Without those columns, finance cannot post connectivity charges and tax separately.
Multi-operator cost can come in each operator’s currency. The customer invoice should still roll up in the one currency the contract states. Conversion must cite a point in time already fixed in FX management. Do not refresh the rate on invoice day and overwrite a preliminary invoice already sent to the customer. Detail that sits beside the unified invoice should keep the original-currency amount, or the customer cannot check why a charge in one country became the converted total. If a tax rate or an exemption changes during the period, split from the change date. Do not rerate the whole month’s usage that already occurred under the new rule.
Using one rate for both the visited country and the contracted country
The contracted-country rate describes how the plan the customer bought is charged inside the agreed networks. The visited-country rate describes the price after traffic leaves those networks. Mixing them posts traffic generated on a high-cost visited network at the cheaper contracted-country unit price, and platform cost and the customer invoice diverge. Or the reverse: local usage is charged at the roaming price, and disputes cluster around “the person never left the country.” The distinguishing key is whether the visited network on the detail record is on the contract’s list of local networks.
Another mix-up is using the invoice mailing address in place of where usage happened. The finance address is in one country and the device is in another. Pricing by mailing address puts every SIM on the same price. The operator’s settlement charges by visited network, the customer invoice charges by country of registration, and the reconciliation gap cannot be split down to a SIM. To correct it, replay the original detail records, match the rate version again by network, and list the adjustment on its own. Do not edit only the rolled-up amount. If a geographic price is missing, stop automatic invoicing of that part, rather than copying the previous country’s price. Roaming detail records can still arrive after the period closes. They enter an adjustment invoice. They do not rewrite the closed period’s original.
The billing calendar should state in advance the expected arrival day of detail records for each country. Roaming records arriving later than local records is normal. Closing the cross-border invoice as soon as local records are complete forces later visited-country usage onto an adjustment, and the customer sees two documents. Before closing, check whether any pending records still have no matched country. If they do, the invoice cannot close. Rounding differences between tax and the pre-tax amount should stay on an adjustment line. Do not spread them into one country’s unit price, or the next period’s rate check will not match the contract. Reopening a closed period must keep the original. The new result appears as a credit or a supplemental charge.