Where ERP Meets Lead-to-Cash

Last updated 12 Oct 2026

At a glance

ERP takes part in Lead-to-Cash at five edges: device stock and cost, physical fulfilment, installation stock, billing-to-ledger posting and network CAPEX. It has no role in decomposition, activation, rating or charging. Receivables, revenue accounting and asset reconciliation are where the boundary needs a decision.

The picture

ERP takes part at the edges of Lead-to-Cash. The core of the flow has no ERP in it.

Lead-to-Cash (BSS / OSS)

Lead / CRMno ERP role
CPQ1
Order capture (COM)1
Physical fulfilment2
Field installation3
SOM, ROM, activationno ERP role
Rating, charging, invoicing4

ERP’s five edges

1Device stock and cost; reservationCatalog keeps the price
2Pick, pack, ship; returnsSerial to resource inventory once assigned
3Van stock and materialsField service owns the job
4Summarised revenue, receivable and tax journalsBilling calculates; ERP owns the ledger
5Network CAPEX: purchase, goods receipt, capitalisationBeside the flow, not in it

Receivables and revenue accounting sit on the boundary and need an explicit decision

The Lead-to-Cash flow runs through BSS and OSS. ERP touches it at five numbered edges; network CAPEX sits beside the flow, and the core steps have no ERP role.

How it works

Why ERP stays at the edges

An ERP has its own order-to-cash: a sales order, a shipment, an invoice, a receivable. It is built around items and discrete orders. Telco Lead-to-Cash adds three things an ERP does not model at subscriber scale: catalog-driven decomposition into CFS, RFS and resources; fulfilment through COM, SOM and ROM; and high-volume rating and charging.

Five touchpoints

Device stock and cost at quote and order

CPQ reads stock availability and device cost; order capture reserves the device. The commercial price stays in the product catalog.

Physical fulfilment and returns

Pick, pack and ship; returns and reverse logistics of routers and set-top boxes, often through a logistics partner.

Field installation stock

Van stock and materials used by engineers, and engineer time costed to projects.

Billing to the ledger

Billing posts summarised revenue, receivable and tax journals; payments and IFRS 15 adjustments follow.

Network CAPEX

Purchase orders and goods receipts for network equipment, collected on build projects and capitalised as fixed assets.

Step by step

Lead-to-Cash step	ERP’s role
Lead / CRM	None; at most a debtor copy for finance
CPQ	Supplies device stock and cost
Order capture (COM)	Reserves the device
Physical fulfilment	Pick, pack, ship; returns
Field installation	Van stock and materials
SOM, ROM, activation	None
Rating, charging, invoicing	None; receives summarised journals
Receivables and collections	Either billing keeps them, or an ERP subledger does
Revenue accounting (IFRS 15)	Contract assets and liabilities, deferred revenue
Dealer commissions	Payable and accrual
Interconnect and roaming	Payables, receivables and accruals
Network CAPEX	Purchase, goods receipt, capitalisation

A pattern, not a standard

No vendor-neutral source publishes this division of ownership for telcos, and operators draw it differently. Use it as the starting position to argue from, and record where your estate departs from it.

Who owns what

Entity	System of Record	System of Engagement	System of Reference	Notes
Commercial price	Product Catalog	—	CPQ	ERP supplies device cost, never the price.
Device stock and cost	ERP	—	CPQ, COM	—
Device reservation	ERP	—	COM	COM owns the order; ERP owns the reservation against stock.
Assigned device (serial)	Resource Inventory	—	ERP or warehouse system	Once the device is assigned to a customer it is a network resource as well as stock.
Installation job	Field service	—	ERP	ERP owns the stock movements and costs.
Dealer commission payable	ERP	Commission engine	—	The commission engine calculates; ERP owns the payable.
Interconnect and roaming ledger	ERP	Wholesale billing	—	Wholesale billing calculates; ERP owns the ledger.
Network asset	ERP (financial asset)	—	Resource Inventory	Resource inventory owns the network instance.

In practice

The edges look simple on a diagram and are often where fallout hides. A device reserved in ERP but never shipped, a serial shipped but never recorded in resource inventory, or a returned router restocked without the customer’s product being terminated: each leaves stock, inventory and the customer’s product disagreeing.

Legacy reality

Older estates often wired these edges point to point as each need arose: a stock check here, a journal file there. The ownership was never written down, so receivables, revenue accounting and asset reconciliation were decided by whichever system was integrated first. A transformation has to make those choices explicitly, because a new BSS will not make them for you.

The trade-off

What it solves

Keeping ERP at five named edges lets each system do what it was built for, and makes every crossing a defined interface with a named owner.

What it does not solve

Who owns receivables and revenue accounting. Those still need a decision.
Stock and inventory drift at the device edge.
Asset reconciliation between ERP and resource inventory.

What it adds

Five interfaces to build, run and reconcile, most of them without a TM Forum standard.
Devices that are stock in ERP and a resource in inventory at the same time.

Architecture decision

How much of the order flow should touch ERP?

Edges only
Choose when BSS and OSS handle the order, the service and the bill, and ERP is fed stock, cost and summarised journals.
ERP-led order-to-cash for some lines
Choose when a line of business sells discrete items with no network service to decompose, such as hardware-only sales.

Breaks if Subscription services are pushed through ERP sales orders. ERP cannot decompose into CFS, RFS and resources, so the order is rebuilt by hand in the OSS.

Takeaways

Key Takeaways

ERP takes part in Lead-to-Cash at five edges: device stock, physical fulfilment, installation stock, billing-to-ledger posting and network CAPEX
It has no role in decomposition, activation, rating or charging
The catalog owns the price; ERP owns stock and cost
Receivables, revenue accounting and asset reconciliation are where the boundary needs a decision

Check yourself

A CPQ designer wants to read device prices from ERP because ERP already holds device cost. Is that right?Show answerHide
No. ERP owns stock and cost; the commercial price belongs to the product catalog. CPQ reads availability and cost from ERP and the price from the catalog.
A router is shipped from the warehouse and installed. Which systems should now know its serial number, and why?Show answerHide
ERP or the warehouse system for the stock movement and its value, and resource inventory because the assigned device is now a network resource that fulfilment and assurance act on.