cra-assistent

← Curriculum /E-services and digital channels /Level 1

Registering for and signing in to My Account

Draft — unverified

Registration is where this line's calls concentrate, and it is deliberately harder than signing up for an ordinary website. CRA is about to disclose someone's income, their family situation and their benefit entitlement to whoever completes the process, so the process has to establish that the person really is who they claim. It does that by asking for things only that person should know, and then by confirming an address CRA already holds — which is why part of registration has historically travelled by post and cannot be rushed. Understanding what each step is actually testing lets an agent explain a refusal without sounding arbitrary, and lets them recognise the cases where registration genuinely cannot succeed yet.

How to work through this tutorial

This follows a person from no access to full access: 1. Understand what registration is actually proving, and why it is slow. 2. Learn what identifying information is asked for. 3. Learn the credential choices and how they differ when something goes wrong. 4. Understand the verification step and the alternatives to waiting. 5. Learn the cases where registration cannot succeed, and what to say instead. 6. Work through an example of a failed registration. 7. Check your work against the common errors. 8. Verify every specific against CRA's published guidance before relying on it.

What registration is proving

Registration answers one question: is the person at the keyboard the taxpayer whose information is about to be shown? It answers it in two parts. First, by asking for information the taxpayer should know and a stranger should not — including an amount from a return they have already filed and CRA has already assessed. Anyone can find a name and a date of birth; far fewer people can produce a specific line from someone else's assessed return. Second, by confirming an address or identity through a channel CRA already trusts. That is the step that introduces delay, and it is the step callers resent. It is worth being direct with them about why it exists: the alternative is an account that can be opened by anyone holding a stolen SIN. An agent who frames the wait as a protection rather than as a queue gets a noticeably better conversation.

What is asked for

The identifying information sits in two groups. The first is who the person is: their social insurance number, their date of birth, and their current postal code or address as CRA holds it. "As CRA holds it" is doing real work in that sentence — a person who moved and never told CRA will fail here while being entirely honest, and that is the single most common innocent failure. The second is proof of a filing history: an amount from a specific line of a return the person has filed and CRA has assessed. CRA specifies which return and which line at the time. A taxpayer reading from a copy of the return they filed can still fail if the return was reassessed and the figure changed, because the check is against CRA's assessed figure, not against what was submitted. Both groups have to match. Neither is negotiable over the phone, and an agent cannot supply the missing piece to get someone through — that would defeat the whole mechanism.

Which credential, and why it matters later

The person chooses how they will sign in from then on. A **CRA user ID and password** is issued and recovered by CRA. If it is forgotten, CRA's own recovery process applies, and CRA can help. A **Sign-In Partner** uses credentials the person already holds with a participating financial institution. Nothing about their banking is shared with CRA and nothing about their taxes is shared with the bank — it is an identity assertion, not a data exchange. But if those credentials fail, the recovery path runs through the bank, and CRA cannot reset them. Some **provincial digital identity services** are also accepted where available, with the same principle: the recovery path belongs to whoever issued the credential. That is the whole practical significance of the choice, and it is worth establishing early on any "I can't sign in" call. Half of those calls are about a credential CRA did not issue and cannot fix, and identifying that in the first minute is a kindness to everyone.

The verification step, and getting in sooner

After the identifying questions, the person's identity is confirmed through a channel CRA trusts. Historically that meant a **security code sent by mail** to the address CRA holds, entered on return to complete access. It is slow by design and by physics. Codes issued this way expire, so a person who lets one sit unused has to start that part again. CRA has also offered a **document verification** route, where the person verifies identity by presenting government-issued identification through the service rather than waiting for post. Where it is available it removes the wait entirely. There is usually **limited access** in the meantime: the account exists and some information is visible while full access is pending. Do not describe that interim state as "registered but broken". It is a designed stage. What is available, and what each stage permits, changes. Confirm the current position rather than describing the version you learned.

When registration cannot succeed yet

Some callers cannot register, and no amount of persistence will change it. Recognising these quickly is more useful than troubleshooting. A person who has **never filed a return** that CRA has assessed has no line amount to quote. There is nothing to verify against. The route forward is filing, not registering, and saying so plainly is better than leaving them to keep trying. A person whose **address with CRA is out of date** will fail the address check honestly. The address has to be corrected through another channel first. A person whose **return was reassessed** may be quoting a figure that no longer matches CRA's. A newcomer who has not yet been assessed on a Canadian return is in the first case, and it is worth being gentle about it: they have done nothing wrong, they are simply earlier in the process than the portal assumes.

A worked example: everything correct, still refused

Teaching example. The figures below are invented to show the method. They are not CRA figures, and no amount here should be used for a real taxpayer.

The figures and details in this example are invented for teaching. Nothing here should be quoted as CRA's position. Amara moved from Halifax to Winnipeg in the spring. She filed her return before the move, it was assessed, and she has a copy in front of her. She now wants access to My Account and registration keeps failing. She gives her SIN correctly. Her date of birth is correct. She reads the line amount from her return — suppose it is $46,200 — and it is exactly what she filed. She fails on the postal code, because CRA still holds her Halifax address. Nothing she has said is untrue and nothing she has done is wrong. The check is against what CRA holds, and what CRA holds is stale because she never reported the move. There is a second trap waiting even if she clears that one. If her return had been reassessed after filing — say her employer amended a slip and the figure became $46,900 — then the copy in her hand would no longer match CRA's assessed figure, and reading carefully from it would still fail. The lesson for a call: when someone insists their information is right, they are often correct. Ask what CRA holds, not what they hold.

Common errors

Treating a failed registration as a sign that the caller is mistaken. Stale CRA records fail honest callers routinely. Asking the caller to "just read it off the return" without checking whether the return was reassessed. Offering to supply or confirm the verification information yourself. That defeats the mechanism registration exists for. Telling someone with no assessed return to keep trying. They cannot succeed; they need to file. Treating a Sign-In Partner failure as something CRA can reset. CRA did not issue that credential. Quoting how long a mailed security code takes, or how long it remains valid, from memory. Both are published and both change. Describing the interim limited-access stage as an error rather than as a designed step. Assuming the document verification option is available to everyone, everywhere, at all times.

What to verify this tutorial against

This was drafted without a source document. Registration steps and the options available change more often than almost anything else in this line, so confirm all of it against current pages. CRA's registration pages for My Account are the primary reference: the identifying information required, which return and which line amount is asked for, and the current verification options. CRA's guidance on the security code covers how it is delivered, how long delivery takes and how long the code remains valid. Take both timings from the page, never from memory. CRA's document verification guidance, where the service is offered, sets out who can use it and what identification is accepted. CRA's sign-in help pages cover the credential types and the recovery path for each, including the point that CRA cannot recover a Sign-In Partner credential. CRA's pages on changing an address explain the routes available to someone who cannot register because their address is out of date — which is the practical answer to the most common failure. The general income tax and benefit guide is the reference for the filing obligation itself, which is the real answer for a caller who has never filed.

Your progress

This is your own record of what you have worked through. It says nothing about whether the content has been verified.

Quiz not attempted. 7 questions available — marking this complete does not require taking it, but the quiz is the only thing here that distinguishes having read the page from having learned it. Take the quiz

Claims to confirm

These are the checkable specifics from this tutorial — the details most likely to be wrong in a drafted page. Confirm each against CRA guidance. 0 of 12 confirmed.

Verify this tutorial

12 claim(s) still unconfirmed. Confirm them above first — verifying the page while its specifics are outstanding would defeat the purpose of listing them.