Demo ConnectaTel: telecom subscription and usage day

Demo ConnectaTel PJSC sells mobile, broadband, and managed-connectivity services in UAE and Bahrain. It bills AED and BHD, buys interconnect capacity in USD, and serves consumers, enterprises, and government accounts. Millions of usage events are summarised into billable records; OSERP owns the customer, contract, tariff, invoice, receivable, payment, service-order, and accounting control around that rating process.

1. Model customers, products, and plans

Create legal companies CNT-UAE and CNT-BH, with branches and service territories. A customer header records legal name, identity or trade licence, tax number, billing profile, currency, credit class, communication preference, and collection method. A service account stores subscriber number, SIM or circuit identifier, installation address, responsible contact, and parent account.

Master / field	Demo value	Impact
Product	Business Fibre 500 Mbps	Plan and revenue identity
Service account	CNT-ENT-004281	Usage and invoice ownership
Billing cycle	Monthly, 1st–last day	Invoice generation boundary
Recurring fee	AED 1,850	Contracted revenue
Included usage	5 TB	Rating allowance
Overage rate	AED 0.18 / GB	Variable usage revenue
SLA	99.9% uptime	Credit and service obligations
Deposit	AED 5,000	Liability and risk control
Suspension rule	15 days overdue	Service and collections workflow
Contract term	24 months	Deferred revenue and early termination

The product master includes plan version, effective dates, tax category, billing UoM, revenue account, deferred-revenue account, discount policy, and allowed add-ons. Never edit a tariff that has already rated usage; create a new version so historic invoices remain reproducible.

2. Activate a service contract

Open Subscriptions → Contract → New. Header fields include customer, service account, product, start date, end date, currency, billing day, payment term, salesperson, installation site, contract status, and approval. Detail lines include recurring charge, quantity, discount, included allowance, add-on, tax code, revenue dimension, and cancellation rule.

For Desert Star Logistics, add 10 managed circuits at AED 1,850 each and a one-time installation fee of AED 12,000. The service order records installation address, access window, circuit ID, equipment serials, technician, and acceptance evidence. A contract cannot become active until provisioning and customer acceptance are complete. The activation event schedules the first invoice and creates any deferred revenue schedule required by policy.

3. Import usage and rate it

At month end, the mediation platform sends a usage summary. Each record contains service account, period, event type, quantity, UoM, source system ID, tariff version, currency, and validation status. For the fibre account, usage is 5,600 GB against a 5,000 GB allowance, producing 600 GB overage × AED 0.18 = AED 108.

OSERP validates duplicate source IDs, account status, tariff effective date, unit conversion, and negative or impossible quantities. Rejected events remain visible with reason and retry status. A corrected event references the original rather than overwriting it. The rating run shows imported, rated, rejected, adjusted, and billed totals and records its correlation ID for API support.

4. Generate a recurring invoice

The invoice header stores customer, service account, billing period, currency, tax date, due date, contract, branch, and source rating run. Detail rows show recurring fee, overage, installation amortisation, discount, tax, revenue account, and dimensions. Example before tax: 10 × AED 1,850 = AED 18,500 recurring charge plus AED 108 usage = AED 18,608.

If VAT is AED 930.40, the invoice total is AED 19,538.40. Posting debits receivable and credits recurring revenue, usage revenue, and output tax. A contract liability or deferred revenue schedule releases the installation fee over the service period when policy requires. Regeneration must be idempotent: rerunning a successful billing cycle cannot duplicate invoice or revenue.

5. Handle roaming and interconnect

ConnectaTel receives roaming usage from a partner and pays interconnect providers. The partner agreement stores country, event type, wholesale rate, settlement currency, effective dates, minimum commitment, dispute window, and tax treatment. A roaming batch records partner file reference, usage period, quantity, rate, and validation result.

For 120,000 roaming minutes at USD 0.04, expected cost is USD 4,800. Import the supplier statement, match usage and rate, and create an accrual for unbilled interconnect. When the invoice arrives, clear accrual and post any variance to the mapped interconnect cost account. A dispute line links the exact event range and contract clause; do not reject an entire month because of one rate mismatch.

6. Provisioning, trouble tickets, and credits

A customer reports a 6-hour outage. Create Service → Ticket with service account, circuit, severity, start time, impact, SLA deadline, network reference, owner, and evidence. The service order records diagnosis, technician, replacement equipment, downtime, root cause, and closure approval.

If the SLA grants a 2% monthly credit, create an approved credit note linked to ticket and contract. The credit reverses the affected revenue and tax dimensions; the original invoice remains unchanged. A ticket cannot be closed until customer communication, service restoration, and credit decision are recorded.

7. Collections and controlled suspension

The receivables dashboard groups invoices by customer, service account, age, plan, currency, dispute, and suspension status. A bank receipt of AED 19,538.40 is imported and allocated to the invoice using reference and amount. Short payments remain unapplied or disputed with an owner.

When an invoice is 15 days overdue, the workflow creates a reminder. At 20 days, it requires collections approval; at 30 days, it may create a suspension order subject to customer class and legal restrictions. Suspension records reason, effective time, services affected, notice, approver, and restoration condition. A government account may require escalation instead of automated suspension.

8. Multi-currency settlement and revenue controls

The Bahrain company bills BHD while the interconnect supplier invoices USD. Store transaction rate, functional currency, settlement rate, and bank reference. Payment posts realised FX gain/loss; month-end revaluation covers open balances. The customer contract’s commercial currency must not be changed to hide an FX variance.

The controller reconciles active contracts to billed periods, deferred revenue schedules to contract liability, rated usage to invoice detail, interconnect accruals to partner statements, and tax to the ledger. Revenue exceptions include service active but not billed, billed but not provisioned, allowance exceeded without rating, and duplicate source usage.

9. Month-end metrics and practice

KPI	Baseline	After OSERP discipline	Improvement
Billing cycle exceptions	4.2%	0.7%	83% lower
Usage-to-invoice reconciliation	2 days	90 minutes	94% faster
Duplicate usage events	0.18%	0.01%	94% lower
Overdue enterprise invoices	AED 8.4m	AED 4.9m	42% lower
SLA credit leakage	6.5%	0.9%	86% lower
Interconnect variance review	9 days	2 days	78% faster

Practice: create a 24-month broadband contract, activate a service order, import usage with a duplicate and an invalid tariff, rate valid usage, generate an invoice, post a partial receipt, raise an outage ticket, issue an SLA credit, and run deferred-revenue and interconnect reconciliations. Explain every field, status, permission, journal, tax, currency, and idempotency result.

Related: E-commerce operations, Multi-currency settlement, Month-end close, Advanced GL Mapping, and API library.