Telecom Billing & Revenue Management

BC-2660 Level 1 Telecommunications 16 providers 33 API surfaces 6 rated strong or better

Mediation, charging, rating, billing, presentment, collections, revenue assurance, and telecom-specific tax and surcharge processing across prepaid, postpaid, and convergent services.

Telecom Billing & Revenue Management (BC-2660) is a level-1 business capability in the Telecommunications model. The catalog holds 33 API surface(s) from 16 provider(s) that can perform some part of it, 6 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Authorities this capability cites

Cited by the capability model itself. These frameworks are referenced, never redistributed, and citing one does not imply its owner endorses this listing.

Sub-capabilities

Usage Mediation Management BC-2660.10

Collection, normalisation, and routing of usage records from network elements to charging and billing systems.

2 providers, 2 API surfaces

Charging & Rating Management BC-2660.20

Online and offline charging, rating, balance management, and recharge across prepaid and postpaid models.

6 providers, 13 API surfaces

Billing Operations Management BC-2660.30

Execution of billing cycles, calculation of bills, and management of adjustments and corrections.

2 providers, 2 API surfaces

Bill Presentment & Inquiry Management BC-2660.40

Multi-format presentation of bills and resolution of customer inquiries and disputes.

6 providers, 8 API surfaces

Telecom Collections Management BC-2660.50

Telecom-specific dunning, suspension, disconnection, and debt collection flows.

no catalog coverage

Revenue Assurance Management BC-2660.60

Detection, quantification, and remediation of revenue leakage across the revenue chain.

1 provider, 2 API surfaces

Telecom Tax & Surcharge Management BC-2660.70

Calculation and remittance of telecom-specific taxes, surcharges, and regulatory fees.

no catalog coverage

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Exemplar 1 Complete, well-documented, and agent-ready
KPNrest-invoice-controller1 API66.9
Strong 5 Solid coverage with minor gaps
SoracomBilling1 API57.6GSMAOne Step PaymentRefundTwo Step Payment3 APIs56.9MTN GroupBalance Buckets MethodsBalance ManagementBalanceTransferUnified Balance Enquiry7 APIs55.8MEFCustomer Bill1 API55.4WebexBroadWorks Billing Reports1 API55.4
Developing 5 Usable, with meaningful gaps to close
1NCEVolume Top Up1 API52.4GSMA Open GatewayOne Step PaymentPaymentTwo Step Payment3 APIs50.9KORE WirelessSupersimV1BillingPeriodUsageRecords Resource2 APIs50.5TelnyxCharges BreakdownCharges Summary2 APIs48.2SubexReconciliationRevenue Assurance2 APIs40.1
Thin 4 Limited public surface area
AmdocsBilling1 API38.7Global System for Mobile CommunicationsOne Step PaymentTwo Step Payment2 APIs33.5TM ForumbillFormatbillPresentationMediabillingAccountbillingCycleSpecification4 APIs31.3Africa's TalkingAirtime1 API30.4
Emerging 1 Early or largely undocumented
BICSCDR1 API23.9

Workflows that realise this capability

Arazzo workflows whose own sourceDescriptions call APIs that carry this capability. The link is derived, not asserted: each workflow declares x-realizes-capability-ids with the spec and confidence behind it.

This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Telecom Billing & Revenue Management. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →