
Paper P2: Corporate Reporting (International)
438 Go to www.emilewoolfpublishing.com for Q/As, Notes & Study Guides © EWP
4.7 DP: Revenue recognition in contracts with customers
Revenue is a key component of a company’s financial statements. Revenue is an
important indicator for providers of capital and is also important to financial
statement preparers, auditors and regulators.
This discussion paper is the result of a joint project between the IASB and FASB (the
US Financial Accounting Standards Board)
The aim of the joint project is primarily to clarify the principles for recognising
revenue.
US GAAP on revenue recognition comprises more than a hundred standards and
can produce conflicting results for economically similar transactions.
IFRS has two main revenue recognition standards (IAS 18 Revenue and IAS 11
Construction Contracts). These are inconsistent and vague, and can be difficult to
apply beyond simple transactions. In particular, those standards provide limited
guidance for transactions involving multiple components or multiple deliverables.
The aim of the project is to provide clearer guidance on when an entity should
recognise revenue and reduce the number of standards to which entities have to
refer. This should remove inconsistencies and improve the comparability and
understandability of revenue for users of financial statements. The proposed
approach would cause little (if any) change for many contracts.
The proposed approach
This discussion paper proposes a single, contract-based revenue recognition model.
This proposed model would only apply to contracts with customers. It might not be
appropriate to apply the model to certain categories of contracts with customers (eg
leases) and the boards will consider this as their deliberations proceed
Recognition
The DP proposes that revenue should be recognised on the basis of increases in an
entity’s net position in a contract with a customer. Revenue would be recognised
when a contract asset increases or a contract liability decreases. That occurs when an
entity performs by satisfying an obligation in the contract.
Identification of performance obligations
A company’s performance obligation is a promise in a contract with a customer to
transfer an asset (such as a good or a service) to that customer. That contractual
promise can be explicit or implicit.
When an entity promises to provide a good, it is promising to transfer an asset to
the customer.
When an entity promises to provide a service, it similarly is promising to transfer an
asset, even though the customer may consume that asset immediately.
A company would account for performance obligations separately if the promised
assets (goods or services) are transferred to the customer at different times. The
objective of separating performance obligations is to ensure that an entity’s revenue
faithfully represents the pattern of the transfer of assets to the customer over the life
of the contract. For example, if a photocopier were sold with a service agreement the
revenue from each would be recognised separately as appropriate.