# T1 not eligible for Efile

**URL:** <https://www.protaxcommunity.com/t/t1-not-eligible-for-efile/7765>\
**Category:** EFILE\
**Created:** [February 6, 2024, 4:14am UTC](https://www.protaxcommunity.com/t/t1-not-eligible-for-efile/7765 "2024-02-06T04:14:55Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![info.vnasolutions](https://avatars.discourse-cdn.com/v4/letter/i/7ab992/32.png) [@info.vnasolutions](https://www.protaxcommunity.com/u/info.vnasolutions)\
**Post date:** [February 6, 2024, 4:14am UTC](https://www.protaxcommunity.com/t/t1-not-eligible-for-efile/7765/1 "2024-02-06T04:14:55Z")

</div>

Hi, There is an error showing up that the return is not eligible for Efile. How to resolve that issue?

---

<div class="post-metadata">

**Author:** ![asifnana](https://avatars.discourse-cdn.com/v4/letter/a/71e660/32.png) [@asifnana](https://www.protaxcommunity.com/u/asifnana)\
**Post date:** [February 6, 2024, 1:35pm UTC](https://www.protaxcommunity.com/t/t1-not-eligible-for-efile/7765/2 "2024-02-06T13:35:46Z")

</div>

T1 EFile is closed until Feb 20

---

<div class="post-metadata">

**Author:** ![pugs1](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/pugs1/32/65_2.png) [@pugs1](https://www.protaxcommunity.com/u/pugs1)\
**Post date:** [February 6, 2024, 3:08pm UTC](https://www.protaxcommunity.com/t/t1-not-eligible-for-efile/7765/3 "2024-02-06T15:08:28Z")

</div>

T1 open on feb 19th

---

<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:** [February 6, 2024, 4:17pm UTC](https://www.protaxcommunity.com/t/t1-not-eligible-for-efile/7765/4 "2024-02-06T16:17:03Z")

</div>

Poster is likely aware of that.

Likely just wants to prepare the paperwork and get signatures and finalize a return **efficiently** now for filing on that day.

Other thread was hi-jacked so I will continue with my beef here.

---

<div class="post-metadata">

**Author:** ![wem](https://avatars.discourse-cdn.com/v4/letter/w/35a633/32.png) [@wem](https://www.protaxcommunity.com/u/wem)\
**Post date:** [February 6, 2024, 5:54pm UTC](https://www.protaxcommunity.com/t/t1-not-eligible-for-efile/7765/5 "2024-02-06T17:54:15Z")

</div>

Go to the Efile worksheet which lists the exclusions to efiling. You probably have an exclusion. Fix it if you can and when Efile opens up again you should be able to efile it.

TaxCycle has a webinar starting in a few minutes on Preparing a Basic T1. I take it every year and always pick up good tips or things I have forgotten.

---

<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:** [February 6, 2024, 6:09pm UTC](https://www.protaxcommunity.com/t/t1-not-eligible-for-efile/7765/6 "2024-02-06T18:09:28Z")

</div>

![Pooh](https://us1.discourse-cdn.com/flex016/uploads/taxcycle/original/2X/4/4c7c24970abccceb9c4303cf80fdc52ba2442507.gif)

---

<div class="post-metadata">

**Author:** ![RichJ](https://avatars.discourse-cdn.com/v4/letter/r/5fc32e/32.png) [@RichJ](https://www.protaxcommunity.com/u/RichJ)\
**Post date:** [February 6, 2024, 7:11pm UTC](https://www.protaxcommunity.com/t/t1-not-eligible-for-efile/7765/7 "2024-02-06T19:11:54Z")

</div>

If I understand @Arliss’ issue correctly, the only exclusion on the Efile Worksheet is the one imposed by TaxCycle. Right now, TaxCycle flags all T1s as not being eligible to efile (which kind of makes sense, seeing as CRA efiling will only re-open Feb 19). Presumably, TaxCycle will release a new update shortly before Feb 19th (once the software has been approved by CRA) that will remove that “can’t be efiled” error/flag.

Because all returns are currently flagged as not eligible, it’s messing with the CLetter (and likely others). In the CLetter there’s a separate section that’s include based on if the return is efile eligble or not. Even though the return will eventually be eligible to be efiled, it’s printing the section of the CLetter letting the client know it’ll be paper filed. Not to mention the T183 which won’t be printed at all until the efile eligibility is changed.

We haven’t used the default print sets in a while but I would guess those are also setup to be used/available based on whether the return is being efiled or not.

I believe @Arliss is asking if that flag/error can be changed/removed. That way a return can be prepares now, have the client sign the appropriate forms (including the T183) and have everything ready/done for Feb 19th when efiling opens.

---

<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:** [February 6, 2024, 7:48pm UTC](https://www.protaxcommunity.com/t/t1-not-eligible-for-efile/7765/8 "2024-02-06T19:48:05Z")

</div>

Could not have said that better myself. Really I couldn’t. 😀

---

<div class="post-metadata">

**Author:** ![Elizabeth](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/elizabeth/32/2588_2.png) [@Elizabeth](https://www.protaxcommunity.com/u/Elizabeth)\
**Post date:** [February 6, 2024, 8:06pm UTC](https://www.protaxcommunity.com/t/t1-not-eligible-for-efile/7765/9 "2024-02-06T20:06:49Z")

</div>

We’re working on something in templates the letters better reflect the status of eligible to EFILE but with the system not yet open.

The print sets are another matter that I’m also looking into but I don’t have a solution for yet.

---

<div class="post-metadata">

**Author:** ![Elizabeth](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/elizabeth/32/2588_2.png) [@Elizabeth](https://www.protaxcommunity.com/u/Elizabeth)\
**Post date:** [February 7, 2024, 3:31pm UTC](https://www.protaxcommunity.com/t/t1-not-eligible-for-efile/7765/10 "2024-02-07T15:31:54Z")

</div>

@Arliss I can confirm that we have a fix so that the EFILE eligible content shows in the letters even when the EFILE systems is closed. I’ve also added a sentence with the EFILE opening date.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/taxcycle/original/2X/a/aa7aa6e9edc01e7eb6b6eb24b172cbc6b4ac4ae5.jpeg)

As for print sets, for the moment, I would suggest creating a print set that works during this time period, so you can get to the T183. Duplicate your client copy and right-click to adjust the form settings, like the T183 so it always appears.

---

<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:** [February 7, 2024, 4:01pm UTC](https://www.protaxcommunity.com/t/t1-not-eligible-for-efile/7765/11 "2024-02-07T16:01:14Z")

</div>

Thanks. Next release I presume?

---

<div class="post-metadata">

**Author:** ![pugs1](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/pugs1/32/65_2.png) [@pugs1](https://www.protaxcommunity.com/u/pugs1)\
**Post date:** [February 7, 2024, 4:30pm UTC](https://www.protaxcommunity.com/t/t1-not-eligible-for-efile/7765/12 "2024-02-07T16:30:41Z")

</div>

Elizabeth that is perfect thank you

Kevin

---

<div class="post-metadata">

**Author:** ![Elizabeth](https://sea2.discourse-cdn.com/flex016/user_avatar/www.protaxcommunity.com/elizabeth/32/2588_2.png) [@Elizabeth](https://www.protaxcommunity.com/u/Elizabeth)\
**Post date:** [February 7, 2024, 4:37pm UTC](https://www.protaxcommunity.com/t/t1-not-eligible-for-efile/7765/13 "2024-02-07T16:37:46Z")

</div>

@Arliss It’s in testing now, so barring anything unforeseen, yes.
