Remitian V. 3.6
Release 3.6 - Released: July 2, 2026 - Type: Compliance and Quebec Payment types - Audience: Firms and taxpayers
At a glance
Remitian 3.6 is a Canadian release focused on closing several Quebec coverage gaps, correcting long-standing GST/HST labeling, and automating identity verification during onboarding. It also delivers a small set of targeted bug fixes and quality-of-life improvements requested by firms.
|
Highlights: full Quebec provincial coverage for corporate and individual taxpayers, two new Quebec remittance types (payroll source deductions and QST), automated Equifax KYC, and consistent GST/HST labeling across the product. |
What's new
Consistent GST/HST labeling
The product previously used "HST" throughout when referencing the GST/HST filing and payment type. Clients in provinces where only GST applies (for example, Alberta) did not recognize "HST" as relevant to them. This release replaces every user-facing "HST" label with "GST/HST" across payment views, the Filings section, subscription plan labels, notification emails, and filing approval messages.
This is a wording-only change. Filing behavior, scheduling logic, and payment routing are unchanged.
Quebec provincial coverage, corporate and individual
Quebec provincial scheduled payments require a 20-character alphanumeric payment code (PCRQ) issued by Revenu Québec. Remitian 3.6 delivers end-to-end support for this code across both corporate and individual taxpayer flows.
- Corporate: a Payment Code field appears in the tax payment modal when the Quebec Provincial subtype is selected. The code is required and validated to the Revenu Québec format at scheduling.
- Individual: the Canadian personal tax account flow now includes a provincial accounts step so individuals can attach a Revenu Québec account alongside their CRA account, and provide their payment code at scheduling.
Quebec payroll source-deduction remittance
Corporate clients can now schedule Quebec payroll source deductions through Remitian.
Quebec QST sales-tax remittance
Corporate clients can now schedule single and recurring Quebec QST sales-tax remittances .
Automated identity verification through Equifax
KYC submissions are now processed automatically through the Equifax API, replacing the previous manual review workflow. Onboarding prioritizes Equifax, with Plaid retained as a fallback. Your clients will move through verification faster and with fewer manual steps.
Improvements
|
Area |
What was happening |
What's fixed |
|---|---|---|
|
CanadianTrust accounts |
Viewing payment details for a schedule linked to a CanadianTrust tax entity returned a server error. |
Trust entities are now fully supported by the payment details view. |
|
Paid status tooltip |
The tooltip shown when hovering over a Paid payment status displayed an earlier draft of the copy. |
The tooltip now reads: "The tax authority have confirmed receipt of the payment. We will notify you and your accountant if any follow-up is needed." |
|
Expired sessions |
Users whose session had expired remained in the app and encountered auth errors. |
Expired sessions now log the user out cleanly. |
|
KYC/KYB awareness cards |
The awareness cards counted every payment rather than only at-risk (will-fail) payments, overstating how many needed attention. |
The cards now count only at-risk payments. |
|
Preview Client Dashboard |
Payment-row fields overlapped on the firm-side Preview Client Dashboard. |
The layout has been corrected. |
What this means for your firm
- Clients in Alberta and other GST-only provinces will recognize the GST/HST option as relevant to them.
- You can now serve Quebec corporate and individual clients end-to-end for provincial scheduled payments.
- Corporate clients with Quebec obligations can add QST and payroll source deductions to their scheduled remittances.
- Onboarding is faster: identity verification runs automatically through Equifax rather than a manual review.
- CanadianTrust taxpayers can open payment details without a workaround.
Questions
If something is not behaving as expected on 3.6, contact your Remitian success partner or reply to the release announcement email. Please include the frontend version numbers shown on the login page so we can reproduce the issue quickly.