Performance of the HIMI Indices for June was:
Total Return, June 2007 |
Index |
Performance |
Ratchet |
+0.86% |
FixFloat |
-0.46% |
Floater |
-0.02% |
OpRet |
-0.30% |
SplitShare |
+0.12% |
Interest |
-1.18% |
PerpetualPremium |
-0.55% |
PerpetualDiscount |
-3.19% |
… which is at least a little bit more cheerful than the results in May.
The Claymore Preferred ETF (CPD) may be viewed, with caution, as a proxy for the S&P/TSX Preferred Share Index. Caution is required due to tracking error – the ETF will deliver performance according to what it actually holds and how well it is able to do things like reinvest its dividends, which is not the same thing as an index return. The fund’s NAV will be reported after MER of 0.45% p.a. Be that as it may, the NAV return for CPD has been calculated elsewhere to be -1.40%, after accounting for all its fees & expenses.
It’s a little difficult to get a handle on the size of this ETF … according to the Toronto Exchange, there are 500,000 “plain” units outstanding and 100,000 “advisor class” (CPD.A). However, the Claymore site claims more: 1.3-million “plain” and 0.1-million “advisor”.
Diversified Preferred Share Trust (DPS.UN) is the main competitor of CPD. It doesn’t publish month-end NAVs, but calculations indicate that it probably marginally outperformed CPD – by about 7 basis points.
Look for huge gains in the Fixed-Floater and Ratchet indices (note that the indices are presented prior to the June month-end rebalancing) over the next month – these are dominated by BCE issues, which are currently the subject of an extremely rich takeover bid. Sadly, there is probably no way to take advantage of this, since the issues may be confidently expected to be bid well above their June 29 closing quotations at the opening on Tuesday morning. While there might be a discount to the price Teachers’ is bidding, attempting to take advantage of this spread will constitute “risk-arbitrage” and – in the absence of insider information, I will suggest that the “risk” will highly outweigh the “arbitrage” if a position is taken.
I will admit to being puzzled by the poor performance of the Interest-Bearing Index, also shown prior to its rebalancing. Note that BAM.PR.T is about to be called, but look at the pre-tax bid-YTWs available for BSD.PR.A and FIG.PR.A! As of June 22 the former had an asset coverage ratio of 1.97:1 (the June month-end distribution will have reduced this a bit, but not much) and a DBRS rating of Pfd-2. As of June 28, the latter had asset coverage of 2.58:1 (and has already accounted for the second quarter distribution), while also being rated Pfd-2. It (FIG.PR.A) remains under review with developing indications (“pending the resolution of their respective reorganization and amalgamation plans, which are expected to occur shortly”) but that reorganization settled months ago … DBRS seems to be dragging its feet a little!
Anyway, look at the credit and the yields available on these things! Remember that the yields will be realized largely as interest income, but really! I won’t suggest that anybody mortgage their house to pile into these investments, but how many people have worse credits yielding less in their RRSPs? Come on – stick your hands up!
BMO.PR.K Slithers onto Market
Tuesday, October 9th, 2007This new issue, announced on September 27 initially looked pretty good … but market yields kept increasing and it looked less and less like a good thing as time went on.
The new issue announcement by TD today probably didn’t help a lot either.
Opening day wasn’t very good, but was at least better than the EPP.PR.A, BAM.PR.N and CCS.PR.A opening days of late last spring. 84,620 shares traded in a range of 24.50-70, closing at 24.50-55, 10×32.
As of the close, HIMIPref™ estimates the fair value of this issue to be 24.67. The issue has been entered into the HIMIPref™ database with a securityCode of A40007. A reorgDataEntry has been created to reflect the change from the preIssue code of P25008.
Update: This issue has been added to the PerpetualDiscount Index.
Posted in Data Changes, Index Construction / Reporting, Issue Comments | 3 Comments »