c2c-oerpscenario team mailing list archive
-
c2c-oerpscenario team
-
Mailing list archive
-
Message #27213
[Bug 801107] Re: Duplicate statement detection can misfire using multiple accounts with same parser.
** Summary changed:
- Duplicate statement detection should take journal into account
+ Duplicate statement detection can misfire using multiple accounts with same parser.
--
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/801107
Title:
Duplicate statement detection can misfire using multiple accounts with
same parser.
Status in Account Banking Framework:
Confirmed
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://doc.openerp.com/v6.0/book/3/3_7/accounting_entries.html),
taking the journal into account when detecting duplicate statements
should solve the problem.
Cheers,
Stefan.
To manage notifications about this bug go to:
https://bugs.launchpad.net/account-banking/+bug/801107/+subscriptions
References