Lead-to-Cash Flow

What Is Lead-to-Cash?

The Lead-to-Cash (L2C) process is the most critical end-to-end flow in any telco. It describes the complete journey from initial customer interest through to revenue collection — spanning marketing, sales, ordering, fulfilment, and billing. In eTOM terms, L2C traverses the entire Fulfilment vertical and touches all horizontal layers.

Getting L2C right is the difference between a telco that can launch products in days and one that takes months. It is also where BSS and OSS must work together most tightly — a commercial order must seamlessly decompose into technical fulfilment without manual intervention.

The Complete L2C Flow

The Lead-to-Cash flow can be broken into eight major stages. Each stage has a primary system owner, specific eTOM process mappings, and TM Forum API touchpoints. Understanding this flow end-to-end is essential for any BSS/OSS architect.

Stage 1: Marketing & Campaign Management

The L2C flow begins before the customer even makes contact. Marketing processes define target segments, design campaigns, and publish product offerings to sales channels. In a catalog-driven architecture, this means configuring Product Offerings in the Product Catalog with appropriate pricing, eligibility rules, and channel visibility.

Stage 2-3: Lead & Opportunity Management

Once a prospect engages, the CRM system captures the lead — a record of expressed interest that has not yet been qualified. Lead qualification assesses whether the prospect is a viable customer (credit-worthy, in a serviceable area, has a genuine need). Qualified leads become opportunities — tracked sales prospects with an estimated value and probability of closure.

In eTOM, this maps to the Selling process (1.1.1.2) at the CRM horizontal layer. The CRM system is the System of Record for leads, contacts, and opportunities. TM Forum APIs involved include TMF629 (Customer Management) for creating/updating customer records and TMF672 for managing user permissions across channels.

Stage 4: Configure, Price & Quote (CPQ)

The CPQ stage is where commercial intent becomes structured. The sales agent (or self-service customer) selects a Product Offering from the catalog, configures it with the required characteristics (e.g., bandwidth speed, number of TV channels), applies pricing rules, and generates a formal quote.

CPQ enforces catalog-driven rules: eligibility constraints (can this customer buy this product?), compatibility rules (which add-ons work with which base products?), and pricing logic (discounts, bundles, promotions). The output is a validated Quote that can be converted to an Order.

Stage 5: Order Capture (COM)

When the customer accepts the quote, it converts into a Product Order — the formal commercial instruction to deliver products and services. The Commercial Order Management (COM) system captures this order, validates it, performs credit checks, and submits it for fulfilment.

The Product Order is the contract between BSS and OSS. It specifies what the customer has bought in commercial terms. It is the responsibility of the downstream systems (SOM, ROM) to interpret this commercial intent and translate it into technical actions.

Stage 6: Order Decomposition & Orchestration

This is the critical BSS-to-OSS handoff. The commercial Product Order must be decomposed into one or more Service Orders (at the CFS level) and subsequently into Resource Orders (at the RFS/Resource level). This decomposition follows the rules defined in the Service and Resource Catalogs.

Stage 7: Service Activation & Resource Provisioning

This stage is where the order becomes real. Service Order items are executed by activating CFS instances in the Service Inventory. Resource Order items are executed by provisioning RFS instances and configuring physical/logical resources via network activation systems (Element Management Systems, SDN controllers, etc.).

Once activation is complete, the status propagates back up: Resource Order complete → Service Order complete → Product Order complete. The Product Inventory is updated with the new product instance, linking the commercial record to the underlying service and resource instances.

Stage 8: Billing & Revenue Collection

The final L2C stage activates billing for the new service. The billing system receives notification that fulfilment is complete and begins the charging lifecycle. This includes setting up recurring charges (subscriptions), one-time charges (installation fees), and usage-based charging configurations.

In eTOM, this maps to Billing & Collections Management (1.1.4) processes. The key TM Forum APIs are TMF678 (Customer Bill Management) for invoice generation and TMF654 (Prepay Balance Management) for prepaid scenarios.

eTOM Level 2 Process Map for L2C

The complete L2C flow touches the following eTOM Level 2 processes. This table shows how the flow traverses across the eTOM matrix from CRM through SM&O to RM&O:

Unified Step-by-Step Mapping: eTOM, System, Data & API

The following reference table maps each Lead-to-Cash step to all four architectural dimensions simultaneously: the eTOM capability being executed, the owning system (BSS or OSS), the SID data entities created or consumed, and the TM Forum API used at the integration point. This is the definitive architect-grade reference for L2C traceability.

TM Forum API Touchpoints Across L2C

Each major integration point in the L2C flow corresponds to a TM Forum Open API. These APIs define the standard contracts between systems, enabling multi-vendor interoperability:

L2C Flow Variations

Not every L2C flow follows all eight stages. The flow varies depending on the sales channel, customer type, and product complexity:

Common L2C Failures and Anti-Patterns