If you've encountered the following error message while submitting your tax return, here's what you need to know:
Message from the CRA: The identification information provided does not match CRA records. Please verify your entries.
Understanding the Error
NETFILE Error N1 means that the identification information submitted with your return doesn't match what the CRA has on record from Service Canada.
This error occurs when something in your return – such as your name (including any middle names or initials), SIN, date of birth, date of entry, or how you answered the "Are you filing an income tax return with the CRA for the first time?" question – isn't lining up with the CRA's existing records. As a result, the CRA's systems are unable to authenticate your identity and electronically accept the tax return via NETFILE.
What You Can Do
Start by carefully checking the following information in your tax return:
- Check your most recent tax return or your SIN card/letter from Service Canada to ensure your name and SIN are entered correctly in your tax profile and match exactly what Service Canada and the CRA have on file.
- Call the CRA to confirm the exact name, date of birth, and date of entry they have on record for your SIN, then update your tax profile to match their records.
After you have carefully reviewed and corrected all this information, try submitting your return again.
If the Error Persists
This NETFILE Error N1 comes directly from the CRA, and if you continue to experience it after verifying your information, you'll need to print and mail your return.
Avoiding NETFILE Account Lock
Multiple submission attempts while this error persists may result in your NETFILE account being temporarily locked. If this happens, you will have to contact the CRA directly to have it unlocked.
Important Notes
- This is a NETFILE error directly from the CRA and not related to your personal information stored in the Wealthsimple app.
- This isn't an issue with Wealthsimple Tax specifically – all tax software will encounter the same problem when there's a mismatch with CRA records.
Comments
0 comments
Article is closed for comments.