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

… auto_join