{"id":95,"date":"2016-04-19T15:12:30","date_gmt":"2016-04-19T15:12:30","guid":{"rendered":"http:\/\/www.qdrodesk.com\/blog\/?p=95"},"modified":"2016-04-19T17:26:06","modified_gmt":"2016-04-19T17:26:06","slug":"common-mistakes-when-valuing-a-pension","status":"publish","type":"post","link":"https:\/\/www.qdrodesk.com\/blog\/common-mistakes-when-valuing-a-pension\/","title":{"rendered":"Common Mistakes When Valuing a Pension"},"content":{"rendered":"<p>A number of common mistakes can happen when valuing defined benefit and defined contribution plans \u2013 including partial offsets and tax consequences.<\/p>\n<p><strong>What\u2019s wrong with using a present value of a defined benefit plan in a marital settlement agreement?\u00a0<\/strong><\/p>\n<p>In a state that uses coverture \u2013 which is roughly half the country \u2013 the marital portion is the benefit at retirement multiplied by the coverture fraction. The coverture fraction is determined at retirement, so it\u2019s going to be a much larger benefit than the current benefit. If the alternate payee is offered a present value, he or she might get a certain sum per month until that number is reached; even if he or she gets an accrued benefit that has the present value stated, that is going to be less than the coverture formula. A perfect example of that was the Able case in New Jersey. They valued the pension at $100,000, and there wasn\u2019t enough money for a complete immediate offset. They should have done a partial offset, but instead, they did a 50% QDRO. The mistake was compounded because they specified that she was to get $50,000 dollars \u2013 but New Jersey follows the coverture methodology, so by specifying a dollar amount, the husband argued that she wasn\u2019t entitled to 50% of the coverture portion. So there was a dual mistake made in getting the pension present valued: not using that present value because there wasn\u2019t enough for a complete offset, and then stating the present value in a property settlement agreement. In general, putting a present value of a pension in a property settlement agreement is a big mistake. It will shortchange the alternate payee.<\/p>\n<p><strong>Why should a defined contribution plan be valued? \u00a0 \u00a0 \u00a0<\/strong><\/p>\n<p>A defined benefit pension is a monthly benefit in the future. We\u2019re valuing the defined benefit pension today, but how are we going to value the 401(k) if their cut-off date is years ago? We\u2019ve seen cases where the cut-off date has been 20 years in the past. We can\u2019t use a balance as of three or four years ago because that doesn\u2019t include gains and losses since that date. It has to be brought forward with gains and losses since that date \u2013 then it can be compared to the house and the other assets.<\/p>\n<p><strong>What about tax consequences?<\/strong><\/p>\n<p>If you look at pension versus cash, the pension is a pre-tax asset and cash is a post-tax asset. Some jurisdictions \u2013 New York, for example \u2013 are very stringent about taking tax into effect. You have to establish exactly what the participant\u2019s tax rate is before you can discount a pension for taxes. Other states, like Pennsylvania, are more lenient and will leave it up to the discretion of the court to discount the pension for taxes. Since the pension pays in the future, you would need to estimate a potential tax rate; we recommend the parties settle on some reasonable tax factor between 12% and 20%. Our partial offset methodology will enable you to gross-down that pension to compare it to cash.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A number of common mistakes can happen when valuing defined benefit and defined contribution plans \u2013 including partial offsets and tax consequences. What\u2019s wrong with using a present value of a defined benefit plan in a marital settlement agreement?\u00a0 In &hellip; <a href=\"https:\/\/www.qdrodesk.com\/blog\/common-mistakes-when-valuing-a-pension\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"_links":{"self":[{"href":"https:\/\/www.qdrodesk.com\/blog\/wp-json\/wp\/v2\/posts\/95"}],"collection":[{"href":"https:\/\/www.qdrodesk.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.qdrodesk.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.qdrodesk.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.qdrodesk.com\/blog\/wp-json\/wp\/v2\/comments?post=95"}],"version-history":[{"count":2,"href":"https:\/\/www.qdrodesk.com\/blog\/wp-json\/wp\/v2\/posts\/95\/revisions"}],"predecessor-version":[{"id":99,"href":"https:\/\/www.qdrodesk.com\/blog\/wp-json\/wp\/v2\/posts\/95\/revisions\/99"}],"wp:attachment":[{"href":"https:\/\/www.qdrodesk.com\/blog\/wp-json\/wp\/v2\/media?parent=95"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.qdrodesk.com\/blog\/wp-json\/wp\/v2\/categories?post=95"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.qdrodesk.com\/blog\/wp-json\/wp\/v2\/tags?post=95"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}