Odoo Changelog — 2024-09-19

Thursday, September 19, 2024

5 changes · master

New Features(3)

New functionality added to Odoo

[ADD] l10n_in_reports_gstr_gstr2a: retrieve GSTR-2A data in Indian localization

PR #62019

Enterprisemasterl10n_in_reports_gstrl10n_in_reports_gstr_gstr2aHigh impact

Adds the ability for Indian localization users to retrieve GSTR-2A tax data from the government portal, including B2B and credit/debit note details. This helps businesses keep tax reporting data more aligned with Indian GST compliance requirements and reduces manual data collection.

Original PR description

This update adds a new feature to the Indian localization module (l10n_in). Now, the system can fetch GSTR-2A data from the portal, including details from the B2B and CDN sections. This enhancement ensures that the module stays in sync with India's specific tax reporting needs.

Task Id: 3551097

#India#GST#GSTR-2A#tax reporting#compliance

[ADD][Draft] l10n_in_reports_gstr: Module for fetching and processing IRN data from GST portal

PR #65791

Enterprisemasterl10n_in_reports_gstrl10n_in_qr_code_bill_scanstock_barcodeHigh impact

Businesses in India can now fetch e-invoice IRN data from the GST portal and use it to match or create vendor bills more efficiently. The update also adds manual IRN entry and QR-based workflows, reducing manual billing effort and improving GST compliance accuracy.

Original PR description

This pull request introduces a new module, `l10n_in_reports_gstr_irn_sync`, and implements an API for better integration with the GST portal.

#### Key Features:
- **Module Addition:**
  - Fetches and processes IRN data from the GST portal.
  - Automatically creates draft bills if no related IRN bill exists.
  - Improves GST compliance and billing efficiency.

- **API Implementation:**
  - Adds an endpoint to get bill details using IRN.
  - Ensures IRN is a 64-character alphanumeric string.
  - Allows setting IRN via QR scanning or GST report.

#### Impact:
- Enhances billing accuracy and compliance.
- Reduces manual work.
- Streamlines billing processes.

Task ID: 3551097

#GST#IRN#vendor bills#e-invoicing#India localization

[Draft][ADD] l10n_in_reports_gstr_gstr2a: retrieve GSTR-2A data in Indian localization

PR #53498

Enterprisemasterl10n_in_reports_gstrl10n_in_reports_gstr_gstr2aHigh impact

Adds the ability for Indian localization users to retrieve GSTR-2A data from the GST portal, covering B2B, credit/debit notes, imports, and SEZ import sections. This helps businesses keep purchase tax reporting data aligned with Indian compliance requirements directly in Odoo.

Original PR description

This update adds a new feature to the Indian localization module (l10n_in). Now, the system can fetch GSTR-2A data from the portal, including details from B2B, CDN, IMPG, and IMPGSEZ sections. This enhancement ensures that the module stays in sync with the specific tax reporting needs in India.

Task Id: 3551097

#India#GST#GSTR-2A#tax reporting#localization

Improvements(2)

Enhancements to existing features

[IMP] {account,payment}_sepa{,_direct_debit}: SDD mandatalypse

PR #69867

Enterprisemasteraccount_sepa_direct_debitpayment_sepa_direct_debitl10n_uk_bacsHigh impact

SEPA direct debit mandate handling has been redesigned to reduce manual work and make customer communications clearer. The update removes unnecessary journal-based restrictions, adds required pre-notification handling, improves mandate status tracking, and introduces better send-and-print flows for signature requests.

Original PR description

### **[IMP] {account,payment}_sepa_direct_debit: SDD mandatalypse**

The aim of this commit is to rework the sepa mandate models
to improve the user experience

Context (non-exhaustive):
Prior to this changes a few frustration points were present:
- The obligation to make a new mandate if another journal was used
- The selection of the right mandate upon payment creation
- Redundant buttons
- Lack of SEPA norm required elements e.g.:
    - the pre-notification period and pre-notification mail
      (account_sepa_direct_debit)
    - the automatic expiration of a mandate for inactivity
- A proper send & print wizard when sending the signature request
- Lots of small UI/UX issues

After this commit (non-exhaustive):
- A lot of constraints removal/displacement further in the flow
- Removal of journal-related fields
  and adding the missing pre-notification period
- A new state when canceling a draft mandate
- New mail templates for the different interactions with the customer
- New Send & Print wizard with a mail composer
- Required collection date computation overhaul
- Mandates state computation overhaul

see task for more details

### **[IMP] l10n_uk_bacs: Change permission groups**

The permission group for the BACS Direct debit Instruction
was deemed too high and it was decided to lower
it to the basic account group.
As an employee able to see/use bank statement feature
is considered trustworthy enough to validate mandates

### **[LINT] {account,payment}_sepa_direct_debit: apply ruff style to module**

The new rules of the ruff linter makes any changes in this module
impossible without correcting the style issues first.
This applies the required changes in a separate commit for
more clarity

task-id: 3722517

#SEPA#direct debit#mandates#payments#customer communications

[IMP] (test_)web_studio: approval rules improved

PR #69171

Enterprisemasterweb_studiotest_web_studioHigh impact

Studio approval rules now support both individual approvers and approver groups, with clearer step-based approval flows. Approvers and notified users receive activity alerts at the right time, and approvers can delegate approval rights when needed.

Original PR description

As before, approval rules are ordered by their "Step" field (notification_order).
Same order rules are of equal importance, higher order rules have higher importance.
Together they compose an approval flow, which is made explicit with a Kanban view where
rules are grouped by their notification order by default.

A "Delegate" feature has been implemented:
- if a user is an approver on a rule, they can add other users permanently or temporarily
as approvers on that rule. They can only remove approvers if they themselves added them.
They can do that via the button "Delegate" on the rule's form view.
Generally speaking, they are not supposed to have create/write access on rules, and must
delegate via the wizard.
- If a user has write access on rules (in the admin group),
modifying approvers on the form view will wipe every delegation previously done.

Technically, it is not necessary anylonger to put `studio_approval="1"` as an attribute on the button
itself to fetch its approvals. The information that tells buttons to fetch approvals is now part
of the get_views.

*: test_web_studio

task-4123107

Co-authored-by: Aaron Bohy <aab@odoo.com>
Co-authored-by: Adrien Dieudonné <adr@odoo.com>
Co-authored-by: Mathieu Duckerts-Antoine <dam@odoo.com>
Co-authored-by: Lucas Perais <lpe@odoo.com>

#approvals#studio#delegation#notifications

This update adds a new feature to the Indian localization module (l10n_in). Now, the system can fetch GSTR-2A data from the portal, including details from the B2B and CDN sections. This enhancement ensures that the module stays in sync with India's specific tax reporting needs. Task Id: 3551097

This pull request introduces a new module, `l10n_in_reports_gstr_irn_sync`, and implements an API for better integration with the GST portal. #### Key Features: - **Module Addition:** - Fetches and processes IRN data from the GST portal. - Automatically creates draft bills if no related IRN bill exists. - Improves GST compliance and billing efficiency. - **API Implementation:** - Adds an endpoint to get bill details using IRN. - Ensures IRN is a 64-character alphanumeric string. - Allows setting IRN via QR scanning or GST report. #### Impact: - Enhances billing accuracy and compliance. - Reduces manual work. - Streamlines billing processes. Task ID: 3551097

This update adds a new feature to the Indian localization module (l10n_in). Now, the system can fetch GSTR-2A data from the portal, including details from B2B, CDN, IMPG, and IMPGSEZ sections. This enhancement ensures that the module stays in sync with the specific tax reporting needs in India. Task Id: 3551097

### **[IMP] {account,payment}_sepa_direct_debit: SDD mandatalypse** The aim of this commit is to rework the sepa mandate models to improve the user experience Context (non-exhaustive): Prior to this changes a few frustration points were present: - The obligation to make a new mandate if another journal was used - The selection of the right mandate upon payment creation - Redundant buttons - Lack of SEPA norm required elements e.g.: - the pre-notification period and pre-notification mail (account_sepa_direct_debit) - the automatic expiration of a mandate for inactivity - A proper send & print wizard when sending the signature request - Lots of small UI/UX issues After this commit (non-exhaustive): - A lot of constraints removal/displacement further in the flow - Removal of journal-related fields and adding the missing pre-notification period - A new state when canceling a draft mandate - New mail templates for the different interactions with the customer - New Send & Print wizard with a mail composer - Required collection date computation overhaul - Mandates state computation overhaul see task for more details ### **[IMP] l10n_uk_bacs: Change permission groups** The permission group for the BACS Direct debit Instruction was deemed too high and it was decided to lower it to the basic account group. As an employee able to see/use bank statement feature is considered trustworthy enough to validate mandates ### **[LINT] {account,payment}_sepa_direct_debit: apply ruff style to module** The new rules of the ruff linter makes any changes in this module impossible without correcting the style issues first. This applies the required changes in a separate commit for more clarity task-id: 3722517

This commit improves the Studio approval models and flow. A rule can now have Users that can approve or a Group, users of which can approve too. Approvers are pinged with a Mail Activity when a rule is up next in the approval flow. Users to notify are pinged whenever an entry has been created or changed. As before, approval rules are ordered by their "Step" field (notification_order). Same order rules are of equal importance, higher order rules have higher importance. Together they compose an approval flow, which is made explicit with a Kanban view where rules are grouped by their notification order by default. A "Delegate" feature has been implemented: - if a user is an approver on a rule, they can add other users permanently or temporarily as approvers on that rule. They can only remove approvers if they themselves added them. They can do that via the button "Delegate" on the rule's form view. Generally speaking, they are not supposed to have create/write access on rules, and must delegate via the wizard. - If a user has write access on rules (in the admin group), modifying approvers on the form view will wipe every delegation previously done. Technically, it is not necessary anylonger to put `studio_approval="1"` as an attribute on the button itself to fetch its approvals. The information that tells buttons to fetch approvals is now part of the get_views. *: test_web_studio task-4123107 Co-authored-by: Aaron Bohy <aab@odoo.com> Co-authored-by: Adrien Dieudonné <adr@odoo.com> Co-authored-by: Mathieu Duckerts-Antoine <dam@odoo.com> Co-authored-by: Lucas Perais <lpe@odoo.com>