ERP Implementation Consultant, Canada

What tends to go wrong in Canadian ERP projects

Canadian implementations share the usual ERP risks, but a few problems appear more often because of how tax, currency and language interact with the build:

• Tax set up from a template. A partner configures sales tax from a standard Canadian template, but nobody checks it against how your business actually sells, so interprovincial or exempt cases fail in testing or, worse, after go-live.
• French documents left late. Bilingual invoice and statement templates are treated as cosmetic and built in the final weeks, then need rework when Quebec customers or staff review them.
• Currency handled inconsistently. USD bank accounts, supplier balances and price lists are migrated at different rates, so revaluation produces confusing results in the first month.
• Partner outside your time zone. A cross-border partner works hours that overlap poorly with yours, and questions wait a day for answers.
• No single client-side owner. Questions drift from the controller to operations to the owner and back, and stay open.

A client-side lead does not make these risks disappear. The role puts each one on a list with an owner and a date, and checks progress every week. If your project is already showing several of these signs, the failed ERP implementation page explains how a reset can work.

How I oversee the implementation partner

Partners work best with a client that makes decisions on time and tests properly. My oversight is designed to give them exactly that, while protecting your interests.

Each week I run a working session with the partner's project manager to review progress, blockers and decisions due. I keep the decision log: what was decided, why and who approved it. Change requests come to me with the partner's estimate; I check whether the need is genuinely new or a gap in the agreed design, then present it to your sponsor with the cost and timeline impact.

I read every design document alongside the people who run the process. For Canadian companies, the finance designs deserve particular attention. Tax codes and groups, account mappings for GST/HST and provincial taxes, the treatment of input tax credits and the structure of USD accounts are reviewed with your controller and accountant before they are configured. Operational designs, such as warehouse flows, approval routes and job costing, get the same treatment with their owners.

If the partner sits in another time zone, I agree response times and a regular overlap slot in the project plan, so questions do not stall. The partner keeps responsibility for configuration and technical delivery; your business keeps responsibility for deciding what is acceptable. The general model is explained under ERP implementation.

Data migration from QuickBooks, Sage and Acomba

Canadian migrations commonly start from QuickBooks Online or Desktop, Sage 50 or a larger Sage product, and in Quebec sometimes Acomba, often alongside spreadsheets for inventory or job costing. The partner's import tools are only as good as the data that goes into them, so preparation matters more than the import itself.

First, finance decides how much history to move. Many companies bring opening balances and open items and keep the old system available for lookups, while others need detailed history for comparison reporting. Your accountant should agree the approach, including how long older records must remain accessible.

Then every test import is compared with the source:

• Trial balance by entity at the cutover point.
• Open receivables and payables by document, with the sales tax on each still traceable.
• USD customer, supplier and bank balances, converted at the agreed rate so revaluation starts cleanly.
• Stock quantities and values by warehouse.
• Customer records with tax exemption details and language preference for documents.
• Supplier records with banking details for EFT payments.

Where account numbers carried department or location codes, I map them to proper dimensions with finance so year-over-year reports still work. See ERP data migration and migrating from QuickBooks for the general method.

Testing and planning a Canadian cutover

UAT has to prove the transactions that matter to your controller and your customers. I write scripts from your own data and business users run them: a sale to another province, a Quebec invoice printed in French, an exempt customer, a USD purchase with duty and freight on landed cost, an EFT supplier payment file accepted by your bank, a payroll journal posted by department, and a month-end close with USD revaluation.

The cutover date is then planned around Canadian reporting cycles:

• Sales tax periods. Switching at the start of a GST/HST reporting period avoids preparing a return from two systems. Quebec businesses also file QST separately, so check both cycles with your accountant.
• Fiscal year-end. Opening a fresh fiscal year on the new platform makes comparatives easier, but year-end and audit work fall on the same finance staff needed for cutover.
• Payroll. If payroll stays with its provider, only the journal integration changes. If payroll itself moves mid-year, year-to-date balances and year-end slips come into scope, so involve the provider and your advisor early.
• Bank formats. Payment files should be confirmed with each bank before go-live, not on the first payment run.

Approval to go live needs evidence: UAT signed by process owners, balances that reconcile, people who have practiced their tasks and a fallback if something breaks. See ERP testing and UAT and go-live support.

Hypercare and remote support across Canada

Launch day is when Canadian users start testing the system with real customers, real suppliers and real money, and the questions arrive quickly. For the hypercare period I chair a short daily call with partner consultants and super users from finance, sales and the warehouse. Every reported problem is classified: a defect for the partner, a training point for the business, or an improvement that waits for a later phase. Nothing is fixed informally without being logged.

A few signals tell me whether the system is settling. Bank, receivables, payables and inventory reconcile at the first period end. USD balances revalue as finance expects. And the first sales tax filing prepared from the new ledger agrees with the underlying transactions when your accountant reviews it. Where any of these fails, the fix is estimated and scheduled through the stabilization backlog rather than patched under pressure.

Hypercare is run remotely like the rest of the project. Daily calls sit in the window that suits your head office, which is straightforward for Eastern and Atlantic teams and needs a little more planning for Alberta or British Columbia. Recorded walkthroughs help staff at branches and warehouses, and a visit around go-live can be arranged where it would genuinely help.

Still choosing a platform or partner? The Canadian ERP selection page describes that stage. Related reading: ERP consulting in Canada, freelance engagement options and the Canada hub.