Merge lp:~openerp-dev/openobject-addons/6.0-opw-50878-pso into lp:openobject-addons/6.0
Proposed by
Priyesh (OpenERP)
Status: | Rejected |
---|---|
Rejected by: | nel |
Proposed branch: | lp:~openerp-dev/openobject-addons/6.0-opw-50878-pso |
Merge into: | lp:openobject-addons/6.0 |
Diff against target: |
28 lines (+6/-4) 1 file modified
account/account_move_line.py (+6/-4) |
To merge this branch: | bzr merge lp:~openerp-dev/openobject-addons/6.0-opw-50878-pso |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
nel (community) | Disapprove | ||
Naresh(OpenERP) (community) | Approve | ||
Review via email: mp+84459@code.launchpad.net |
Description of the change
Hello,
To reproduce the issue:
1. Configure a tax included in price with amount 0.2 also assign tax invoice tax accounts,account tax code
2. Go to accounting -> journal entries -> journal entries
3. Create a move line with credit = 100 and tax = the previously created tax
4. Save
You get 2 lines:
tax line with credit = 16.67 (correct)
base line with credit = 100 (wrong)
base line should be 83.33
Can you please share your views ?
Thanks,
Priyesh
To post a comment you must log in.
Unmerged revisions
- 4945. By Lorenzo Battistini - Agile BG - Domsense
-
[IMP] account: Improved create method of move line to create the correct entries(case:50878)
This will give a strange behavior to the system. Suppose a user, that doesn't know about this feature, enters a value 100(like in your example). This user expects the system to keep this value and not to calculate it. So that's why, we suppose that accountant or users that create vouchers basing on tax included, should enter right amounts in all cases.
We prefer avoid making such calculation on fillable fields because it could cause many problems.