Stand-Alone Selling Price

The stand-alone selling price is the price at which a company would sell a promised good or service to a customer separately from any bundle or contract. Under IFRS 15 and ASC 606, stand-alone selling prices are the starting point for allocating the total transaction price across performance obligations. Without them, companies cannot split bundled revenue correctly.

Why bundled revenue must be carved up

When a company sells a bundle of goods or services—software with maintenance, equipment with installation, goods with promotional rebates—the customer pays a single price for the package. But under IFRS 15 and ASC 606, each distinct promise (performance obligation) must be recognized as revenue separately, often at different times. The software revenue is recognized upfront; the maintenance revenue is recognized over the maintenance period. The equipment revenue is recognized at delivery; installation revenue is recognized as installation work progresses.

To know how much revenue to recognize for each obligation, the company must split the bundled price. Stand-alone selling price is the tool for that split. If a printer vendor sells a bundled package of hardware, setup, and three years of supply contracts for $5,000, the vendor cannot simply claim that all $5,000 is hardware revenue. It must estimate how much of that $5,000 relates to the hardware and how much to the services. Stand-alone selling prices—the prices at which each element would sell separately—drive that allocation.

Observable stand-alone selling prices

The cleanest case is when the company regularly sells the performance obligation separately. If a software vendor sells licenses for $1,000 and maintenance contracts for $200 per year, and these prices are charged to all customers, those are observable stand-alone selling prices. If the same vendor bundles the licence with five years of maintenance for $2,000, the allocation is clear: the licence gets $1,000 and the maintenance gets $1,000.

Observable prices carry the most credibility with auditors and regulators. They are based on actual market transactions and require minimal judgment. Accountants prefer them because they are defensible and verifiable.

However, many performance obligations are never sold separately. A custom software system built for a single customer will never have a “stand-alone” price because it is unique. A service that is only offered as part of a bundle has no market price of its own. In those cases, the company must estimate.

Estimating stand-alone selling prices

When the performance obligation is not sold separately, IFRS 15 and ASC 606 allow the company to estimate using one of three methods:

Adjusted market assessment approach — The company identifies a market in which similar obligations are sold separately, then adjusts for differences in the company’s costs, competitive positioning, or the specific customer’s circumstances. If a vendor offers custom IT consulting services, it might look at the market rate for comparable consulting (observable prices from competitors), then adjust for the company’s expertise or the customer’s industry complexity.

Expected cost plus margin approach — The company calculates its expected cost to deliver the obligation, then adds a reasonable profit margin. If a company manufactures a printer and bundles it with five years of supplies, it might estimate the standalone printer price as its manufacturing cost plus a typical markup of 30%. This method is common for goods but requires careful definition of “reasonable margin”—too low and the estimate is defensible; too high and auditors will push back.

Adjusted comparable unobservable prices approach — The company uses prices of similar obligations sold by competitors or in analogous transactions, adjusted for differences. This is used when the company’s own prices are not available but market data exists.

The allocation decision in practice

Suppose a cloud services provider signs a customer contract for €2,000,000 covering: (1) hardware installation (performance obligation A), (2) software licenses for five years (performance obligation B), and (3) support services for five years (performance obligation C). The customer will take all three but pays a single price that includes a 15% “bundle discount.”

The company estimates the stand-alone selling prices as follows:

• Hardware installation: €400,000 (based on similar projects sold separately)
• Software licenses: €1,200,000 (list price from price list)
• Support services: €800,000 (historical cost of support plus 20% margin)
• Total (unadjusted): €2,400,000

The actual contract price is €2,000,000. The allocation is proportional to the estimated stand-alone prices:

• Hardware: €2,000,000 × (€400,000 ÷ €2,400,000) = €333,333
• Licenses: €2,000,000 × (€1,200,000 ÷ €2,400,000) = €1,000,000
• Support: €2,000,000 × (€800,000 ÷ €2,400,000) = €666,667

Hardware revenue is recognized at delivery; license and support revenue are recognized over five years. The bundle discount is absorbed proportionally into each obligation’s allocated price.

When adjustments are allowed

The standard allows companies to adjust the basic stand-alone selling price allocation in specific cases. For example, if the company offers volume discounts (lower prices for larger quantities), the allocation should reflect those discounts. If the contract includes a pricing term unique to this customer—say, a price cap or escalation clause—that customer-specific adjustment applies to all obligations, not just one. The principle is that stand-alone selling prices are the starting point, but the actual contract terms matter.

Companies must document these adjustments. An auditor or regulator reviewing the revenue policy will ask: Why did you use those stand-alone prices? Where did the €1,200,000 software license price come from? Is it still current? Are there any special deals in the market that should lower it? The company should have clear answers.

Transparency and disclosure

IFRS 15 and ASC 606 require companies to disclose the significant judgments involved in determining transaction prices and allocating them to performance obligations. For contracts with estimated stand-alone selling prices (rather than observable ones), companies often explain their methodology in the notes to the financial statements. This is particularly important when the estimates have changed over time or when actual realized prices (if some obligations are later sold separately) differ materially from the original estimate.

Some companies also disclose ranges of estimates or sensitivity analysis: “If the estimated support services price had been 10% higher, revenue would have been X instead of Y.” This transparency helps investors and analysts understand how dependent reported revenue is on management’s judgments.

Real-world challenges

In practice, estimating stand-alone selling prices can be contentious. Managers want to minimize revenue recognized early (to smooth earnings or avoid debt covenant breaches). Auditors want estimates to be conservative. When the company has limited pricing history or operates in markets where pricing varies widely, disagreements are common.

A recurring issue: the “market assessment” is hard to pin down. A software vendor might claim the market rate for similar licenses is €1.5 million because a competitor once quoted that price, but that quote was three years old and in a different currency. A construction company might estimate the installation labour at cost-plus-30%, but 30% could reasonably be 25% or 40% depending on market conditions. These uncertainties are inherent to estimation.

The most defensible approach is to tie stand-alone selling prices to actual recent transactions. If the company sold the same obligation separately in the last 12 months, use that price. If it sold similar obligations, adjust transparently. If estimation is required, document the assumptions, show sensitivity analysis, and be prepared to defend the margin assumptions to auditors.

See also