Canadian Retail Software: What US-Built Tools Get Wrong and What to Look For Instead

The Canadian Tax Problem: GST, HST, and PST

Canadian retail tax is more complex than US sales tax — not dramatically so, but meaningfully enough that software built for US tax structures handles it poorly without specific engineering investment. The three-tier system of GST, HST, and provincial PST requires different handling depending on the province the sale occurs in, the type of product being sold, and whether the customer is a registered business claiming input tax credits.

In provinces with Harmonised Sales Tax (Ontario, Nova Scotia, New Brunswick, Prince Edward Island, and Newfoundland and Labrador), a single HST rate applies to most retail sales. In provinces with separate GST and PST (British Columbia, Saskatchewan, Manitoba), the two taxes must be calculated, collected, and remitted separately — to different government agencies on different remittance schedules. In Alberta, only federal GST applies, with no provincial sales tax.

For businesses operating in Quebec, the tax calculation involves both federal GST and Quebec Sales Tax (QST), which is administered by Revenue Quebec separately from the Canada Revenue Agency. Businesses with a Quebec operation must register with both agencies, file separate returns, and handle input tax refunds under Quebec's TVQ system.

Software that handles this correctly applies tax rules based on the province of sale, not the province of business registration. A retailer with locations in Ontario, British Columbia, and Alberta should apply HST at Ontario locations, GST + PST at BC locations, and GST-only at Alberta locations — automatically, without manual tax code management at each register.

• HST provinces (ON, NS, NB, PEI, NL): single harmonised rate applied at point of sale
• GST + PST provinces (BC, SK, MB): two taxes calculated and remitted separately
• Alberta: federal GST only, no provincial sales tax
• Quebec: federal GST + QST, separate registration and remittance to Revenue Quebec
• Zero-rated goods: basic groceries, prescription drugs, and certain medical devices exempt from GST/HST

Statutory Holiday Pay: The QuickBooks Gap

Statutory holiday pay is one of the most documented compliance gaps in QuickBooks for Canadian businesses. Canadian employment standards legislation across all provinces requires specific calculations for stat holiday pay that depend on the employee's average daily earnings over a qualifying period, the province of employment, and whether the employee worked on the holiday itself.

The rules differ by province. In Ontario, stat pay is calculated as 1/20 of the wages earned in the four weeks prior to the holiday, excluding overtime. In British Columbia, the calculation uses average daily wages over a 30-day period. In Quebec, stat pay requires calculating 1/20 of wages from the preceding four weeks. These are not minor variations — they produce materially different amounts for the same employee.

QuickBooks Online's payroll module does not natively handle provincial stat pay calculation variations correctly for all Canadian provinces. This has been a documented complaint in the QuickBooks community forums for years. Businesses using QuickBooks for Canadian payroll typically manage stat pay with manual overrides, spreadsheet calculations, or a separate payroll service — adding administrative overhead and creating audit risk.

For retail businesses with hourly staff and fluctuating hours — precisely the employment profile that makes stat pay calculation most complex — this gap is a recurring monthly problem. Payroll software built for Canada handles stat pay calculation natively, per-province, without manual intervention.

Multi-Currency: CAD/USD and Beyond

Canadian retailers near the US border frequently process transactions in both CAD and USD. Retailers selling to international wholesale customers may deal with additional currencies. The multi-currency handling in US-built software is often designed around USD as the base currency, with other currencies treated as edge cases.

For Canadian businesses, CAD is the functional currency for tax reporting, financial statements, and CRA compliance. A platform built for Canada treats CAD as the primary currency and handles USD, EUR, and other currencies as transaction-level conversions with proper exchange rate tracking — not as a workaround requiring manual journal entries to reconcile the currency difference.

The accounting treatment of multi-currency transactions in Canada also differs from US GAAP in certain respects. Foreign exchange gains and losses must be reported in CAD on the business's financial statements, and the exchange rate used must be the Bank of Canada nominal rate or a rate that can be demonstrated to be reasonable. Software that uses live exchange rates from a US source and does not provide CRA-compliant rate documentation creates audit risk.

French-Language Compliance for Quebec Retailers

Quebec's Charter of the French Language (Bill 96 and its predecessor Bill 101) requires that software used by businesses operating in Quebec be available in French. This is not a preference — it is a legal requirement for businesses with more than 25 employees, and a practical necessity for smaller businesses whose customers and staff are primarily French-speaking.

Most US-built retail software offers French-language localisation as an afterthought: a translation of the most common interface elements, with English fallbacks for anything the localisation team did not cover. For customer-facing interfaces — receipt content, on-screen prompts during payment, loyalty program messages — partial French localisation fails the Charter's standard.

A platform built for Canada supports full French-language operation across all customer-facing and staff-facing interfaces. Receipts, error messages, inventory labels, reports, and administrative menus should all be available in French without English fallbacks. For bilingual operations — businesses serving both English and French-speaking customers — the platform should switch language at the session level, not require a separate installation or configuration.

Payment Processing: Canadian Rails and EMV Requirements

Canadian payment processing operates on different rails than the US market. Interac — the Canadian debit network — is not Visa or Mastercard. It has its own processing protocols, different interchange rates, and specific terminal certification requirements. US-built POS software that does not natively support Interac processing requires a separate terminal for debit transactions, creating a split-payment workflow that slows checkout and frustrates customers.

EMV chip-and-PIN is also the default payment method in Canada, not a secondary option. Canadian customers expect to enter a PIN for debit transactions and many prefer it for credit transactions as well. POS software designed primarily for the US market — where magnetic stripe and tap-to-pay dominate — may deprioritise the PIN pad flow in ways that create friction for Canadian customers.

Canadian merchant accounts are also structured differently than US accounts. Interchange rates, monthly volume thresholds, and chargebacks are governed by Canadian networks and the Office of the Superintendent of Financial Institutions (OSFI) in ways that affect how a business's payment processing costs are structured. A payment processor that is genuinely optimised for the Canadian market will offer Interac processing natively and structure merchant accounts around Canadian interchange categories.

What to Look for in Canadian-Built Retail Software

The clearest signal that retail software is genuinely built for Canada — not localised from a US product — is whether Canadian compliance features were part of the original design or added as an afterthought. A few questions reveal the difference quickly.

Does the platform calculate GST, HST, and PST correctly by province, including the Quebec QST system, without requiring manual tax code management at each location? Does the payroll or HR module handle provincial statutory holiday pay calculations natively, per-province, without manual overrides? Does the platform support Interac processing at the same level as Visa and Mastercard, not as an integration with a separate terminal? Is the full platform available in French, including all customer-facing interfaces, without English fallbacks?

These are not trick questions — they are compliance requirements for Canadian businesses. A vendor that cannot answer yes to all of them is selling you a US product with a CA flag on the pricing page.

Also ask about the support infrastructure. A Canadian-built product means Canadian support hours, staff who understand Canadian tax law, and a development team that tracks changes to CRA requirements, provincial employment standards, and Quebec language law as they evolve. US-based support teams are competent for US compliance questions. They are not the right resource when your GST filing does not match your software's tax summary.

• Native GST, HST, PST, and QST calculation by province of sale
• Provincial statutory holiday pay calculation without manual overrides
• Interac debit processing natively, not via separate terminal
• Full French-language interface for all customer-facing and staff-facing screens
• CAD as primary functional currency with proper CRA-compliant exchange rate handling
• Canadian-based support with knowledge of CRA, provincial employment standards, and Quebec language law