New Zealand employers must file employment information with Inland Revenue within two working days of every payday, not once a month. If your payroll sits in a separate silo from your ERP, that deadline turns into a recurring export-reconcile-upload chore, and every mid-cycle change (a new starter, a KiwiSaver opt-out, a corrected pay run) becomes a second reconciliation between two systems. Odoo's core payroll gives you contracts, salary structures and payslip runs, but it ships no NZ localisation: no PAYE tables, no KiwiSaver employee and employer contribution logic, no ESCT tiers, no Holidays Act leave rules, and nothing that emits an Employment Information return in the shape IR expects. Community has no payroll app at all — hr_payroll is Enterprise — so the ground floor differs depending on your edition, and we scope for the one you actually run.

We build a dedicated NZ payroll localisation module that sits on top of the standard payroll spine rather than forking it. Salary rules are defined as data so PAYE thresholds, ACC earner levy rates, student loan repayment thresholds and KiwiSaver percentages are versioned records with effective-from dates, not constants buried in Python — when IR changes a rate at the start of a tax year, you load a new rate set and historical pay runs stay reproducible. New models carry the NZ-specific fields Odoo lacks: IRD number with checksum validation, tax code (M, ME, SB, S, SH, ST, SA and their SL variants), KiwiSaver status and contribution rate, savings suspension dates, ESCT rate derived from prior-year earnings, and payday-filing submission state. Computed fields use @api.depends so a change to a contract or a mid-period tax-code switch recalculates the affected payslip lines rather than silently leaving stale amounts.

On the filing side, each pay run produces a payday filing document: a persisted record with its own state machine (draft, generated, submitted, amended), the exact file payload, a submission reference, and a chatter trail of who generated and lodged it. That record is the audit artefact, so an amendment is a new versioned document linked to the original rather than an overwrite. Employee details returns for new and departing staff are generated from the same data. Where you want lodgement automated, we integrate against IR's gateway services with credentials held in system parameters and a scheduled action driving the queue with retry and error capture; where you prefer to keep a human in the loop, the same record produces the file for manual upload to myIR.

Payslips and remittance advices are QWeb reports you can rebrand, and bank files are generated to the format your bank accepts (ANZ, ASB, BNZ, Westpac and Kiwibank direct credit layouts are all straightforward to target). Year-end summaries and reconciliation reports read from the same posted data, so what you file, what you pay and what hits the general ledger agree by construction. Access is enforced through ir.model.access.csv plus record rules that keep payroll officers inside their own company and keep employees off other people's records — payroll data is the most sensitive table in the database and we treat it that way. Views are standard XML with OWL components only where an interaction genuinely needs them, so the module survives upgrades. Everything is also reachable over XML-RPC and JSON-RPC if you drive pay runs or pull filing status from another system.

This is a build-to-order product, not a download. We start with a scoping call to confirm your Odoo version and edition, pay frequencies, entities and payroll headcount, which leave types you operate under the Holidays Act, whether you want automated IR lodgement or file generation for myIR, and which bank format you need. From that we write a fixed scope and a fixed quote. Typical delivery is two to four weeks from confirmed scope, longer only if you want multi-entity consolidation or an integration with an existing time and attendance system. We build against your target version, deliver to a staging database first, run UAT with your payroll officer on a parallel pay cycle so you can compare results against your current process before you cut over, then install to production with a documented rollback. You get the full source, a git repository handover, and a post-go-live support window during which we fix defects against the agreed scope.