Performance Obligation Templates: Automating Bundles for Accurate Revenue Recognition

Under ASC 606 and IFRS 15, companies must identify distinct performance obligations within customer contracts and allocate revenue fairly based on their Standalone Selling Prices (SSPs).

But what happens when products and services are always sold together as bundles? Manually splitting them into separate obligations for every contract would be tedious, error-prone, and inconsistent.

That’s where Performance Obligation Templates come in.

What is a Performance Obligation Template?

A performance obligation template is a predefined blueprint that groups multiple goods or services into a bundle, making it easier to:

• Automatically recognize each component as a separate performance obligation.
• Apply consistent SSP-based revenue allocation rules across all similar transactions.
• Reduce manual intervention, speed up contract processing, and ensure compliance.

Think of it as a rulebook that says:

“Whenever these items are sold together, treat them as a bundle, and split the revenue according to this SSP profile.”

Why Templates Matter

1. Consistency – Ensures bundled items are always handled the same way.
2. Compliance – ASC 606 / IFRS 15 require correct identification of performance obligations. Templates enforce consistent accounting.
3. Efficiency – Businesses often sell the same bundles (e.g., products + services). Templates avoid rework each time. Hence it automates allocation, eliminating manual calculations.
4. Pricing & Allocation: Templates link to the Standalone Selling Price (SSP) profiles so the system knows how to fairly allocate transaction price across items.
5. Audit Readiness – Provides a standardized, repeatable process auditors can validate.

Real-World Examples of Performance Obligation Templates

1. Software + Support + Training

• The Bundle: Annual software license, 1-year support, and 2 days of training.
• The Challenge: The system might only capture the software line item.
• The Template: Groups all three as separate obligations and allocates revenue automatically.

2. Hardware + Warranty

• The Bundle: Industrial equipment with a 3-year extended warranty.
• The Challenge: Only the equipment is recorded in Order Management.
• The Template: Splits the sale into equipment (immediate revenue) and warranty (deferred revenue), based on SSP percentages.

3. Telecom Bundles

• The Bundle: Handset, monthly service plan, and free upgrade after 12 months.
• The Challenge: Invoice only shows the monthly service fee.
• The Template: Automatically creates separate obligations for the handset, service, and upgrade.

4. Retail Promotions (Free Add-ons)

• The Bundle: Printer + free ink cartridges delivered later.
• The Challenge: Sales order only shows the printer.
• The Template: Ensures a portion of revenue is deferred for the ink cartridges.

5. Car Manufacturer

• A car manufacturer sells a truck and trailer together as a bundle.
• Instead of treating them as two separate obligations, they want the bundle to be one performance obligation.
• A PO Template is created for “Truck + Trailer bundle.”
• When this combo appears in a sales contract, the system automatically applies the bundle template and recognizes revenue accordingly.

How SSP Profiles Fit In

A Standalone Selling Price (SSP) profile defines how revenue is allocated across the grouped obligations.

Example:

• Bundle Price: $1,200 (Software + Support + Training)
• SSPs:
  • Software = $1,000
  • Support = $300
  • Training = $200
• Total SSP = $1,500

Allocation Calculation:

• Software: $1,200 × (1000 ÷ 1500) = $800
• Support: $1,200 × (300 ÷ 1500) = $240
• Training: $1,200 × (200 ÷ 1500) = $160

Without templates, this process would be manual and prone to errors. With templates, it’s automated and consistent.

Why It Matters Beyond Revenue Recognition

• Accounting: Proper timing of revenue and deferred revenue.
• Financial Reporting: Transparency in how revenue is earned from each bundle component.
• Business Insights: Understand profitability of individual elements (e.g., warranties vs. hardware).
• Strategic Decisions: Evaluate which bundles drive the most margin.
• Standalone Selling Price (SSP) Compliance: Supports fair allocation of revenue across items.
• Audit Trail: Auditors can see consistent application of rules, reducing risk of misstatements.

System Capabilities (Specific to Oracle RMCS)

Revenue Management allows multiple templates to be defined; each with a unique combination of items. For example: a car manufacturer may be selling a truck and a trailer as a bundle to the customers on regular basis and wants to treat both of them as one performance obligation. PO Templates take precedence over the PO Identification Rules in forming POs.

Define Performance Obligation Template to manage the items that are grouped together to be easily associated to the Standalone Selling Price Profile.

The Performance Obligation Templates are specific to the business and cannot be predefined.

When creating PO Templates, you can:

1. Flag as Exempt from Allocation – Example: A free training session offered with software. It’s tracked but no value allocated.
2. Set Default Classification – Example: Bundle always classified as “Software Package.”
3. Duplicate Templates – Save time when creating similar bundles.
4. End-Date Templates – Example: Old bundle no longer sold (e.g., 3G plan), so template is retired to avoid misclassification.

Final Thoughts

Performance Obligation Templates are more than just a compliance tool. They bring clarity, automation, and fairness into revenue allocation for bundled goods and services.

By leveraging templates, companies can:

• Automate repetitive revenue recognition tasks.
• Avoid compliance risks under ASC 606 and IFRS 15.
• Deliver accurate, transparent financial reporting.
• Gain better insights into the profitability of bundled offerings.

In today’s subscription-driven and bundle-heavy business environment, templates are essential for scaling revenue recognition without sacrificing accuracy.