ERPNext Consultant in Canada

GST/HST, PST and QST in ERPNext: what to configure and test

ERPNext does not calculate Canadian sales tax through a built-in national engine. Instead, it gives you the tools to model it: tax templates on sales and purchases, item-level templates for exempt or zero-rated goods, tax categories for customers and suppliers, and tax rules that choose the right template based on the shipping province. For most Canadian businesses, that is a workable foundation, provided it is designed carefully.

In practice, I build a matrix with your accountant before configuring anything:

• Which provinces you ship to or provide services in, and which taxes apply in each.
• Which items or services have different treatment.
• Which customers are exempt, and what evidence you keep.
• Where PST applies to your own purchases and needs self-assessment.
• How QST is handled for Quebec customers, given its separate administration.

Each row becomes a test case for quotations, sales orders, invoices and credit notes. I also check that the reports your accountant needs for GST/HST and provincial returns can be produced from posted transactions, or plan a custom report if they cannot. Rules change, so please confirm current requirements with your accountant. For sales tax considerations that apply whichever platform you choose, see my ERP consultant in Canada page.

French documents, CAD and USD, and a US subsidiary

Two Canadian realities shape ERPNext design more than anywhere else: language and the border.

The Frappe framework includes French translations, and each user can work in their preferred language, so a Quebec warehouse team and a Toronto finance team can use the same system. Documents need more thought. Invoices, quotations, packing slips and statements sent to Quebec customers often need French or bilingual versions, which means print formats that pull French item descriptions and terms from master data. I plan those fields before migration, and suggest you check language obligations for your business with your advisors.

On currency, CAD is usually the base, with USD price lists for American customers, USD bank accounts and US suppliers invoicing in dollars. Each ERPNext document keeps the rate used at the time, and realized and unrealized differences come through payment entries and period revaluation. I test these with real examples, including partial payments and credit notes.

Many Canadian companies also own a US entity. Both can sit side by side in a single ERPNext installation, keeping separate books, currencies and tax setups, with inter-company invoices linking them and consolidated reports for management. I design shared and separate masters with your controller, and test the multi-currency and multi-company reporting before go-live.

Leaving Sage 50 or QuickBooks, and keeping payroll separate

Sage 50 and QuickBooks are the usual starting points for Canadian ERPNext projects. Both handle bookkeeping and sales tax reasonably well; the strain comes from stock spread across locations, production records, job costing and approvals that live in spreadsheets around them.

The migration plan covers:

• Mapping the chart of accounts, often simplifying it with cost centers and accounting dimensions.
• Moving customers and vendors with their province, tax registration details and payment terms, because tax rules depend on them.
• Loading items with units, valuation method and opening stock by warehouse.
• Bringing open receivables and payables across at a period end aligned with your sales tax filing.
• Reconciling trial balance, aging reports and inventory value with your accountant after every trial load.

Payroll is a separate decision. Frappe HR does not, as a standard feature, produce T4 slips, Records of Employment or CRA remittances for Canadian payroll, so I recommend keeping a specialist Canadian payroll product. Summarized payroll entries then flow into ERPNext against the right province, department and job, without anyone re-keying wages. Frappe HR can still help with leave and attendance where useful. The ERP data migration service explains the method in more detail.

Hosting, data location and the Canadian ERPNext market

Some Canadian businesses have customers or contracts that expect data to stay in Canada, and privacy obligations apply to the personal information you hold. Because ERPNext is open source, location is your decision. Ask Frappe Cloud whether a Canadian hosting location is currently available if that matters; otherwise a Canadian region with a major cloud provider, run by your IT team or a managed service firm, is the usual route, with that party then responsible for security and upgrades.

The ERPNext implementer market in Canada is small. You may work with an independent Frappe developer, a firm in another country or a mixed team. That can work well, but only when requirements are written down, custom apps are documented and someone on your side checks the work against the business need.

That is the role I take. As an independent consultant, I document what the business needs, judge which gaps genuinely justify custom work, help you pick a developer, check customizations for upgrade risk and lead UAT with your finance, warehouse and production teams. I work remotely, with live sessions in the overlap with your working day; Eastern and Atlantic time are easiest, while Pacific teams usually meet early in their morning. Industry context is on the manufacturing and food and beverage pages, and the ERPNext manufacturing page covers production features.

Canadian cases where ERPNext is the wrong choice

ERPNext is not the answer for every Canadian business. I would look elsewhere, or test very carefully, when:

• You sell into many provinces with complex taxability: maintaining the rules by hand may be more effort than a platform with a supported Canadian tax engine.
• French must be flawless everywhere from day one: translations and print formats can be improved, but if every screen, report and document must meet strict language standards immediately, test this hard.
• You expect payroll inside the ERP: Canadian payroll belongs in a specialist product.
• Your accountant works in Sage or QuickBooks every day: if your bookkeeping relies on outside advisors using familiar tools, factor that change cost in.
• There is no technical owner: without someone to manage upgrades and fixes, an open-source system becomes fragile.

None of these rules ERPNext out automatically, but each one should be weighed honestly. For bilingual manufacturers, comparing Odoo with ERPNext is often the useful next read; service-led companies may prefer to look at Zoho alongside ERPNext. My main ERPNext consulting page describes the platform, and the Canada hub sets out how remote projects with Canadian teams are organized.