[19.0][MIG] payroll_account: Migration to 19.0

[neoand]

Migration of payroll_account from 18.0 to 19.0.

Module history was replayed with git format-patch --keep-subject --stdout origin/19.0..origin/18.0 -- payroll_account | git am -3 (69 commits), and the migration itself is the single commit on top.

What Odoo 19 broke

Odoo 19 removed the hr_contract addon: contract data now lives on hr.version, which is exactly the model this module extends. The payroll module already made that jump on 19.0, so this migration follows the same pattern.

Change	Fix
hr_contract addon is gone	models/hr_contract.py: _inherit "hr.contract" → "hr.version"
Parent view hr_contract.hr_contract_view_form no longer exists	Inherit payroll.hr_contract_view_form (model hr.version) and anchor the accounting fields after struct_id
hr.employee.gender → sex	Fixed in tests
hr.employee.bank_account_id (m2o) → bank_account_ids	Fixed in tests

Tests now build the contract through employee.version_id.write() with contract_date_start, the pattern used by payroll/tests/common.py on 19.0.

The 18.0.1.0.2 migration scripts were dropped.

Testing

On odoo:19.0 Community:

Module payroll_account: 0 failed, 0 error(s) of 3 tests

Beyond the module's own suite, I checked the feature end-to-end on a fresh database: a payslip whose rules carry account_debit / account_credit, confirmed with action_payslip_done(), produces a balanced account.move posted on the journal configured on the version.

Entry MISC/2026/04/0001 | journal=Miscellaneous Operations | state=posted
ACCOUNT   LABEL          DEBIT       CREDIT
443000    Salary     12,000.00         0.00
201000    Salary          0.00    12,000.00
201000    ISR             0.00     1,200.00
443000    ISR         1,200.00         0.00
          TOTALS     13,200.00    13,200.00

I also re-ran a payslip-engine check on payroll alone before and after installing this module to confirm nothing regressed.

Note

Loading demo data changed in Odoo 19 — --without-demo is no longer enough and there is a new odoo module force-demo subcommand. Without demo data these tests fail on base.res_partner_12, which does exist in 19.0's demo. Worth knowing when reproducing locally.

@appstogrow @nimarosa

---

Assisted-by: Claude Opus 4.8

Disclosed per the OCA Generative AI / LLM Policy.
Developed and verified under my direction and review; I take responsibility for the contribution.