BSS/OSS Academy
πŸ—ΊοΈ
Section 8.3

Lead-to-Cash Flow

The complete Lead-to-Cash process flow mapped to eTOM, with system ownership at each step.

Section 1.4 introduced Lead-to-Cash and its sub-domain processes. This section maps the L2C flow to specific eTOM process areas, system responsibilities, and API interactions β€” showing how each sub-process executes in practice.

Lead-to-CashTop-Level ProcessCovers the full customer journey from first engagement (lead)β†’ service delivered (activation) β†’ revenue realised (cash)SUB-PROCESSES← VALUE STREAM β†’Lead-to-Order(L2O) β€” Commercial Front-Endβ€’ Lead Generation & Captureβ€’ Opportunity Managementβ€’ Customer Lifecycle Mgmtβ€’ Offer, Price & Quote (CPQ)β€’ Credit Risk Assessment / KYCβ€’ Order Entry / Capture (COM)β€’ Contract Managementβ€’ Logistics (ERP)Order-to-Activation(O2A) β€” Technical Fulfilmentβ€’ Order Validation & Decompositionβ€’ Fulfilment & Provisioning (SOM)β€’ Service Orchestrationβ€’ Change Order Handling (eCOF)β€’ Service Activation (ROM)β€’ Field Installation Handlingβ€’ Subscription Lifecycle Mgmtβ€’ Send Billing FilesOrder-to-Cash(O2C) β€” Revenue Realisationβ€’ Service Activation Confirmationβ€’ Billing & Invoicingβ€’ Payment Processingβ€’ Collections & Dunningβ€’ Revenue Assuranceβ€’ Financial Reporting & Accβ€’ Customer Dispute Resolutionβ€’ Bill Adjustments / RCATrouble-to-Resolve(T2R) β€” ITSM & Operationsβ€’ SLA Mgmt (Service Assurance)β€’ ITIL Ticket & Case Mgmtβ€’ Asset Managementβ€’ Field Servicesβ€’ Change Managementβ€’ Backend Engineering Tasksβ€’ Order Process Trackerβ€’ Source of Billing AccountsStrongest interaction with ITSM processes
Figure 8.2a β€” L2C as the top-level process, its three sub-processes (L2O, O2A, O2C), and T2R as the separate assurance process

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.

Lead-to-Cash: End-to-End Flow

1
Marketing & Campaign
Marketing / Product Catalog

Define target segments, create campaigns, and generate awareness. Product offerings are defined in the catalog and made available to channels.

2
Lead Capture
CRM

Capture prospect interest from campaigns, web, retail, or partner channels. Qualify leads and assign to sales resources.

3
Opportunity Management
CRM

Convert qualified leads into sales opportunities. Identify customer needs and map to appropriate product offerings.

4
Configure, Price & Quote
CPQ / Product Catalog

Build a valid product configuration, apply pricing rules, and generate a formal quote. Validate feasibility and eligibility.

5
Order Capture
COM (Commercial Order Management)

Convert accepted quote into a formal commercial order. Validate completeness, perform credit checks, and submit for fulfilment.

6
Order Decomposition & Orchestration
SOM / ROM

Decompose the commercial order into service orders (CFS-level) and resource orders (RFS-level). Orchestrate the fulfilment sequence.

7
Service Activation & Resource Provisioning
SOM / ROM / Network Activation

Activate CFS instances in SLM. Provision RFS instances and configure network resources. Run automated testing.

8
Billing & Revenue Collection
Billing / Revenue Management

Activate billing for the new service. Generate the first invoice. Collect payment and recognise revenue.

Stage-by-Stage Breakdown

Each L2C stage has a clear owner, eTOM mapping, and handoff point. Navigate through the stages below.

Stage 1: Marketing & Campaign

BSS

Define target segments, create campaigns, and publish Product Offerings to channels via the catalog. eTOM: Marketing Fulfilment Response (1.1.1.1). APIs: TMF620 (catalog), TMF691 (loyalty). System: Marketing Platform + Product Catalog.

1 / 7

L2C Flow Variations

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

  • Customer performs their own CPQ β€” stages 2-3 compressed or eliminated
  • CPQ logic runs in digital frontend via BFF APIs
  • Requires fully automated zero-touch fulfilment end-to-end
  • Typical for simple consumer products (mobile, broadband)

Common L2C Failures and Anti-Patterns

Anti-Pattern: Order Fallout
Orders fail in fulfilment because CPQ skipped feasibility. Fix: pre-order qualification (TMF645) and real-time inventory checks before quoting.
Anti-Pattern: Manual Decomposition
Manual translation from commercial to service/resource orders creates bottlenecks and errors. Fix: catalog-driven decomposition using service and resource catalog rules.
Anti-Pattern: Billing Disconnect
Billing not tied to activation events means customers charged for undelivered services, or billing starts weeks late. Fix: activation-triggered billing, not order-triggered.

Lead-to-Cash β€” Key Points

  • L2C is the primary value chain: Marketing β†’ Lead β†’ Opportunity β†’ Quote β†’ Order β†’ Fulfilment β†’ Billing β†’ Revenue
  • It traverses the entire eTOM Fulfilment vertical across CRM, SM&O, and RM&O layers
  • The BSS-to-OSS handoff happens at order decomposition: Product Order β†’ Service Order β†’ Resource Order
  • TMF622 (Product Ordering) is the critical API at the BSS/OSS boundary
  • CPQ must include feasibility checks (TMF645) to prevent order fallout
  • Catalog-driven decomposition eliminates manual translation from commercial to technical
  • Billing should be activation-triggered, not order-triggered
  • The flow varies by channel (self-service, assisted, partner) but the stages remain the same