Monday, July 28, 2025
4 changes · 18.0
Enhancements to existing features
Point of Sale payments in Argentina, Peru, and Uruguay now request an invoice by default. This supports local requirements that sales generate an electronic document, reducing the risk of missed invoicing during checkout.
Original PR description
[IMP] l10n_*: set default invoice true in pos modules: l10n_pe_pos, l10n_ar_pos, l10n_uy_pos In the POS, in the payment screen, the button to request an invoice is set to true by default. This is done because a sale in these countries must generate an electronic document. task-4612192
Indian companies will now keep HSN codes on point-of-sale accounting entries even when POS orders are reversed after session closure. This helps maintain accurate HSN-wise tax reporting for GSTR filings and reduces manual correction work.
Original PR description
This commit ensures that the `l10n_in_hsn_code` is also included in the accounting move lines are generated for reversal entries of POS orders when the The company’s fiscal country is India. Key changes: * Introduced the method `_prepare_product_aml_dict` in `point_of_sale` to centralize journal line creation logic. * Overridden the method in `l10n_in_pos` to append the `l10n_in_hsn_code` from the base values for Indian companies. * Ensured this applies consistently for both regular and reversal entries. This enhancement is essential for maintaining accurate HSN-wise reporting in GSTR filings, even when entries are reversed after session closure. OPW: 4931360
The French tax report now shows a warning when key declared tax amounts do not balance against related totals. This helps users spot possible reporting errors before submitting or reviewing the report.
Original PR description
This commit will add a warning banner when the sum of field 08+09+9B+10+11+T1->T7 is not equal to sum of field A1+A2+A3+B2+B3+B4 Task-4933787
The database expiration message now reflects the updated payment grace period, where expiration is set 15 days after the next invoice date. This helps customers understand the real deadline earlier and encourages timely payment before access is affected.
Original PR description
Previously, the database expiration date was set to the same date as the expiration field, which is now defined as 15 days after the next invoice date. Issue: Users tend to wait until the last minute to pay. This improvement aims to better handle expiration timing and encourage timely payments. TaskID: 4384877 Forward-Port-Of: odoo/enterprise#90810 Forward-Port-Of: odoo/enterprise#90664