Duplicate statement detection can misfire using multiple accounts with same parser.
Bug #801107 reported by
Stefan Rijnhart (Opener)
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Account Banking Framework |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Hi,
we have two different bank accounts with the same characteristic name and date pattern, as bank statements are made available at regular intervals. This triggers duplicate detection, as it only takes statement name and date into account. Of course, statements for two different accounts are never duplicates.
As each bank account should have their own journal ("ideally", says the OpenERP documentation: http://
Cheers,
Stefan.
Related branches
summary: |
- Duplicate statement detection should take journal into account + Duplicate statement detection can misfire using multiple accounts with + same parser. |
To post a comment you must log in.
Lets see if I got you right. To rephrase this problem and fix in my own words:
You have two bank accounts for which you use the same import parser and thus share the same statement numbering generator. When searching for processed statements with the current search parameters, there is no way of telling which statement belongs to which account, which can lead to wrong duplicate identification and thus wrongly skipped statements.
You suggest that adding a journal_id to the search parameters should make that distinction, based on OpenERP's advisory to use a unique journal for each owned bank account, and assuming that every OpenERP user will follow this advise.
Is this correct?