# Refresh Carryforward n/a

**URL:** <https://www.protaxcommunity.com/t/refresh-carryforward-n-a/12861>\
**Category:** T1\
**Created:** [September 17, 2026, 12:56am UTC](https://www.protaxcommunity.com/t/refresh-carryforward-n-a/12861 "2026-09-17T00:56:15Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![msbuttar](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/msbuttar/32/2516_2.png) [@msbuttar](https://www.protaxcommunity.com/u/msbuttar)\
**Post date:** [September 17, 2026, 12:56am UTC](https://www.protaxcommunity.com/t/refresh-carryforward-n-a/12861/1 "2026-09-17T00:56:15Z")

</div>

I am running version 16.064783.0. Today I created T1 2025 and then click prior year to create T1 2024. I filed 2024 return and now when I try to refresh carryforward for 2025 return but it is not available.

 ![Screenshot 2026-09-16 174450](https://us1.discourse-cdn.com/flex016/uploads/taxcycle/original/2X/2/22e7d121706b2311623c0065755128422da6b5a5.png)

---

<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:** [September 17, 2026, 11:47am UTC](https://www.protaxcommunity.com/t/refresh-carryforward-n-a/12861/2 "2026-09-17T11:47:11Z")

</div>

I made them aware of this July 29th.

I had hoped it would have got fixed in subsequent releases but it has not.

In the situation you describe I have been just been carrying forward the 2024 and saving over the 2025 year if it didn’t have any significant data entry.

This seems to effect all years I have noticed.

---

<div class="post-metadata">

**Author:** ![SmallBizGuy](https://avatars.discourse-cdn.com/v4/letter/s/74df32/32.png) [@SmallBizGuy](https://www.protaxcommunity.com/u/SmallBizGuy)\
**Post date:** [September 17, 2026, 4:30pm UTC](https://www.protaxcommunity.com/t/refresh-carryforward-n-a/12861/3 "2026-09-17T16:30:27Z")

</div>

Yah…I think that Quality Control has decreased rather surprisingly over the past while…lots of little bugs. One can only hope that big bugs aren’t around the corner.

Still waiting for them to fix the issue below:

> [@Design changes in 16.0.63993.0 or just me?](https://www.protaxcommunity.com/t/design-changes-in-16-0-63993-0-or-just-me/12719/17):
>
> LOL \_ just figured out what happens when one selects the “move to the left edge of the window button” and it is DEFINITELY a bug: Before clicking is shown above, after clicking it is below: It moved to the left edge of the window all right…the WRONG window…

Small, but annoying…and given the increase in pricing, concerning. Xero has not, so far, been as good a steward as one might have hoped for IMNSHO.

---

<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:** [September 18, 2026, 4:20pm UTC](https://www.protaxcommunity.com/t/refresh-carryforward-n-a/12861/4 "2026-09-18T16:20:53Z")

</div>

I just tested this with a simple file and it works as I would expect. Have you got a minimal file that you could share with me so I can test it? I guess I need two files… the original 2024 version and the 2025 file that you carried forward.

Any help would be appreciated.

---

<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:** [September 18, 2026, 4:47pm UTC](https://www.protaxcommunity.com/t/refresh-carryforward-n-a/12861/5 "2026-09-18T16:47:32Z")

</div>

Just to make sure I was understood.

This occurs when I create a 2025 file and then carry back any number of years.

Say I carried back to 2023. Prepare 2023 return to completion.

Open the 2024 and then try to refresh carryforward. If memory serves the option does not exist.

I will play around to make sure I Have that right.

---

<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:** [September 18, 2026, 4:56pm UTC](https://www.protaxcommunity.com/t/refresh-carryforward-n-a/12861/6 "2026-09-18T16:56:48Z")

</div>

Just created a 2025 and saved. Carried back to 2024 and saved. Opened 2025 and no refresh from prior is available. Selecting prior year gives message that the prior year cannot be found.

---

<div class="post-metadata">

**Author:** ![SmallBizGuy](https://avatars.discourse-cdn.com/v4/letter/s/74df32/32.png) [@SmallBizGuy](https://www.protaxcommunity.com/u/SmallBizGuy)\
**Post date:** [September 18, 2026, 6:21pm UTC](https://www.protaxcommunity.com/t/refresh-carryforward-n-a/12861/7 "2026-09-18T18:21:44Z")

</div>

Did you reindex? Maybe that solves it?

---

<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:** [September 18, 2026, 6:34pm UTC](https://www.protaxcommunity.com/t/refresh-carryforward-n-a/12861/8 "2026-09-18T18:34:14Z")

</div>

I assume things are working normally for you then?

I know I am not alone as I didn’t start the thread but I will reindex in case that could solve it, but I believe it has to be some sort of linking problem.

---

<div class="post-metadata">

**Author:** ![SmallBizGuy](https://avatars.discourse-cdn.com/v4/letter/s/74df32/32.png) [@SmallBizGuy](https://www.protaxcommunity.com/u/SmallBizGuy)\
**Post date:** [September 18, 2026, 6:50pm UTC](https://www.protaxcommunity.com/t/refresh-carryforward-n-a/12861/9 "2026-09-18T18:50:46Z")

</div>

Just retested…if the 24 file is open, TC25 just brings it forward and if closed, TC25 just opens it on the refresh…no data update.

Then I tried closing TC entirely and reopening the 25 file…same result…just reopens the 24 file without updating the 25. BUG!

---

<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:** [September 18, 2026, 7:50pm UTC](https://www.protaxcommunity.com/t/refresh-carryforward-n-a/12861/10 "2026-09-18T19:50:11Z")

</div>

That seems a bit different then what is happening with me but it does seem there are linking issues. And as I expected the reindex accomplished nothing for me.

---

<div class="post-metadata">

**Author:** ![Nezzer](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/nezzer/32/3845_2.png) [@Nezzer](https://www.protaxcommunity.com/u/Nezzer)\
**Post date:** [September 19, 2026, 3:08am UTC](https://www.protaxcommunity.com/t/refresh-carryforward-n-a/12861/11 "2026-09-19T03:08:22Z")

</div>

I’ve had similar issues occasionally, but usually able to fix the problem by removing and re-establishing the link. If you are unfamiliar with this, go to **File-\> Info** and click **Linked Files** :

 ![image](https://us1.discourse-cdn.com/flex016/uploads/taxcycle/original/2X/6/6c6ff386341cc53aaae72d4e82b520a476dad09c.png)

If there is a link to a file, remove it:

![image](https://us1.discourse-cdn.com/flex016/uploads/taxcycle/optimized/2X/7/73b728e88e98778ddb0519cf469be8d4bd050803_2_690x69.png)

Then, go back and try to open a prior year file:

 ![image](https://us1.discourse-cdn.com/flex016/uploads/taxcycle/original/2X/b/bea5f0029f0dc7bd0f34b72b4105e96009be1d71.png)

It should prompt you to navigate to the file you want to link. Find it, and complete the process.

---

<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:** [October 13, 2026, 4:24pm UTC](https://www.protaxcommunity.com/t/refresh-carryforward-n-a/12861/12 "2026-10-13T16:24:20Z")

</div>

Removing and reestablishing the link does work, but this is still happening for me for newly created files in the scenario described.
