🇪🇸Spain @briantes

Hi. Thanks for your help.
We have products in all kind of rates. We can't use "reduced rate" because it is different to "aceites_pasta". At this moment It has the same percentage, but It may change sooner. The tax rate is assigned individually to each product and I have to assign the right tax to every one base on the kind of tax and not by the percentage. It works good with this rates.
But actually, my problem is with json:api. When I add the new rates to those files, I don't know why It throws an error. If I remove my new rates, I works good. Investigating the problem, I have found that in the validate function in TaxNumberConstraintValidator class, $tax_number_type returns "other" type instead of "european_union_vat". And then, $tax_number_type instanceof SupportsVerificationInterface returns false.

I have reopened the issue because It isn't solved.

Sorry for the long response delay. @jacsick The page you are referring to is outdated. You should read the current taxes in the official government website: https://sede.agenciatributaria.gob.es/Sede/en_gb/iva/calculo-iva-repercu...
Since the beginning of October (2024), there is a new tax for bread and other kind of food (2%).

I have changed two files for the new conditions and mantain the others:

$zones['es'] = new TaxZone([
      'id' => 'es',
      'label' => $this->t('Spain'),
      'display_label' => $labels['vat'],
      'territories' => [
        // Spain without Canary Islands, Ceuta and Melilla.
        ['country_code' => 'ES', 'excluded_postal_codes' => '/(35|38|51|52)[0-9]{3}/'],
      ],
      'rates' => [
        [
          'id' => 'standard',
          'label' => $labels['standard'],
          'percentages' => [
            ['number' => '0.21', 'start_date' => '2012-09-01'],
          ],
          'default' => TRUE,
        ],
        [
          'id' => 'reduced',
          'label' => $labels['reduced'],
          'percentages' => [
            ['number' => '0.1', 'start_date' => '2012-09-01'],
          ],
        ],
        [
          'id' => 'super_reduced',
          'label' => $labels['super_reduced'],
          'percentages' => [
            ['number' => '0.04', 'start_date' => '1995-01-01'],
          ],
        ],
        [
          'id' => 'second_reduced',
          'label' => $labels['second_reduced'],
          'percentages' => [
            ['number' => '0.02', 'start_date' => '2024-10-01'],
          ],
        ],
        [
          'id' => 'aceites_pasta',
          'label' => $labels['aceites_pasta'],
          'percentages' => [ 
            ['number' => '0.1', 'start_date' => '2023-01-01'],
          ],
        ],
        [
          'id' => 'exento_alm',
          'label' => $labels['exento_alm'],
          'percentages' => [ 
            ['number' => '0.00', 'start_date' => '2023-01-01'],
          ],
        ],
      ],
    ]);

It works good on the website, but the problem with JSON:API isn't solved.

We review the ticket and recommend that we should not be fixing this issue in consideration with the international community that speaks multiple languages.

The community has aggree to support core in multiple languages for clients and developers as well. We do not see any reason why this specific message should make any exception.

As an alternative, site administrators can use configuration to disable translations alert messages for specific user roles.

The issue should be closed. I don't know any reason why it shouldn't be translatable.

briantes → created an issue.

briantes → created an issue.