Thursday, June 26, 2025
4 changes · 18.0
Enhancements to existing features
When an online payment provider is activated, Odoo now automatically assigns the appropriate outstanding account to the payment method it creates. This keeps online payment setup consistent with invoicing rules and reduces manual accounting configuration for integrated providers.
Original PR description
In this PR: - When activating an Online Payment provider that creates a payment.method.line in a journal, automatically assign an Outstanding account to the payment method. - Uses the existing Outstanding Account resolution method from Invoicing module to ensure consistency across the system. - Applied to all Online Payment Providers that rely on provider integration, excluding manual payment providers without external integrations. task-4826385
This update clarifies how Odoo's record creation method can be used, allowing tools to recognize both single-record and multi-record inputs. It helps developers get better editor guidance without changing business workflows or user-facing behavior.
Original PR description
As soon as the `model_create_multi` decorator exists, `create()` function arguments can be either a list of dict values or a single dict. Moreover, make IDE's happy when creating with single dictionary values. @rco-odoo --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Australian payroll rule parameters have been updated for the 2025 period to keep payroll calculations aligned with current requirements. This helps businesses using Australian payroll process payslips with the latest applicable values.
Accounting report test cases were updated to use the default outstanding payment and receipt accounts that are now created automatically with the chart of accounts. This reduces test conflicts and helps keep accounting report validation aligned with current setup behavior.
Original PR description
In this PR: - As part of recent changes, the default Outstanding Payment/Receipts accounts are now always created when the Chart of Accounts is loaded, and several test cases were updated to avoid unique constraint errors. - Previously, these test cases manually created accounts with codes like `OSTR00` and `OSTP00`. Now that these accounts are created by default, attempts to redefine them or change their codes have led to conflicts. - This commit updates the affected test cases to: - Use the correct default account codes directly (101403, 101404) - Avoid reassignment of codes that are now created by the CoA template task-4826385