No warning when Paid Amount and Invoice amount do not match

Bug #872854 reported by jlinkels
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
Invalid
Low
OpenERP R&D Addons Team 3

Bug Description

Go to Accounting -> Customer Invoices
Select an open invoice
Click the Payment button
In the Pay Invoice Window, the Amount Paid is proposed. Say 75.00
In the Pay Invoice window, select a Payment Method
The open invoice of the customer appears
Enter an amount to be paid, less than the Open Balance, say 70.00
FORGET to adjust the Paid Amount on top of this form, leave at 75.00
Press Validate
The payment is accepted without any warning.
The journals are booked with this result:
- Debt of the Customer to the Company becomes 0.00 on the Customer form
- The bank account of the company is debited for the Amount Paid: 75.00
- The Customer invoice remains Open for the Open Balance 5.00
This can only be corrected by entering journal items manually.
Any attempt to correct this by entering another payment, say:
Amount paid 0.00
Amount on Customer Invoice 5.00
Will NOT correct the situation. It should, because the first time
the mistake was made the amounts were accepted and booked. I
expect that this payment would be processed in the same way.
This is a vey messy situation, which is almost impossible
to find and correct due to a human error. The system should at least
warn for it, but even better not accept a payment where the
amounts received do not match the change in bank account.

jlinkels

Revision history for this message
Jignesh Rathod(OpenERP) (jir-openerp) wrote :
Revision history for this message
Jignesh Rathod(OpenERP) (jir-openerp) wrote :

Hello jlinkels,

I have checked this issue at my end.

I am confirming issue for this points :

1) Warning message when you not adjust payment amount .
2) Customer-> account tab there should be display amount
     Total payable or Total receivable.
3) Account entry It should display paid amount.

Thanks.

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

Hi,

I have watched your video carefully, and as far as I can see you correctly reproduced my reported bug.

The absence of a warning is clear. What do you propose? To prohibit executing the payment if
the total of all amounts is not equal to Amount Paid on top of that form?

At 01:10 of your video you see that the bank account is debited for 75.00 (which is clearly not)
At 01:30 you show that the accounting tab in the customer form shows an open amount of 0.00

I think we agree on that.

I assume that when this is solved, it will also be possible to make a second payment for the open balance which is then processed correctly as well. Please check that as well after fixing.

Regards
jlinkels

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

Hello jlinkels,

Although you find it a bit messy, the voucher is *made* to allow differences between the paid amount and the total splitted by voucher lines.

This is to allow to easily treat situations like:
1) your customer paid 90€ to pay 2 invoices of 50€, but because he doesn't agree to pay the rest (because he wasn't glad of your services for example), you want to fully reconcile the 2 invoices with the 90€ received. What you encode is: paid amount 90€, 50€ on both invoices. By default, the missing 10€ will be left on his customer account (meaning: the 2 invoices are paid/reconciled but the customer still own you 10€), but you can change the payment difference fields.selection and set it to be taken from a different account (choose a writeoff account to depict the 2 invoices are paid/reconciled and the missing 10€ are definitively lost)
2) a customer paid 60€, but you don't know what he's paying exactly. You can just encode the paid amount to 60€ and leave everything at 0 on the lines, that means you encode the payment but don't assign it on (don't try to reconcile it with) existing invoices. That's a very nice feature because it's easy in every case (what if you receive a prepayment and there is no existing invoice for this customer?) and if you change the defaults, every amount missing/overpaid will be set on the customer account and you will find it again at the next voucher encoding.

So, to sum up: this ain't a bug but a feature. I'm setting the bug status accordingly.

Thanks,
Quentin

Changed in openobject-addons:
status: Confirmed → Invalid
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.