The FASB’s update to ASC 718 is a gift that keeps on giving, at least in terms of blog entries. Today I discuss something many of you may not have considered: the impact the update will have on the calculation of common equivalents under the Treasury Stock Method.
EPS: A Story of a Numerator and a Denominator
Earnings per share simply allocates a company’s earnings to each share of stock. It is calculated by dividing earnings (the numerator) by the number of shares common stock outstanding (the denominator). Public companies report two EPS figures: Basic EPS and Diluted EPS. In Diluted EPS, the denominator is increased for any shares that the company could be contractually obligated to issue at some point in the future, such as shares underlying stock options and awards. These arrangements are referred to as “common equivalents.”
A Quick Refresher on the Treasury Stock Method
The Treasury Stock Method is used to determine how many shares should be included in the denominator of Diluted EPS for all of the arrangements that could obligate the company to issue shares in the future. Under the Treasury Stock Method, companies assume that all of these arrangements are settled (regardless of vesting status), the underlying shares are issued, and any proceeds associated with the settlement are used to repurchase the company’s stock. The net shares that would be issued after taking into account the hypothetical repurchases increase the denominator in the EPS calculation.
The possible sources of settlement proceeds include any amount paid for the stock, any windfall tax savings (“windfall” is the operative word here), and any unamortized expense. For a more detailed explanation, see the chapter “Earnings Per Share” in Accounting for Equity Compensation in the United States.
What the Heck are “Windfall” Tax Savings?
“Windfall” tax savings are those that increase paid-in capital rather than decreasing tax expense. Normally, tax savings result from expenses and reduce the company’s tax expense. But this isn’t always the case with the tax savings from stock compensation. Sometimes the company’s tax deduction is greater than that expense recognized for an award. Currently when that occurs, the tax savings resulting from any deduction in excess of the expense simply increases paid-in capital; this savings doesn’t reduce tax expense.
How Does the Update to ASC 718 Change This?
Any windfall tax savings have to be accounted for somewhere in the EPS calculation. Right now, because these savings don’t impact tax expense or earnings, and thus aren’t reflected in the numerator of the EPS equation, they are treated as a source of settlement proceeds and reduce the denominator.
Once the update goes into effect, this is all changed. All tax savings, windfall or otherwise, will reduce tax expense and increase earnings, which means these savings will be reflected in the numerator for EPS. Because the savings will be reflected in the numerator, they will no longer be treated as a source of settlement proceeds under the Treasury Stock Method.
You Have to Admit, It Does Simply Things
The upshot is that, once a company has adopted the update to ASC 718, the settlement proceeds when applying the Treasury Stock Method to awards will be limited to just two sources: the purchase price and any amortized expense. Windfall tax benefits will be eliminated as a source of proceeds.
For my last installment (at least for the moment—expect another blog when the FASB officially adopts the new standard) in my series on the FASB’s ASC 718 simplification project, I answer a few questions relating to early adoption of the new standard.
Can companies adopt it early?
Yes, companies can adopt the amended standard in any interim or annual period after the FASB approves the official amendment. If the FASB approves the amendment as expected in this quarter, companies could adopt it in this quarter.
Can companies adopt it now?
No, not quite yet. Companies have to wait until the final amendment is approved by the FASB to adopt it.
Can companies adopt just the parts of the update they like early and wait to adopt the rest of it?
Heck no! This isn’t a salad bar; it’s all or nothing. You have to take the bad with the good.
If we start allowing employees to use shares to cover tax payments in excess of the minimum required withholding now, are my auditors really going to make me use liability accounting, given that we all know the rules are changing soon?
Well, I can’t really speak for your auditors, so you’d have to ask them—accounting-types do tend to be sticklers for the rules, however. If the FASB approves the amendment on time, you could adopt it this quarter and there’d be no question about liability treatment. But you’d have to adopt the whole standard, including the tax accounting provisions, so you would want to make sure you are prepared to do that.
If you don’t want to adopt the entire update as soon as the FASB approves it, liability treatment applies if shares are withheld for more than the minimum tax payment. For awards that are still outstanding when you adopt the update, this liability treatment will go away. You’ll record a cumulative adjustment at the time of adoption (see my blog last week on the transition) to switch over to equity treatment. But for the awards that are settled prior to when you adopt the standard, you won’t reverse the expense you recognize as a result of the liability treatment.
If the awards that will settle between now and when you expect to adopt the standard are few enough, the expense resulting from the liability treatment might be immaterial. Likewise, if your stock price is at or below the FMV back when the awards were granted, you might not be concerned about liability treatment because it likely wouldn’t result in any additional expense.
Note, however, that if you establish a pattern of allowing share withholding for excess tax payments, liability treatment applies to all awards, not just those for which you allow excess withholding. You could have liability treatment for all award settlements that occur before you adopt the amended standard.
For today’s installment in my series on the FASB’s ASC 718 simplification project, I explain what the next steps are in this process.
Is the update final now?
Not quite yet. For the most part, we know what the final update is going to look like because the FASB’s decisions with respect to each issue in the exposure draft are public. But the FASB staff still has to draft the actual amendment to ASC 718 and the FASB has to vote to adopt the amendment.
In addition, there are a few technical details in the exposure draft that were commented on and that we expect the staff to clean up, but we won’t know for sure until the amendment is issued. The FASB didn’t vote on these details because they don’t change the board’s overall position; it is merely a matter of clarifying what the board’s decision means with respect to some aspects of practical implementation. For example, the language of the proposed amendment relating to share withholding seemed to imply something different than the FASB’s explanation of what this change would be. I am assuming the staff will modify this language but we won’t know for sure until the final amendment is issued.
When will the FASB adopt the amendment?
According to the FASB’s Technical Agenda, this project is expected to be finalized in Q1 2016. Anyone who’s been in the industry for a more than a couple years knows, however, that these things tend to slip a bit. In my 20 years in this industry, I can’t think of a single regulation, rule, amendment, etc. that, when targeted for issuance during a specific time frame, came out earlier than the very last week or so in that time frame. (10 pts to anyone who can prove me wrong on this—I started in the industry in 1994, so stuff before that doesn’t count.) The FASB is no exception, so I’m guessing that we are looking at the end of March or maybe even Q2 2016.
When will companies be required to comply with the new guidance?
Public companies will have to adopt the update by their first fiscal year beginning after December 15, 2016 (and in the interim periods for that year). Private companies have a year longer to adopt for their annual period and two years longer for interim periods.
Will the standard now be called ASC 718(R)?
No. For people like me who write about accounting, that would be handy because it would make it easy to distinguish when I’m talking about the pre-amendment vs. the post-amendment ASC 718. Now I’ll have to use some sort of unwieldy clarification, like “ASC 718, as amended in 2016.” But under the FASB’s codification system, the existing standard is simply updated to incorporate the amendments. The name of the standard will stay the same.
If the Codification system didn’t exist, maybe we would call it FAS 123(R)(R). Or would it be FAS 123(R)2?
For my first blog entry of 2016, I look at the transition methods that will apply under the FASB’s Accounting Standards Update (ASU) to ASC 718. (If you’ve forgotten what this is all about, read Part I and Part II of my update on the FASB’s decisions on the ASC 718 simplification project.) Also, see my handy chart showing how FASB voted on each issue in the exposure draft and the required transition method for it.
Prospective
The prospective transition method is perhaps the easiest to understand. Under this method, the company just changes its accounting procedures on a go-forward basis, with no restatement of prior periods or cumulative adjustments.
The prospective transition method will be used for the tax accounting provisions. For transactions that occur after a company adopts the ASU, the amounts that would have been recorded to additional paid-in capital will now simply be recorded to tax expense. It’s that easy: no adjustments to paid-in capital or tax expense for past transactions and the ASC 718 APIC pool calculation is no more.
Retrospective
Retrospective transition is also fairly straightforward. With this method, the company changes its accounting procedures going forward, but also adjusts any prior periods reported in its current financials. For example, most companies show three fiscal years in their annual financial statements. Where retrospective transition is required, a company that adopts the ASU in 2016 would not only change their accounting procedures for 2016, but would go back and adjust the 2015 and 2014 periods as if the new rules had applied in those periods.
The adjustment is presented only in the current financials; the company does not reissue any previously issued financial statements or re-file them with the SEC.
The only provisions in the ASU that are subject to retrospective transition are the provisions related to classification of amounts reported in the cash flow statement (and for the classification of excess tax benefits, the company can choose between prospective and retrospective).
Modified Retrospective
This transition method is used when a cumulative adjustment is necessary. Accounting for forfeitures is a good example. A company can’t just switch from applying an estimated forfeiture rate to accounting for forfeitures as they occur on a prospective basis: since previously recorded expense was adjusted based on estimated forfeitures, companies would end up double-counting forfeitures when they occur. Retrospective restatement wouldn’t fix this problem because some of the prior expense may have been recorded outside of the periods presented in the company’s current financials.
It also doesn’t make sense to make companies record a big change in expense in their current period; this would be confusing (and possibly alarming) to investors and isn’t reflective of what is happening. So instead, the transition is handled with a cumulative adjustment that is recorded as of the start of the fiscal period. This adjustment is recorded in retained earnings (which is the balance sheet account where net earnings end up) with an offsetting entry to paid-in capital.
In the case of forfeitures, the company calculates the total expense it would have recognized as of the start of the period if it had been accounting for forfeitures as they occur all along and compares this to the actual amount of expense recorded to date (which should generally be lower). The difference is then deducted from retained earnings, with a commensurate increase to paid-in capital.
In addition to the forfeitures provision, modified retrospective is used for private companies that take advantage of the opportunity to change how they account for liability awards. It is also used theoretically for the share withholding provisions if companies have been allowing employees to tender shares in payment of taxes in excess the minimum statutorily required withholding and has outstanding awards that are subject to liability treatment as a result. But I doubt anyone has been doing that, so in practice, I don’t think a transition will be necessary for the share withholding provisions.
As followers of this blog know, the FASB recently issued an exposure draft proposing amendments to ASC 718 (see “It’s Here! The FASB’s Amendments to ASC 718,” June 9, 2015). In today’s blog, I take a look at common themes in the comment letters on the exposure draft.
A Lot Less Controversial
The FASB received just under 70 comment letters on the exposure draft, making this proposal far less controversial than FAS 123 or FAS 123(R) (by contrast, the FASB heard from close to 14,000 commenters on FAS 123(R)). In general, the letters are supportive of the proposed amendments.
Opposition to Proposed Tax Accounting
The area of most controversy under the exposure draft is the proposal to require all tax effects (both excess deductions and shortfalls) to be recognized in the income statement. Virtually all of the letters submitted mention this issue and this was the only issue that a number of letters address. A little over 70% of the letters oppose the FASB proposal. About half of the letters suggest that all excess deductions and shortfalls should be recognized in paid-in capital, instead of in earnings.
Many commenters mention the volatility the proposed approach would create in the P&L and express concern that this would be confusing to the users of financial statements. This is the argument we made in the NASPP’s comment letter (see “The NASPP’s Comment Letter,” August 18).
Here are a few other arguments in opposition of the FASB’s proposal that I find compelling (and wish I had thought of):
Several commenters refer to the FASB’s own analysis (in the Basis for Conclusions in FAS 123(R)) that stock awards comprise two transactions: (i) a compensatory transaction at grant and (ii) an equity transaction that occurs when the award is settled. They point out that it is inconsistent to recognize the tax effects of the second transaction in income when the transaction itself is recognized in equity.
Several commenters point out that the increase or decrease in value between the grant date and settlement is not recognized in income, therefore it would be inconsistent to recognize the tax effects of this change in value in income.
One commenter points out that this would merely shift the administrative burden from tracking the APIC pool to forecasting the impact of stock price movements on the company’s earnings estimates, negating any hoped for simplification in the application of the standard.
Share Withholding
The comment letters overwhelming support the proposal to expand the exception to liability accounting for share withholding. Several letters point out what appears to be an inconsistency in the language used to amend the standard with the FASB’s described intentions. While the FASB indicated in its discussion of the exposure draft that it intended to permit share withholding up to the maximum individual tax rate in the applicable jurisdiction, the proposed languages refers to the individual’s maximum tax rate. Also, the exposure draft appears to have inadvertently excluded payroll taxes from the tax rate. Hopefully these are minor issues that will be addressed in the final update.
One commenter suggests that, for mobile employees, companies should also be allowed to consider hypothetical tax rates that might apply to individuals under the company’s tax equalization policy for purposes of determining the maximum withholding rate.
Forfeitures
While the letters also were very supportive of the proposal to allow companies to choose to recognize forfeitures as they occur, I was surprised to find that a couple of letters suggested that companies should be required to recognize forfeitures as they occur.
What’s Next?
The comment period ended on August 14, so the FASB has had close to two months to consider the comments. I heard a rumor at the NASPP Conference that the Board will discuss them at one of its November meetings but I haven’t seen anything on this in the FASB Action Alerts yet. I expect that we won’t see the final amendments until next year. Given the controversy of the tax accounting proposal, possibly late next year.
This is the most controversial aspect of the exposure draft. The volatility that this change introduces to the P&L is likely to be significant for companies that rely heavily on stock compensation. We performed a very quick analysis of a handful of companies and found that, for several of them, recognizing excess tax benefits in their P&L would have increased EPS by 10%. In one case, EPS increased by 60%. Ultimately, we think this will be incredibly confusing to investors and other financial statement users. We also feel that it is highly unintuitive for changes in a company’s stock price to generate significant profits and losses for the company. While eliminating the ASC 718 APIC pool is very attractive, ultimately, we felt that the impact on earnings and effective tax rates would offset the benefits of simplifying this area of the standard. Because of this, we recommended against this amendment.
We suggested that companies record all excess tax benefits and shortfalls to paid-in capital, rather than tax expense. This would eliminate the need to track the APIC pool without impacting the P&L.
Forfeitures
We supported the proposal to allow companies to make a policy election to account for forfeitures as they occur. Our only comment on this topic was to suggest that the FASB provide a mechanism for companies to change their election without treating it as a change in accounting principle (which requires a preferability assessment and retrospective restatement).
Share Withholding
We supported the proposal to amend the standard to provide that shares can be withheld to cover taxes up to the maximum individual tax rate without triggering liability treatment.
We asked the FASB to provide additional guidance on how this requirement applies to mobile employees and suggested that share withholding be allowed up to the combined maximum tax rate in all jurisdictions that the transaction is subject to.
We also asked the FASB to remove the requirement that the tax withholding be mandated by law.
Practical Expedient to Expected Term
We supported allowing private companies to treat the midpoint of the vesting period and contractual term of an option as the option’s expected term for valuation purposes. We asked the FASB to remove the condition that the option be exercisable for only a short period of time after termination of employment and also requested removal of the conditions applicable to performance-based options.
The Rest of It and Thanks
We supported the remaining proposals in the exposure draft without comment.
Thanks to everyone that completed the NASPP’s quick survey on the exposure draft—I hope to have the results posted by the end of this week.
Thanks also to individuals who agreed to serve on our task force for this project: Terry Adamson of Aon Hewitt, Dee Crosby of the CEP Institute, Elizabeth Dodge of SOS, Sean Kelly of Morgan Stanley, Ken Stoler of PwC, Sean Waters of Fidelity, Thomas Welk of Cooley, and Jason Zellmer of Bank of America Merrill Lynch. Their help was invaluable.
The FASB has issued the exposure draft of the proposed amendments to ASC 718. The FASB alert showed up in my email at approximately 1 PM Pacific yesterday and it’s 105 pages long. Suffice it to say, I haven’t exactly read the whole thing yet. Here are some initial thoughts based on a quick skim of the draft.
Don’t remember what the proposed amendments are about? Refresh your memory with my blog entry “Proposed Amendments to ASC 718 – Part I.” Also, don’t miss the 23rd Annual NASPP Conference, where we will be waxing nostalgic about the first ten years under ASC 718 (FASB Chair Russ Golden is even going to say a few words) and will have special session focused on the steps companies need to take to prepare for the amendments.
I Thought This Was About Simplification
105 pages! Come on. The whole entire standard including all the illustrations and basis for conclusions was only 286 pages. This “simplification” is over one-third the length of the original standard.
There’s More to It Than You Might Think
I’ve been focusing on just three areas that will be amended, but the exposure draft addresses nine issues. Two of the issues relate to the classification of stuff on the cash flow statement (snore). Three relate to private companies—I’ll get to these in a subsequent blog entry. And one makes FSP FAS 123(R)-1 permanent, which is a relief. You will recall that this relates to the treatment of options that provide for an extended time to exercise after termination of employment. Perhaps I wasn’t paying attention, but I wasn’t aware that the FASB was considering this.
Share Withholding
The proposed amendments relating to share withholding clarify that the company must have a withholding obligation to avoid triggering liability treatment. So share withholding for outside directors and ISOs will still trigger liability treatment. But, as expected, where the company is obligated to withhold taxes, the proposal allows share withholding for taxes up to the maximum individual tax rate. The proposal doesn’t address mobile employees (i.e., can you use the maximum rate out of all of the applicable jurisdictions?) or whether rounding up is permissible if you are withholding at the maximum rate.
Tax Accounting
Also, as expected, the proposal provides that all tax effects will run through the income statement. What may come as a surprise is that this eliminates the tax benefit under the Treasury Stock Method calculation used for diluted EPS. Because net earnings (the numerator of EPS) is reduced for the full tax benefit to the company, there won’t be any adjustment to the denominator for this benefit anymore.
Expected Forfeitures
For service conditions only, the proposal would allow companies to account for forfeitures as they occur, rather than applying an estimated forfeiture rate to expense accruals. For performance conditions, however, companies will still be required to estimate the likelihood of the condition being achieved.
Comments
Comments on the exposure draft can be submitted using the FASB’s Electronic Feedback Form and must be submitted by August 14, 2015.
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 FASB recently ratified an EITF decision and approved issuance of an Accounting Standards Update on “Accounting for Share-Based Payments When the Terms of an Award Provide That a Performance Target Could Be Achieved after the Requisite Service Period” (their words, not mine).
What the Heck?
I was completely baffled as to when an award would have a performance condition that could be met after the end of the service period. After all, isn’t the period over which the performance goals can be met the very definition of a service period? So I spoke with Ken Stoler of PwC, who translated this into English for me.
Turns out, it’s a situation where the award is no longer subject to forfeiture due to termination of employment but is still subject to some sort of performance condition. Here are two situations where we see this occur with some regularity:
Retirement-Eligible Employees: It is not uncommon for companies to provide that, to the extent the goals are met, performance awards will be paid out to retirees at the end of the performance period. Where this is the case, a retirement-eligible employee generally doesn’t have a substantial risk of forfeiture due to termination but could still forfeit the award if the performance goals aren’t met.
IPOs: Privately held companies sometimes grant options or awards that are exercisable/pay out only in the event of an IPO or CIC. The awards are still subject to a time-based vesting schedule and, once those vesting requirements have been fulfilled, are no longer subject to forfeiture upon termination. But employees could still forfeit the grants if the company never goes public nor is acquired by a publicly held company.
The EITF’s Decision
The accounting treatment that the EITF decided on is probably what you would have guessed. You estimate the likelihood that the goal will be met and recognize expense commensurate with that estimate. For retirement-eligible employees, the expense is based on the total award (whereas, for other employees, the expense is also commensurate with the portion of the service period that has elapsed and is haircut by the company’s estimate of forfeitures due to termination of employment).
For example, say that a company has issued a performance award with a grant date fair value of $10,000, three-fourths of the service period has elapsed, and the award is expected to pay out at 80% of target. In the case of a retirement-eligible employee, the total expense recognized to date should be $8,000 (80% of $10,000). In the case of an employee that isn’t yet eligible to retire, the to-date expense would be, at most, $6,000 ($80% of $10,000, then multiplied by 75% because only three-fourths of the service period has elapsed). Moreover, the expense for the non-retirement-eligible employee would be somewhat less than $6,000 because the company would further reduce it for the likelihood of forfeiture due to termination of employment.
The same concept applies in the case of the awards that are exercisable only in the event of an IPO/CIC, except that, in this situation, the IPO/CIC is considered to have a 0% chance of occurring until pretty much just before the event occurs. So the company doesn’t recognize any expense for the awards until just before the IPO/CIC and then recognizes all the expense all at once.
Doesn’t the EITF Have Anything Better to Do?
I had no idea that anyone thought any other approach was acceptable and was surprised that the EITF felt the need to address this. But Ken tells me that there were some practitioners (not PwC) suggesting that these situations could be accounted for in a manner akin to market conditions (e.g., haircut the grant date fair value for the likelihood of the performance condition being met and then no further adjustments).
I have no idea how you estimate the likelihood of an IPO/CIC occurring (it seems to me that if you could do that, you’d be getting paid big bucks by some venture capitalist rather than toiling away at stock plan accounting). And in the case of performance awards held by retirement-eligible employees, my understanding is that the reason ASC 718 differentiates between market conditions and other types of performance conditions is that it’s not really possible for today’s pricing models to assess the likelihood that targets that aren’t related to stock price will be achieved. Which I guess is why the EITF ended up where they did on the accounting treatment for these awards. You might not like the FASB/EITF but at least they are consistent.