# Recalculate glitches

**URL:** <https://www.protaxcommunity.com/t/recalculate-glitches/1331>\
**Category:** T1\
**Created:** [April 30, 2017, 12:40am UTC](https://www.protaxcommunity.com/t/recalculate-glitches/1331 "2017-04-30T00:40:27Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![TimParris](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/timparris/32/240_2.png) [@TimParris](https://www.protaxcommunity.com/u/TimParris)\
**Post date:** [April 30, 2017, 12:40am UTC](https://www.protaxcommunity.com/t/recalculate-glitches/1331/1 "2017-04-30T00:40:27Z")

</div>

I’ve had a few issues with the recalculate. It would be nice to be able to force a recalculate.

Example, I printed a set of forms for signature, including the Quebec return. Unbeknownst to me, the return was recalculated when I reopened to file, once the forms were signed, and there no longer was an amount owing on Schedule K. The return was transmitted without realizing that the bottom line had changed in the week while the forms were in the post.

What gives?

---

<div class="post-metadata">

**Author:** ![james1](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/james1/32/47_2.png) [@james1](https://www.protaxcommunity.com/u/james1)\
**Post date:** [April 30, 2017, 12:48am UTC](https://www.protaxcommunity.com/t/recalculate-glitches/1331/2 "2017-04-30T00:48:59Z")

</div>

I have not had any issues with he recalculate. The only file I had something similar to that occurring was user error where I likely did not save it in error.

Now I never file a T1 without checking the taxes owing on the T183 to the program since I did exactly what you mentioned several years back and then had to fix it.

At least you have refile now to fix it easily.

---

<div class="post-metadata">

**Author:** ![Arliss](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/arliss/32/52_2.png) [@Arliss](https://www.protaxcommunity.com/u/Arliss)\
**Post date:** [April 30, 2017, 1:24am UTC](https://www.protaxcommunity.com/t/recalculate-glitches/1331/3 "2017-04-30T01:24:17Z")

</div>

I have found at least 5 files change on me this year after printing and waiting for signatures. All had pension splitting and foreign tax credits. I haven’t had any others jump on my thread and rant about it so I assumed it may have been related to a one off version I was using for a while. It did make me realize however that I would like the ability to lock the file on printing.

---

<div class="post-metadata">

**Author:** ![james1](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/james1/32/47_2.png) [@james1](https://www.protaxcommunity.com/u/james1)\
**Post date:** [April 30, 2017, 1:42am UTC](https://www.protaxcommunity.com/t/recalculate-glitches/1331/4 "2017-04-30T01:42:09Z")

</div>

Which is why the balance owing needs to be checked against the signed T183 prior to filing. You never know when one of the three happen;

1. You forgot to save;
2. Someone else in your office made a change after you printed;
3. The program calculation was updated and the balance changed.

@TimParris, have you checked the history of the file to see what version you printed from and whether there is a save after the print job? Look for the day you printed it and then saved the file. If you do not see it, it could indicate that the save was missed.

@Arliss, You can do the same to determine which version was the problem.

![](https://cdck-file-uploads-us1.s3.dualstack.us-west-2.amazonaws.com/flex016/uploads/taxcycle/original/1X/69ece039a521489bef13c24c1eb9a4ee48a61104.png)

---

<div class="post-metadata">

**Author:** ![TimParris](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/timparris/32/240_2.png) [@TimParris](https://www.protaxcommunity.com/u/TimParris)\
**Post date:** [April 30, 2017, 1:52am UTC](https://www.protaxcommunity.com/t/recalculate-glitches/1331/5 "2017-04-30T01:52:13Z")

</div>

Schedule k is Quebec. No refile.

---

<div class="post-metadata">

**Author:** ![james1](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/james1/32/47_2.png) [@james1](https://www.protaxcommunity.com/u/james1)\
**Post date:** [April 30, 2017, 1:53am UTC](https://www.protaxcommunity.com/t/recalculate-glitches/1331/6 "2017-04-30T01:53:46Z")

</div>

> [@TimParris](#):
>
> Schedule k is Quebec. No refile.

That is too bad. Did you check the history to see the steps that happened?

---

<div class="post-metadata">

**Author:** ![Arliss](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/arliss/32/52_2.png) [@Arliss](https://www.protaxcommunity.com/u/Arliss)\
**Post date:** [April 30, 2017, 1:58am UTC](https://www.protaxcommunity.com/t/recalculate-glitches/1331/7 "2017-04-30T01:58:00Z")

</div>

You have made me think I might have done it to myself. If it was around the time of the REFILE release I may have opened and saved to clear the little red exclamation point. I think I would like the ability to have the file lock on printing to save me from myself. 😁

---

<div class="post-metadata">

**Author:** ![Cameron](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/cameron/32/12_2.png) [@Cameron](https://www.protaxcommunity.com/u/Cameron)\
**Post date:** [April 30, 2017, 3:38am UTC](https://www.protaxcommunity.com/t/recalculate-glitches/1331/8 "2017-04-30T03:38:09Z")

</div>

> [@TimParris](#):
>
> It would be nice to be able to force a recalculate.

Shift+F2 will force a recalculate.

[http://get.taxcycle.com/TaxCycle-Keyboard-Shortcuts.pdf](http://get.taxcycle.com/TaxCycle-Keyboard-Shortcuts.pdf)

---

<div class="post-metadata">

**Author:** ![dharnish](https://avatars.discourse-cdn.com/v4/letter/d/ba8739/32.png) [@dharnish](https://www.protaxcommunity.com/u/dharnish)\
**Post date:** [May 9, 2017, 5:50pm UTC](https://www.protaxcommunity.com/t/recalculate-glitches/1331/9 "2017-05-09T17:50:58Z")

</div>

I am with you!  
Would absolutely love to lock the file on printing!  
I have asked for this but been advised there are few wanting it and there are too many options now!  
However, there are at least 2 of us wanting this!  
I have had at least 2 files that data changed on me. (These are the ones I caught anyway.)

It seems taxcycle wants you to work on the file and then efile it one at a time before closing the file. Then the file locks and a snapshot is taken after Efile. This is the perfect scenario within taxcylce.  
When you get outside that perfect, I find little problems and glitches like this.

Anyway, thats my 2 cents.

This lack of file locking and no snapshot after printing has been an ongoing issue I have fought with all tax season.

Overall, I am very pleased with the product. I hope there may be someone listening out there???

Dan

---

<div class="post-metadata">

**Author:** ![Cameron](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/cameron/32/12_2.png) [@Cameron](https://www.protaxcommunity.com/u/Cameron)\
**Post date:** [May 9, 2017, 6:22pm UTC](https://www.protaxcommunity.com/t/recalculate-glitches/1331/10 "2017-05-09T18:22:08Z")

</div>

@dharnish –

A snapshot on printing is already available. Start with the CRA Condensed print set, copy it, rename it, add any forms you want and then tick the box… I’ll make this easier to configure in the next little while,

 ![](https://us1.discourse-cdn.com/flex016/uploads/taxcycle/original/1X/31b8af6ac70ed3837b1039d16acbead46eef6092.png)

We are going to allow for lock on printing as well. It will be configurable on a print set by print set basis. Watch for it over the summer.

~ Cameron

---

<div class="post-metadata">

**Author:** ![james1](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/james1/32/47_2.png) [@james1](https://www.protaxcommunity.com/u/james1)\
**Post date:** [May 9, 2017, 6:38pm UTC](https://www.protaxcommunity.com/t/recalculate-glitches/1331/11 "2017-05-09T18:38:36Z")

</div>

> [@Cameron](#):
>
> We are going to allow for lock on printing as well. It will be configurable on a print set by print set basis. Watch for it over the summer.

So this would lock everything but the transmit? Or are you intending that thy unlock to file? if so, you may need to have to build the unlock into the transmit button

---

<div class="post-metadata">

**Author:** ![dharnish](https://avatars.discourse-cdn.com/v4/letter/d/ba8739/32.png) [@dharnish](https://www.protaxcommunity.com/u/dharnish)\
**Post date:** [May 9, 2017, 6:58pm UTC](https://www.protaxcommunity.com/t/recalculate-glitches/1331/12 "2017-05-09T18:58:21Z")

</div>

Thanks very much for pointing this out!

I will definitely use this next filing season.

Now, if I could only lock the file on printing!

Thanks so much for your help!!

Dan

---

<div class="post-metadata">

**Author:** ![james1](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/james1/32/47_2.png) [@james1](https://www.protaxcommunity.com/u/james1)\
**Post date:** [May 9, 2017, 7:35pm UTC](https://www.protaxcommunity.com/t/recalculate-glitches/1331/13 "2017-05-09T19:35:43Z")

</div>

> [@dharnish](#):
>
> Now, if I could only lock the file on printing!

I see where you guys and gals are coming from; however, I can see all kinds of problems regarding this. You print it and the file locks, unless you can file the return as printed with no changes, you run the risk of a recalculation of the file prior to filing once you unlock it resulting in the amount changing. What happens if Taxcycle fixes a calculation due to a CRA or provincial mandate between the printing and filing which changes the balance owing?

If your purpose is to ensure nothing has changed from printing to filing, would it also be efficient for Taxcycle to always take an as printed snapshot linked to your final print job for the client. When you open the Eile for filing later on, the program can check say the taxes payable in the snapshot against the current taxes payable alerting the user that something has changed. They could also look at certain total lines in the snapshot like line 150 for changes that do not affect the balance owing.

Taxcycle could also alert you if there is no printed snapshot to compare against and maybe tell you if there are multiple “final print” snapshots.

Personally, I think this is a much better system than locking the file after printing since those files that do not change are always good to go, and those that have differences give you a change to review it and sign off prior to sending. Regardless of the system, I will continue to compare the signed T183 to the online one prior to filing. That brings me to something I would prefer to see, when I confirm the signature to file a T1, I would like the T183 to display prior to transmit so I can check the numbers

And once a file is locked, I should not see error messages when I open the file later on because of changes

---

<div class="post-metadata">

**Author:** ![TimParris](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/timparris/32/240_2.png) [@TimParris](https://www.protaxcommunity.com/u/TimParris)\
**Post date:** [May 9, 2017, 8:32pm UTC](https://www.protaxcommunity.com/t/recalculate-glitches/1331/14 "2017-05-09T20:32:17Z")

</div>

Small comment…

About 60% of my clients no longer come in to sign the papers. So it can be  
a day or two between printing and signing, or 20 days for the Yukon  
clients. I usually post-date the date on the T183/TP1000 to accommodate the  
delay in signature.

However, I have found that I can lock the file (manually) once the  
T183/TP1000 has been printed, then return to the file to efile without  
unlocking. I can change the file status on the info screen as well, even  
though the file is locked.

That solves my issue - IF I REMEMBER TO LOCK THE FILE AFTER PRINTING THE  
T183/TP1000.

---

<div class="post-metadata">

**Author:** ![Cameron](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/cameron/32/12_2.png) [@Cameron](https://www.protaxcommunity.com/u/Cameron)\
**Post date:** [May 10, 2017, 12:31pm UTC](https://www.protaxcommunity.com/t/recalculate-glitches/1331/15 "2017-05-10T12:31:58Z")

</div>

> [@james1](#):
>
> So this would lock everything but the transmit? Or are you intending that thy unlock to file? if so, you may need to have to build the unlock into the transmit button

You won’t need to generally need unlock the file to transmit the return. We will however, give you a warning if an update to the calculations causes the return to change in any way that affects the filing, allowing for configurable tolerances.

We’re working on the exact details of how we’ll deal with this, and plan to share more well in advance of next season.

---

<div class="post-metadata">

**Author:** ![dharnish](https://avatars.discourse-cdn.com/v4/letter/d/ba8739/32.png) [@dharnish](https://www.protaxcommunity.com/u/dharnish)\
**Post date:** [May 16, 2017, 8:28pm UTC](https://www.protaxcommunity.com/t/recalculate-glitches/1331/16 "2017-05-16T20:28:54Z")

</div>

Thanks for this Cameron.

I really appreciate it.

This will make next tax season so much easier for our office.

Dan
