ERP Rescue Consultant, Canada

Symptoms of a Canadian ERP project in trouble

Every implementation hits obstacles. A rescue is worth considering when the obstacles stop being resolved and start repeating. In Canadian projects, these symptoms are worth taking seriously:

• UAT keeps failing on sales tax for particular provinces, and each fix seems to break another scenario.
• French documents for Quebec customers or staff were scoped late and are now holding up go-live.
• A partner based in another country is hard to reach during your working day, and decisions wait for the next scheduled call.
• Data from QuickBooks, Sage or Acomba has been loaded more than once, and opening balances still do not agree.
• The system is live, but month-end now takes much longer and USD balances are revalued by hand.
• Change orders keep arriving while the original scope remains unfinished.

Several of these together usually point to deeper causes: requirements that never captured provincial and cross-border detail, a timetable set before scope was understood, or unclear ownership of decisions on the client side. More hours on the same plan rarely change the outcome. A neutral assessment first, along the lines set out in fixing a failed ERP rollout, shows which problems are real and which are symptoms.

Triage: one honest list of what works and what does not

When a project is in difficulty, everyone has a list: the business has complaints, the partner has open tickets and change orders, finance has reconciliation problems. These lists overlap, contradict each other and are rarely ranked by business impact. Triage replaces them with one.

I start with separate conversations: your sponsor, the internal project lead, process owners, key users and the partner's team. Then I look at the system directly, running the end-to-end processes that matter most, from a sale to a customer in another province through to cash received, or from a purchase in US dollars through to payment. Data migration status, integrations and the test record are reviewed alongside.

Every open item goes into one of four groups:

• Blocks operations: must be fixed before the business can rely on the system.
• Needed soon: important, but can follow a first stable release.
• No longer needed: requested once, but no longer worth the cost.
• Disputed: client and partner disagree on whether it was in scope.

The resulting list, with the reasons behind each classification, becomes the basis for every later decision. Your leadership and the partner receive the same version, written in neutral terms so it can be accepted rather than argued over. If you need only this outside view, an independent ERP second opinion covers it.

Agreements, change orders and the cross-border dimension

Canadian businesses often contract with a partner incorporated elsewhere, or with a Canadian firm that subcontracts part of the work to a team abroad. That makes the paperwork worth reading carefully when a project goes wrong. I am not a lawyer, and nothing here is legal advice; the goal is to give your lawyer a clean, factual picture.

I put together a timeline of the engagement: what each phase promised, when it was billed, which change orders moved it and where it stands today. Alongside the timeline, I list points your lawyer may want to weigh:

• which jurisdiction's law governs the agreement and where disputes would be heard;
• the currency of invoices and who bears exchange differences;
• how acceptance is defined and whether anything was formally accepted;
• subcontracting terms and who is accountable for the work of a subcontracted team;
• ownership of configuration, scripts and documentation;
• transition assistance if the engagement ends.

The preferred outcome is a commercial reset rather than a formal dispute. A clear chronology helps, because both sides can discuss the same facts instead of competing recollections. Where a new partner is needed, my ERP selection work in Canada provides a structured way to compare replacements.

Keeping filings and month-end on track

A troubled system must not make the business late with the CRA, Revenu Québec, payroll remittances or lender reporting. Before redesign begins, I work with your controller and accountant to agree interim arrangements and write them down.

• Sales tax returns. If the system's tax reports are not yet reliable, your accountant decides how returns will be prepared and checked for the interim period, for example by reconciling tax collected to invoice listings. Any adjustments to earlier filings are for your accountant to handle.
• Payroll. Your payroll provider continues to calculate pay and remittances. My concern is that the journals still post correctly, so the balance sheet remains reliable.
• Month-end. A stopgap close routine, owned by your controller, lists the workarounds, checks and revaluation entries required while repairs continue.
• Customer-facing documents. Invoices and statements are checked first, including French versions for Quebec customers, which your team or a local partner reviews for wording.

Data repair runs alongside, in a planned sequence, each fix followed by a reconciliation. Where earlier loads are badly compromised, a controlled reload may be cleaner than repeated corrections. The ERP data migration page describes how reloads are planned.

Choosing the way forward

The route out of a troubled project is decided by a handful of questions, each answered with evidence from the triage rather than with frustration. I put them to leadership in a short table:

A platform change only goes on the table when the first question gets a clear no. Whichever route is chosen, I can stay involved to run the recovery: one integrated plan, a risk log reviewed with both sides, real change control and release criteria fixed before anyone announces a date. The general approach is on the ERP recovery page.

Delivery is remote, with live sessions aimed at your head office's day and recorded walkthroughs for staff in other provinces. The engagement runs in English. Site days can be arranged. If your system is live and broadly working, the Canadian ERP audit fits better. See also ERP consulting in Canada and the Canada hub.