c2c-oerpscenario team mailing list archive

["Jan Verlaan \(Veritos\)" <833605@xxxxxxxxxxxxxxxxxx>]

@fabien, you are right as far as it concerns the invoice, but the
discussion is about bankstatements.

Bankstatements are reflections of transactions done at the bank into the past.
A statement can contain transactions that fall into more then one period and that generates the problem Sebastian in logging. This depends on how many statements you receive from your bank. Into the Netherlands it is common to have monthly paper statements. As a result many people do check every day or week their banktransactions file via internet-banking.
Those transactions can fall into several periods.
As Stefan mentioned the account-banking module does not use periods anymore. They are not of interest at all for banking transactions.

So I agree that the period can be removed from the bank transactions or
as alternative (to keep in line) is hidden and calculated separately on
every bank transaction line based on the transaction date. Keep in mint
that a closed period could then still create a problem while this is not
that important so a choice should be given to reopen that period or the
nearest open period could be taken.

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

Title:
  period on bank statement

Status in OpenERP Modules (addons):
  Opinion

Bug description:
  Hi all
  This is not a code bug but a fonctionnal problem.

  Indeed bank statement have a field period_id and when you fill a bank statement this field is mandatory and so your bank statement can have only one period.
  In my case I am importing bank statement from external system (such amazon, paypal, bank cic). This external don't create one bank statement per month but there generate bank statement each X days. The problem is that an external bank statement can have move line on two periode. As OpenERP require one period per bank statement, I have two split my external bank statement in two, which is not very user friendly (one bank statement from the external system should match with one bank statement in OpenERP).

  This problem of period is not only present in the bank statement but
  in generaly on each object (invoice, account_move..) Indeed by default
  OpenERP, allow to have a period that don't match with the date, and
  it's why there is a editable field period_id on bank statement and on
  invoice, account_move and account_move line.

  In France for example, the period should match with the date it's why
  we are using the module account_date_check. But it's not perfect,
  Indeed this module don't solve the problem on bank statement. And also
  the period_id on the invoice is still editable but very useless (the
  user can 'choose' only the correct period, it will be better to have a
  function field)

  So my first question is:
  Did some country need this feature : "allow to have account move line with a date that doesn't match with the period" ?
  Regarding the answers 3 solutions :
  - If nobody use it, It's better to remove this useless feature.
  - If just some country use it, this functionality should be extracted and done by an external module.
  - If only France require consistent date and period, I will create an extra module that will remove the period fields where is useless, keeping it in read-only in some view, and replacing it by a function fields (it will be cleaner than the account_date_check)

  What do you think? Which solution look's the best for everybody? Did I
  miss something?

  Best Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/openobject-addons/+bug/833605/+subscriptions