Capitalizing costs to fulfil a contract

Where setup or onboarding work is not a distinct performance obligation (bundled into the subscription), the direct costs of performing that work can still qualify as fulfilment cost assets under IFRS 15 and be amortized over the benefit period, rather than hitting profit or loss immediately while the corresponding fee is deferred as revenue. Expensing these costs on day one while the related revenue trickles in over years creates an artificial margin dip that misrepresents the true unit economics of onboarding a customer.

Has it been confirmed that the setup or onboarding activity is NOT a distinct performance obligation before applying the fulfilment-cost analysis? Do the costs relate directly to a specific identified contract, and do they create or enhance resources that will be used to satisfy performance obligations in the future? Are the costs expected to be recovered through the contract, and would another standard (e.g., IAS 38 or IAS 2) capture them first rather than IFRS 15 fulfilment costs?

1. First confirm the setup/onboarding activity is not a distinct performance obligation (if it were distinct, its costs would simply be matched to revenue recognized as that service is delivered, and this fulfilment-cost analysis would not apply).
2. Check whether the costs fall within the scope of another standard (e.g., property, plant and equipment, or intangible assets under IAS 38); if so, apply that standard instead.
3. If not in scope of another standard, apply the three IFRS 15 fulfilment-cost criteria cumulatively: the costs relate directly to an identifiable, specific contract (e.g., a specific customer's data migration, not general capability-building); the costs generate or enhance resources that will be used to satisfy performance obligations in the future (not costs relating to past performance already delivered); the costs are expected to be recovered through the contract's transaction price.
4. Exclude costs that are general and administrative in nature, that relate to satisfied (past) performance obligations, or that relate to remaining obligations that cannot be distinguished from costs of past performance.
5. Capitalize only the qualifying, contract-specific direct costs (e.g., engineer time on a specific customer's migration), not general overhead or wasted/inefficient effort.
6. Set the amortization period consistent with the pattern of transfer of the related good or service, typically the same period used for the deferred setup fee or the expected customer relationship period, whichever reflects the actual benefit pattern.

Measure the capitalized fulfilment cost asset at the actual direct cost incurred (e.g., engineer hours at a fully burdened rate, or amounts paid to a subcontractor for the specific migration), excluding general overheads, cost of wasted materials or labor, and costs relating to past performance already satisfied. Amortize on a systematic basis consistent with the transfer of the related goods or services, typically matching the period over which the corresponding deferred setup fee (if any) is released to revenue, or the expected customer relationship period if the benefit extends beyond the initial term. Test the asset for impairment whenever its carrying amount exceeds the remaining consideration expected to be received less directly related costs still to be incurred.

Disclose: the closing balance of capitalized fulfilment cost assets, presented alongside (but distinguishable from) contract cost assets arising from incremental costs to obtain a contract (e.g., commissions); the amortization method and period applied and its consistency with the related deferred revenue; the amortization expense recognized in the period and the line item where it sits; any impairment losses recognized on fulfilment cost assets; the judgment applied in distinguishing capitalizable contract-specific costs from expensed general/administrative costs.

• Expensing implementation labor immediately while deferring the matching setup fee as revenue, creating an artificial margin distortion in the onboarding period
• capitalizing general engineering overhead or platform-wide infrastructure costs that are not specific to an identifiable contract
• capitalizing wasted or inefficient effort (e.g., rework caused by errors) that should be expensed as incurred
• failing to check whether costs actually fall within the scope of IAS 38 or IAS 16 first, before defaulting to the IFRS 15 fulfilment-cost criteria
• using an amortization period disconnected from the actual pattern of benefit (e.g., amortizing over the initial 1-year term when the customer relationship is expected to last much longer).