esköre™

InsightsERP Systems16 min readNovember 15, 2026

Odoo Canadian Payroll Setup: A Practical Guide for 2026

Odoo has no native Canadian payroll, so setup starts with choosing a route. This guide compares the three options and covers CPP, EI, tax, Quebec, testing and year-end for 2026.

ERP Systems at Eskore
Photo by Unsplash on Unsplash

Odoo does not ship a Canadian payroll localization, so an Odoo Canadian payroll setup starts with choosing a route, not with a settings screen. When we checked, Odoo's payroll localizations page for version 20.0 listed the United States and did not list Canada. Odoo's Canada fiscal localization, documented for version 18.0, covers taxes, fiscal positions, reporting and a chart of accounts, but not payroll. That is a dated position, so check the live Odoo editions and payroll localization pages before you plan around it. This guide covers the three routes that work for Canadian employers, a setup checklist, testing, year-end and cost, with sections for Quebec and for US companies that have Canadian staff.

Does Odoo have Canadian payroll?

Odoo is strong on the accounting side for Canadian businesses. Taxes, reporting and a predefined chart of accounts are covered. What is missing is statutory payroll: calculating CPP, EI and income tax from each employee's TD1 claims, then producing T4 slips and Records of Employment (ROEs).

The real question is which route will keep those statutory rules correct from one January to the next. An app in the Odoo App Store does not prove Canadian coverage. Read each listing for the statutory items it covers, and check the Odoo version and edition it needs.

Decide three things first: which route you take, who owns the rate tables, and where the payroll data lives. The screens come after that.

Three routes to Canadian payroll in Odoo

Three routes work for a Canadian employer that runs Odoo: a third-party Canadian payroll module installed in Odoo, a dedicated Canadian payroll provider synced to Odoo, and a custom payroll build. They differ on statutory coverage, who updates rates each January, audit trail, year-end forms, licence cost and who fixes a calculation when it breaks.

In short:

  • Third-party module if your pay rules are standard, you want payroll inside Odoo, and you trust one vendor to keep rates current.
  • Hybrid if you want statutory certainty from a provider whose core work is Canadian payroll, and you accept running two systems that talk to each other.
  • Custom build if your pay rules are unusual enough that no module fits, and you have an internal owner for the annual maintenance.

Native Odoo payroll is not available for Canada

Odoo's strengths still matter for payroll. Accounting, invoicing, purchasing and inventory are where payroll costs land and get reported. Employee records in the HR app are a sensible starting point, and payroll journal entries can be posted to the ledger.

What Odoo does not do natively for Canada is calculate CPP, CPP2, EI or federal and provincial income tax, or produce T4, T4A or ROE outputs. If a partner says Odoo “handles payroll”, ask which Canadian statutory calculations it performs and where they are configured.

Third-party modules: what to check before you buy

Third-party modules are the fastest start, and the easiest purchase to make on the strength of a listing. Check these before you commit:

  • Odoo version. Confirm the module supports the version you run or plan to run (19 or 20 in 2026). Listings for older versions are not a guide to current rules.
  • Edition requirement. Listings disagree. One Odoo 19 Canada payroll listing says it requires Enterprise. Another vendor says its module runs on Community edition. Check Odoo's editions comparison page on the day you buy, and get the vendor to confirm the edition in writing.
  • Last update date. A module that has not been tested against a new year's CRA figures is a risk. Ask when it was last tested.
  • Coverage. Confirm it covers CPP, CPP2, EI, TD1 federal and provincial tax, T4, T4A, ROE and WCB, and which provinces it handles, including Quebec.
  • Rate updates. Many listings say rates update automatically. That is a vendor claim. Get in writing what triggers the update, who tests it and how far ahead of January it lands.
  • Price. Check the currency and whether the fee is one-time or recurring. Then add any Enterprise licence the module needs.

Hybrid: a Canadian payroll provider synced to Odoo

In the hybrid route, payroll runs in a dedicated Canadian provider. Employee data and summary journal entries flow into Odoo through REST APIs or a connector, so finance and operations work from the same numbers as inventory, invoicing and purchasing.

This suits businesses that want statutory certainty without owning the rules. The provider handles CPP, EI, tax and year-end forms. Odoo handles the ledger and operations.

The cost is complexity. You now have two systems, two sets of users and a sync that can fail. Before you commit, ask what syncs (employee master data, pay runs, summary entries or individual lines), how often, what happens when a sync fails, and how the two systems are reconciled each period.

Custom build inside or alongside Odoo

A custom build makes sense when pay rules are unusual: shift premiums tied to scheduled hours, several pay schemes running side by side, union rules, or commission linked to invoicing or inventory. A module built for standard salary and hourly pay will struggle with these.

The build cost is front-loaded. The ongoing cost is statutory maintenance. CPP, EI and tax parameters change, and someone has to test and deploy them every year. A custom build needs a named owner for the rate tables, a test cycle before January and a rollback plan. Without those three things, a custom payroll becomes a liability.

Eskore works from a written scope, a fixed price and a launch date agreed before work starts, and you own the code and the accounts. Our custom software development team can scope the build, and our ERP systems work can show how it sits alongside Odoo's ledger. For more on keeping a fixed-price build predictable, read our guide to fixed-price custom software development.

What a Canadian payroll setup must cover

Whichever route you choose, the setup has to handle these items. Each one matters to the operator, not only the accountant.

  • CPP. Employee and employer contributions on earnings above the basic exemption and up to the year's maximum. For 2026, the CRA figures are a year's maximum pensionable earnings (YMPE) of $74,600, a basic exemption of $3,500 and a rate of 5.95%, for a maximum of $4,230.45 each side. A wrong CPP deduction shows on the pay stub and comes back later as a CRA adjustment.
  • CPP2. A second tier on earnings between the YMPE and $85,000, at 4%, with a maximum of $416 each side for 2026. Payroll that handles the first tier but not CPP2 under-deducts for higher earners.
  • EI. For 2026, maximum insurable earnings are $68,900, at an employee rate of 1.63% outside Quebec. The employer pays 1.4 times the employee premium. Older articles and calculators still show last year's figures, so check every number against the CRA's 2026 tables before you configure anything.
  • Federal and provincial income tax. Withholding depends on each employee's TD1 claims. Missing or outdated claim data is a common cause of wrong deductions, and it is the first thing to check when an employee questions their net pay.
  • WCB. Workers' compensation premiums are set by province, and the rules vary by province and industry. In Ontario that is the WSIB. Many payroll setups leave this cost out, which understates what an employee costs you.
  • T4 and T4A slips. T4s report each employee's employment income and deductions for the year. T4As cover payments that are not employment income but still need reporting, such as some pensions and retiring allowances.
  • Records of Employment. An ROE is issued to the employee and to Service Canada when employment is interrupted, such as a layoff. Wrong insurable earnings or dates delay the employee's EI claim, and that becomes your problem quickly.
  • Remittances. Deductions and employer contributions go to the CRA under your payroll account, on a schedule set by how much you withhold. Late or mismatched remittances carry penalties and interest.

The CRA's general information for the January payroll deduction tables is the reference for the current year.

Quebec payroll in Odoo: QPP, QPIP and the Quebec EI rate

Quebec is not a variation on the rest-of-Canada setup. Configure it as its own case.

Quebec employees are covered by the Quebec Pension Plan (QPP) in place of CPP. Retraite Québec administers QPP. Quebec also runs its own parental insurance plan, QPIP, and provincial income tax is administered by Revenu Québec.

Quebec employees still have EI premiums deducted, but at a lower rate than the rest of Canada, because QPIP covers parental benefits. Do not apply the rest-of-Canada EI rate to a Quebec employee. Quebec employers also generally issue RL-1 slips alongside T4s.

Confirm all Quebec rates, maximums and filing requirements with Revenu Québec and CRA guidance before you use them. The CRA's Quebec payroll deduction tables is the starting point. This guide does not quote Quebec figures, because they must be checked against the current year.

When you assess a module or provider, check three things: whether Quebec has its own rate tables, whether QPP and QPIP are handled separately, and whether the reduced EI rate applies to Quebec staff. Test one Quebec employee on their own before go-live.

Cross-border payroll: US head office, Canadian staff

If your head office is in the US, the question changes. Odoo's 20.0 documentation lists a United States payroll localization, so a US employer should assess that for its US staff. A Canadian setup is not the answer for US employees.

Canadian staff on a US company's books are a separate matter. Employees who work in Canada are generally subject to Canadian statutory deductions, wherever the employer is based. A company headquartered in New York, Austin, Raleigh or Denver with a Toronto-based salesperson still needs CPP, EI and TD1 handling for that person. Confirm the position with your accountant or the CRA before you set up.

Take a hypothetical 80-person company headquartered in Denver with a team in Toronto. Its payroll runs two statutory frameworks: US withholding, Social Security and Medicare, and state rules for US staff, plus CPP, EI and provincial tax for the Canadian staff. Both should post to one ledger with clear accounts and currency handling. Forcing one configuration to do both usually produces errors on both sides.

Eskore has offices in Toronto, Thornhill, London and New York, so one scoping call can cover both sides of a cross-border payroll. Choose the route for each country separately, then agree one written scope.

Odoo Canadian payroll setup checklist

Collect this information before you configure anything. Missing data is the most common reason a first pay run goes wrong.

  • Province of employment for each employee, including anyone who works across a provincial line
  • Pay frequency for each employee (weekly, biweekly, semi-monthly or monthly)
  • TD1 federal and provincial claim amounts for each employee, with the date of the latest version
  • Employment contract details: start date, job title, salary or hourly rate, and benefits
  • Salary types in use: salary, hourly, overtime, commission, taxable benefits, vacation pay
  • Payroll expense accounts for wages, employer CPP, employer EI and any WCB premium
  • Payroll liability accounts for CPP, EI, income tax and any other withholding
  • CRA payroll program account number and remittance frequency
  • Employee SIN, address and T4 data, with access limited to the people who need it
  • ROE data for each employee: reason for interruption, dates and insurable earnings
  • WCB account number and industry classification, where applicable
  • Year-to-date gross, CPP, CPP2, EI and tax for each employee, if you are switching mid-year

Check the TD1 fields first. Missing or outdated claim data is the usual reason deductions come out wrong.

Odoo payroll rates and salary rules, step by step

The exact screens and field names depend on the module or custom build you choose. The sequence below is a general pattern used in most payroll systems, not a vendor-specific manual. Use it to check any module's setup, and ask the provider how their version maps to each step.

  1. Load yearly rate tables. Enter the 2026 CPP, CPP2, EI and tax parameters, with separate tables for each province. Check each figure against the CRA's current tables.
  2. Set up salary rule categories. Group rules into basic pay, gross, statutory deductions, employer contributions and net pay. The categories control how each line flows to the payslip and the ledger.
  3. Define salary rules and assign them to salary structures. Each rule calculates one item, such as the employee CPP contribution. Assign the rules to the structure for each pay type.
  4. Link employee contracts to structures. Each contract should point to the right structure, pay frequency and province.
  5. Generate test payslips. Run a sample employee through each pay type, including one with overtime, one with a TD1 change and one in Quebec.
  6. Run the pay batch. Run a full pay period only after the tests match what you expect.

A formula that is slightly wrong, such as a rounding error or a missed threshold, can look correct on one payslip and fail across a full run. That is why the test step matters.

Posting payroll to accounting and CRA remittances

A payroll run should post to the ledger in a way that matches the cash leaving the bank. Using symbols rather than figures, a posted run does the following:

  • Debit wages expense for gross pay (G).
  • Debit employer CPP expense and employer EI expense for the employer's share.
  • Credit net pay payable for the amount owed to employees.
  • Credit CPP payable for employee and employer contributions combined.
  • Credit EI payable for employee and employer premiums combined.
  • Credit income tax payable for the tax withheld.

When you remit to the CRA, debit each payable (CPP, EI and income tax) and credit the bank. When employees are paid, debit net pay payable and credit the bank. If the three payable accounts reconcile to your remittance confirmations at the end of the period, the mapping works.

If the business also uses QuickBooks or Xero alongside Odoo, decide early which system is the book of record for payroll liabilities. Posting the same payroll in two places is one of the most common and expensive mistakes in a mixed setup. Account mapping is part of our ERP systems work.

Testing before go-live: parallel runs and the PDOC

Before the first live payroll, run one or two pay periods in parallel with your current process. For each employee, compare gross pay, each deduction and net pay. Explain every difference before go-live.

Then check the deductions against the CRA's Payroll Deductions Online Calculator (PDOC) for 2026. Enter each sample employee's pay and TD1 details, and compare the PDOC result with what your system calculates. The PDOC is the CRA's own tool, so it is the simplest independent check you can run. Keep a record of the comparison. It is your evidence if the CRA asks how you calculated deductions.

Include these cases:

  • at least one employee in Quebec, tested on their own
  • an employee near the CPP and EI maximums
  • an employee with a TD1 change partway through the year
  • an ROE scenario, from a simulated termination through to the form
  • a rate change, if one lands during testing

Finish with a named sign-off. One person, usually the finance lead, confirms in writing that the parallel run matched, that the PDOC comparison was checked and that the owner accepts the result. Go live only after that sign-off, not because the software says it is ready.

Switching payroll mid-year without double-counting CPP and EI

Switching payroll partway through the year is where avoidable errors happen. CPP, CPP2 and EI stop at annual maximums. If the new system does not know what has already been deducted this year, it will deduct from zero, over-collect, and produce a T4 that does not match what the CRA has on file.

Import each employee's year-to-date figures before the first live run in the new system: gross pay, CPP, CPP2, EI and income tax withheld. These become opening balances, so the system respects the maximums from the first pay period.

Reconcile the imported totals against the previous provider's year-to-date reports and against the remittances already made to the CRA. Cut over on a pay period boundary, not in the middle of one. Confirm the approach with your accountant or provider before cutover, and ask them to check the imported totals against the last reports from the old system.

Year-end: T4, T4A, ROE and reconciliation

Year-end produces T4 slips for each employee and T4A slips for payments that need reporting outside employment income. T4 slips are due to employees by the end of February, so start the reconciliation in January.

Records of Employment are not a year-end task. They are issued each time employment is interrupted. Year-end is the point to check that every ROE issued during the year matches the payroll data.

Reconcile these items before you file:

  • Remittances to payroll totals. Total CPP, EI and tax remitted should match the totals the payroll runs produced for the year.
  • T4 box totals to the general ledger. Employment income, CPP, EI and tax on the T4s should match the wage and liability accounts.
  • ROE dates and earnings. Each ROE should match the employee's last day and insurable earnings.
  • Maximums. No employee should exceed the CPP, CPP2 or EI maximums for the year.
  • Employee data. SINs, addresses and TD1 details should be current.

Check the export format from your module or provider against the CRA's current electronic filing requirements, and test a file before you rely on it.

The January rate update

CPP, EI and tax parameters change most years, and the new figures apply to the first pay runs of the year. The update is recurring, and it needs an owner.

Name the owner before the update arrives: the vendor, an internal administrator or a partner. That person needs a process for loading new rates, testing them against last year's pay periods and confirming the result before January. Build test runs with sample employees on either side of each threshold: the YMPE, the CPP2 ceiling and the EI maximum.

Treat any vendor claim of automatic updates as a claim until it is in writing. Ask what is covered (federal and each province, including Quebec), when the update lands, how you are notified, and what happens if a parameter changes mid-year. An update that arrives on 2 January is one you cannot test in time.

What drives the cost of an Odoo Canadian payroll setup

Cost depends on the route you choose and the complexity of your business. These are the drivers to ask about:

  • Odoo edition, including whether an Enterprise licence is required for the module you choose
  • module licence, and whether it is one-time or recurring
  • number of provinces, and whether Quebec is included
  • pay types: salary, hourly, overtime, commission, benefits and vacation
  • accounting integrations, including QuickBooks, Xero and the Odoo ledger mapping
  • data migration: employee records, TD1 data and year-to-date balances
  • testing time, including parallel runs and the PDOC comparison
  • year-end support for T4, T4A and ROE checks
  • the annual rate update, and who owns it
  • WCB or union rules, if they apply

Eskore does not quote payroll work from a generic range, because the total depends on scope. We work from a written scope, a fixed price and a launch date agreed before work starts, so the total is visible before the build begins.

When to bring in a partner, and what to ask

Consider a partner if any of these apply:

  • you have employees in several provinces, or any in Quebec
  • your pay rules are unusual, such as shift premiums or union rules
  • you are moving payroll mid-year
  • payroll runs on spreadsheets that only one person understands
  • nobody in-house owns the January rate update
  • payroll has to tie to inventory, job costing or invoicing in Odoo

Ask any provider or partner these questions before you sign:

  1. Which Odoo versions and editions do you support, and will you confirm that in writing for our version?
  2. Who updates CPP, EI and tax rates each January, by what date, and how do we test before go-live?
  3. Which provinces and pay types are covered, and is Quebec (QPP, QPIP and the Quebec EI rate) included?
  4. How do you test against CRA figures, and will you run a parallel period with us?
  5. Who owns the code, data and accounts when the project ends, and how do we export everything?
  6. What year-end support do you provide for T4, T4A and ROE, and who handles CRA queries?

If you are still shortlisting developers, our guide to choosing a custom software developer for your small business in Toronto covers what to ask before you sign.

Eskore's ERP work, custom development and data migration are delivered by one team across our offices in Toronto, Thornhill, London and New York. If you are still choosing a route, our independent advice on ERP and technology decisions is the simplest place to change direction before you commit to a build. You can also browse our case studies.

Talk to Eskore about your Odoo Canadian payroll setup

If you run Odoo, or are about to, and need an Odoo Canadian payroll setup that works from the same numbers as your accounts and operations, book a free 30-minute scoping call. We will look at your provinces, pay rules and current process, and tell you which route we would recommend, including when a module is enough.

Questions

Need help with this?

Talk to our erp systems team.