Bank Statement Import Generate Unique ID
Some bank statement sources (e.g. some CSV/sheet exports or camt files) do not provide a unique identifier for their transactions. Without it, importing an overlapping period creates duplicate statement lines.
This module adds an option on bank journals to generate a unique_import_id for statement lines that come without one. The value is a SHA-256 hash of the normalized account number, date, payment reference, amount, reference and partner name. An identifier provided by the source always takes priority.
Identical transactions within the same import are numbered (<hash>, <hash>-2, <hash>-3, …), so they are all imported, while importing the same statement again still ignores all of them.
Table of contents
Configuration
Go to Invoicing > Configuration > Journals, open a bank journal and enable Generate Missing Import IDs.
Only statement lines imported after enabling the option get a generated import ID. To set it for the existing statement lines of the journal that have none, click Generate for Existing Lines next to the option. Lines whose generated import ID is already used by another line are skipped and reported, as they may be duplicates. Check them manually.
Usage
Only enable this option for journals whose source provides no transaction identifier.
Identical transactions (same account number, date, payment reference, amount, reference and partner name) can only be told apart within the same import. If an import ends between two identical transactions of the same day, the second one gets the same identifier in the next import and is ignored as already imported. Therefore always import complete days, and do not enable this option when such identical transactions are common and statements may cover partial days.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Michael Tietz (MT Software) <mtietz@mt-software.de>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
Current maintainer:
This module is part of the OCA/bank-statement-import project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo-addon-account-statement-import-generate-unique-id 18.0.1.0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| odoo_addon_account_statement_import_generate_unique_id-18.0.1.0.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Release files / odoo_addon_account_statement_import_generate_unique_id-18.0.1.0.0.1-py3-none-any.whl
| Download URL | odoo_addon_account_statement_import_generate_unique_id-18.0.1.0.0.1-py3-none-any.whl |
|---|---|
| Size | 30.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7a00cb6e9b3dbb43adc538ef71030c7a1c78dbded26b511a36ab7cba15d6e686
|
|
BLAKE2b-256 checksum How to use checksums |
d75ab1d922dea6e8fabe9aeabdeddcf3ea7bddce821c5168265879f81a94daf2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for odoo-addon-account-statement-import-generate-unique-id 18.0.1.0.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
