The ERP Vendor Landscape for Telcos
Last updated 12 Oct 2026
At a glance
No analyst ranks ERP vendors for telecoms. On public operator evidence, SAP and Oracle lead and IFS, Microsoft and Workday follow on thin evidence. SAP BRIM overlaps BSS billing, and the SAP ECC 2027 deadline is behind many programmes.
The picture
Five ERP vendors by public telco evidence, and the dates that start programmes
Operator evidence
- 1SAP · S/4HANA, RISE, BRIMLargest base among large operatorsStrong
- 2Oracle · Fusion Cloud ERP, EBSMost visible recent replacement winsStrong
- 3IFS · IFS CloudAssets, projects, field serviceWeak
- 4Microsoft · Dynamics 365 Finance + SCMMid-size operators and altnetsWeak
- 5Workday · Financial ManagementNo operator group ledger foundWeak
Mostly vendor-announced: shows what was chosen, not how it went
Support deadlines
- 2027SAP ECC mainstream maintenance ends (31 Dec)
- 2030SAP ECC extended maintenance
- 2033SAP RISE transition option (terms vary)
- 2037+Oracle EBS 12.2 Premier Support, at least
A forcing date for SAP ECC estates; none for Oracle on-premise
How it works
How the ranking is built
The ranking weighs, in order: documented operator customers, fit for large multi-entity groups, handling of network assets and CAPEX, and telco-specific capability. Almost all of the telco evidence is vendor-announced: it shows what was chosen, not how it went.
| # | Vendor | Operator evidence | Strengths | Limitations | Evidence |
|---|---|---|---|---|---|
| 1 | SAP (S/4HANA, RISE, BRIM) | Deutsche Telekom, Vodafone (26 countries), BT, AIS | Largest base among large operators; the only ERP with native convergent invoicing (BRIM) | BRIM overlaps BSS billing and receivables; heavily customised ECC estates are costly to convert | Strong |
| 2 | Oracle (Fusion Cloud ERP, EBS) | AT&T, Bharti Airtel, KPN, VEON, VodafoneZiggo | Most visible recent replacement wins; ERP, supply chain and HR as one suite | Wins are vendor-announced with little outcome data | Strong |
| 3 | IFS (IFS Cloud) | TDC NET, for field service | Assets, projects and field service on one platform | Few core-finance operator references; often runs beside another vendor’s ledger | Weak |
| 4 | Microsoft Dynamics 365 Finance + SCM | Fibrus, a UK fibre altnet | Fits mid-size operators and altnets with multi-entity CAPEX | No large-operator reference found; telco capability comes from partners | Weak |
| 5 | Workday (Financial Management) | Telstra, for HR | Strong in HR; a Leader for service-centric companies | No network operator found running Workday as its group ledger | Weak |
SAP and Oracle are close
By estimated ERP revenue, Oracle edged past SAP in 2024 (about 6.6% each; both figures are modelled estimates, as neither vendor reports ERP separately). Installed base among large operators favours SAP; recent momentum favours Oracle. The core ERP of several large operators, including Telefónica, Orange, Verizon and Singtel, could not be confirmed from primary sources, and would change the order if found.
Deadlines that drive programmes
- SAP ECC: mainstream maintenance ends 31 December 2027; extended maintenance runs to 2030, and a RISE transition option to 2033 (terms vary between sources). This deadline is behind many telco S/4HANA programmes.
- Oracle E-Business Suite 12.2: Premier Support runs to at least 2037, so Oracle on-premise operators have no forcing date.
Who owns what
| Entity | System of Record | System of Engagement | System of Reference | Notes |
|---|---|---|---|---|
| General ledger and fixed assets | ERP (whichever vendor) | — | — | The same capability areas across SAP, Oracle and Microsoft (7.1). |
| Invoice and customer receivable | BSS billing, or SAP BRIM convergent invoicing with FI-CA: one, never both | — | ERP general ledger | BRIM puts invoicing and receivables on the ERP side (7.3). |
| Field service jobs and passive assets | Field service or OSS | — | ERP fixed assets | IFS is often deployed here, beside another vendor’s ledger. |
In practice
Group operators can run more than one ERP across legal entities after acquisitions, and specialist products such as IFS for field service sit beside the group ledger. The boundary questions in this module apply to each of them.
The trade-off
What it solves
An evidence-weighted view separates vendors with documented operator use from those with thin public evidence, before a selection relies on marketing claims.
What it does not solve
- Outcome data; most evidence shows what was chosen, not how it went.
- The ERP of several large operators, which could not be confirmed.
- The boundary decisions on receivables, revenue and assets, which no vendor makes for you.
What it adds
- Overlap with BSS where the ERP vendor also offers charging and invoicing.
- Programme timing driven by vendor support dates rather than business need.
Architecture decision
How should the SAP ECC 2027 deadline be used?
Technical conversion to S/4HANA
Choose when the billing interface, receivables ownership and asset reconciliation already work and are documented.
Conversion plus boundary redesign
Choose when receivables are split across systems, the ledger feed is undocumented, or the asset register has drifted from inventory.
Breaks if the programme is funded as an upgrade only. The platform changes and the boundary problems move across unchanged.
Takeaways
Key Takeaways
- SAP and Oracle lead on strong evidence; IFS, Microsoft and Workday follow on thin public evidence
- Most telco ERP evidence is vendor-announced: what was chosen, not how it went
- SAP BRIM overlaps telco billing, so receivables ownership must be decided explicitly
- The ECC 2027 deadline is a chance to fix the ERP boundary, not just the platform
Check yourself
An operator with a telco BSS billing platform is offered SAP BRIM as part of an S/4HANA deal. What must be decided first?Show answerHide
Which system owns invoicing and customer receivables. BRIM overlaps BSS billing; running both live for the same customers gives two balances and two dunning runs.
A vendor shows a list of operator logos as evidence of telco fit. How much weight do you give it?Show answerHide
Limited. Announcements show what was chosen, not how it went, and some name a single function such as field service or HR rather than the group ledger. Ask which capability each operator runs and what the outcome was.