Openbravo Issue Tracking System - POS2
View Issue Details
0057531POS2POSpublic2024-12-23 12:122025-01-22 10:15
gowthamveeramuthu 
jorgewederago 
highmajoralways
scheduledopen 
5
 
24Q2 
No
0057531: in Backoffice Sales order Payment details is not same as customer paid
The amount paid by customer is not showing correctly in Sales order's -> payment Details tab.
sales total amount is 18.90
customer paid
1. 0.60 as cash
2. 100 as voucher/card (overpayment)

in Sales order -> payment details tab its showing as
1. cash => received amount as 1 (linked payment_in shows 0.60)
2. voucher => received amount as 18.50 (linked payment_in shows 100)
3. cash => received amount as -0.60 (there was no -0.60 showed in POS while doing payment. but in receipt shown as change)
https://livebuilds.openbravo.com/context/retail_pos2_modules_pgsql [^]

add product "HeadLamp Ultralight" (18.90)
click on pay
enter 0.60 in keypad and click cash.
now cash payment 0.60 is registered.
enter 100 in keypad and click on voucher
now voucher payment 100 is registered.
click on "Done"
check the sales order details in Backoffice
No tags attached.
png POS Receipt.png (158,048) 2024-12-23 12:13
https://issues.openbravo.com/file_download.php?file_id=20680&type=bug
png

png POS payment .png (144,023) 2024-12-23 12:13
https://issues.openbravo.com/file_download.php?file_id=20681&type=bug
png

png PaymentDeatils-all.png (333,983) 2024-12-23 12:13
https://issues.openbravo.com/file_download.php?file_id=20682&type=bug
png PaymentDeatils1.png (97,418) 2024-12-23 12:13
https://issues.openbravo.com/file_download.php?file_id=20683&type=bug
png

png PaymentDeatils2.png (95,858) 2024-12-23 12:13
https://issues.openbravo.com/file_download.php?file_id=20684&type=bug
png

png PaymentDeatils3.png (99,724) 2024-12-23 12:13
https://issues.openbravo.com/file_download.php?file_id=20685&type=bug
png
Issue History
2024-12-23 12:12gowthamveeramuthuNew Issue
2024-12-23 12:12gowthamveeramuthuAssigned To => Retail
2024-12-23 12:12gowthamveeramuthuTriggers an Emergency Pack => No
2024-12-23 12:13gowthamveeramuthuFile Added: POS Receipt.png
2024-12-23 12:13gowthamveeramuthuFile Added: POS payment .png
2024-12-23 12:13gowthamveeramuthuFile Added: PaymentDeatils-all.png
2024-12-23 12:13gowthamveeramuthuFile Added: PaymentDeatils1.png
2024-12-23 12:13gowthamveeramuthuFile Added: PaymentDeatils2.png
2024-12-23 12:13gowthamveeramuthuFile Added: PaymentDeatils3.png
2024-12-24 07:12guillermogilAssigned ToRetail => jorgewederago
2024-12-24 07:12guillermogilStatusnew => acknowledged
2024-12-26 07:34Bimla_vmAssigned Tojorgewederago => Bimla_vm
2024-12-26 07:34Bimla_vmStatusacknowledged => scheduled
2025-01-10 17:43aaroncaleroNote Added: 0174015
2025-01-10 17:43aaroncaleroTypedefect => design defect
2025-01-22 10:15Bimla_vmAssigned ToBimla_vm => jorgewederago

Notes
(0174015)
aaroncalero   
2025-01-10 17:43   
Moving to design defect. We need input from product management to define the behavior in this cases and then implement what it is specified.

For context: the code that is triggering this strange behavior has existed for almost 10 years