Telecommunications · Bundled contracts and revenue recognition
When every subscriber contract is really two contracts
A handset plus a subscription is one commercial offer and two performance obligations. IFRS 15 / MFRS 15 requires the total contract price to be allocated between the device, recognised at a point in time, and the service, recognised over time. Multiply that by millions of subscribers, then add upgrades, plan changes, early terminations and promotional pricing, and the accounting question becomes a data question.
See how it worksThe problem
A national mobile operator was managing millions of bundled subscriber contracts where the CRM and the general ledger held different versions of the same commercial reality. Unbilled revenue and contract asset positions had to be tracked across the life of each bundle, and the reconciliation between the two systems was absorbing significant manual effort every close.
CRM and ledger drift
Manual contract asset tracking
How Hamilton CEM is applied
Hamilton CEM identifies performance obligations from the contract category structure and allocates the transaction price across them. Business events such as activation, upgrade or plan change trigger the corresponding accounting treatment as the event happens, generating the contract asset and contract liability entries in the sub-ledger before selected results are posted back to the general ledger. Remaining performance obligation and movement reporting are produced from the same processed dataset.
Contract category
Performance obligations
Transaction price allocation
Event processing
Projection, movement and status reporting
In the revenue assurance lead’s words
“I want transaction prices allocated across complex handset bundles from the event itself, so the team can reduce reliance on manual Excel reconciliation and support IFRS 15 / MFRS 15 disclosure from a consistent, traceable record.”
What changes
BeforeWith Hamilton CEM
Allocation logic maintained in spreadsheetsAllocation driven by configured contract rules
CRM and ledger drift discovered at closeReconciliation reporting against a common event record
Contract asset and unbilled tracking manualGenerated as part of event processing
Disclosure assembled from multiple extractsProjection, movement and status reporting from one source
Standards in scope
IFRS 15 / MFRS 15 revenue from contracts with customers, including performance obligation identification, transaction price allocation and reallocation, contract asset and contract liability treatment.
Deployment
Available as an SAP-native edition for SAP S/4HANA landscapes and as a standalone edition where revenue contract processing sits outside SAP.
