Daily updates from Odoo
Thursday, March 12, 2026
6 changes
1 change
New functionality added to Odoo
This update introduces support for accepting MPESA payments in Kenya through two methods: Express and Lipa Na Mpesa. These integrations allow businesses to accept payments via mobile apps and QR codes, streamlining the checkout process for customers using Safaricom.
Original PR description
This pr introduces MPesa payment methods using Safaricom APIs for Kenya. There are two types of payment methods : - Mpesa Express: This is implemented with the M-Pesa Express API. It's the Merchant…
This pr introduces MPesa payment methods using Safaricom APIs for Kenya. There are two types of payment methods : - Mpesa Express: This is implemented with the M-Pesa Express API. It's the Merchant Initiated payment method. The merchant create a payment method M-Pesa Express with Safaricom payment provider. The merchant is allowed to ask for payment through the API with an USSD prompt on the customer phone number. Customer enters the PIN and the API call the callback of the POS to reconcile transaction with order. (https://daraja.safaricom.co.ke/dashboard/apis?api=MpesaExpressSimulate) - Lipa Na Mpesa: This is implemented with the Customer To Business (C2B) API. This payment method is different from the first one. It is a Merchant-Initiated payment method. The POS registers callback URLs through the register URL. The POS listen on its callbacks. Customer sends a payment through his Safaricom or MPesa application with some informations of the business. When a transaction is catch in the callback, POS displays it. The cashier needs, manually, to reconcile it with the current order. To reconcile, cashier see a popup with every transaction done on this business account number. (https://daraja.safaricom.co.ke/dashboard/apis?api=CustomerToBusiness) Dynamic QR Code API is also implemented to allow customers to scan the QR Code in the official Safaricom application and send the payment easily without errors of amount or till number. (https://daraja.safaricom.co.ke/dashboard/apis?api=DynamicQRCode) Note : The problem with this payment method is that there is two steps. The first step is a "Verification" step, which is optional. Businesses needs to manually sends an email to Safaricom to allows them to add this step. This step is useful because it is used to accept or reject a transaction before charging the customer. But, in reality, not all of the businesses ask Safaricom to add this step. So, we don't configure it for the moment. The second step is the "Confirmation" step, before this step, the customer is already charged. The API sends transaction data to the POS, we display it in the POS to allow cashier to reconcile the current order with a transaction. Requirements : If you want to test this API, https is needed and a valid kenyan (+254) phone number is also needed. But, you can simulate requests in the Daraja Portal. (https://daraja.safaricom.co.ke/dashboard/apis) task: 5886047 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#247615
1 change
New functionality added to Odoo
This update introduces a new report specifically designed to track outstanding payments to Micro, Small, and Medium Enterprises (MSMEs). The report includes fields for MSME type and number within partner records and company settings, allowing for more targeted debt analysis. The PDF export now also incorporates MSME information for registered companies.
Original PR description
In this PR: - Added MSME Type and Number fields to the res_partner model and displayed them in the form view. - Added related MSME fields in res_company via partner_id and displayed them in Settings under the Indian Integration section. - Added Aged Payable MSME report variant to track dues to MSME partners, with filtering by MSME Type and a default aging interval of 45 days. - PDF export of the MSME report shows company MSME info in the header if the company is MSME registered. task-4140405
1 change
New functionality added to Odoo
This update introduces a new report to track outstanding payments to MSME vendors, improving financial compliance. It includes an MSME-specific XLSX export and a new 'MSME Report' variant within the aged payable reports. This enhances visibility and reporting for MSME vendor relationships.
Original PR description
- Provides a report for monitoring payment dues to MSME registered vendors. - Adds MSME-related XLSX export. - Adds a new aged payable report variant 'MSME Report'. Comm PR: https://github.com/odoo/odoo/pull/226297 task-4140405
1 change
New functionality added to Odoo
This update adds support for triangular taxes to the tax reporting system. This is necessary to accurately generate the EC Sales List report, ensuring compliance with Finnish tax regulations. The changes improve the accuracy of tax reporting for Finnish businesses using Odoo.
Original PR description
The aim of this commit is adding the triangular taxes into the tax report to use it in EC Sales List report. task-4010767 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
2 changes
New functionality added to Odoo
This update enables Danish companies to automatically generate official FIK payment references on customer invoices through their sales journals. Users simply configure their bank's FIK creditor number, ensuring compliant Danish FIK payments without disrupting existing workflows. This improves financial reporting and reduces manual effort for Danish customers.
Original PR description
Before: - Danish companies had to rely on manual or non-standard payment communication on invoices. - They could not generate official FIK payment references. After: - Sales journals can now generate Danish FIK payment references automatically. - Users configure an 8-digit bank-issued FIK creditor number on sales journal. Impact: - Enables compliant Danish FIK payments without changing user workflows. Related PR: https://github.com/odoo/enterprise/pull/102612 taskID-5401553
This update incorporates new required fields for Section F of Uruguayan tax regulations (DGI version 25). These changes ensure compliance with the latest tax reporting requirements, specifically for businesses operating in Uruguay. This addition is crucial for accurate financial reporting and avoiding potential penalties.
Original PR description
Regards to DGI new spec version 25.