Blog

Choosing an ERP for a small or medium-sized business in Quebec: criteria and pitfalls

For organizations · By KTMA SOLUTIONS · Published · 9 min read

You are thinking of replacing a patchwork of spreadsheets and software with an integrated management system, and you want to know how to choose an ERP for a small or medium-sized business in Quebec without regretting it in two years. This article offers a selection grid, flags the pitfalls documented by independent sources and describes a migration and trial approach. Sources are cited as such: public bodies, a consulting firm, and vendors when it is their own documentation. This text is not legal or tax advice.

An ERP, for what need?

According to BDC (Business Development Bank of Canada), an ERP brings activities such as accounting, sales, inventory and operations together on a single platform, which improves the accuracy and consistency of data. BDC places the point at which it generally becomes essential at around CAD 10 million in revenue, specifying that "it is not a fixed threshold." In other words: the criterion is not size alone, but the manual workarounds, re-keying and paper processes that slow your work.

KPMG, in an article aimed at small and mid-sized businesses (SMEs and mid-sized companies, or ETIs), asks the first question before any product choice: is an ERP necessary given the size and the issues at stake, and is the priority scope defined? If the answer is vague, that is the work to do first.

Eight selection criteria

1. Functional scope

List the processes to be covered, in order of priority, and distinguish what is necessary from what is merely desirable. BDC advises examining your needs thoroughly before comparing, and KPMG describes a diagnostic with workshops to prioritize functional and non-functional needs. Spendesk, a vendor of expense management software, sums up the main criterion this way: if the ERP does not take the specifics of your business into account, walk away.

2. Data

What data goes in, from where, and in what condition? Spendesk points out the duplication trap: without a central system, updates are made in several tools and create inconsistencies. Plan who owns each piece of reference data (customers, suppliers, items, rates).

3. Integrations

An ERP fits into an existing environment: accounting, email, bank, industry-specific tools. KPMG distinguishes three approaches: a highly integrated solution, full coverage, or an ERP complemented by specialized solutions. For each integration, ask: who builds it, who maintains it, and what happens during an upgrade.

4. Off-the-shelf or customized

BDC is decisive: small and mid-sized businesses are better off looking for the off-the-shelf system that best meets their needs. An off-the-shelf solution often allows faster and less costly implementation. Conversely, according to BDC, customization can be expensive, each upgrade generally requires redoing the customizations, not doing so may mean losing technical support, and a heavily customized system can increase dependence on the vendor.

5. Law 25, language and taxes

Law 25. According to the Commission d'accès à l'information (CAI) of Quebec, a privacy impact assessment (évaluation des facteurs relatifs à la vie privée, EFVP) is required for a project to acquire, develop or overhaul an information system involving personal information. This assessment must be started at the very beginning of the project, and not only before launch. If the project involves disclosing personal information outside Quebec, or entrusting its collection, use, disclosure or retention to someone outside Quebec, the CAI requires a prior EFVP: the disclosure may take place only if the assessment shows that the information will be adequately protected, and it must be the subject of a written agreement. You need to examine where data is processed and stored, and not only the vendor's headquarters. When a business entrusts a mandate or service contract involving personal information to a service provider, the contract must be in writing and provide for the measures necessary to ensure the information's confidentiality, limit its use to carrying out the mandate and prevent its retention after the mandate expires. If the processing also involves a transfer outside Quebec, the requirements specific to that transfer apply in addition. See also our Law 25 checklist.

GST/HST and QST. For input tax credits (ITCs), consult the Canada Revenue Agency (CRA; Agence du revenu du Canada) Memorandum 8-4 on documentary requirements. It sets minimum requirements that vary with the total amount paid or payable: under CAD 30, CAD 30 to under CAD 150, and CAD 150 or more. From the first threshold, the document must identify the supplier, the date and the total amount, and make it possible to determine the amount of the credit. From CAD 30, the requirements also include the supplier's GST/HST registration number, the amount of tax (or a statement that tax is included, with the applicable rate) and the status of each supply where those statuses differ. From CAD 150, the purchaser's name, the payment terms and a description of each supply are added. The exact requirements depend on the circumstances and the rules in force. The CRA does not prescribe any particular form. In practical terms: ask the vendor to demonstrate that the invoices produced by the system carry this information, and have your accountant confirm the requirements that apply to your situation and those specific to the QST, which this article does not describe.

Language. This article does not address language requirements; if needed, consult a lawyer. In all cases, test the screens, documents and emails generated in the language of your customers and your staff yourself.

6. Deployment and hosting

Where does the system run, who updates it, who backs it up, and what happens to your access if the relationship ends? Spendesk notes that cloud-based ERPs, accessible through a browser, benefit from updates without downloads. Also ask how you get your data back, and in what format.

7. Total cost

BDC recommends comparing the total cost of each proposal: software licence, hardware, implementation and maintenance. Spendesk adds the cost of the integrator, of any planned development work and of maintenance, to be weighed against the quality of service. None of these sources gives a figure that applies to your case, and we are not making one up: request written quotations on the same scope, and add your own internal time, which is often forgotten.

8. The implementation partner

Spendesk warns against choosing an integrator by default, because the relationship will be a long one. KPMG points out that the main cause of failure it identifies is a project that is poorly organized on the human side, and that change management is at the heart of success. Ask for references you can actually reach, and involve your staff from the selection stage, as BDC advises.

The most expensive pitfalls

  • A scope without boundaries. Each "small addition" adds to the customization, whose life-cycle cost BDC points out.
  • An undersized or oversized system. KPMG flags both risks; Spendesk notes that a solution suited to a very small business can become a burden as users and suppliers multiply.
  • Mistaking the initial cost for the real cost. See above.
  • An unrealistic schedule. BDC advises allowing at least one year for an effective selection and implementation process.
  • Data carried over as is. See the next section.

Migration and pilot test

The documentation from the vendor Frappe (ERPNext) gives guidance that holds beyond its own product: move only the data needed to operate and produce reports from the switchover date, and keep the old system accessible for history rather than loading years of low-value transactions. It recommends cleaning the data first, then importing the reference data and opening balances.

Before launch, the same documentation advises confirming customer and supplier accounts, bank balances, and stock quantities and values, then checking fixed assets, taxes and the trial balance, and correcting the configuration before the first real transaction. It suggests having real users perform their most common tasks, with the same access they will have in production, and running a full cycle of sales, purchasing, inventory and accounting before launch. KPMG adds the selection logic: score the offers against weighted criteria, hold comparable presentations by all the candidates, then decide collectively.

Pilot test checklist

  • Written pilot scope (processes, teams, period)
  • Cleaned and representative data set
  • Real users, access identical to production
  • Full cycle run from end to end
  • Balances and taxes validated by your accountant
  • Success and abandonment criteria set in advance
  • Old system kept for history

Frequently asked questions

My business is small: do I need an ERP? BDC says the revenue threshold is not fixed. Ask yourself about manual workarounds and re-keying, and look at whether a specialized tool, linked to your accounting, is enough for now.

Open source or proprietary? The sources read do not settle the matter. The useful question is dependence: who can maintain the system, and in what format do you get your data back.

How much time should I allow? BDC advises at least one year for selection and implementation. Your project may differ; nothing in the sources read allows us to promise a shorter timeline.

Conclusion

A good ERP choice starts with a written scope and ends with a pilot that proves the processes, the data and the taxes hold up. In between: a total cost compared on a common basis, a solid partner, and an EFVP done at the right time. Have your legal and tax advisors validate the legal and tax aspects.

Going further with KTMA SOLUTIONS

Depending on your situation, you can discuss your project with KTMA SOLUTIONS, explore the migration and integration services, or look at the KTMA ERP presentation to check whether its features match your needs.

  • IT consulting: talk with KTMA SOLUTIONS about your ERP project, your needs and the options to consider.
  • Data migration and Systems integration: discover the services offered for your data projects and for connecting tools.
  • KTMA ERP: a system organized around mandates, consultants and their dated, versioned rates, with timesheets requiring dual approval (internal validation, then approval by an authorized person at the client, without access to the whole ERP back office) and invoicing based on approved time. KTMA ERP does not cover payroll or tax filings.
  • Talk about my project: describe your situation and contact KTMA SOLUTIONS.

Sources

Back to the blog · Blog RSS feed