To no one’s surprise, the IASB has issued an amendment to the revenue standard, IFRS 15 Revenue from Contracts with Customers, formalizing the deferral of its effective date by one year to 2018.
Here’s how the news release summarizes this action:
- “The publication of the amendment, Effective Date of IFRS 15, follows from the IASB’s decision in July to defer the Effective Date from January 1, 2017 to January 1, 2018, having considered the feedback to its consultation.
- Companies applying IFRS continue to have the option to apply the Standard early.
- The main reason for the amendment is that the IASB is currently consulting on some proposed clarifications to the Standard. These proposals follow discussions within the Revenue Transition Resource Group (TRG). The TRG was established by the IASB and the US Financial Accounting Standards Board (FASB) after the Standard was issued in May 2014 to support companies in its implementation.
- Consultation on the proposed clarifications ends on October 28, 2015. The IASB expects to complete its discussions on the clarifications in the light of the feedback received by the end of 2015, after which any final amendments to the Standard will be issued.”
(NB We’ve covered the proposed clarifications in several recent posts, most recently here).
The basis for conclusions to the amendment observes: “changing the effective date of a Standard shortly after its issuance creates uncertainty for stakeholders and has the potential to set a bad precedent. The effective date is set after consideration of information obtained in the exposure process about the time needed to implement the requirements. Accordingly, the IASB would consider changing the effective date only in exceptional circumstances.” These are the stated reasons why the IASB thinks it met that hurdle here:
- “The IASB acknowledged that, although intended to provide clarity, the proposed amendments to IFRS 15…may affect some entities that would wish to apply any amendments at the same time as they first apply IFRS 15. Those entities are likely to wish to avoid reporting changes to revenue when first implementing the Standard and then, within a year or two, potentially reporting further changes to revenue as a result of applying any amendments to the Standard. For those entities, a deferral of the effective date by one year would provide additional time to implement any amendments to the Standard.
- IFRS 15 was issued later than had been anticipated when the IASB set the effective date of the Standard, which absorbed some of the implementation time that entities were expecting to have.
- IFRS 15 is a converged Standard with Topic 606—although this was not the only consideration, the IASB observed that there are benefits for a broad range of stakeholders of retaining an effective date that is aligned with the effective date of Topic 606.”
My views on this haven’t changed much since I wrote about the exposure draft here. It’s no surprise that “almost all respondents to the Exposure Draft agreed with the proposal to defer the effective date of IFRS 15 for one or more of the reasons noted by the IASB.” I can’t say I’m very enthusiastic about it though. These supposedly exceptional circumstances sound to me merely like standard-issue whining and foot-dragging. Companies pull off remarkable feats of change all the time – their ability to do so is supposedly part of why we venerate private sector entities (and the highly paid people who lead them) more than the slow-moving wheels of government. It’s not remotely believable that a few months here or there in 2014 would make a difference to meeting a 2017 reporting deadline, to an entity that was really trying. Likewise, the other factors seem well within the range of challenges that entities deal with every day without missing a beat.
But even if I’m wrong there, and if a 2017 implementation date actually would cause some difficulties for some entities and their stakeholders, it shouldn’t have been enough to tip the balance. IFRS 15 is meant to represent a major step forward in (using the IASB’s own words) the quality and consistency of financial statements, enhancing the reporting of a “vital metric” within the financial statements. If that’s true, it follows that current financial reporting is deficient (or at least sub-optimal) in this regard, and will continue to be so until the new standard is in place, and if that’s true in any way that matters, then investors must on a regular basis be making resource allocation decisions that aren’t appropriate given their tolerance for risk. If so, then fixing that as soon as possible should count for more than all the reasons cited.
The IASB’s deferral decision suggests it isn’t actually such an urgent priority, which in turn only invites you to conclude that the new standard isn’t truly addressing a vital lack in current decision-making – if it takes until 2017 for a discussion paper published in 2008 to generate actual changes in financial statements, then indeed, why not wait until 2018, or 2020, or 2030, or forever? Rather than fretting and tweaking, the IASB squandered a good opportunity here to say, basically: it may have taken a long time to get here, but now we’re serious about this, and you should be too.
The opinions expressed are solely those of the author.