[17.0][MIG] l10n_es_aeat: Migration to 17.0 #3387

…c module for aeat models, 347 module was portedto v6.0 and adds new module to print AEAT model 349.

…ueñas mejoras generales (vistas, traducciones, código) y corrección pequeño bug por un olvido en la adaptación de la v5 a la v6

…s formatted correctly. With this number 'dec_part' would become 100 (instead of 0) and fail in the final assertion. Instead of providing a workaround for this case, I simply replace the formatting with '%0*.*f' which seems easier specially because it already does the appropriate rounding.

…recía Pexego en la licencia, quedan los compartidos.

…en la 6.0 de estos módulos

…ron marcados como no instalables mientras no se compruebe que funcionan o migren, para poder usarlos o probarlos se debería poner el atributo installable de los ficheros __openerp__.py de cada módulo a True

…eption)

- Algo de PEP8 y refactorización de código [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. - Añadido wizard para ver el resultado de la exportación sin necesidad de tener el módulo document. - Puesta transición de estados sin workflow. - Pequeños ajustes de interfaz. [IMP] l10n_es_aeat_mod303: Adaptado al nuevo mecanismo. Se elimina workflow anterior mediante un script de migración.

…l modelo 340

…el 347 y el 340.

* Eliminación de la mayoría de warnings que da runbot. * Usar librería unidecode en lugar de reemplazos manuales para las tildes y caracteres no soportados.

[MIG] Eliminados módulos no migrados a v7

- Mover import de unidecode para evitar error

* unificar campos en el módulo base + migrar a la nueva api. * README.rst mejorado * mejora de código * usabilidad del atributo _aeat_number * secuencia automatica * control al instanciar los modelos * correcciones necesarias para el correcto funcionamiento de los módulos

…do + tratamiento residentes 216 y cálculo

…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.

…ó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".

…ortación

…lugar de recordset + gestionar grupos de compañías

…pacio. Fixes OCA#228

PR related with: OCA#236

====================== 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.

…w other values in export config

…ebe y haber a la vez.

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.

- Change field name: 'sequence' by 'name' - Isolate report identifier number calculation in order to be inheritable - Change methos name: _name_get by _report_identifier_get - Remove sequence constraints

…Closes OCA#305 If some tax lines have to been regularized, and they have the same account, previous to this commit, they appear in separate lines. Now, all are merged in only one line (if the balance sign is the same).

…stas

OCA#375

…1 para los ejercicios 2016 y siguientes

…arización

…CA#317)

When you fill a bank or cash statement with taxes for cancelling an expense, those amounts weren't included on the reports, as the move type is 'liquidity', not 'receivable' or 'payable'. This fix includes also this type on the search domain.

ORM launches a rewrite on origin table for related fields without readonly flag. Preventing this marking it as readonly, we will gain a bit in performance or avoid write errors.

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`.

If the declaration is complementary or substitutive, there should be a previous declaration number.

…onditional

Due to a bug in ORM that unlinks other tables' records, we have to avoid (0, 0, x) syntax Reference: odoo/odoo#18438

Calling it with decorator @api.model_cr

…olves compatibility problems with python3) (#1) * Adds tests for exporting files to boe with an export config (OCA#2)

…odBase._chart_of_accounts_create() in order to fix travis tests * remove fax, field does not exist

…units

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

… period

With this, cash basis can be done in an easy way, and it's a base field in account module.

It includes tests for the new cases.

- Standard procedure - Adapt views - Adapt tests - README by fragments

* Standard procedure * Adapted tests * README by fragments

So it works for multi-company environments.

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

New feature for viewing a BOE exported file with each field properly mapped to their export config line for showing the values.

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.

* Add controller for automatic confirmation/rejection * Improve data model * Clean code * Clean UI * Spanish translation * Tests * ...

When a new company is created, its sequences are not populated, so an Odoo service restart is needed for being able to use AEAT models. With this, you don't need this restart. It includes a test with a hack for populating a model in the test itself for testing complete flow.

This dependency is not strictly needed by the module, but the test base for other modules needs the module, so let's put it explicitly

It's not accepted by AEAT.

So that inherited models are able to access this value.

* 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 100.0% (228 of 228 strings) Translation: l10n-spain-12.0/l10n-spain-12.0-l10n_es_aeat Translate-URL: https://translation.odoo-community.org/projects/l10n-spain-12-0/l10n-spain-12-0-l10n_es_aeat/es/

…on parse_vat_info

…llas

[ADD] l10n_es_aeat: certificates and soap. AEAT Partner check [ADD] l10n_es_aeat: certificates and soap. AEAT Partner check [ADD] l10n_es_aeat: certificates and soap. AEAT Partner check [ADD] l10n_es_aeat: certificates and soap. AEAT Partner check

It was solved in v9 (see odoo/odoo@9ae7832).

…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

Due to a weird chained operations, posting the invoice with billing user permissions leads to an AccessError trying to read `l10n.es.aeat.mod303.report`. And even more, this only happens on first test execution during install. Consecutive test executions don't fail. Possible reasons for this are: - Registry state in SavepointCase in setUpClass - New ORM API malfunction Anyway, as doing this on UI or successive test executions don't fail, let's use the shortcut of doing the post with sudo for avoiding the problem.

- Redo the tax computation for efficiency and reliability - Add test suite for checking obtained JSON for different tax configurations - SII description computation reworked for new computed writable - Added migration scripts

It was provoking an invalid extension in Windows.

- Being sure company is created with EUR - Setting a resilient environment for USD

From this version, there's no more "Allow cancelling entries" option in journals to choose from, so we should force the removal of the entry in these cases.

…ests - Put minimal certificate test in l10n_es_aeat - Remove deprecation warning due to use of password as str. - Extend properly tests in l10n_es_aeat_sii_oca for the SII part.

Due to a newly introduce check, journal type must be compatible, so we can't put in a misc journal any refund, but it's not needed to force it, as reverse code handle this.

…unts and taxes templates to make it compatible with objects of type NewID.

Since odoo/odoo#68474, the tests are failing as Odoo is not able to recognize the country for VAT check. We do the writing for both values at the same time for avoiding the problem.

…djust rule It includes the migration scripts for the module. As the field is required, no need to check for empty company in the record rule.

- Always assign value to non stored computed field - Put archived ribbon ala v13 style - Adopt it as maintainer

- Standard procedure. - Add tests for full coverage. - Fix compatibility with `l10n_es_aeat_vat_prorrate` due to a problem with ormcache and virtual records.

…ger user for testing.

…e Account mana…"

We have a page for this info, and the previous place was breaking the layout of such part.

As enterprise module `account_accountant` is using another root menu, and other kind of hacks are not desirable, making a dynamic search over the parent of another well know menu (Customers - menu_finance_receivables), makes the trick for having the menu correctly placed in both editions. Thanks to Martin Trigaux for suggesting this solution.

Co-authored-by: Ethan Hildick <[email protected]>

…onies When we have a Greek VAT number (ELXXXXXXXXX), `_parse_aeat_vat_info` was incorrectly returning `GR, XXXXXXXXX, 02`. For AEAT, the country code is always the original one [1], not the official ISO one. We only need the ISO one for checking the inclusion in the European union. Thus, we make the mapping only for this inclusion check. [1] https://sede.agenciatributaria.gob.es/static_files/Sede/Disenyo_registro/DR_300_399/archivos_20/DR_Anexo_349.pdf

Followup of b4fe6bf, as tests were testing the exact incorrect behavior without context.

For French overseas territories (https://en.wikipedia.org/wiki/Overseas_France), there are no intracommunity fiscal rules, but the country code that AEAT requires should be FR, as it can be seen here: https://sede.agenciatributaria.gob.es/Sede/todas-gestiones/impuestos-tasas/declaraciones-informativas/modelo-347-decla_____racion-anual-operaciones-personas_/instrucciones/codigos-paises-territorios.html Thus, we need to call the mapping function differently if you want to convert `EL` to `GR` for getting the European countries than to pass the proper country code. This is done adding an extra parameter for saying if we want to include such replacements, and only being executed when the check about European country is rejected, on contrary than with Greece (EL), that should be included as intracommunity. The country code is now also obtained from the vat itself if the first 2 letter belongs to any country code. TT38835

This module requires the specified cryptography version. Make that explicit in its manifest, now that thanks to odoo/odoo#25549 we can specify the package version. @moduon MT-1067

New hook for managing changes on the function New field for tax_amount

- Enables backwards compatibility and warns the user, to be removed in future migrations

this commit : OCA@2dc5f549f91bda2f97f8b39624c1ea137ec18042~ introduces thirdparty_invoice as a compute store true on account_move table on large database, the initial compute is too long I created a hook and a migrate in order to fill it

… to l10n_es_aeat

Without this field, the update of the 303 addon, throws an error with the counterpart_account_id field that use the company_id in the domain

It includes unit tests.

…rror warnings.warn("Warning is a deprecated alias to UserError.", DeprecationWarning)

This model access is restricted to administrator, so we: - sudo operations that require to access it. - remove an auxiliary field computing it that is not used. Fixes OCA#3016

- remove deprecated flush() method. - replace deprecated invalidate_cache() method with env.invalidate_all().

…ions Steps to reproduce the problem: - PoS installed. - Have a session with only payment methods with outstanding accounts (no cash payments received). - Close and post session. - The resulting journal entry is of type = "Other". Such entries, even if having taxes, won't be included in the AEAT 303 model, as the type = "Other" is not considered till now. That's because it can't be deduced if the operation is regular or not. Let's assume that such operations are always regular (as 99.9% of the times will be), for not having differences in the amounts of the report vs balances in the tax. TT44503

…ting taxes - New hook for managing changes on the function - New field for tax_amount - Call l10n_es_aeat method in SII instead of own (+ remove specific one)

…f tax info

…ests

Fulfills the need (seen in l10n_es_aeat_mod369) to obtain the ISO code of a country based on the country code stored in Odoo. It is an inverse function of _map_aeat_country_code.

Fixes one more remaining unauthorized access to ir.model On export_config_id field, domain calculation searched on ir.model Added sudo() to avoid unauthorized access. fixes OCA#3016

COM (collectivité d'outre-mer - https://es.wikipedia.org/wiki/Colectividad_de_ultramar) are also considered France for the AEAT, so we need to map the existing countries to FR. TT46789

@moduon MT-4519

- Switch to XML-ID names models - Adapt API and calls - Some other minor adjustments - Translations

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[17.0][MIG] l10n_es_aeat: Migration to 17.0 #3387

[17.0][MIG] l10n_es_aeat: Migration to 17.0 #3387

Commits on Mar 21, 2024