Ever since I took the latest update whenever I carry forward a T2 return the “Valid Authorization Already on File and Accepted by CRA” is missing from the AuthRepBus form. What this means is I don’t get prompted to AFR and there is a diagnostic message that I need to complete the AuthREpBus form.
I have looked in the T2 options and under the Select the authorization to prepare all of the selections are available except “authorization already on file”.
I must be missing the area in TaxCycle options where I must configure this each year. Hoping someone can lead me to the correct option setting. It’s getting a bit aggravating to have to answer this every year for every corporation. I thought I had it figured out last year.
@snoplowguy With a new T2 file, I just tried the CFWD of AuthRepBus with the selection of “Valid authorization already on file and accepted by CRA” then the T2 file carried forward with the same selection. (Please read on as I could not get TaxCycle to do this again…very weird!)
Then, I went to the T2 new file option and selected the Authorization type. From then on, when an existing file is carried forward, AuthRepBus drop down would carry forward to the drop down type that I selected in the T2 options.
So, for example, if I select “Online access by an individual” in T2 options and then carry forward a T2 file with “Valid authorization already on file and accepted by CRA”, TaxCycle carries forward the file and selects “Online access by an individual”.
I would have expected that the carried forward file would have selected “Valid authorization already on file and accepted by CRA”. At least to me, that is what I would want since the AuthRepBus was already on file last year.
I will speak to someone about the CFWD. I may not be able to get back to you right away as everyone is quite busy with a pending release but I will get back to you.
I tried again at home. In the office I was using an internal development build.
I used the latest release (version 13.2.53500 from 2024-05-29) on our website to test again.
So, the behaviour I am seeing is this. If the AuthRepBus drop down is “Valid authorization already on file and accepted by CRA”, carried forward file will always carryforward and retain the same status in the drop down. This applies even if you select any of the following selection in T2 options under the “Authorization type”.
To me, you sound like that is not the behaviour you are experiencing. In the T2 option under the Authorization type, even when it was added back in the first release of T2, a default new file selection never existed for "“Valid authorization already on file and accepted by CRA”.
If you provide additional detail I am happy look into this further or you could even give us a call.
I usually have my staff do the carry forward (and other corp. file prep) before I review it, so I was assuming they were messing with the AuthRep setting or something. I haven’t addressed the issue with any of them yet, since there are always more critical issues going on. But, I just tested it - carried forward a 2023 T2 that had “Valid authorization already on file and accepted by CRA ”, and yes - the new 2024 file has reverted to “Online access by a firm”. Not sure when this behaviour changed, but I think it’s been at least a month.
Your assumptions are correct @Steven. The behaviour that I am experiencing (as well as @Nezzer and @Arliss it seems) is the software is not retaining last year’s selection. If last year’s T2 return was set to “Valid authorization already on file and accepted by CRA” it gets changed upon carry forward to whichever of the 4 selections you have circled in your image. You then have to go to the AuthRep form and manually change it back to “authorization already on file” in order to clear the review message and get the software to prompt an AFR.
See screenshots below of a T2 file from January 31, 2023 and a subsequent carryforward to January 31, 2024.
Thanks. Strange that I was experiencing that same issue in the office but not when I tried at home using the latest release. I have asked Kyle to help me with this. I mat also check with Andrew. As soon as I have a good understaning of the cfwd source code and how to address it. I will report back.
Geez…curiosity got the best of me, I could not stop looking into this further.
I am still trying to understand this but this is what i found so far.
In the Engagement form, if you have set the “Cancellation method” to be “Select the cancellation method to prepare”, then AuthRepBus will CFWD and retain “Valid authorization already on file and accepted by CRA”
However, if the “Cancellation method” field in the Engagement form is “Cancel by EFILE”, TC will CFWD the AuthRepBus type drop down according to the T2 new file option.
Please check
So, the first thing I am going to ask both of you @snoplowguy@Nezzer is … in your source file (the previous year T2 file) what selection do you have in the T2 Engagement form in the Consent section under the “Cancellation method”? Does it show “Cancel by EFILE”?
I “think” the logic is that if an AuthRepBus was cancelled then you no longer have “Valid authorization already on file and accepted by CRA” and ths TaxCycle sets the Authorization type according to the T2 option default upon a CFWD.
Having said that something tells me that you probably have not selected “Cancel by EFILE” in the Engagement form. So, I will continue to investigate what would set the Engagement field to select “Cancel by EFILE” upon a CFWD. I was hoping it would be an easy thing to look up but it is turning out to be something beyond what I can understand. Anyway, I am still in the investigation mode.
It is set to “Select the cancellation method to prepare”. However, when I change it to “Cancel by EFILE”, then save the file, then carry it forward, both that field and the {{CurrentClient.RC59OnLine.Consent.Consent}} field on the AuthRepBus form get reset. That is:
{{CurrentClient.RC59OnLine.Consent.Consent}} changes to “Online access by a firm”
{{CurrentClient.Engage.Consent.CancellationType}} changes to “Select the cancellation method to prepare”
Furthermore, when I set {{CurrentClient.Engage.Consent.CancellationType}} to “Cancel by EFILE”, TaxCycle immediately requires me to enter a few fields on the AuthRepBusCancel form, which is even more work than setting {{CurrentClient.RC59OnLine.Consent.Consent}} to “Valid authorization already on file and accepted by CRA”
I have not selected “Cancel by EFILE” in the engagement form. I have never selected anything in that area of the engagement form for any client, and this issue has not happened until recently.
Since I have never needed to select anything in that box my T2 returns carry forward as “Select the cancellation method to prepare”. as seen below.
If I change that to “Cancel by EFILE” which is the only other option it does not seem to help the AuthRep form. I’d also be worried that changing that field to “Cancel by EFILE” will cause my RAC access to terminate for that client. As @Nezzer said… having that set to “Cancel by EFILE” only makes things worse.
