Formal notice · Proof of receipt

Formal notice by email in Quebec: how to prove it was received

Yes, a formal notice (mise en demeure) can be sent by email in Quebec: article 1595 of the Civil Code requires a writing, not paper. The real issue lies elsewhere: if the recipient claims they never received it, how do you prove receipt?

This guide summarizes what the Civil Code of Quebec, the Act to establish a legal framework for information technology (LCCJTI) and recognized Quebec legal-information sources say — then compares the sending methods and the evidence each one leaves behind.

See doclinc's proof of delivery Start a free trial

General information only. This page is not legal advice and does not replace consulting a lawyer. Every situation is different: for yours, speak with a legal professional.

Is email valid for a formal notice?

In principle, yes. Article 1595 of the Civil Code of Quebec requires that the extrajudicial demand by which a creditor puts the debtor in default be made in writing and allow sufficient time to perform — it imposes no particular medium.

An email is a writing. The LCCJTI (s. 5) sets out the principle of functional equivalence: the legal value of a document is “neither increased nor diminished solely because a specific medium or technology was chosen.”
Case law has confirmed it — down to text messages. In Forget v. Gareau, 2017 QCCS 5428, the Superior Court recognized that a text message could satisfy the written-notice requirement of article 1595 C.C.Q., provided the message clearly demands performance of the obligation within a reasonable time.
The caveats. The content must still be complete (facts alleged, precise demand, deadline, consequences); some contracts or specific statutes may impose a transmission method; and above all, you will need to be able to prove sending and receipt if the matter reaches a court.

Sources: C.C.Q., art. 1595 (legisquebec.gouv.qc.ca) · LCCJTI, CQLR c. C-1.1, s. 5 (lccjti.ca) · SOQUIJ blog, “Une mise en demeure peut être transmise par texto” (2017) · JuriGo.ca, “Puis-je envoyer une mise en demeure par courriel au Québec?”.

The real problem: proving receipt

A formal notice only produces its effects if it reaches its recipient. With an ordinary email, your evidence stops at your Sent folder. The typical challenges:

“I never received it.” Without a reliable acknowledgment, it is your word against theirs; your Sent folder proves dispatch, not receipt.
“It went to my junk folder.” The spam filter is the most common objection — and often one that neither you nor the court can verify.
“That's no longer my address.” The LCCJTI's presumption of receipt applies to an address the recipient indicated or publicly represents as theirs, active at the time of sending.
“Someone else opened it.” An inbox is not an identity: an assistant, a spouse, a shared mailbox — nothing shows who actually took cognizance of the document.
The declined read receipt. Outlook and Gmail read receipts are optional: the recipient can simply choose not to send one.

Sources: JuriGo.ca (difficulty of proving receipt, junk-mail risk) · Juriclik.com, “Lettre de mise en demeure par courriel versus par envoi postal” · LCCJTI, s. 31 para. 2.

Your sending options and the proof they leave

Method	Proof of sending	Proof of receipt	Proof of the recipient's identity	Cost / delay
Registered mail	Canada Post receipt	Signature on delivery — but the item can be refused or go unclaimed	Signature of someone at the address (not necessarily the recipient)	≈ $15 · a few days
Bailiff (service)	Certificate of service (procès-verbal)	Certificate of service — the strongest evidence before the courts	Personal delivery witnessed by an officer of justice	≈ $125 to $400 · a few days
Ordinary email	Copy in your Sent folder	Nothing reliable: read receipts are optional, junk-folder risk	None — an inbox is not an identity	Free · instant
Secure link with authentication	Time-stamped sending log (date, time, origin, destination)	Log of every access to the document, time-stamped to the second	Recipient authenticated by SMS or voice call before each opening	A few dollars · instant

In fairness: for heavyweight litigation or a hard-to-reach debtor, service by bailiff remains the gold standard — an officer of justice attests to the delivery. An authenticated secure link combines the speed of email with documented technological evidence. Indicative costs (July 2026): JuriGo.ca and Quebec small-claims resources.

What good technological evidence contains

The LCCJTI specifically governs proof of transmission and receipt of a technology-based document. Its section 31 provides that the time of sending or receipt may be established by a transmission slip or an acknowledgment of receipt, or by producing information kept with the document where it guarantees the date, hour, minute and second of sending or receipt and indicates its origin and destination. In practice, robust evidence combines:

A precise, preserved timestamp. Date, hour, minute, second of sending and of each access — the exact level of detail section 31 para. 3 LCCJTI names.
Origin and destination. Who sent it, to which address — an address the recipient actually uses (s. 31 para. 2).
The authenticated identity of the recipient. This is what ordinary email lacks: out-of-band verification (SMS code, voice call) ties the opening of the document to a person, not just to a mailbox.
A tamper-evident access log. Every consultation recorded, kept with the document, producible in evidence. The section 31 presumptions are rebuttable: the more complete the log, the better it withstands challenge.
Document integrity. Being able to show the document opened is the one that was sent, unaltered (LCCJTI, ss. 5 and 6).

Sources: LCCJTI, CQLR c. C-1.1, s. 31 (full text at lccjti.ca) · case law applying s. 31, e.g. Lainez v. St-Pierre, 2013 QCRDL 4132 (rebuttable presumption).

Frequently asked questions

Is a formal notice sent by email valid in Quebec?

In principle, yes. Article 1595 C.C.Q. requires a writing without imposing paper, and the LCCJTI (s. 5) gives a technology-based document the same legal value. Case law has even accepted a formal notice by text message (Forget v. Gareau, 2017 QCCS 5428). The practical condition: being able to prove the recipient received it.

What if the recipient claims they never received my formal notice?

Everything turns on your evidence. A reply from the recipient to your email, a signed Canada Post delivery confirmation, a bailiff's certificate of service, or a time-stamped access log meeting section 31 LCCJTI can each establish receipt. With none of these, a court may find the notice never reached its recipient.

Is registered mail mandatory for a formal notice?

No. No general provision requires registered mail; official guides (including the Quebec government's small-claims resources) recommend it because it leaves proof of receipt that is easy to demonstrate. Check your contract or the applicable statute, though: some specific situations do impose a method.

Is an Outlook read receipt enough as proof of receipt?

Better than nothing, but fragile: read receipts are optional (the recipient can decline to send one), they do not say who opened the message, and they do not confirm the attached document was accessed. A written reply from the recipient, or an authenticated, time-stamped access log within the meaning of section 31 LCCJTI, is considerably stronger.

What counts as good proof of receipt for a technology-based document?

Under section 31 para. 3 LCCJTI: a transmission slip, an acknowledgment of receipt, or information kept with the document guaranteeing the date, hour, minute and second of sending or receipt, together with its origin and destination. Authenticating the recipient (SMS, call) adds what the statute does not presume: the identity of the person who opened the document.

Proof of receipt, built into your Outlook

With doclinc, your formal notice goes out like an email — but every access to the document is authenticated by SMS or voice call. The proof of delivery shows who opened the document, when (to the second) and how their identity was verified — a log aligned with the guarantees named in section 31 LCCJTI, hosted in Canada.