[16.0][MIG] l10n_es_aeat_mod303: Migration to 16.0 #2693

[MIG] l10n_es_aeat_mod303: Migración a v7 del módulo con las siguientes mejoras: - Convenciones de la comunidad. - PEP8 en la mayoría de código. - Icono para el módulo. - Adaptación de vistas a las posibilidades de la v7. - Restringidas las cuentas bancarias a las de la compañía.

…más código. [IMP] l10n_es_aeat: Añadido wizard para ver el resultado de la exportación sin necesidad de tener el módulo document. [IMP] l10n_es_aeat: Puesta transición de estados sin workflow. [IMP] l10n_es_aeat_mod303: Adaptado al nuevo mecanismo. Se elimina workflow anterior mediante un script de migración.

…l modelo 340

…bién para la v8.

[MIG] Eliminados módulos no migrados a v7

…zado Presentación del Modelo AEAT 303 ================================ * Incluye un motor genérico para obtener los totales de códigos de impuestos de manera parametrizada y con posibilidad de versionado por fechas * Incluye un motor de parametrización de las exportaciones a formato BOE con posibilidad de versionado por fechas. * Se incluyen las parametrizaciones de ambos motores para el 303.

…dacion y corregido formulario de mod303, sustituido campo casilla_46 repetido por campo casilla_69.

…ón cuando se hace la declaración * Generador del asiento de regularización con cargo a un proveedor "Agencia Estatal de Administración Tributaria" creado al efecto. Configuración ============= Para activar la creación del asiento de regularización en un modelo, hay que poner en el modelo correspondiente el campo allow_posting a True, y establecer en la configuración de impuestos los conceptos que se regularizarán con el flag "to_regularize".

====================== AEAT - Prorrata de IVA ====================== Módulo para gestionar la prorrata del IVA en las declaraciones de la AEAT (por el momento, en el modelo 303), según el artículo 92 de la Ley 37/1992, de 28 de diciembre, del Impuesto sobre el Valor Añadido. Uso === Realizando el modelo 303, se puede seleccionar si se desea aplicar prorrata de IVA. Prorrata general ---------------- En el caso de seleccionar "Prorrata general", aparece un nuevo campo llamado "Porcentaje de prorrata de IVA" que puede ser rellenado a mano. Además, cuando se realice el asiento de regularización, la parte proporcional de la cuota no deducida se compensará como gasto. Se ha incluido un calculador del porcentaje de prorrata, utilizable en 2 casos: * Al comienzo de un nuevo ejercicio, para determinar el porcentaje provisional a aplicar hasta el último periodo de ese ejercicio. * En la última declaración del ejercicio, para determinar el porcentaje definitivo de prorrata, y sobre el que se compensará la diferencia. Problemas conocidos / Hoja de ruta ================================== * La prorrata especial de IVA no está contemplada aún.

…ixes OCA#290 Cuando se tienen campos related, aunque el valor no se cambie, Odoo lanza una escritura en el objeto relacionado cada vez que se guarda el objeto principal. En el caso de la moneda asociada a la compañía, hace que aquellos usuarios que no tengan permiso para modificar la compañía (la mayoría), falle en la creación del modelo.

El anterior método utilizado, al tener una clase y un many2one genérico, no permitía poner los datos en múltiples modelos hijos, ya que se repetían los IDs, y cogía los datos de un modelo en otros. Con este nuevo sistema, se sigue utilizando una tabla, pero con doble índice: el modelo y el ID, parecido a un campo reference, pero gestionado por código propio en el método de cálculo. El 303 está adaptado a este nuevo sistema, y se incluye un script de migración que conserve los datos.

… 303

Debido a que se utiliza una sola tabla para almacenar las líneas de los impuestos de todos los modelos, hay una limitación en el ORM de Odoo cuando se coloca el campo one2many de dichas líneas (tax_line_ids) como dependencia en la definición del cálculo de un campo (entrada con @api.depends), que recalcula los campos calculados de todos los modelos con el mismo ID que el del registro en curso, lo que puede ser un problema en entornos multi-compañía. Una solución a ello (aunque no evita el recálculo), es poner en esos campos calculados `compute_sudo=True`.

…onditional

Si no estás inscrito en el REDEME (Registro de Devolución Mensual), y la declaración sale negativa, la única posibilidad es la de compensar, por lo que no tiene sentido que se tenga que marcar manualmente la casilla, ya que si olvida y se exporta, Hacienda no lo admite. Por eso, este cambio detecta automáticamente esta situación y coloca el tipo de resultado, eliminando la casilla extra. Se incluye script de migración para restituir correctamente los datos de anteriores declaraciones. También se hace obligatoria la cuenta bancaria cuando la declaración sea a devolver, ya que es también un dato obligatorio al presentarlo a Hacienda.

Due to compute non stored field

- En a casilla de importes a compensar debe constar, EN POSITIVO, las cuotas a compensar procedentes de periodos anteriores. - Incluye mensaje para advertir que existen cuotas a compensar en periodos anteriores. - Borra campo 'bank_account_id', que está ya duplicado en 'partner_bank_id' e incluye script de migración.

…units

…hange iteritems() to iter(items())

* No need to change test structure with create * Optimize code * Fix tests in l10n_es_vat_prorrate * Translations * Other minor things

Odoo's operator "like" encloses the text to search into "%s", making the search to match with accounts like "157000" and others as addition to the expected "570000".

* Don't show the warning for draft reports * When you have to return result, don't propagate the result to next report * Put only once the warning

Currently translated at 100,0% (45 of 45 strings) Translation: l10n-spain-11.0/l10n-spain-11.0-l10n_es_aeat_mod303 Translate-URL: https://translation.odoo-community.org/projects/l10n-spain-11-0/l10n-spain-11-0-l10n_es_aeat_mod303/ca/

…unts They were ignored previously

* Standard procedure * Adapted tests * README by fragments

Updated by Update PO files to match POT (msgmerge) hook in Weblate.

* BOE format * Exonerated from 390 * Fields * Mappings * BOE export * README update * Little change in AEAT engine * Tests adapted + expanded

Updated by Update PO files to match POT (msgmerge) hook in Weblate.

As numbers have changed, the view was not adjusted.

…last period Inform this field only in the case where this proceeds.

This way, we don't initially see all the subconfigs for each model and we can concentrate on main export configurations. This is got through `active` field default behaviour. Archived config are still directly searchable through the subconfig selector in the configuration line. All models export configs have been adapted to this new approach.

* Include chatter (mail.thread) * Include activities (mail.activity.mixin) * Track AEAT report state change * Include new admin user in AEAT group by default

Currently translated at 32.3% (54 of 167 strings) Translation: l10n-spain-12.0/l10n-spain-12.0-l10n_es_aeat_mod303 Translate-URL: https://translation.odoo-community.org/projects/l10n-spain-12-0/l10n-spain-12-0-l10n_es_aeat_mod303/es/

…ax fee fields Given this regular invoice: 1, IVA 10%, 10 €, 1 € tax 2, IVA 21%, -1 €, -0,21 € tax that can happen when you return some packages (like returnable bottles), you have a valid invoice with total positive amount to due, but in 303, the -0.21 € of the tax fee is not included as there's no other positive tax fee to compensate that negative amount, and the tax map line indicated that only credit operations are included. As the move type is already checked for avoiding to include refunds, we can change to include both move lines types (debit and credit) for this. In fact, in the base, both are already included. As this can happen as well with other taxes and with supplier invoices, all involved fields are changed in the same commit.

It's the sum of all the year of field 61, so the definition is the same.

Field 88 doesn't include the new field 84

…n tests This way, we can reuse it in other modules that don't inherit AEAT report like SII. We also clean a non needed reading of the tax description field. Tests were still using description method for populating data, so we switch to new system and perform needed changes in dependent tests. s

… VAT AEAT now forces to be a proper VAT format. We adjust at the same time the version and some old year references.

…OADMAP

…rollo'

Currently translated at 32.9% (55 of 167 strings) Translation: l10n-spain-12.0/l10n-spain-12.0-l10n_es_aeat_mod303 Translate-URL: https://translation.odoo-community.org/projects/l10n-spain-12-0/l10n-spain-12-0-l10n_es_aeat_mod303/es/

…silla 60. fix OCA#1300

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: l10n-spain-13.0/l10n-spain-13.0-l10n_es_aeat_mod303 Translate-URL: https://translation.odoo-community.org/projects/l10n-spain-13-0/l10n-spain-13-0-l10n_es_aeat_mod303/

Currently translated at 100.0% (158 of 158 strings) Translation: l10n-spain-13.0/l10n-spain-13.0-l10n_es_aeat_mod303 Translate-URL: https://translation.odoo-community.org/projects/l10n-spain-13-0/l10n-spain-13-0-l10n_es_aeat_mod303/es/

Now "IVA Exento No Sujeto" is not included in field 60, but it should be included in field 83 for period 12 (December) in 303 for those exempted of the 390.

… state This way, we avoid the misunderstanding of changing that but not computing fields 76 to 99. Relates to OCA#1553

- Added missing tax "No sujeto (Bienes)" in field 84. - Removed tax "Exportación (Bienes)" from field 94 (already on 84).

Follow-up of 3a55cf3 Fix tests for the change.

Remaining pieces of 6c3a6f2. At the end, the refund part is controlled by move_type, not by balance sign.

- Requires new field for not compensating full pending fee. - New BOE format. - Removed incorrect es_ES translation. - Updated and completed Spanish translation.

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: l10n-spain-14.0/l10n-spain-14.0-l10n_es_aeat_mod303 Translate-URL: https://translation.odoo-community.org/projects/l10n-spain-14-0/l10n-spain-14-0-l10n_es_aeat_mod303/

If not, the constraint is evaluated each time, and can lead to inconsistent states. Fixes OCA#1624

The operator like searches for any coincidence, so it can select account 147000 instead of 470000. We switch to =like operator for avoiding the problem.

Currently translated at 98.7% (160 of 162 strings) Translation: l10n-spain-14.0/l10n-spain-14.0-l10n_es_aeat_mod303 Translate-URL: https://translation.odoo-community.org/projects/l10n-spain-14-0/l10n-spain-14-0-l10n_es_aeat_mod303/es/

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: l10n-spain-14.0/l10n-spain-14.0-l10n_es_aeat_mod303 Translate-URL: https://translation.odoo-community.org/projects/l10n-spain-14-0/l10n-spain-14-0-l10n_es_aeat_mod303/

* New tax mapping, field 84 now split on 84 and 125 * New export config, now in csv * New marca_sepa field * Update field 80

* Transform tax map to CSV * Incorrect BOE export definition * Simplify certain expressions * Move CSV to subdirectory to classify them by format change batch * End date for previous BOE format * Fix marca_sepa computation * Restore back field 85 for older reports

Remove taxes from field 61, and add them to both fields 120 y 122. That's because since 2021/07, these fields contains such values, and as the tax mapping is only used since this date, it's safe to do it. Something similar applies to marca_sepa, as even if doing a previous report, this field is not used at all, so we can remove the initial condition and put the value only when performing return.

…o return This hasn't been detected before, as testing reports didn't have bank account populated, but on a new one, it seems AEAT doesn't allow to have any content in these fields if the result is not to return.

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: l10n-spain-14.0/l10n-spain-14.0-l10n_es_aeat_mod303 Translate-URL: https://translation.odoo-community.org/projects/l10n-spain-14-0/l10n-spain-14-0-l10n_es_aeat_mod303/

This field is deprecated since 07/2021, and bringing it, even empty, can be confusing for users, so better to remove it.

- Don't apply sign to "Volumen operaciones" - Don't export SWIFT if Spanish or European bank

TT34690

Currently translated at 100.0% (168 of 168 strings) Translation: l10n-spain-15.0/l10n-spain-15.0-l10n_es_aeat_mod303 Translate-URL: https://translation.odoo-community.org/projects/l10n-spain-15-0/l10n-spain-15-0-l10n_es_aeat_mod303/ca/

Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: l10n-spain-15.0/l10n-spain-15.0-l10n_es_aeat_mod303 Translate-URL: https://translation.odoo-community.org/projects/l10n-spain-15-0/l10n-spain-15-0-l10n_es_aeat_mod303/

Following odoo/odoo#95967, the mapping is done for mapping the corresponding fields in the 303 model. If someone sells electricity at that rate, there's no mapping yet, as we don't know how the AEAT is going to reformat the model. TT38004

When doing mathematical operations over several rounded amounts, you can get a non rounded result. Example: >>> tax_lines.mapped("amount") [1022.18, 125899.42, 5399.41, 7354.03, 30.5, -3104.6, -181.45, 0.27, 18.03, 0.0, -0.34] >>> sum(tax_lines.mapped("amount")) 136437.44999999995 Leading to possible wrong report result ("Solicitud de devolución" instead of "Resultado cero"). In this commit, we round all the amounts + use float_compare for the result to avoid the problem. TT40670

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[16.0][MIG] l10n_es_aeat_mod303: Migration to 16.0 #2693

[16.0][MIG] l10n_es_aeat_mod303: Migration to 16.0 #2693

Commits on Dec 21, 2022

Commits on Dec 27, 2022