{"id":791,"date":"2007-04-24T01:03:08","date_gmt":"2007-04-24T05:03:08","guid":{"rendered":"http:\/\/www.prefblog.com\/?p=791"},"modified":"2007-04-24T01:03:08","modified_gmt":"2007-04-24T05:03:08","slug":"himipref-data-simplification-figpra-dividends","status":"publish","type":"post","link":"https:\/\/prefblog.com\/?p=791","title":{"rendered":"HIMIPref™ Data Simplification : FIG.PR.A Dividends"},"content":{"rendered":"

As assiduous readers will remember, FIG.PR.A was the “target security” in a four way merger<\/a> earlier this year.<\/p>\n

In what was presumably an effort to ensure that each class of shareholder got their due, FIG.PR.A paid a partial dividend of 0.05308 on 2007-2-9 to holders of record 2007-1-31. They then paid the balance ($0.10317) of the regular quarterly amount on 2007-4-2 to holders of record 2007-3-22.<\/p>\n

Unfortunately, this sort of thing gives HIMIPref\u2122 stomach-ache. There are several layers of checks built into the system to ensure that quarterly dividends are recorded quarterly, by billy-dam, or at least approximately. The good old Argus preferreds, for instance, have been in default for … a while … but on every dividend date I dutifully put in a dividend of $0.0001, just so the programmatic editors will see the entry and tick off their lists. There’s a wobble allowed, so that issuers like ABK.PR.C<\/a> with their idiosyncratic ideas regarding the definition of “regular” and “quarterly” don’t cause me too many problems.<\/p>\n

However, things like special dividends throw me for a loop. I can handle it on redemptions, but not with a continuing security. Therefore:<\/p>\n

1:<\/strong> The dividend of 0.05308 paid 2\/9 has been deleted from HIMIPref\u2122<\/p>\n

2:<\/strong> The dividend of 0.10317 paid 4\/2 has been entered on the system as $0.15625.<\/p>\n

This approximation means that intra-period returns on FIG.PR.A will be miscalculated.<\/p>\n

It also means that in simulations, returns on holdings of FCN.PR.A \/ FCF.PR.A & FCI.PR.A will be overstated. But it’s either that, or re-write my edit routines to be even more complicated (which I might do eventually, but hardly seems worthwhile right now) or scrap my editors (which, given the number of times they’ve saved my hide, seems to me to be the worst option).<\/p>\n","protected":false},"excerpt":{"rendered":"

As assiduous readers will remember, FIG.PR.A was the “target security” in a four way merger earlier this year. In what was presumably an effort to ensure that each class of shareholder got their due, FIG.PR.A …<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[33],"tags":[],"class_list":["post-791","post","type-post","status-publish","format-standard","hentry","category-data-fixes"],"_links":{"self":[{"href":"https:\/\/prefblog.com\/index.php?rest_route=\/wp\/v2\/posts\/791","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prefblog.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prefblog.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prefblog.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prefblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=791"}],"version-history":[{"count":0,"href":"https:\/\/prefblog.com\/index.php?rest_route=\/wp\/v2\/posts\/791\/revisions"}],"wp:attachment":[{"href":"https:\/\/prefblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=791"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prefblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=791"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prefblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=791"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}