-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Cross Border Trade kicks in even when no tax should be calculated #35592
Comments
Hi @hostep. Thank you for your report.
Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:
For more details, review the Magento Contributor Assistant documentation. Add a comment to assign the issue: To learn more about issue processing workflow, refer to the Code Contributions.
🕙 You can find the schedule on the Magento Community Calendar page. 📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket. ✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel |
Hi @engcom-Lima. Thank you for working on this issue.
|
@magento give me 2.4-develop instance |
1 similar comment
@magento give me 2.4-develop instance |
Hi @engcom-Lima. Thank you for your request. I'm working on Magento instance for you. |
Hi @engcom-Lima, here is your Magento Instance: https://0da443ed116034647d637f0a5494741e.instances.magento-community.engineering |
✅ Jira issue https://jira.corp.magento.com/browse/AC-5982 is successfully created for this GitHub issue. |
✅ Confirmed by @engcom-Lima. Thank you for verifying the issue. |
@engcom-Lima: thank you very much for testing! Could you also try to drag in the product owner of this part of Magento in this discussion and ask their opinion? To make sure this is a valid request? |
Hi @hostep Thanks for your detailed information provided by you. In order to involve product owner I will confirm with my internal team members. Then, I will update you further on this. Thanks!! |
Hello @hostep, We are putting this issue on hold to confirm the expected behavior with the PO. Thanks |
Mail has been sent to PO for his confirmation on the expected result. After his confirmation on the expected result we will proceed further. Thanks |
@engcom-Lima, @engcom-Hotel: this makes no sense, why did the issue got closed? Never even got feedback from the PO so I don't understand why this got closed for no good reason? Update: I just noticed those |
Hey @engcom-Lima: is there already some feedback from the PO about this? And if not, how long is it still going to take? Thanks! |
Hello, is there any further update on this issue or the PR that is in progress please? Also, thank you @hostep for writing this very detailed description of my biggest headache :) |
@engcom-Lima, @engcom-Hotel: is there already feedback from the PO? You said a mail was send to him/her about 8 months ago, I'm assuming it got forgotten, maybe send a reminder (or even better: let the PO answer in public here, it will be much easier to discuss the options that way) ... |
Hi @hostep, Thanks for your patience. As per jira PO had provided feedback as "This issue will be consider as Feature Request and Tax expert input would be needed to handle these complex scenarios" . Thanks |
Thanks @engcom-Lima, am I correct in understanding that you guys will try to involve a tax expert? Or am I considered to find a tax expert myself? |
Hi @crmccann , Need yours intervention here. Thanks |
Hey @crmccann: is there already an update around this? We keep running into clients of ours that run against this issue... |
Hi @hostep, Thanks for your patience! The internal team has recommended to leverage dedicated tax module e.g. Avalara, Vertex etc. to cover tax calculations. Thanks |
@engcom-Lima: I completely disagree. Magento has tax calculation support build in, so why not extend it to support more cases? What do you think? We've been using this PR as a patch on a couple of the shops we maintain for a few months in production and our clients are happy with the results. |
Preconditions and environment
Steps to reproduce
bin/magento setup:install ...
was executed, further configure your instance like this:Setup these tax rates
Setup this one tax rule - while setting it up, make sure to also create the Customer Tax Class 'Other Customer', but don't check it in this tax rule
Create a customer group 'Other Customer' and associate it with the 'Other Customer' Tax Class that you setup in the previous step
In the backoffice, create these 2 customers with these addresses as default shipping & billing address:
Expected result
Following totals should be displayed:
Actual result
Following totals are being displayed:
Additional information
So the cross border trade option in Magento is used to show prices inclusive tax the same across all EU countries even if each EU member state has a different tax rate for a product (
well, in Magento it's implemented for ALL countries, instead of only for EU countries, but that's another bug I still need to report=> update: probably not really a bug but a config option for this would be nice). It does so by changing the prices excl tax so those are different between the EU member states.However, when a customer doesn't have to pay taxes - in the case of a B2B order from one EU member state to another member state for example (which I'm simulating here with the different customer groups that are assigned to the 2 customers) - it makes little sense for the cross border trade option to kick in when no taxes should be calculated.
Possible solution that I found so far but it's maybe not accurate:
The added check on the
$rate
to be higher than 0, means that the cross border trade option does not kick in when no taxes should be calculated.However, the end result is not correct, as it calculates the price excl tax based on the Belgium rate (21%) instead of the Luxembourg rate (17%).So the end result looks like this with this solution:Which is in my opinion still not correct.So to have a full fix, we'll somehow need to calculate 17% tax instead of 21% for prices excl tax in this case when the tax rate is 0.Update: I'm not longer convinced this is a correct assumption. The outcome with this fix might be correct because in the case when you sell to countries outside of the EU, it also subtracts 21% from the price incl tax. So maybe this is the correct outcome then for B2B sales to other EU member states after all... But I'm not an expert in international trade, so I'm not sure ...
Hope this makes sense, because it's quite complicated 🙂
Release note
When this issue gets fixed, release notes:
Fixes subtotal for orders with zero tax when cross border trade is enabled.
Triage and priority
The text was updated successfully, but these errors were encountered: