Skip to content

[16.0][FIX] l10n_es_aeat_mod303: Caso de uso cuando la casilla 87 es igual a 0 en el informe anterior #4337

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

Open
wants to merge 1 commit into
base: 16.0
Choose a base branch
from

Conversation

EmilioPascual
Copy link
Contributor

@EmilioPascual EmilioPascual commented Aug 4, 2025

Si en el informe anterior la casilla 87 es igual a 0, el resultado es para compensar y la 71 es negativa, entonces también se debe traer a la 110 del informe actual la cantidad pendiente de compensar.

@ArantxaSudon @rafaelbn por favor revisad.

@moduon MT-10979

@OCA-git-bot
Copy link
Contributor

Hi @pedrobaeza,
some modules you are maintaining are being modified, check this out!

… is equal to 0 in previous report.

In the previous report when box 87  is equal to 0, result is 'To compensate' and box 71 is negative, then box 110 must also contain pending fees to compensate.

@moduon MT-10979
@EmilioPascual EmilioPascual force-pushed the 16.0-l10n_es_aeat_mod303-87_equal_to_0 branch from 163713e to c70178f Compare August 4, 2025 11:27
Copy link
Contributor

@ArantxaSudon ArantxaSudon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Revisado funcionalmente

Confirmadas factura y sacados los 303 del 2025 y primer trimestre del 2026 y traslada los importes de resultados negativos si la casilla 87 es igual o superior a cero

Muchas gracias @EmilioPascual

@pedrobaeza pedrobaeza added this to the 16.0 milestone Aug 7, 2025
@@ -500,27 +500,27 @@ def test_model_390_using_303_03(self):
self.model390_2018.button_calculate()
# Check casilla_85, casilla_95, casilla_97, casilla_98, casilla_662
self.assertAlmostEqual(self.model390_2018.casilla_85, 0.0, 2)
self.assertAlmostEqual(self.model390_2018.casilla_95, 2302.12, 2)
self.assertAlmostEqual(self.model390_2018.casilla_95, 3107.37, 2)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Estos datos no deberían cambiar, y más si lo que se hace es tener disponible cantidad para compensar, ¿no? En cambio, la cantidad a ingresar está creciendo. Parece más una indefinición de los datos iniciales de este test.

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.

4 participants