BCE.PR.O To Be Redeemed

BCE Inc. has announced (on February 24):

that it intends to redeem all of its outstanding Cumulative Redeemable First Preferred Shares, Series AO (the “Series AO Preferred Shares”) on March 31, 2022 at a redemption price of $25.00 per Series AO Preferred Share, less any taxes required to be deducted and withheld by the Corporation.

On February 2, 2022, the board of directors of the Corporation declared a quarterly dividend of $0.26625 per Series AO Preferred Share. This will be the final dividend on the Series AO Preferred Shares and will be paid in the usual manner on March 31, 2022 to shareholders of record as of February 28, 2022. After March 31, 2022, the Series AO Preferred Shares will cease to be entitled to dividends and the only remaining rights of holders of such shares will be to receive payment of the redemption amount.

A notice of the redemption of the Series AO Preferred Shares will be provided in accordance with the rights, privileges and conditions attached to the Series AO Preferred Shares. Beneficial holders of Series AO Preferred Shares should contact the financial institution, broker or other intermediary through which they hold these shares to confirm how they will receive their redemption proceeds.

BCE.PR.O was issued as BAF.PR.C, a FixedReset, 4.55%+309, that commenced trading 2011-12-7 after being announced 2011-11-21. BCE privatized Bell Aliant in 2014 and included an Exchange Offer for its preferreds. The offer was successful and later became mandatory. After the first round, the ticker symbol, etc., was changed. BCE.PR.O reset to 4.26% in 2017; I recommended against conversion; and there was no conversion.

Thanks to Peculiar_Investor and CanSiamCyp for bringing this to my attention!

5 Responses to “BCE.PR.O To Be Redeemed”

  1. Another test comment from a different device (PC)

  2. CanSiamCyp says:

    James: Testing, testing! LOL!

  3. CanSiamCyp says:

    Eureka! It worked again!

  4. jiHymas says:

    I’m glad to see that things have returned … for now, anyway. I’m still working with my server-guy to resolve a few issues.

Leave a Reply

You must be logged in to post a comment.