Daily updates from Odoo
Wednesday, June 18, 2025
2 changes · master
Enhancements to existing features
Payroll batch management has been redesigned around Pay Runs, making it easier to view run details alongside the related payslips. Users can now browse Pay Runs in a kanban-style view and create them through a guided two-step flow for setup and employee selection.
Original PR description
Problem ---------- Change the UX of payroll batches. Objective ---------- Batches are now Pay Runs. No more form view in full size. Pay Run information is displayed above the list of payslips when they are filtered by a specific pay run. All pay runs are accessible from a vertical kanban view. To create a new kanban, there is a wizard in 2 steps. One to select the dates, structure_id, etc. of the pay run And the other to select the employees that fit the constraints Solution ---------- All action buttons, smart buttons and fields of the form are used to display the pay run card. The form arch is fetched and compiled in the kanban view and list view of payslips. The wizard of pay run creation is the form view of payrun. The wizard to select employees is the employee list view. See : odoo/upgrade#7861 task-4568268
Code cleanup and technical improvements
The General Ledger report has been rewritten to use a cleaner, dedicated engine, making it easier to maintain and improve. Report line labeling can now be processed in batches for better performance and ordering, while the separate US Check Register report is removed because the same information is available through the General Ledger.
Original PR description
**[IMP] account_reports: batch label builder** When using a custom groupby, we can use a label builder using the grouping key. Before it was called once for each grouping key and some optimization…
**[IMP] account_reports: batch label builder** When using a custom groupby, we can use a label builder using the grouping key. Before it was called once for each grouping key and some optimization might have not been done as we could not batch it. The new way call the label builder once with all the grouping keys. This way it is batched and we can make optimization if required. The label builder function returns a dict with each grouping key containing the name of the line. The order of this dict is important as it will be the order rendered on the report. So another feature allowed by this is that we can manually order grouping keys and therefor lines. **[REF] l10n_us_reports: remove check register** It is a subset of the general ledger that is useless as a standalone report as it can be done in the General Ledger **[REF] account_reports: General Ledger Rewrite** Before this commit, the general ledger had lots of uselessly complex code that was coupled with the trial balance. See https://github.com/odoo/enterprise/pull/73298 for the trial balance rewrite. This commit aims to refactor the general ledger and use a custom engine. task-4251472