c2c-oerpscenario team mailing list archive

["qdp \(OpenERP\)" <qdp-launchpad@xxxxxxxxxxx>]

Hello,

thanks for the bug report. Unless i agree with you that the current behavior is not good, let me clarify some points:
*we are currently reviewing the account_voucher module for it to accept write-off. This feature won't allow us to make some check rules like "the total of the voucher that should be equal to the total of the mount lines".
*the problem here seems more that you created a _new_ line (like if it was an existing invoice for that partner) wich is not what that screen was intented to: i think that's there we should have put some check.
*i guess that the above point is guilty of the weird creation of the accounting entries that you described on point 2.

I'm confirming this bug because indeed i think that we still have some
work to do on that module (and should be done for rc2), but also i'd
like to emphasize that our current working process doesn't allow anymore
the drivers to set the milestone themselves but i don't think that we
already communicate about that... so in the meanwhile, please do not put
milestone yourself otherwise we can't keep track of wich bugs are
assigned to our development teams.

Thanks for your contribution,
Quentin

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

** Changed in: openobject-addons
     Assignee: (unassigned) => OpenERP R&D Addons Team 3 (openerp-dev-addons3)

** Changed in: openobject-addons
   Importance: High => Medium

-- 
[6.0][account_voucher] customer payment seems broken
https://bugs.launchpad.net/bugs/672638
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.

Status in OpenObject Addons Modules: Confirmed

Bug description:
Hello,

using addons #3894, with demo data + account_voucher module + default chart of account.
Try to encode a new "customer payment" with the following data:
- partner: Axelor
- journal: bank (test)

Also encode one statement line specifying only the "amount" field with 100.

Now try to validate the voucher. Well it will valid!!
But there are critical bugs:
1) the voucher "Paid Amount" field has been left to 0. I think some check was expected against the sum of the lines, just like for bank statements instead. Look in the voucher list view for instance, that voucher has an amount of 0 while it's wrong!
2) look at the account moves in the "journal items" tab:
both debit an credit moves are done using the same partner account!!!
Instead, the debit move line should be done in the account specified at the voucher level, just like a bank statement would do.

This makes "customer payment" via voucher unusable currently I think.
Hope this helps