Mapping multi-element contracts to performance obligations
· James Okonkwo
Bundled deals look simple commercially and complex on the ledger. A three-year licence, implementation, and ongoing support may be one customer conversation — and three or more distinct performance obligations for recognition purposes.
Start with the contract language, not the invoice schedule. Identify promises the customer can benefit from separately, then allocate transaction price on relative stand-alone selling prices. Where SSPs are not observable, document the estimation method and keep it consistent across similar deals.
UK mid-market teams often skip the allocation step when billing is front-loaded. That creates a deferred revenue balance that nobody can explain eighteen months later. A short mapping sheet per material contract — obligation, SSP basis, recognition pattern — prevents that drift.
When in doubt, treat the mapping as a living control: update it when change orders land, not only at year end.