Failure Patterns and Official Sources
Why ERP projects fail: common patterns and the official sources to check
The recurring reasons ERP projects overrun or disappoint, early warning signs, and the Canadian regulators and official portals that matter when buying ERP SaaS.
ERP projects rarely fail because the software cannot do the job. They fail, or deliver less than promised, because of decisions around the software: vague requirements, too much customisation, dirty data, too little internal time, unrealistic timelines, weak contracts, and compliance questions left until after go-live. The good news is that these patterns are predictable, so each one has an early warning sign and a countermeasure. This pillar guide summarises them and lists the official Canadian sources you need, then links to a detailed guide for each risk.
We describe failure patterns generically and do not name companies. Published surveys on ERP project overruns vary widely in method and sample, so we do not quote a failure rate; treat any single headline figure with caution.
The ten patterns
| Pattern | Early warning sign | Countermeasure | Detailed guide |
|---|---|---|---|
| Vague scope | Requirements described as "like today, but better" | Written process list with owners and acceptance criteria | Selection checklist |
| Customising everything | Many change requests in the first month | Adopt standard processes; approve customisations only with a business case | Overruns |
| Dirty data moved as-is | Duplicate customers and items found in test loads | Clean before you migrate; limit history | Data migration mistakes |
| No internal time | Key users miss workshops | Back-fill day jobs; name a project lead with authority | Overruns |
| Unrealistic timeline | Go-live fixed before scope is known | Plan backwards with contingency | Timelines |
| Budget for software only | No line for internal time, training or contingency | Five-year TCO with all lines | TCO |
| Weak contract | No renewal cap, unclear exit and export | Negotiate before signature | Contract exit and data export |
| Privacy left to the end | No one knows where data is hosted | Privacy review during selection; PIA in Quebec | PIPEDA and Law 25 |
| Records and tax overlooked | Old system switched off with no archive | Retention and access plan | CRA record-keeping |
| Counting on funding that is not there | Business case assumes a grant | Check program status; include only approved funding | Funding and tax treatment |
A further pattern specific to Canada is underestimating French-language and accessibility needs for Quebec staff and customers or for employees with disabilities; see accessibility and French-language requirements.
A short case pattern (composite, illustrative)
A composite example, not a real company: a 30-person distributor signs a one-year contract with a fixed go-live date three months away. Workshops show that pricing rules live in a spreadsheet nobody fully understands. The partner builds custom pricing logic. Data migration reveals thousands of duplicate items. The go-live date holds, but testing is squeezed, and the first month-end takes three weeks. The business pays for extra partner hours, overtime and a second data clean-up, and the first renewal arrives before the system is stable, with no cap on the increase. Each step was avoidable: a realistic timeline, a decision to simplify pricing rules, earlier data cleaning, and a renewal cap negotiated at signature.
Official sources for Canadian ERP buyers
| Topic | Official source | What to check there |
|---|---|---|
| GST/HST, ITCs, payroll deductions, records | Canada Revenue Agency | Digital economy rules, ITC requirements, keeping records, payroll guides |
| QST, Quebec payroll, Quebec records | Revenu Québec | QST registration, specified registration, source deductions, RL-1 |
| Federal privacy law (PIPEDA) | Office of the Privacy Commissioner of Canada | Accountability for third-party processing, breach reporting |
| Quebec privacy (Law 25) | Commission d'accès à l'information du Québec | Person in charge, privacy impact assessments, incidents |
| Statutes | Justice Laws Website and LégisQuébec | Income Tax Act, Excise Tax Act, PIPEDA; Quebec private-sector privacy act |
| French language in Quebec | Office québécois de la langue française | Software and workplace language rules |
| Federal accessibility | Accessibility Standards Canada | Standards for federally regulated organisations |
| Cyber security | Canadian Centre for Cyber Security | Cloud security guidance for SMBs |
| Exchange rates | Bank of Canada | Published rates for USD contracts |
| Programs for businesses | Innovation, Science and Economic Development Canada | Current status of federal programs |
Provincial privacy laws for the private sector also exist in Alberta and British Columbia, and some provinces have their own accessibility legislation, such as Ontario's AODA. Check the relevant provincial government site if you operate there.
When to bring in professionals
- A lawyer for the master subscription agreement, data-processing terms and statement of work when the contract value or data sensitivity is significant.
- Your accountant for the tax treatment of subscriptions, licences and implementation costs, and for sales-tax set-up.
- A privacy professional if you process sensitive personal information or operate in Quebec and need a privacy impact assessment.
- An independent project advisor if no one internally has led an ERP selection or implementation.
FAQ
What is the most common reason ERP projects go over budget?
There is no single reason, but scope growth, data problems and unpriced internal time recur in most post-mortems. Each is controllable if addressed early.
Is it better to delay go-live or go live with known issues?
If the issues affect invoicing, payroll, inventory accuracy or month-end close, delaying is usually cheaper. Minor issues with workarounds may be acceptable.
Can I recover costs from a vendor if the project fails?
Only to the extent the contract provides. That is why acceptance criteria, milestone payments and holdbacks matter. Seek legal advice if a dispute arises.
Are there official ERP standards in Canada?
No certification is required to sell ERP in Canada. The rules that apply are general ones: tax, privacy, records, language and accessibility.
Sources
- Canada Revenue Agency — tax, payroll and record-keeping rules
- Office of the Privacy Commissioner of Canada — PIPEDA guidance
- Commission d'accès à l'information du Québec — Law 25 obligations
- Innovation, Science and Economic Development Canada — federal business programs
