If you sell software in Canada, two bodies of rules reach quietly into your billing stack: language obligations that center on Quebec, and federal anti-spam rules that govern the emails your billing sends. This is a practical orientation from a billing-tooling perspective — not legal advice; for contracts, talk to a lawyer.
Why language is a billing concern in Quebec
Quebec's Charter of the French Language, strengthened by the amendments known as Bill 96, makes French the default language of commerce in the province. In practice this reaches documents your billing system generates:
- Contracts of adhesion — standard-form SaaS agreements — generally must be available in French
- Invoices and receipts must be available in French
- Customer-facing written communications tied to the transaction should not leave French-speaking customers at a disadvantage
"Available in French" is the operative phrase: you can also offer English, but French cannot be an inferior experience — harder to find, less complete, or slower.
What this touches in a SaaS billing stack
| Surface | What to check |
|---|---|
| Invoice documents | French version available by default in Quebec |
| Subscription terms | French contract of adhesion before checkout |
| Dunning emails | French versions of payment-failure notices |
| Customer portal | French UI for invoice and payment-method views |
| Support macros | Bilingual canned responses for billing questions |
What "available in French" means in practice
The obligation is generally about availability and equivalence, not exclusivity:
- You may offer English — but the French version cannot be harder to find, less complete, or delivered slower
- The French contract cannot impose worse terms than the English one
- A French version produced by machine translation technically exists; a French version a francophone would sign is what the obligation is aiming at. Treat fluency as the bar for anything touching money.
For most small SaaS teams the practical posture is simple: ship French everywhere by default in Canada, rather than maintaining province-detection logic and exceptions.
Rest of Canada: English default, French ready
Outside Quebec there is no equivalent language statute for billing documents. The pragmatic pattern for a Canadian SaaS: English as the default locale, French one click away, and both generated from the same source of truth so they never drift. Spanish or other languages can follow the same pipeline when the market calls for it.
CASL: the consent side of billing email
Canada's Anti-Spam Legislation (CASL) governs commercial electronic messages. Messages that exist to complete or service an existing transaction — an invoice notice, a failed-payment alert — are generally treated differently from marketing. But the lines blur fast:
- A payment-failure email with a "check out what is new" section may drift into commercial territory
- Consent records matter: express consent needs proof, implied consent expires
- Every commercial message needs valid sender identification and an unsubscribe path
| Consent type | How it arises | Practical note |
|---|---|---|
| Express | Customer checks a box, fills a form | Record source, date, and wording |
| Implied (existing relationship) | Current customer, recent purchase | Has an expiry window — track it |
| Transactional | Message completes or services a transaction | Keep it free of promotional content |
The safe pattern for billing teams: keep transactional notices clean (transaction only), and move anything promotional into properly consented marketing streams.
A shipping checklist for bilingual billing
- Invoice documents render in French for Quebec customers — by default, not by request
- Standard terms available as a French contract before checkout
- Dunning templates written in both languages, with the French version reviewed by a fluent reader — not machine output
- Customer portal language follows the customer's choice
- Email consent recorded with source and timestamp
- Transactional and marketing email streams separated
- A named owner for language compliance on the team
How Floatless approaches it
Floatless ships its console in English, French, and Spanish precisely because bilingual is a requirement, not a nice-to-have, for Canadian billing operations. Language lives in the product's i18n layer — including customer-facing billing surfaces — rather than bolted on per document.