Renewal period error

I am having some issues with the renewal period settings and hope you can take a peek to see if I'm overlooking the correct settings.

I have an annual membership plan with an expiry date of October 1 and want to allow renewals 3 month before expiration for the forthcoming year (October 1 2013 - September 30, 2014). I also want to allow new members the option to purchase a plan commencing now but in October 1 2013.

Regular validity period: 10-01
I have a plan with an expiration setting set to the following:
Bonus time: 3 months
Renewal in advance by: 3 Months
Manual renewal extends expiration date: Renewal extends (without gap)

I'm trying to figure out why the renewal option appearing in the subscription tab shows the following:

Renew Now: CAD 20.00 for 1 October 2012-30 September 2013 (valid from now on)

Should it not be? : Renew Now: CAD 20.00 for 1 October 2013-30 September 2014 (valid from now on)

FYI: New plans are working fine. I had a new member sign up and they have an expiry date of in 2014 as expected. The issue is with renewals.

Running:
CB 1.9
CBSubs 3.00

It's bugged. There's some sort of calculation error going on for renewals when using "This calendar year" duration. I was able to isolate where the calculation goes wrong. I've passed all this information onto to Beat for fixing in next CBSubs release. Unfortunately I've no workaround to suggest. It sometimes can happen due to timezone offset and setting it back to UTC for the site and the user can sometimes fix the calculation error.

Will a SQL action help push the renewal to the correct date until the fix is made work? Even if not displayed properly in the subscription tab

I've tried UTC reset step to see if this helped, but without success.

Is it the display of the button only that has the issue here, or also on the ordering text ? and if you order is the issue also there ?

When I click the renew button the next page also indicated the wrong dates:

1 October 2012 - 30 September 2013 (valid from now on)

Instead of: 1 October 2013 - 30 September 2014

Just following up on my inquiry about the SQL action option I mentioned below. If I set up an auto action (activated on renewal only) to push the renewal date to the correct month/year, is this a possible workaround? Even though the renew button is is displaying the wrong renewal period the SQL action should hopefully solve the problem.

Alternatively, I members renew and I dive into the database and manually change the expiry date , will this work also?

Last possible option: What if I change to change the renewal period to one year (instead of calendar year 10-01 along with the SQL action - Will this be a workaround also? That said, what happens with it next year?

I'm in a bind and anxious to find a solution. The renewal date is approaching and will not be able to promote renewals if the system isn't working properly.

I'm hoping the bug fix will come sooner than later

FYI: Here is the SQL Action I was referring to:
using-sql-action-to-force-expiry-dates