Skip to content
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

[15.0][MIG] l10n_de _tax_statement #143

Closed

Conversation

MrGigSolutions
Copy link

@MrGigSolutions MrGigSolutions commented Jan 19, 2024

Migration of l10n_de_tax_statement to 15.0

Changes:

  • Adjusted manifest
  • Removed migrations
  • Refactored unlink() to @api.ondelete
  • Removed unused methods and imports from tests
  • Tests now use setUpClass instead of setUp
  • Chatters now don't have specified widgets anymore

@MrGigSolutions MrGigSolutions marked this pull request as draft January 19, 2024 08:00
@MrGigSolutions MrGigSolutions force-pushed the 15.0-mig-l10n_de_tax_statement branch from 241eb73 to 89544f9 Compare January 19, 2024 08:04
@MrGigSolutions MrGigSolutions changed the title 15.0 mig l10n de tax statement [MIG] 15.0 l10n_de _tax_statement Jan 19, 2024
@MrGigSolutions MrGigSolutions marked this pull request as ready for review January 22, 2024 10:37
@MrGigSolutions MrGigSolutions changed the title [MIG] 15.0 l10n_de _tax_statement [15.0][MIG] l10n_de _tax_statement Jan 22, 2024
@MrGigSolutions
Copy link
Author

The failing pre-commit doesn't seem to be an issue with this branch.

tv-openbig and others added 23 commits April 23, 2024 22:37
we have cloned and adopted the l10n-netherlands tax report module from
Onestein B.V.  The report is constructed in the same way as official
german „Umsatzsteuervoranmeldung“. The values from the report could be
easily transmitted via official portal https://www.elster.de/ in order
to declare and transfer your monthly (or quarterly) vat taxes.
…fig wizard

most removed tests are not relevant for germany as they was related in
the clone from netherlands to invoice basis (related to invoice or
account move dates which is probably not relevant for germany). The
change in the config wizard was required as the tax tag mappings for
the tax statement should work with skr03 and skr04 accounting plans.
The prior change raised an error. The two additional dependencies
account_invoicing, l10n_de should help to allow immediate runbot
testing without any manual installation steps in advance.
I have applied proposed changes of Andrea Stirpe in order to get
through the testing procedure.
The old lines 39 disappeared and was merged together with the old line
40 (now they are line 39 in 2019 edition). Furthermore the old lines 49
and 51 disappeared and was merged into the line 50. There is a
relevance for the tax codes (tag_ids). The old tag „USt-VA KZ 68“ have
to be mapped to the same line as the tag „USt-VA KZ 60“. The old tags
„USt-VA KZ 52“ and „USt-VA KZ 78“ have to be mapped the same way as the
old and single remaining „USt-VA 84“ (= base values). The old tags
„USt-VA KZ 53“ and „USt-VA KZ 79“ have to be mapped the same way as the
old and single remaining „USt-VA KZ 85“ (tax values). Furthermore we
might have formatting changes caused by the different line numbering.
Therefore i expect further adoptions in the files
„l10n_de_tax_statement_line.py“ and also in the
„l10n_de_tax_statement_config_wizard.xml“ and the
„l10n_de_tax_statement_config_wizard.py“. I assume we cannot avoid
deeper changes in order to adopt what we really want.
… compare conversation: OCA#39
astirpe and others added 26 commits April 23, 2024 22:37
Changes:
- Adjusted manifest
- Removed migrations
- Refactored unlink() to @api.ondelete
- Removed unused methods and imports from tests
- Tests now use setUpClass instead of setUp
- Removed widgets from chatter
@MrGigSolutions MrGigSolutions force-pushed the 15.0-mig-l10n_de_tax_statement branch from 89544f9 to 5634c62 Compare April 23, 2024 14:40
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Aug 25, 2024
@github-actions github-actions bot closed this Sep 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants