Magento 2.4.4: Bug in the tax calculation for customers with a VAT number

[Jackom9147]

Preconditions and environment

I am experiencing a problem with Magento 2.4.4:

I have created two customer groups: Bronze and Bronze_Vies (for European customers with valid VAT number). The Bronze_Vies group should be tax-free, but:

New users: They are not always correctly assigned to the Bronze_Vies group, even with a valid VAT number.

Tax calculation: Even if assigned to the correct group, some customers still see taxes in the checkout. This happens inconsistently and sometimes the taxes only appear after choosing a payment method. I need to understand if this is a known bug in Magento 2 and how I can fix it.

Steps to reproduce

Reproduction of bug in account creation:

Backend configuration: Enable automatic assignment to customer group and choose the group ‘Bronze_vies’ for customers with a valid VAT number.
Frontend account creation: Register a new account by entering a valid VAT number.
Check assignment: Check whether the account has been correctly assigned to the group ‘Bronze_vies’.

Reproduction of bug in tax calculation:

Log in with account: Log in to the newly created account (which should be in the ‘Bronze_vies’ group).
Addition to cart: Add products to cart.
Check Taxes: Check if taxes are calculated correctly in the order summary and checkout.
Test with different payment methods: Try completing the checkout with different payment methods to see if the problem recurs.

Expected result

Expected Result:

Correct assignment: The customer with a valid VIES VAT number should automatically be assigned to the group ‘Bronze_Vies’.
Tax exemption: The customer of the group ‘Bronze_Vies’ should pay no tax, neither in the shopping cart nor in the checkout.

Actual result

Current Result:

Incorrect assignment: In some cases, the customer is not correctly assigned to the group ‘Bronze_vies’.
Incorrect calculation of fees: Even when the customer is in the correct group, the fees are calculated incorrectly and applied at checkout.

Additional information

No response

Release note

No response

Triage and priority

• 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 @Jackom9147. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

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

[m2-assistant]

Hi @engcom-Delta. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - 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 @Jackom9147 ,

Thanks for your reporting and collaboration.
We have verified the issue in 2.4-develop instance, but we are unable to reproduce the issue. Kindly refer the screenshots.

Steps to reproduce

1. Create customer groups: Bronze (for European customers with valid VAT number)
2. Create customer groups Bronze_Vies The Bronze_Vies group should be tax-free.
   Observe we are unable to provide tax-free class for bronze_vies customer group.

Can you please provide more testing steps.

Thanks.