Skip to content

[19.0][MIG] l10n_es_account_statement_import_n43 - #4644

Merged
OCA-git-bot merged 65 commits into
OCA:19.0from
Studio73:19.0-mig-l10n_es_account_statement_import_n43
Feb 9, 2026
Merged

[19.0][MIG] l10n_es_account_statement_import_n43#4644
OCA-git-bot merged 65 commits into
OCA:19.0from
Studio73:19.0-mig-l10n_es_account_statement_import_n43

Conversation

@ferran-S73

Copy link
Copy Markdown
Contributor

No description provided.

pedrobaeza and others added 30 commits December 2, 2025 12:15
…bank_statement para importar extractos bancarios N43
…on monedas distintas de euros segun issue OCA#217 y basado en comentario de @fgarciag2001
…baciones extra para obtener el partner extraídas del n43 de Bankia Y Sabadell
Improvements
------------

* Counterpart account automatically detected from N43 type (deactivated for now)
* Tests
* Metafiles updated
* Test adapted to Python 3
* Test coverage improved
…te_type

With this, this is compatible with tests that creates journals before this
module is loaded.
* Standard procedure
* Override method for adding the supported format
* README by fragments
* Tests adapted for new date format and order
…tween type of exception raised adn type of exception catched
Currently translated at 100.0% (14 of 14 strings)

Translation: l10n-spain-12.0/l10n-spain-12.0-l10n_es_account_bank_statement_import_n43
Translate-URL: https://translation.odoo-community.org/projects/l10n-spain-12-0/l10n-spain-12-0-l10n_es_account_bank_statement_import_n43/gl/
…compatibility with BBVA files (OCA#1056)

Some statement files include BOM data (https://es.wikipedia.org/wiki/Marca_de_orden_de_bytes) at the beginning of the file, making them non readable by current parser, as fixed positions are moved in these cases and thus expected data is not matched.

As ASCII, which is the encoding used in files according specification, is a subset of UTF-8, there's no danger in using it with the variant 'utf-8-sig' for handling if BOM marker is present or not.
…n tests with other statement import modules

Journal in context should be available since the beginning, as it can be used in default get for example.
…r importers

- Don't store in `note` field temporary data for later operations
- Don't force N43 partner detection if other importers fill `note` field.
- Rename some methods for avoiding possible collapses.

Closes OCA#1350 OCA#1363
Currently translated at 100.0% (15 of 15 strings)

Translation: l10n-spain-13.0/l10n-spain-13.0-l10n_es_account_bank_statement_import_n43
Translate-URL: https://translation.odoo-community.org/projects/l10n-spain-13-0/l10n-spain-13-0-l10n_es_account_bank_statement_import_n43/es/
…lient

Other modules can add a partner called "Test partner", as the name is very generic,
provoking an error in the test. We specify another name that don't collapse with other
data for avoiding it.
@ferran-S73
ferran-S73 force-pushed the 19.0-mig-l10n_es_account_statement_import_n43 branch 2 times, most recently from 213afc6 to bfd846e Compare December 2, 2025 12:05
@pedrobaeza

Copy link
Copy Markdown
Member

/ocabot migration l10n_es_account_statement_import_n43

@OCA-git-bot OCA-git-bot added this to the 19.0 milestone Dec 2, 2025
@OCA-git-bot OCA-git-bot mentioned this pull request Dec 2, 2025
40 tasks

@pedrobaeza pedrobaeza left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

¿Puedes incluir #4808 antes del commit de migración?

Por otro lado, en el mensaje de commit de la migración, puedes quitar [19.0]. Eso solo se pone en el título del PR.

raise exceptions.ValidationError(
self.env._("Record type %s is not valid.") % raw_line[0:2]
self.env._(
"Record type %(record_type)s is not valid.",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Aquí se está cambiando la cadena origen, pero no se han tocado las traducciones, perdiéndose. ¿Estás seguro que este cambio te lo pide pre-commit? Hay solo una cadena de sustitución, por lo que en esos casos, no hace falta, ya que se puede identificar posicionalmente de forma unívoca.

You may be interested in not importing certain statement lines if they
come from complicated operations like third party payment providers
with several charges/incomes, and you are interested in importing them
by other means.

This commit includes a new field at journal level for defining an
excluding pattern that allows this.

TT59339
@Alexgars73
Alexgars73 force-pushed the 19.0-mig-l10n_es_account_statement_import_n43 branch from bfd846e to 8d6261d Compare February 9, 2026 10:26
@Alexgars73
Alexgars73 force-pushed the 19.0-mig-l10n_es_account_statement_import_n43 branch from 8d6261d to 4bf8612 Compare February 9, 2026 10:32

@pedrobaeza pedrobaeza left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Gracias!

/ocabot merge nobump

@OCA-git-bot

Copy link
Copy Markdown
Contributor

On my way to merge this fine PR!
Prepared branch 19.0-ocabot-merge-pr-4644-by-pedrobaeza-bump-nobump, awaiting test results.

@OCA-git-bot
OCA-git-bot merged commit 42617ea into OCA:19.0 Feb 9, 2026
7 checks passed
@OCA-git-bot

Copy link
Copy Markdown
Contributor

Congratulations, your PR was merged at 3a7accc. Thanks a lot for contributing to OCA. ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.