Daily updates from Odoo
Monday, December 2, 2024
3 changes
New functionality added to Odoo
Kenya payroll now supports the move from NHIF to SHIF contributions, applying the correct calculation based on the payslip date. Reporting has also been updated so businesses can generate the appropriate NHIF or SHIF reports for the transition period.
Original PR description
Problem ---------- Since 1st October, the SHIF replace the NHIF, the only difference is the computation of the amount. All payslip before and on the 9 October use the NHIF and all new payslip from the 9 October use the SHIF Objective ---------- Adapt the salary rules to compute the good rule. Adapt the NHIF Report to make NHIF or SHIF reports. Solution ---------- Create new SHIF rule parameter with a min amount and rate computation. Create a new report wizard to manage the 2 different rules NHIF and SHIF task-4294419
Resolved issues and error corrections
Invoices now correctly account for online down payments that were made before the invoice existed, even when those payments do not create accounting journal entries. This prevents customers from being asked to pay more than the actual order total and keeps invoice and portal payment displays accurate.
Original PR description
Steps to reproduce: - Install sign; account; sales - Payment Providers > Enable Demo - Sales app > New Quotation > Other Info tab > Online Payment: 50% - Preview > Sign and pay > Make the 50% down…
Steps to reproduce: - Install sign; account; sales - Payment Providers > Enable Demo - Sales app > New Quotation > Other Info tab > Online Payment: 50% - Preview > Sign and pay > Make the 50% down payment - Back to SO > Create invoice > Regular invoice > Confirm > Preview Coupled with https://github.com/odoo/enterprise/pull/74108 The down payment amount is not deducted from the invoice, meaning we essentially force the customer to pay 150% of the total price. This is a by-product of the rework 01b87f1230beac0568f4e3b1b76e547909506892 which made the creation of journal entries optional, on which the invoice was previously dependant to track existing payments. Since the first payment here is made before any invoice is created, we want to create a separate payment with no associated journal entry (See the rework commit for more details on why we would want to do that, but in short we don't necessaily want to track payments that could be cancelled, etc...). However the matched_payment_ids on the invoice we create afterwards is not updated correctly, and above all the field is not taken into account by many views and functions which still assume there will be a corresponding account_move. This fix mostly aims to recompute the amount_residual of the invoice since that is the source most places draw from, and to reestablish the customer displays to prevent excessive payments from being made. To avoid disturbing other functions which could depend on the edited method payment_content is being kept separate (Not all fields are available without an account move so we would risk accessing missing fields unexpectedly by mixing them with regular move lines. opw-4208717 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Invoices now correctly account for online down payments made before the invoice exists, even when those payments do not create accounting journal entries. This prevents customers from being asked to pay more than the actual order total and keeps invoice payment information accurate.
Original PR description
Steps to reproduce: - Install sign; account; sales - Payment Providers > Enable Demo - Sales app > New Quotation > Other Info tab > Online Payment: 50% - Preview > Sign and pay > Make the 50% down…
Steps to reproduce: - Install sign; account; sales - Payment Providers > Enable Demo - Sales app > New Quotation > Other Info tab > Online Payment: 50% - Preview > Sign and pay > Make the 50% down payment - Back to SO > Create invoice > Regular invoice > Confirm > Preview Coupled with https://github.com/odoo/odoo/pull/185645 The down payment amount is not deducted from the invoice, meaning we essentially force the customer to pay 150% of the total price. This is a by-product of the rework 01b87f1 which made the creation of journal entries optional, on which the invoice was previously dependant to track existing payments. Since the first payment here is made before any invoice is created, we want to create a separate payment with no associated journal entry (See the rework commit for more details on why we would want to do that, but in short we don't necessaily want to track payments that could be cancelled, etc...). However the matched_payment_ids on the invoice we create afterwards is not updated correctly, and above all the field is not taken into account by many views and functions which still assume there will be a corresponding account_move. This fix mostly aims to recompute the amount_residual of the invoice since that is the source most places draw from, and to reestablish the customer displays to prevent excessive payments from being made. To avoid disturbing other functions which could depend on the edited method payment_content is being kept separate (Not all fields are available without an account move so we would risk accessing missing fields unexpectedly by mixing them with regular move lines. opw-4208717