Subscription Billing & Revenue Management

BC-4250 Level 1 Software & Technology 8 providers 22 API surfaces 4 rated strong or better

Usage metering, rating, invoicing, dunning, subscription revenue recognition, subscription tax handling, and recurring-revenue analytics for the SaaS commercial model.

Subscription Billing & Revenue Management (BC-4250) is a level-1 business capability in the Software & Technology model. The catalog holds 22 API surface(s) from 8 provider(s) that can perform some part of it, 4 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 Metering BC-4250.10

Ingestion and aggregation of usage events that feed downstream rating and analytics.

3 providers, 3 API surfaces

Rating & Charging BC-4250.20

Application of subscription tariffs, usage tariffs, prorations, and discounts to compute charges.

no catalog coverage

Invoicing & Statement Management BC-4250.30

Generation, delivery, and adjustment of invoices and customer billing dispute handling.

2 providers, 4 API surfaces

Payment Collection & Dunning BC-4250.40

Payment-method management, payment authorisation, dunning, and involuntary churn recovery.

3 providers, 6 API surfaces

Subscription Revenue Recognition BC-4250.50

Identification of performance obligations and management of revenue schedules in line with ASC 606 / IFRS 15.

no catalog coverage

Subscription Tax Management BC-4250.60

Tax-jurisdiction determination, calculation, and exemption handling across recurring and usage-based charges.

1 provider, 1 API surface

Subscription Revenue Analytics BC-4250.70

Computation and analysis of recurring-revenue health metrics including ARR, MRR, NRR, GRR, and cohort views.

1 provider, 1 API surface

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
LeadpingPaymentMethodsUsage2 APIs78.4
Strong 3 Solid coverage with minor gaps
NexGen CloudPaymentauto-topup2 APIs65.6EVEDEXRefund1 API57.6Pomopayment1 API56.1
Developing 3 Usable, with meaningful gaps to close
Platform.shInvoicesOrdersRecords3 APIs52.9BlngBilling1 API49.0Vehicles.devControl1 API44.2
Thin 1 Limited public surface area
CacheflowInvoiceInvoice ConfigurationsInvoicesMetrics11 APIs30.3

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 Subscription 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 →