None of this worked... thought that maybe upgrading would do because it's an insert to the database but it didn't.

The error is:

2025-04-01 11:29:20,160 1 ERROR odoo odoo.sql_db: bad query: INSERT INTO "account_tax" ("active", "amount", "amount_type", "company_id", "country_id", "create_date", "create_uid", "description", "facturae_code", "include_base_amount", "invoice_label", "is_base_affected", "l10n_es_bien_inversion", "l10n_es_edi_facturae_tax_type", "l10n_es_type", "name", "price_include", "sequence", "tax_exigibility", "tax_group_id", "tax_scope", "type_tax_use", "write_date", "write_uid") VALUES (true, '10.0000', 'percent', 1, 68, '2025-04-01 11:29:16.205726', 2, '{"en_US": "VAT 10% import (services)"}', '01', false, DEFAULT, true, false, '01', 'sujeto_isp', '{"en_US": "10% EX S"}', false, 1, 'on_invoice', 51, 'service', 'purchase', '2025-04-01 11:29:16.205726', 2), (true, '0.0000', 'percent', 1, 68, '2025-04-01 11:29:16.205726', 2, '{"en_US": "VAT 0% intra-community (goods)"}', DEFAULT, false, DEFAULT, true, false, '01', 'sujeto', '{"en_US": "0% EU G"}', false, 1, 'on_invoice', 34, 'consu', 'purchase', '2025-04-01 11:29:16.205726', 2), (true, '0.0000', 'percent', 1, 68, '2025-04-01 11:29:16.205726', 2, '{"en_US": "VAT 0% import (goods)"}', DEFAULT, false, DEFAULT, true, false, '01', 'sujeto', '{"en_US": "0% EX G"}', false, 1, 'on_invoice', 34, 'consu', 'purchase', '2025-04-01 11:29:16.205726', 2), (true, '0.0000', 'percent', 1, 68, '2025-04-01 11:29:16.205726', 2, '{"en_US": "VAT 0% intra-community (good)"}', DEFAULT, false, '{"en_US": "Intra-Community (Goods)"}', true, false, '01', 'no_sujeto_loc', '{"en_US": "0% EU G"}', false, 1, 'on_invoice', 34, 'consu', 'sale', '2025-04-01 11:29:16.205726', 2), (true, '0.0000', 'percent', 1, 68, '2025-04-01 11:29:16.205726', 2, '{"en_US": "VAT 0% export (goods)"}', DEFAULT, false, '{"en_US": "Non-EU"}', true, false, '01', 'no_sujeto_loc', '{"en_US": "0% EX G"}', false, 1, 'on_invoice', 34, 'consu', 'sale', '2025-04-01 11:29:16.205726', 2), (true, '0.0000', 'percent', 1, 68, '2025-04-01 11:29:16.205726', 2, DEFAULT, '01', false, DEFAULT, true, false, '01', 'sujeto', DEFAULT, false, 1, 'on_invoice', 34, DEFAULT, 'sale', '2025-04-01 11:29:16.205726', 2) RETURNING "id"
ERROR: null value in column "name" of relation "account_tax" violates not-null constraint
DETAIL:  Failing row contains (403, 1, 1, 34, null, 68, 2, 2, sale, null, percent, on_invoice, null, null, null, 0.0000, t, f, f, t, null, 2025-04-01 11:29:16.205726, 2025-04-01 11:29:16.205726, null, sujeto, f, 01, 01).
 2025-04-01 11:29:20,166 1 WARNING odoo odoo.http: The operation cannot be completed:
- Create/update: a mandatory field is not set.
- Delete: another model requires the record being deleted. If possible, archive it instead.

Model: Tax (account.tax)
Field: Tax Name (name)

​Experiencing errors when reloading the Spanish fiscal localization package in Odoo 17 Community Edition can stem from various factors. Here's a structured approach to diagnose and resolve the issue:​

1. Update the Invoicing Module:

Ensure that your Invoicing (account) module is up-to-date, as outdated modules can lead to compatibility issues with localization packages.​

• Steps:
  • Navigate to Apps.​
  • Locate the Invoicing module.​
  • Click on Upgrade to install the latest version.​

This approach has been effective for other users encountering similar localization errors. ​

2. Verify Company Country Settings:

The fiscal localization package aligns with the country specified in your company settings. Confirm that Spain is set as the country for your company.​

• Steps:
  • Go to Settings → Companies.​
  • Select your company.​
  • Ensure the Country field is set to Spain.​

Proper country configuration ensures the correct localization package is applied. ​

3. Check for Existing Journal Entries:

If there are existing journal entries, changing the fiscal localization package may be restricted.​

• Solution:
  • If possible, delete draft journal entries.​
  • For posted entries, consider creating a new database if no critical data exists.​

This limitation is noted in Odoo's community discussions. ​

4. Review Error Logs:

Examining server logs can provide insights into the specific cause of the error.​

• Steps:
  • Access your server's log files, typically located at /var/log/odoo/odoo-server.log.​
  • Look for detailed error messages related to the localization loading process.​

5. Seek Community Support:

If the issue persists, consider reaching out to the Odoo community or consulting with Odoo experts who may have encountered and resolved similar challenges.​

By systematically addressing these areas, you can identify and resolve the issues affecting the reloading of the Spanish fiscal localization package in Odoo 17 CE.