c2c-oerpscenario team mailing list archive

["Stefan Rijnhart \(Therp\)" <801107@xxxxxxxxxxxxxxxxxx>]

On 23-06-11 13:58, Pieter J. Kersten (EduSense BV) wrote:
> 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?
>

Yes. I would like to add that it is my impression that having a single 
journal for each bank account is more a best practice in bookkeeping 
than just a suggestion in the OpenERP documentation, although 
technically not necessary.

Cheers,
Stefan.

-- 
Therp - Maatwerk in open ontwikkeling

Stefan Rijnhart - Ontwerp en implementatie

mail: stefan@xxxxxxxx
tel: +31 (0) 614478606
web: http://therp.nl

-- 
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 should take journal into account

Status in Account Banking Framework:
  New

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