[V6.01] BIG ISSUE - Bank statement do not handle correctly partial payment

Bug #713116 reported by Frederic Clementi - Camptocamp
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Fix Released
Low
OpenERP R&D Addons Team 3
6.0
Invalid
Medium
Unassigned

Bug Description

- create a supplier invoice for 1116.47
- Import it in a new Accounting/Bank and Cash/bank statement (using import invoice button)

1st problem: Col. Amount and Payment are wrongly named and used - Amount is the money you pay and payment is, in fact, the invoice amount to be paid...

- Now, let's say you pay 1000 and it the full payment (I want a write-off for 116.47). I guess you enter -1000 in col "amount" and go to col "payment" and press F2 to get in the payment voucher. There, you try again to paid only 1000, validate and the accounting entry you get is the other way around it should be:

Entry posted :
Debit: Supplier debt (1000), Debit Adjustment (116.47), Ct Bank (1116.47)
Entry expected :
Debit: Supplier debt (1116.47), Credit Adjustment (116.47), Ct Bank (1000)

Other consequence is that my bank statement is totally wrong because the system change my payment for -1116.47 instead of -1000

This is a serious issue. Thanks for putting it in priority, guys.

Related branches

Revision history for this message
Joël Grand-Guillaume @ camptocamp (jgrandguillaume-c2c) wrote :

Dear all,

I confirm this bug exists and is quite important for the Accounting !

Regards,

Joël

Changed in openobject-addons:
importance: Undecided → High
status: New → Confirmed
Changed in openobject-addons:
assignee: nobody → OpenERP R&D Addons Team 3 (openerp-dev-addons3)
importance: High → Medium
Revision history for this message
qdp (OpenERP) (qdp) wrote :

hi,

i'm not getting this error at my side. Can you check my screenshots and see if you encode correctly the payment?

Thanks

Revision history for this message
qdp (OpenERP) (qdp) wrote :
Revision history for this message
qdp (OpenERP) (qdp) wrote :
Revision history for this message
qdp (OpenERP) (qdp) wrote :
Revision history for this message
qdp (OpenERP) (qdp) wrote :

as far as i understand, you simply encoded wrongly the bank statement and let -1116.47 as amount instead of -1000 (amount really paid, removed from your bank account and written down on the paper bank statement you received).

So, except if i missunderstood something, i think that there is no bug at all here. I'm setting this bug as invalid.

Thanks for the contribution,
Quentin

Changed in openobject-addons:
status: Confirmed → Invalid
Revision history for this message
Frederic Clementi - Camptocamp (frederic-clementi) wrote :

Hi quentin,

Ok, you are right there is a way to make it correct but this is so unfriendly and confusing....I like very much the payment_voucher but behind a bank statement this is a nightmare...unless you can fix 2 things maybe:
- 1 - (same example as above...) once in the payment_voucher, the total at the top is 1000 and the amount is 1116.47 ; if you select reconcile with write-off, the write off amount does not appear (but it is correctly computed once you validate) + if you change the selection again on payment diff., you suddenly see all invoices/credit notes reletive to this supllier (very confusing)
- 2 - At the bottom, you see the 2 buttons of the payment _voucher (that you must avoid...that was my mistake) + 2 buttons (OK and cancel as well) just below. please see attached doc. I think 2 buttons should be enough ;)

But to be honest, now I wondering what is the point of using import invoices via bank statement since we have the payment_voucher...both post payment entries in a similar way.

Thank you and good week end in case you're not gone already

Frederic

Revision history for this message
Mustufa Rangwala (Open ERP) (mra-tinyerp) wrote :

We can disable two buttons from the form view and also disable six fields (pay amount, pay method, date, etc..) when user is on bank statement.

Changed in openobject-addons:
status: Invalid → Confirmed
importance: Medium → Low
Changed in openobject-addons:
status: Confirmed → In Progress
Revision history for this message
filsys (office-filsystem) wrote :

@Joel +1
Although it seems a usability issue, I agree with Joel that is of great importance in accounting because it can generate the accounting implications difficult to detect and subsequently repaired.
Thanks

Revision history for this message
Purnendu Singh (OpenERP) (purnendu-singh) wrote :

Hello,

I have fixed the problem in lp:~openerp-commiter/openobject-addons/trunk-dev-addons3-psi2

Revision No: 4644
Revision ID: <email address hidden>

Thanks
PSI

Changed in openobject-addons:
status: In Progress → Fix Committed
Revision history for this message
Mustufa Rangwala (Open ERP) (mra-tinyerp) wrote :

Purnendu Singh,

Its take write-off string for sale/receipt also so you have to move it in if condition

if inv.payment_option == 'with_writeoff':
   name = inv.comment

otherthings in your diff are correct.

thanks,
mra

Changed in openobject-addons:
status: Fix Committed → Confirmed
milestone: none → 6.1
Changed in openobject-addons:
status: Confirmed → In Progress
Revision history for this message
Purnendu Singh (OpenERP) (purnendu-singh) wrote :

Hello Mustufa Rangwala,

Code improved as per your suggestion.

Thanks,
PSI

Changed in openobject-addons:
status: In Progress → Fix Committed
Revision history for this message
Mustufa Rangwala (Open ERP) (mra-tinyerp) wrote :

Hello Frederic Clementi,

For comment #7 we have implemented point 2, for point 1 you can create new bug as wishlist.

Thank you,
mra

Changed in openobject-addons:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.