cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
vanessamoss
Level 2

Letter coding incorrect

Since the update, the joint and individual letter are not showing the Ontario Trillium Benefit even though the client T1 Summary shows an amount being paid.  Help!

11 Comments 11
oliveoyl
Level 1

Letter coding incorrect

Yes, I and having same problems. Please correct the letter coding, Profile!

MikeACGA
Level 3

Letter coding incorrect

I think the ONTrilliumBenefit in the letter needs to equal {GST[387]} in the GST form, but that's not happening. I'm not sure the fix that can be done by end user. The work around is top personalize the letter and add the paragraph for the Trillium Benefit. Maybe this was done so as to have fewer ppl using the letter form and it could then be discontinued.

Mario B
ProFile Team

Letter coding incorrect

You need to use the default template. If you have a custome template, you need to update it to match the default template.

Mark193
Level 2

Letter coding incorrect

Mario, that is the dumbest and most ignorant reply a Profile employee could ever give.  Most of us don't like the wording of the openning and closing of the default letter (or font or otherwise) so early in the season we spend time to customize the letter to our liking.  For Profile to update letter coding part way through the season is a major issue and for you to brush it off shows really how out of touch with your customers you really are...

Mark193
Level 2

Letter coding incorrect

For people with customized letters, this is what you need to rechange the coding to for the Trillium section:

{if (GST[387] > 360)}
{if (ONTrilliumBenefitLumpSum > 0)}

You have elected to receive the estimated Ontario Trillium Benefit of ${ONTrilliumBenefitLumpSum} as a lump sum in June {TaxConstant("CurrentTaxYearPlusTwo")}.
{else}

We estimate that you will receive the Ontario Trillium Benefit of ${GST[387]}, payable in twelve monthly installments of ${GST[387]/12} commencing on July {TaxConstant("CurrentTaxYearPlusOne")}.
{endif}
{else}
{if (GST[387] > 0)}

We estimate that you will receive the Ontario Trillium Benefit of ${ONTrilliumBenefit} in July {TaxConstant("CurrentTaxYearPlusOne")}.
{endif}{endif}
{if (GST[133] > 0)}

 

MikeACGA
Level 3

Letter coding incorrect

Thanks Mark193. This worked. I think this might also be the required fix for those using default letters.

MikeACGA
Level 3

Letter coding incorrect

Oops, I hit reply too fast. Also required is to change the remaining 3 ONTrilliumBenefit to the GST[387] otherwise the amount prints $0. The issue is that the variable ONTrilliumBenefit is (wrongly) always 0.

Mark193
Level 2

Letter coding incorrect

I should also point out they changed the Climate Credit $ cell - the total over the year to be paid is correct, but the quarterly amount pulls from a cell that no longer exists (which seems to be somewhere you can't see and is last year's payment amount). Example the total will say $540 but the quarterly says $122 (which the math doesn't work)

Mario B
ProFile Team

Letter coding incorrect

Your method might work for you Mark, but there is a reason why Profile provides the Default templates. You can have your own custom templates and makes changes in your own custom templates every time there is a change in the forms.  If it works for you perfect.

 

Personally, I always prefer to do the reverse, start from the Default, and make my the changes that I want from the Default template, because its easier to change what you want as opposed to change what the designers have already done and tested.

 

Both solutions will work, one has to choose what is the best way for himself. As per the changes happening so late in the cycles, I understand your point of view very well and its unfortunate, but the forms from CRA are not ready early in the season. The changes can not happen before the forms are ready. 

 

Regards,

Mario

Mark193
Level 2

Letter coding incorrect

Mario, can you point me to where in the update notes it would guide me that cells in the default letters changed with the latest update (or 2023.4.0 if it is not the current version)? That would have been helpful to have pointed out to your clients in the release notes.  I cannot (nor do I think it is reasonable to expect me to) review the default letters in detail every time there is an update released by profile.  I realize that forms change, and I do use 99% of the default letters (just change the openning and closing paragraphs and font mostly plus fix the blank line bugs that your coding staff seem to always overlook) but I would suggest that at least 50% of Profile users do not use the fully default letters.

 

Mark

Mario B
ProFile Team

Letter coding incorrect

That would have been in the release notes from Online Menu, Update Informations, Whats new.  I totally understand that this was a miss and we apologize. Going forward,  these changes are included in the release notes.  We can see that for the 2023.4.1 release notes, there is a line covering the templates. 

 

Regards

Mario