Actual tax rate not shown for zero tax

[twosg]

Preconditions (*)

1. Magento 2.X.X (including current 2.4.3)

Steps to reproduce (*)

1. Create two new tax rates and add them to the "Rule1" default tax rule. One rate for Germany with 0% and one for Netherlands with 21%.
   

2. Set Configuration->Tax according to this:
   
   

Expected result (*)

As the settings "Display Full Tax Summary" as well as "Show Zero Tax Subtotal" are enabled, I would expect to see the actual tax rate applied, even though it is zero/0%.

Actual result (*)

1. In the estimate block select "Netherlands" as country. You will see the 21% tax rate:
   
2. Now switch the country to Germany. It does not show the actual tax rate, instead it shows nothing but "Tax":
   

From my point of view it is critical because there are tax administrations as well as bookkeeping systems which take it very seriously.

---

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @twosg. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

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:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 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.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Delta]

Hi @ Sven Geiß

Thank you for reporting the issue.
We tried to reproduce the issue on the Magento 2.4-develop branch but the issue is not reproducible.

Steps performed:
1:Install a clean version of Magento version 2.4-develop
2:Create two new tax rates and add them to the "Rule1" default tax rule. One rate for Germany with 0% and one for Netherlands with 21% as shown in the screenshot

3: then go to configuration<sales<tax<calculation settings<catalog prices<including tax
go to configuration<sales<tax<calculation settings<shopping cart display settings as shown in the screenshot

Result: In the estimate block select "Netherlands" as country. You will see the 21% tax rate as shown in screenshot

Now switch the country to Germany. It does not show the actual tax rate, instead it shows nothing but "Tax"

Note:we have applied 0 %tax rate to Germany , as it not reflected on frontend as it is a default magento behaviour

please let me know if this is exactly what your issue was or if there is some more configuration required from my end. Will update accordingly.
Thanks!

[twosg]

Note:we have applied 0 %tax rate to Germany , as it not reflected on frontend as it is a default magento behaviour

That is the actual issue. There are different tax cases where you want to show the underlying reason, like "zero rated" (because some products are zero rated) or "intracommunity delivery" for the B2B area.

What is the reason for not showing the rate at all when it is 0%? I think at least when Display Full Tax Summary is enabled, it should show the rate with 0%.

[engcom-Lima]

Hi @twosg,
Thank you for reporting the issue.
As per this comment the issue is reproducible however it is the expected behaviour of Magento 2.

But w.r.t this comment it can be considered as a feature improvement and moved ahead.

Based on this I am moving the ticket ahead as a feature improvement.

Thanks!