Last week, I blogged about the proposed amendments to ASC 718. This week, I have some more information about them.
Is This a Done Deal?
Pretty much. The FASB has already considered—and rejected—a number of different alternatives on most of these issues. My understanding is that there was consensus among Board members as to each of the amendments and most of the changes aren’t really controversial, so we don’t expect there to be much debate about them.
Tax accounting is an exception, of course. This change is very controversial; in fact, the FASB considered this approach back when they originally drafted FAS 123(R) and ultimately rejected it is because of the volatility it introduces to the income statement. So perhaps there will be some opposition to this change.
What’s the Next Step?
The FASB will issue an exposure draft with the text of the changes, then will solicit comments, make changes as necessary, and issue the final amendments. I have hopes that we’ll see an exposure draft by the end of the year, with possibly the final amendments issued in the first half of next year.
ASC 718(R)?
No, the new standard will not be called “ASC 718(R),” nor will the amendments be a separate document. That’s the advantage of Codification. The amendments will be incorporated into existing ASC 718, just as if they had been there all along. In a few years, you may forget that we ever did things differently.
What’s the Next Project?
This isn’t the FASB’s last word on ASC 718. They have a number of additional research projects that could result in further amendments to the standard:
Non-Employees: In my opinion, the most exciting research project relates to the treatment of non-employees. As I’m sure you know, it is a big pain to grant awards to consultants, et. al., because the awards are subject to liability treatment until vested. The FASB is considering whether consultants should be included within the scope of ASC 718, with awards to them accounted for in the same manner as employee awards. If not for all consultants, than at least for those that perform services similar to that of employees.
Private Companies: Another research project covers a number of issues that impact private companies, such as 1) practical expedients related to intrinsic value, expected term, and formula value plans and 2) the impact of certain features, such as repurchase features, on the classification of awards as a liability or equity.
Unresolved Performance Conditions: Another project relates to awards with unresolved performance conditions. I’ll admit that I’m not entirely sure what this is.
That’s All, For Now
That’s all I have on this topic for now. You can expect more updates when we hear more news on this from the FASB.
A big thank-you to Ken Stoler and Nicole Berman of PwC for helping me sort through the FASB’s announcement. If you haven’t already, be sure to check out their Equity Expert Podcast on the amendments.
The Financial Accounting Foundation has completed their post-implementation review of FAS 123(R) (see my August 27, 2013 blog entry, “FAF to Review FAS 123(R)“) and the upshot is that they think the standard (now known as ASC 718) needs to be simplified. In response the FASB has proposed some very significant amendments to the standard. In addition to the summary I provide here, be sure to listen to our newest Equity Expert podcast, in which Jenn Namazi discusses the proposed amendments with Ken Stoler and Nicole Berman of PwC.
Share Withholding
Currently, ASC 718 provides that withholding for taxes in excess of the statutorily required rate triggers liability treatment. This has been a problem because of rounding considerations (if companies round the shares withheld up to the nearest whole share, does that constitute withholding in excess of the required rate) and, more significantly in jurisdictions (e.g., US states and other countries) that don’t have a flat withholding rate. The FASB proposal would change the standard to allow share withholding up to the maximum tax rate in the applicable jurisdiction, regardless of the individual’s actual tax rate.
This is obviously great news and would make share withholding a lot more feasible for non-US employees. There is still the question of rounding, however. It also isn’t clear how this would apply in the case of mobile employees. Finally, don’t forget that, here in the US, the IRS still opposes excess withholding at the federal level (see my January 9, 2013 blog entry “Supplemental Withholding“).
Estimated Forfeitures
Estimating forfeitures is one of the most complicated aspects of ASC 718—I’ve seen multiple presentations of over an hour in length on just this topic. The FASB has proposed to dispense with this altogether and allow companies to simply recognize the effect of forfeitures as they occur. Companies would be required to make a policy decision as to how they want to recognize forfeitures that would apply to all awards they grant. I assume that this would apply only to forfeitures due to service-related vesting conditions, but I don’t know this for certain.
Tax Accounting
Another area of the standard that has provided a wealth of material for NASPP webcasts and Conference sessions is how companies account for the tax deductions resulting from stock awards. FASB’s proposal would change the standard to require that all tax savings and all shortfalls flow through the income statement. If an award results in a deduction in excess of the expense recognized for it, the excess savings would reduce tax expense (currently, the excess is recorded to APIC). Likewise, shortfalls would always increase tax expense (currently, shortfalls are deducted from the company’s APIC balance to the extent possible, before reducing tax expense).
With this change, companies would no longer need to track what portion of APIC is attributable to excess tax deductions from stock plan transactions. But this would introduce significant variability into the income statement (which is the reason FASB decided against this approach ten years ago). This approach gets us closer to convergence with IFRS 2, but is still not completely aligned with that standard (in IFRS 2, all excess deductions run through APIC and all shortfalls run through the P&L). But this makes me wonder if companies will simply record the windfall/shortfall tax deductions as they occur, or would they have to estimate the potential outcome and adjust tax expense each period until the deduction is finalized (as under IFRS 2)?
Now? Now They Figure This Out?!
All of these changes will eventually make life under ASC 718 a heck of a lot simpler than it is now. That’s the good news. The bad news is that it’s really too bad the FASB couldn’t have figured this out ten years ago. Not to say “I told you so” but I’m sure there were comment letters on the exposure draft that warned the FASB that the requirements in at least two of these areas were too complicated (I’m sure of this because I drafted one of them).
If you are already thinking wistfully about how much more productively you could have used all that time you spent learning about estimated forfeitures and tax accounting, imagine how your administrative providers must feel. They’ve spent the last ten years (and a lot of resources) developing functionality to help you comply with these requirements; now they’ll have to develop new functionality to comply with the new simpler requirements.
More Info
I’ll have more thoughts on this and some of the FASB’s other decisions—yes, there’s more!—next week. For now, check out the PwC and Mercer alerts that we posted to the NASPP website (under “More Information” in our alert, “FASB Proposes Amendments to ASC 718“). And listen to our Equity Expert podcast on the proposed amendments with Ken Stoler and Nicole Berman of PwC.
The Financial Accounting Foundation, or FAF, has announced that they are going to conduct a post-implementation review of FAS 123(R). In today’s blog, I take a look at what this might mean for the future of stock plan accounting.
What the Heck?
The FAF oversees and provides funding for the FASB, as well as several other entities involved in promulgating US accounting standards. The FAF has recently begun conducting post-implementation reviews to evaluate the effectiveness of standards issued by the FASB (and also standards issued by GASB, Governmental Accounting Standards Board, which is the only other accounting standards board here in the United States–they aren’t just targeting the FASB).
You Can Take Your Aluminum Hat Off–They’re Probably Not Out to Get Us
Upon reading that the FAF is planning a post-implementation review of FAS 123(R), my first reaction was alarm. In the past, when various accounting authorities have reviewed US accounting standards on stock compensation, the outcomes haven’t been particularly favorable for those of us on team stock awards (notable examples include FIN 44, EITF 96-18, and, of course, FAS 123(R)). The FAF says (on its website) that standards are selected for a PIR based on “considerable amount of stakeholder input indicating that the standard might not be meeting its stated objectives.”
So I asked Bill Dunn at PwC about it and he put me in touch with his colleagues Ken Stoler and Pat Durbin (Pat is PwC’s national practice leader on standard setting). Ken and Pat don’t think the PIR signals any significant changes for stock plan accounting. They think that FAS 123(R) was selected for review merely because it is complex, pervasive, and has raised numerous practice issues–not because the FAF thinks there is anything wrong with the standard. They suspect that any changes that the FAF recommends will be minor and only in areas where divergence in practice has developed.
What Is a PIR?
According to the FAF website, the PIR has three main goals: to determine if the standard meets its stated objectives, to evaluate the standard’s implementation and compliance costs and benefits, and to provide feedback to improve the standard setting process. The PIR team uses a variety of procedures, including reviewing the project archives, reviewing academic and other research, and collecting stakeholder input via surveys and interviews. They then present their findings to the FASB’s chair and oversight committee.
As I understand it, the PIR team doesn’t recommend any specific standard-setting actions, they simply point out areas of concern and it is up to the FASB to decide whether or not to take action. Which means that this is a loonnnng process. First the FAF has to conclude the PIR, which takes a long time, and then the FASB has to act on their concerns, which takes even longer. But, the silver lining for me is that it sounds like there could be fodder for several blog entries along the way, especially if the FAF finds any areas of concern (which surely they will–it’s a big standard).
Why “FAS 123(R)”?
My other thought upon reading this was to wonder why the FAF calls the standard “FAS 123(R)” when the rest of us have to call it “ASC 718.” Because, frankly, it’s been a struggle to get used to the ASC 718 moniker. If the FAF can call it FAS 123(R), I thought maybe the rest of us could too. But, unfortunately, Ken doesn’t think we’ll all go back to calling it FAS 123(R) anytime soon.