diff options
| author | Lucas Perais (lpe) <lpe@odoo.com> | 2018-08-07 09:41:36 +0200 |
|---|---|---|
| committer | Lucas Perais (lpe) <lpe@odoo.com> | 2018-08-20 10:23:27 +0200 |
| commit | b2be451c7ce6184d54a3e1f74781dc24e37cf1a2 (patch) | |
| tree | b7c877e5b324c5b4311df0dff01498bdccf3ded0 /addons/web/static/src/js/views/basic/basic_controller.js | |
| parent | 89bea8ef43de34eacb60b537829e5a504ea49879 (diff) | |
[FIX] point_of_sale: fix rounding logic
Use case specifically for round globally, but the justifications hold anyway
Have a session with one tax, multiple partners, and returns of freight (negative amounts)
When validating a pos.session, the computation of amls was a bit out of logic,
Namely, we grouped tax lines by :
1. their tax id (correct)
2. their partner_id (not wrong but limited)
3. their balance > 0 (wrong)
The justification for point 2 and 3 is two fold:
- Ultimately, the order is level of granularity that really makes sense
It's the order that is paid and therefore that has both legal and business meaning
and on which the amounts are retrieved anyway
- On the order, we litterally make the sum of tax amounts of each line, aggregating
credit and debit under the same variable
It is only logic to do the same for grouping the taxes at validation time
This commit only corrects the behavior for the rounding method 'globally'
OPW 1865700
closes #26203
Diffstat (limited to 'addons/web/static/src/js/views/basic/basic_controller.js')
0 files changed, 0 insertions, 0 deletions
