Skip to content

[IMP] l10n_in: assign gstr section for purchase documents #4823

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: master-l10n_in_reports-gstr-mapping-field-jasa
Choose a base branch
from

Conversation

vivp-odoo
Copy link

This commit adds purchase-related selection values to the l10n_in_gstr_section field and extends the logic to assign appropriate GSTR sections to purchase move lines (vendor bills and credit notes).
This enhancement simplifies the domain logic used in the GSTR-2B report by avoiding complex conditions.

task-4750259

jasa-odoo and others added 2 commits July 14, 2025 12:43
With this commit,
-Added the `l10n_in_is_lut_tax` field to the `account.tax` model to easily
 identify LUT taxes.
-Removed the RC tags, as the existing `l10n_in_reverse_charge` field already
 indicates reverse charge taxes. Standard GST tags will now be used instead.
-Introduced a GSTR section mapping field on account.move.line to facilitate
 efficient cross-verification between user-entered data and GSTR reporting.
 This field is also included in the journal item list view for better
 visibility.

task-3360018

Co-authored-by: Jay Savaliya <[email protected]>
Co-authored-by: Josse Colpaert <[email protected]>
Co-authored-by: Zeel Patel <[email protected]>
This commit adds purchase-related selection values to the `l10n_in_gstr_section`
field and extends the logic to assign appropriate GSTR sections to purchase move
lines (vendor bills and credit notes).
This enhancement simplifies the domain logic used in the GSTR-2B report by
avoiding complex conditions.

task-4750259
@robodoo
Copy link

robodoo commented Jul 14, 2025

This PR targets the un-managed branch odoo-dev/odoo:master-l10n_in_reports-gstr-mapping-field-jasa, it needs to be retargeted before it can be merged.

@jasa-odoo jasa-odoo force-pushed the master-l10n_in_reports-gstr-mapping-field-jasa branch from e73032b to 6cbf25d Compare July 16, 2025 06:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants