credativ team mailing list archive

["Amit Bhavsar \(Open ERP\)" <900790@xxxxxxxxxxxxxxxxxx>]

Hello DR Ferdinand,

We have implemented a Account_assert for the following manner.
1) Depreciation date  start with 1st January, If we have don't set a "Prorata Temporis" .
2) If have used a "Prorata Temporis" then depreciation date start from the purchase date, which you can give it as a manually when you want to start/use it. So I think it is working same as a "Usage date" as you specified in bug report.

So this is not a bug it's your suggestion and also not a generalise
issue. That's why I am setting this as "Opinion".

@Experts: Would you please share your view on this.

Thanks and more suggestions are welcomed!

** Changed in: openobject-addons
       Status: New => Opinion

-- 
You received this bug notification because you are a member of OpenERP
Framework Experts, which is subscribed to OpenERP Addons.
https://bugs.launchpad.net/bugs/900790

Title:
  account asset - depreciation starts with usage

Status in OpenERP Addons (modules):
  Opinion

Bug description:
  
  quote from
  http://www.ehow.com/info_8413513_depreciation-start.html

  If you buy a car then depreciation starts the moment you drive it off
  the lot. For business purposes, however, depreciation starts when an
  item is placed into service. In order to claim a tax deduction, the
  item must officially start usage before the end of the tax year.

  hence we need an optional "start usage date" which is used instead of
  purchase date if entered.

  the purchase date must be taken from the invoice - invoice-date (mandatory)
  it will almost never be 
  'purchase_date': lambda obj, cr, uid, context: time.strftime('%Y-%m-%d'),
  this is a source of errors,especially if the invoice arrives in the month after issued from the supplier.

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