Profile HelpIntuitKnown issues in ProFile
by Intuit• Updated 5 days ago
Heads up! Microsoft is ending support for Windows 10 on October 14, 2025. This means no more free technical assistance or security fixes. To keep your system secure and your ProFile experience optimal, we recommend upgrading to Windows 11.
The following are known issues in the current release of ProFile. Don't see your issue listed below? Search for other issues and errors on our ProFile Community and Support site.
ProFile does not carry forward TaxCycle data for more than one S125 form
| Issue | When carrying forward T2 returns, forms subsequent to the first S125 aren't populated with TaxCycle data. Only the initial form populates. |
| Modules Impacted | T2/CO-17 |
| Workaround | Review the equivalent S125 forms in TaxCycle and enter the additional statements manually in ProFile. |
| Resolution | This issue will be fixed in a future ProFile release. |
Issues with EFILE Error #353
| Issue | CRA EFILE# 353 The claim for the spouse or common-law partner amount at field 58120 of the provincial form 428 differs from the maximum allowable |
| Modules Impacted | T1 |
| Workaround | You'll need to paper-file the return. |
| Resolution | The CRA is aware of this error, but hasn't committed to a timeline to fix it. |
The AExempt form prevents an AT1 return from EFILE, even though a AS10 loss carryback was prepared
| Issue | In ProFile, the AExempt form prevents an AT1 return from EFILE, even though a AS10 loss carryback was prepared. |
| Modules Impacted | T2 |
| Workaround | Open the AExempt form for an AT1 return. Next, uncheck box number 3 (it has no taxable income for the taxation year). |
| Resolution | The AExempt form is calculating as it should. Once that box is unchecked, you will be able to EFILE. |
Special character support on Foreign Property Return Schedule (TP1079.8.BE)
| Issue | We've identified a technical vulnerability within the Foreign Property Return Schedule (TP1079.8.BE). This is in Column A of the detailed reporting section. Right now, we don't support using special characters in certain situations. Attempting to include these characters in Column A may result in validation errors that prevent a successful submission. |
| Modules Impacted | T2/CO-17 |
| Workaround | You can continue with internet filing if you remove all special characters in column A. |
| Resolution | This issue will be fixed in a future ProFile release. |