Industries We Serve.
Sector-specific SAP configurations, domain knowledge, and honest capability statements across six industries. We lead with where we’ve genuinely delivered and are transparent about where we bring expertise rather than a long reference list. Our proven anchor is Consumer Products & Retail / luxury brand distribution in the GCC, delivered for AlMalki Group.
Complexity at the speed of digital.
Technology, media, and telecom companies are unusual among SAP clients: the ERP is rarely the system of record for revenue-generating activity, but it’s always the system of record for revenue recognition. That split — billing and subscription systems upstream, SAP Finance and RAR downstream — creates an integration and compliance burden that most other sectors don’t face. And because the 2027 ECC deadline lands on the same estates that are running end-of-support SAP PI/PO middleware, TMT organizations are often further behind on migration planning than they realize.
Key SAP modules & platforms in this sector
- SAP Revenue Accounting and Reporting (RAR) for IFRS 15 / ASC 606 performance obligation and revenue scheduling.
- SAP Integration Suite for BSS/OSS, CRM, and CDN connectivity, replacing legacy SAP PI/PO middleware.
- SAP Subscription Billing on BTP for recurring-revenue and usage-based commercial models.
- SAP Analytics Cloud for ARPU, churn, and subscriber lifetime value reporting.
Challenges this sector faces
- Fast-moving revenue models: subscription billing, usage-based pricing, and complex revenue recognition (IFRS 15).
- System proliferation: TMT organizations run heterogeneous IT estates; SAP integration with CRM, billing, and OSS is a recurring challenge.
- The 2027 pressure: TMT firms often have ECC estates powering billing and finance, making the migration timeline more urgent.
- Revenue recognition complexity: IFRS 15 / ASC 606 for software licences, SaaS subscriptions, multi-element arrangements, and contract modifications — SAP Revenue Accounting and Reporting (RAR) is the specialized module; incorrect IFRS 15 accounting is an audit risk.
- Billing system integration: telecom operators run separate BSS (Business Support Systems) for billing; SAP must receive billing data and process revenue recognition without double-counting.
- ECC estates in billing finance: many TMT firms run SAP ECC for financial accounting with a separate billing system upstream; the 2027 deadline adds urgency because the integration layer (often SAP PI/PO) also loses support in 2027.
- Contract lifecycle management: for technology companies managing multi-year customer contracts, SAP CLM (Contract Lifecycle Management) and SAP Ariba contract management integration.
Typical engagement shape
- Revenue model assessment first: mapping current billing-to-finance data flows and identifying where IFRS 15 performance obligations are currently handled manually or incorrectly.
- SAP RAR configured and parallel-tested against the existing revenue recognition process for at least one full reporting cycle before cutover.
- Integration layer migration (PI/PO to Integration Suite) planned alongside the ERP migration, not as a separate follow-on project.
- Analytics and ARPU/churn dashboarding delivered as an early, visible win to build stakeholder confidence in the broader transformation.
Common question: our billing system already calculates revenue — why do we need SAP RAR as well?
Billing systems calculate what to invoice; RAR determines when and how much of that value is recognized as revenue under IFRS 15 / ASC 606, which is frequently a different number and a different period, especially for multi-element arrangements and contract modifications. Running both without a reconciled bridge between them is one of the more common sources of restatement risk we see in TMT audits.
How we help
- S/4HANA Finance and Revenue Accounting (RA&R / IFRS 15) for complex subscription and usage-based revenue models.
- SAP Integration Suite for connecting SAP to the surrounding TMT system landscape.
- Analytics and operational reporting via SAC and Power BI.
- SAP Revenue Accounting and Reporting (RAR): the IFRS 15 / ASC 606 engine that handles performance obligation identification, transaction price allocation, and revenue recognition scheduling — IOTEK configures RAR within S/4HANA Finance.
- SAP Integration Suite for TMT: connecting SAP to BSS/OSS systems (Amdocs, Netcracker, Oracle Siebel), CRM (Salesforce), and CDN/content platforms; event-mesh for real-time billing event processing.
- Subscription management: SAP Subscription Billing on BTP for technology companies moving to recurring revenue models — integrated with S/4HANA Finance via APIs.
- SAP PI/PO migration: SAP PI and SAP PO mainstream maintenance ends 2027 alongside ECC; IOTEK migrates the middleware layer to SAP Integration Suite as part of the overall transformation.
- Analytics for TMT: SAC-based ARPU (Average Revenue Per User) dashboards, churn analytics, margin by product/service line, subscriber lifetime value reporting.
We describe Technology, Media & Telecom as a sector we can serve with genuine RAR, integration, and analytics depth; formal named client references for this sector are shared under consent as those relationships develop.
Secure systems for high-stakes environments.
Defense contractors, government agencies, and humanitarian organizations share a common thread: the technology has to work correctly in environments where failure has consequences well beyond a missed KPI — classified data exposure, audit findings on government contracts, or a broken identity record for a displaced person. IOTEK positions this as a capability sector built from three practices working together — SAP delivery, biometric identity, and Global Mobility deployment infrastructure — rather than a sector where we lead with a client reference list.
Key SAP modules & platforms in this sector
- SAP Project Systems (PS) and FICO for government contract accounting, indirect cost pools, and DCAA-aligned labor distribution.
- SAP Materials Management with serialization and batch traceability for defense supply chain integrity.
- SAP Global Trade Services (GTS) for ITAR/EAR export control screening.
- SAP configurations for humanitarian operations: grants management, field office accounting, and donor reporting.
Challenges this sector faces
- Security and compliance requirements that exceed standard enterprise norms: data classification, access controls, and deployment constraints are fundamental.
- Complex operational environments: deploying enterprise technology and specialist consultants to field environments requires a mobility practice.
- Identity assurance: high-assurance identity management for access control and field identity programs.
- Security classification and data handling: defense environments require data classification at the application layer, not just the network layer; SAP system architecture must accommodate classified data handling requirements (US DoD IL4/IL5, NATO Restricted).
- Contract and project accounting: defense contracts typically run under cost-plus or fixed-price-incentive-fee (FPIF) structures; SAP Project Systems (PS) and cost reporting must support government contract management requirements (DCAA audit compliance in the US).
- Supply chain integrity: defense supply chains have serialization, chain of custody, and ITAR (International Traffic in Arms Regulations) compliance requirements.
- Field deployment: deploying technology and consultants to operational environments requires security clearance management, travel risk management, and field-hardened systems.
Typical engagement shape
- Security and data classification requirements scoped before technical design begins, since they constrain hosting, integration, and even which consultants can be assigned.
- Contract accounting and cost-pool structures validated against the specific government or donor compliance framework in play (DCAA, UN agency financial rules, or equivalent).
- Biometric identity components piloted in a controlled environment before field rollout, given the operational and reputational stakes of field identity programs.
- Global Mobility coordination for any in-country or field consultant deployment, run as a distinct workstream alongside the technical implementation.
Common question: can you deploy SAP consultants into restricted or field environments, not just standard corporate offices?
That is precisely what our Global Mobility practice exists to coordinate — security vetting, travel risk management, and in-country logistics for consultants working in GCC locations, conflict-adjacent environments, or field operations tied to humanitarian programs. It runs as its own workstream alongside the technical SAP delivery, not as an afterthought bolted on once a project is already underway.
How we help
- SAP and ICT for defense and public-sector organizations — finance, supply chain, and operational systems for classified or restricted environments.
- Biometric identity capability for high-assurance environments (see Biometric Technologies).
- Global consultant deployment to complex or sensitive locations via our Global Mobility practice.
- SAP for Defense: Government Contract Accounting within SAP PS/FICO (DCAA compliance, indirect cost pools, labor distribution), Material Management with serialization and batch traceability, SAP GTS for ITAR/EAR export control screening.
- SAP for Humanitarian Organizations: SAP has specific humanitarian operations functionality used by UN agencies and NGOs — grants management, field office accounting, multi-currency operations, donor reporting; IOTEK can configure SAP for humanitarian contexts.
- Biometric field identity: IOTEK’s biometric practice covers field identity programs — voter registration, beneficiary identity, refugee identity management — using mobile biometric collection integrated with central ABIS.
- Global consultant deployment: IOTEK’s Global Mobility practice manages consultant deployment to complex or restricted locations — GCC, conflict-adjacent environments, field operations — with security vetting, travel risk management, and in-country support coordination.
- Secure hosting architecture: SAP in air-gapped, government cloud (GovCloud AWS, Azure Government), or on-premise secure environments — IOTEK designs the architecture, partners with certified hosting providers for classified workloads.
This is a sector we discuss in terms of capability composition rather than a client logo list: SAP delivery experience, a functioning biometric identity practice, and a Global Mobility function capable of deploying consultants into complex environments. Where we do have relevant engagements, they are discussed only under the appropriate consent and clearance arrangements.
Start with one process. See it work.
Thirty minutes, one process in your SAP estate, an honest read on whether an agent earns its keep and what it would take to build it.