Usage and reconciliation help partners understand service activity after purchase.
Usage data can update after network reporting completes. Partners should present usage as a service state, not as an instant financial ledger.
Usage Visibility
Usage visibility can include:
- package purchased
- included data
- data used
- data remaining
- service status
- activation state
- validity period
- reporting timestamp
Availability depends on the approved partner integration and current service state.
Reporting Timing
Usage reporting can lag behind real activity.
Delays can happen because of:
- local network reporting
- roaming partner timing
- session updates
- account synchronization
- service state changes
Partners should show the reporting timestamp when it matters.
Reconciliation
Reconciliation connects partner orders, package versions, usage state, and commercial records.
Partners should keep:
- order ID
- package ID
- catalogue version
- purchase time
- customer reference
- service state
- refund or credit state where applicable
These records help support billing review and operational support.
Billing Support
Billing support depends on the partner agreement.
Partners should not promise refunds, credits, or reversals outside the approved policy.
If a billing issue depends on Onyx service state, collect the order reference and current state before escalation.
Usage Disputes
For usage disputes, check:
- package allowance
- validity period
- activation state
- reporting timestamp
- device usage settings
- current service status
Escalate only when the usage state cannot be explained from available records.