Canadian payroll fails on the details. Statutory deductions are not one number: CPP has a basic exemption prorated per pay period, a first-tier maximum and a second-tier (CPP2) band above it; EI runs on insurable earnings with a separate employer multiplier; income tax is federal plus a provincial or territorial layer with its own brackets, credits and tax reduction rules. Odoo's core hr_payroll module gives you a genuinely capable engine — salary structures, rule categories, hr.salary.rule records evaluated in Python, payslip lines, and the accounting entry behind them — but it ships with no maintained Canadian rule set, no T4, no T4A and no Record of Employment. Odoo's own localized payroll packs are an Enterprise feature and do not cover Canada in core. So Canadian employers end up running the ERP for everything except payroll, then re-keying results back in, or exporting payslips to a spreadsheet every January to assemble slips by hand.\n\nWe build a Canada payroll and year-end pack that lives inside your Odoo database rather than beside it. The deduction engine is a set of salary rules driven by effective-dated CRA parameter records — a models.Model holding YMPE, YAMPE, the CPP and CPP2 rates and exemptions, EI maximum insurable earnings and employee/employer multipliers, and federal and provincial bracket tables — so a January rate change is a data record with a date_from, never a code edit. Payslip lines compute through @api.depends chains against contract, pay frequency and year-to-date accumulators, so maximums stop contributing at the right pay period instead of overshooting. Employer-side CPP and EI are computed alongside the employee amounts because the remittance needs both.\n\nYear-end outputs are first-class models, not report exports. T4 and T4A slips are generated as their own records with box-level fields sourced from posted payslip lines, so every box amount traces back to the pay period that produced it; slips render as QWeb PDF reports in CRA layout for distribution and export as the CRA XML transmitter file for electronic filing, with amended and cancelled slips tracked as distinct states rather than overwritten. Records of Employment are assembled from contract, payslip and leave history — insurable hours and insurable earnings mapped to the correct pay-period blocks, reason for issuing, final pay-period ending date — and exported in the format your ROE Web upload expects. Period remittance summaries group employee and employer contributions by payroll account number and reconcile against the payroll journal entry, so the amount you send CRA matches what your general ledger says you owe. Bank files for direct deposit are generated per your financial institution's specification.\n\nSecurity is designed in, not bolted on. Payroll data is the most sensitive table in the database, so slips, ROEs and rate records get explicit ir.model.access.csv entries plus record rules that keep payslips visible to the payroll officer group and to the employee who owns them, and nobody else — including HR users who legitimately need every other employee record. Views are standard XML with OWL components only where an interactive year-end wizard genuinely earns one, keeping the module upgradeable. Automated actions can flag employees approaching a CPP or EI maximum, or pay runs missing a required field before year-end. Everything the module writes is reachable over XML-RPC and JSON-RPC, so an existing time-tracking or scheduling system can feed hours in without a manual import step.\n\nThis is a build-to-order product, not an instant download. After you request a quotation we run a scoping call — typically 30 minutes — to confirm your Odoo version and edition, provinces of employment, pay frequencies, benefit and taxable-allowance treatment, and which year-end outputs you file yourself versus through a service provider. We then quote a fixed scope, build against your exact release, and test on a staging copy of your database with a parallel run against a recent real pay period so you can see our numbers next to your current ones before anything goes live. Typical delivery is two to four weeks from confirmed scope. You receive the full source in a git repository with technical documentation, so you are never dependent on us to keep it running. We are the implementer, not the filer — you remain the employer of record and are responsible for what is submitted to CRA; our job is to make the numbers correct, traceable and easy to produce.