ERP Development Company in Vancouver

More than most implementers expect, because British Columbia is not an HST province. BC charges a 7 percent Provincial Sales Tax that applies when taxable goods, software or services are acquired in BC or brought into BC for use here, and it operates alongside the 5 percent federal GST rather than being blended into it. Those two taxes behave differently in your general ledger. GST is a value-added tax where registrants recover input tax credits on business purchases. PST is a retail sales tax with no equivalent recovery mechanism, so PST paid on a business input is generally a cost that has to land in expense or in inventory value rather than in a recoverable tax account. That single distinction breaks a surprising number of chart-of-account designs copied from an Ontario or American template. Then there is self-assessment: goods purchased outside BC and brought in for use in BC can create a PST liability the vendor never charged, which the ERP has to detect and accrue rather than leaving to a spreadsheet at year end. Add Ontario HST at 13 percent, an Atlantic rate that stopped being uniform when Nova Scotia dropped from 15 to 14 percent on April 1, 2025 while New Brunswick, Newfoundland and Labrador and Prince Edward Island stayed at 15, Quebec GST plus QST, and Alberta GST only, and the tax determination matrix becomes a design deliverable in its own right rather than something the finance team reverse-engineers at quarter end.

The Canada Border Services Agency's CARM system became the official system of record for assessing and collecting duties and taxes on commercial imports on October 21, 2024, and it shifted responsibilities that importers had comfortably delegated to their customs broker for decades. Importers now register in the CARM Client Portal under their own business number, post their own financial security to keep Release Prior to Payment privileges rather than relying on the broker's bond, and are accountable for their own commercial accounting declarations and corrections. For an ERP that has three consequences. First, the customs data model has to be real: tariff classification, country of origin, valuation method and applicable trade agreement need to live on the item master rather than in a broker's system you cannot query. Second, landed cost has to reconcile against the actual CARM statement of account, which means the ERP needs to consume that data rather than accept whatever the broker invoices. Third, the accounting calendar changes, because duties and GST on imports now settle against a CBSA billing cycle the finance team has to reconcile monthly. For a port city where a large share of businesses import, this is not an edge case.

In Canadian dollars, with the caveat that ERP ranges are wider than any other category because scope varies by an order of magnitude. A mid-market implementation on NetSuite, Acumatica, Odoo or Business Central for a single-entity distributor or light manufacturer, covering finance, inventory, purchasing, sales, tax determination and two or three integrations, typically runs CAD 150,000 to 450,000 in services. A multi-entity or multi-site implementation on Dynamics 365 Finance and Supply Chain or a mid-tier SAP footprint, with manufacturing execution, warehouse management, EDI, payroll integration and a real migration, typically runs CAD 450,000 to 1,500,000. A full SAP S/4HANA programme for a manufacturer or resource company with foreign subsidiaries runs well past that and is governed more by programme management than by engineering. Custom module work is quoted separately. Licences and cloud hosting are vendor costs on top. Two things reliably blow the number: master data that turns out to be worse than anyone admitted, and a fit-gap register that keeps growing after build starts. We price the data assessment separately and up front so both are visible early. All proposals are fixed fee against a signed statement of work.

A mid-market single-entity implementation typically runs nine to fourteen months from kickoff to a stable close after go-live. A multi-site or multi-entity programme runs eighteen to thirty months. The phases we work to are consistent. Discovery and fit-gap takes six to ten weeks and produces the process maps, the fit-gap register, the tax determination matrix and the data readiness report. Design and configuration takes twelve to twenty weeks and covers chart of accounts, costing method, warehouse and production structure, approval hierarchies and security roles. Integration and custom development runs in parallel and is usually the long pole. Data migration runs as a repeated cycle rather than a single event, with at least two full mock conversions, each reconciled and signed off. User acceptance testing takes six to ten weeks and must be run by the people who will actually use the system, not by a project team proxy, which is the most common cause of a rejected go-live. Cutover is a rehearsed weekend with a written runbook, a rollback decision point and a defined command structure. Hypercare runs four to eight weeks with daily triage before the system transitions to steady-state support.

Yes, and in most builds we integrate a specialist payroll engine rather than trying to compute Canadian payroll inside the ERP, because the compliance surface changes every year and a general-purpose ERP module is the wrong place to carry that risk. What the ERP does own is the cost side: labour distribution to jobs, work orders and cost centres, accruals, and the general ledger interface. The BC-specific items we design for are the Employer Health Tax, an annual tax on BC remuneration paid to employees that has applied since January 1, 2019 and needs accurate BC-only remuneration totals separated from remuneration paid in other provinces, and WorkSafeBC premiums, which are assessed by classification unit so the ERP has to carry the right classification against each labour category rather than applying one blanket rate. On top of that sit federal payroll obligations including source deductions, T4 reporting and Records of Employment, and the BC Employment Standards rules on overtime, statutory holiday pay and averaging agreements that drive how hours are captured on the shop floor. For unionised operations we build the collective agreement rules into time capture rather than leaving them to a supervisor's judgement.

We start from the opposite end of the question: which parts of an ERP programme actually fail when nobody is in the building. There are four, and we travel for all of them. Shop-floor process observation is first, because what an operator does at a station is never what the process document says, and you only catch the difference by standing there. Warehouse layout and scanning walkthroughs are second, since bin logic, pick paths and label placement are physical decisions that a video call flattens. User acceptance testing facilitation is third, and it is the phase most often faked by a project team clicking through scripts on behalf of the people who will actually use the system, which is the single most common cause of a rejected go-live. The cutover weekend is fourth. Everything else, meaning configuration, fit-gap sessions, integration development, conversion runs and steering governance, runs from Edmonton and Chandigarh without loss, and Codazz has no Vancouver office to pretend otherwise. Contracts are Canadian, invoicing is in Canadian dollars, and where residency is a requirement the system deploys into Canadian cloud regions, with ca-west-1 in Calgary the closest to Vancouver.