Consolidated hotspot billing brings usage from participating networks onto a customer’s bill. Settlement determines what the participating organizations owe each other. A reliable process preserves the chain from a session record to the tariff applied and the resulting charge.
This guide is for operations staff evaluating a billing workflow. The example below is entirely fictional. Actual tariffs, taxes, dispute rules and settlement obligations come from the applicable agreements; the accounting protocol supplies usage evidence.
Name the parties and the records
The venue or access operator provides the connection. A service provider may maintain the customer account. A roaming intermediary or clearinghouse may exchange accounting records and reconcile amounts between those organizations. A single organization can perform several roles, but their responsibilities still need to be explicit.
RFC 2866, RADIUS Accounting, describes accounting requests from a network access server to an accounting server. Its fields include session identifiers, status, elapsed session time and usage counters. These help describe service delivery; a received accounting response is not a customer-payment receipt.
Keep the original records, normalized session ledger, tariff version, customer invoice reference and operator settlement reference connected. Preserve corrections as adjustments with reasons so someone can reconstruct the result later.
Work through one fictional session
On a narrow screen, scroll sideways. Keyboard: focus the table and use the arrow keys.
| Stage | Input or rule | Result |
|---|---|---|
| Usage | Access server A, session S-104, duration 1,250 seconds | One accepted session, approximately 20.83 minutes |
| Retail tariff | USD 0.10 per started minute, capped at USD 3.00 per session | 21 billable minutes × USD 0.10 = USD 2.10 |
| Wholesale agreement | USD 0.06 per started minute; no cap in this example | 21 × USD 0.06 = USD 1.26 owed to access operator |
| Difference | Retail charge less wholesale amount | USD 0.84 before any other costs |
| Repeated record | A retransmission of the same final usage record | No additional session or charge |
The rounding rule is part of this invented tariff: divide 1,250 seconds by 60 and round upward once, giving 21 minutes. Apply the USD 3.00 cap to the retail result. The wholesale calculation uses its own rule. The USD 0.84 difference is not net profit; this example excludes processing fees, taxes, support and other costs.
A system needs enough context to identify a session across operators and access servers. Record the identifier’s source and namespace instead of assuming one short session string is globally unique. Distinguish a retransmitted record from a new, legitimately separate connection.
Resolve exceptions before posting charges
RADIUS accounting can retry requests when responses are missing. That makes duplicate handling part of normal processing. Define the ledger’s idempotency rule: receiving the same accepted event again should leave the same billing result.
Place incomplete or conflicting records into an exception queue. A missing final record, unexplained duration change or ambiguous customer mapping needs an agreed resolution. Avoid inventing a final duration merely because the billing cycle has ended. Record the contractual rule used for any estimate or adjustment.
If interim usage counters are cumulative, summing every update would overcount the session. Verify counter semantics in the actual implementation and retain the received values. Also document timestamp timezone, clock quality and how delayed delivery is represented.
Another fictional case: session S-105 has an opening event but no usable final duration. Keep it separate from S-104’s USD 2.10 charge. Assign an owner to obtain the missing evidence or apply the documented exception policy. The invoice reviewer should see which result was measured and which was adjusted.
Close the reconciliation with evidence
- Count received records, accepted unique sessions, duplicates and unresolved exceptions.
- Check that every posted charge points to its session and tariff version.
- Reconcile invoice totals separately from operator-payable totals.
- Record credits, reversals and disputes with their original references.
- Have a second reviewer reproduce a sample calculation, including a capped session and an exception.
Download the editable reconciliation sheet. It includes the fictional example, its units and rules, plus fields for your own documented agreement. Use pseudonymous test identifiers in demonstrations and protect operational logs that reveal customer activity.
For the connection and identity side, read Wi-Fi roaming and guest Wi-Fi management.