-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tax with Counterparty #14
Comments
@blaggacao No comprendo muy bien el issue, veo que el impuesto (10,20) no lo está mostrando en la imgen 3, pero no entiendo la imagen 4. Nosotros no hemos tenido ese problema, es posible que tenga relación con la forma cómo gestionas el CREE. Quita el CREE del producto y realiza de nuevo la prueba. Si puedes hacer un screencast nos ayudaría a entender mejor el isuue. |
Para replicar es suficiente crear un grupo de impuestos con dos hijos uno siendo la contrapartida del otro. Para aclarar: Claramente esperaba que ustedes tambien hayan encontrado ese bug. 😄 Lo que pasa: |
The reason is that code taxes are not supported in the POS, while we make heavy use of those... Obviously this won't work.... More precisely, one of the children - the counterparty - is a code tax, which is simply ignored, while its predecessor child is applied, beeing a percentage tax. |
You can use the reinstalled "division" type to get the correct counterparty amount:
Well you can also just do -0.8 +0.8 without any of the above... 😸 |
We have discussed this, I think, but I'm not 100% affirmative on congruency of the issues, yet.
I have noticed, that a tax with counterparty used in the POS, while generating a wrong receipt (image 1 & 2), the synched order is correct (image 3), resulting in a payment difference (image 4)
Image 1
Image 2
Image 3
Image 4
@dkrimmer84 It seems that counterparty is not employed in POS. Can you confirm that it was this issue that you solved on master?
/cc @xyklex
The text was updated successfully, but these errors were encountered: