c2c-oerpscenario team mailing list archive

["Pieter J. Kersten \(EduSense BV\)" <801107@xxxxxxxxxxxxxxxxxx>]

That may be, but there are valid reasons to use multiple journals per
bank account. So I wouldn't count on it.

I suggest to increase the traceability instead of assuming manual
conformity. Statements already have a link to the imported file, so by
adding a link to the settings when creating an import file, one could
check the bank account itself, which seems a much cleaner approach to
me. One could even generate warnings about different import parsers used
beforehand.

If you can wait, I'll fix this in a week or two. Otherwise, you can try
it yourself and propose a fix here.

Thanks for reporting.

** Changed in: account-banking
       Status: New => Confirmed

** Changed in: account-banking
   Importance: Undecided => Medium

-- 
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