Spanish Tax Localization in NetSuite: SII, Verifactu, E-Invoicing and AEAT Forms (2026)

Last updated: 2 November 2026. Regulatory dates checked against the BOE, the AEAT and the Spanish Ministry of Finance on that day.

This guide explains what Spanish tax localization in NetSuite includes, which deadlines apply between 2026 and 2028, and how Oracle's official localization compares with partner solutions.

Transparency note: BIT Technologies is an Oracle NetSuite Alliance Partner. We implement and support NetSuite for companies in Spain and the DACH region. This guide is based on Oracle's public documentation and official Spanish sources, linked throughout.

What is Spanish tax localization in NetSuite?

Spanish tax localization in NetSuite is the set of tax codes, fields, reports and AEAT connections that lets a Spanish subsidiary meet Spain's tax rules inside the ERP: calculating VAT, filing Modelos 303, 349, 390 and 347, sending SII records and printing Spanish financial statements. Oracle delivers it through the Spain Localization SuiteApp; partners offer alternatives.

Why NetSuite needs a localization to operate in Spain

NetSuite's core is global. It knows VAT in general, but not the specific boxes of a Spanish VAT return, the XML format the AEAT expects for SII, or the layout of a Spanish balance sheet. Those rules change often, and each one depends on Spanish law.

A localization fills that gap. It maps your transactions to the right box in each AEAT form, adds Spain-only fields (such as invoice types for SII) and creates the files the tax agency accepts. Without it, your finance team ends up rebuilding tax returns in spreadsheets, which is slow and risky.

What Spain's NetSuite localization includes

Oracle's Spain Localization SuiteApp covers VAT reporting, SII and Spanish financial statements. It has firm technical requirements: it only works in NetSuite OneWorld accounts with the SuiteTax engine, and only for subsidiaries whose country and nexus are Spain and whose currency is EUR.

VAT codes in SuiteTax: rates, intra-EU transactions, reverse charge and equivalence surcharge

Oracle publishes a fixed tax code table for Spain. The reports read these codes by name and properties, so you can't edit them or replace them with your own.

• Rates: ES_SR (21%), ES_RR (10%), ES_SRR (4%), ES_SSRR (5%) and ES_ZR (0%).
• Reverse charge on purchases: one code per rate (for example ES_SR_RC). These also feed the intra-EU acquisition boxes of Modelos 303 and 390.
• Reverse charge on sales and non-taxable lines: ES_RCS and ES_NL.
• Equivalence surcharge (recargo de equivalencia): the SuiteTax table for Spain does not include surcharge codes. If you sell to retailers under this regime, check how it will be handled before you go live.

AEAT forms: 303, 349, 390 and 347

The SuiteApp generates these forms as TXT files that you upload to the AEAT portal. It prepares the file; you still submit it.

If your company is in the SII, the AEAT exempts you from filing Modelos 347 and 390.

SII: automatic submission of VAT books to the AEAT

The SII (Immediate Supply of Information) replaces paper VAT books with electronic records sent to the AEAT within four working days. It is mandatory for companies with turnover above €6,010,121.04 in the previous year, companies registered in the monthly VAT refund scheme (REDEME) and VAT groups. Other companies can join voluntarily.

The SuiteApp creates the four SII files (registration and correction of issued and received invoices) in XML. You can send them manually or schedule automatic submission per report and per Spanish subsidiary. It can also read the AEAT's response file so you see which records were accepted or rejected.

Accounting books and reports under the Spanish General Accounting Plan (PGC)

The SuiteApp adds five Spain-specific financial reports: Balance de Situación (balance sheet), Balance de Sumas y Saldos (trial balance), Cuenta de Pérdidas y Ganancias (profit and loss), Libro Diario (journal) and Libro Mayor (general ledger). They only display correctly if your Spanish chart of accounts (PGC) is loaded. It also adds a workbook of issued and received invoices. With Multi-Book Accounting, all reports read only the subsidiary's primary book.

VAT on EU distance sales: OSS

If you sell to consumers in other EU countries, the separate One Stop Shop SuiteApp generates OSS reports for the Union, non-Union and Import schemes. The Spain Localization SuiteApp itself only supports the Union scheme.

Spain-specific fields and data: tax ID (NIF), invoice series and transaction type

Spanish compliance depends on clean master data. Every customer and vendor needs a valid tax ID (NIF or EU VAT number), because SII rejects records with unknown IDs. Invoices need correct, sequential numbering per series. SII also needs a classification of each invoice, for example standard, simplified or corrective, which the SuiteApp stores in dedicated SII fields on the transaction.

Spain's 2026–2028 tax calendar: what your NetSuite must comply with

Four obligations shape the next two years. Dates below were checked on 2 November 2026.

B2B e-invoicing: Crea y Crece Law, Royal Decree 238/2026 and Order HAC/1028/2026

The Crea y Crece Law (Law 18/2022) made electronic invoicing mandatory between Spanish businesses. Royal Decree 238/2026, published in the BOE on 31 March 2026, sets the rules. Invoices must be structured files based on the European standard EN 16931, not PDFs. Buyers must also report whether they accepted, rejected or paid each invoice.

Order HAC/1028/2026 was published on 5 October 2026 and entered into force on 6 October 2026. It regulates the AEAT's free public e-invoicing platform and starts the clock: 12 months for companies above €8 million, 24 months for everyone else. Self-employed individuals must issue e-invoices from 6 October 2028, but only report invoice and payment status from 6 October 2029.

For NetSuite users this is the biggest open item. At the time of writing, Oracle's documentation for Spain describes Verifactu support but not a solution for this B2B mandate. Plan for it now, whether with Oracle or a partner.

Verifactu: the new postponement and who is excluded because of SII

Verifactu (Royal Decree 1007/2023) sets rules for invoicing software: every invoice record must be secure, chained and traceable, and can be sent to the AEAT. Under Royal Decree-law 15/2025, the legal deadlines are 1 January 2027 for companies that pay corporate income tax and 1 July 2027 for everyone else.

On 5 October 2026 the Ministry of Finance announced it plans to move these obligations to October 2028, to match the B2B e-invoicing deadline for smaller companies. As of 2 November 2026 this change is not yet published in the BOE, so the 2027 dates are still the legal ones.

Important: companies in the SII are outside Verifactu for the invoices they issue themselves (article 3.3 of Royal Decree 1007/2023). In NetSuite, Oracle offers Verifactu through the European Union Electronic Invoicing SuiteApp, using Avalara as the service provider. Oracle notes that these features can't be used at the same time as the SII features of the Spain Localization SuiteApp, which matches the legal rule.

TicketBAI and the Basque provincial tax offices

The Basque Country's three provinces (Álava, Bizkaia and Gipuzkoa) have their own tax offices and their own invoicing system, TicketBAI. In Bizkaia it is part of a wider system called Batuz. If a Spanish subsidiary is taxed in one of these provinces, Verifactu doesn't apply, but TicketBAI does. Oracle's Spain documentation doesn't list TicketBAI support, so this usually needs a partner solution.

Official Oracle localization or partner localization: which one to choose

There is no single right answer. The best choice depends on your NetSuite setup, where your Spanish entities pay tax and which obligations apply to you.

Oracle's Spain Localization SuiteApp: what it covers and what it doesn't

Covers: Modelos 303, 349, 390 and 347; the four SII files with manual or scheduled submission; reading AEAT responses; five PGC financial reports; and Spanish, Latin American Spanish and English interfaces. Oracle keeps adding features, for example SII and Modelo 347 enhancements in release 2025.2.

Doesn't cover (per Oracle's documentation, November 2026): NetSuite accounts without OneWorld or SuiteTax; subsidiaries with a currency other than EUR; equivalence surcharge codes; OSS schemes other than Union; TicketBAI; and corporate income tax (Modelo 200). Verifactu is a separate feature in the European Union Electronic Invoicing SuiteApp.

Localization SuiteApps built by partners

Several NetSuite partners sell their own Spanish localization SuiteApps. They often aim to fill the gaps above, such as Legacy Tax accounts, TicketBAI or extra forms. Coverage, quality and pricing vary a lot, so ask each vendor for a written list of supported forms, SII scenarios and their plan for B2B e-invoicing.

Comparison

SuiteTax or Legacy Tax: why the tax engine matters

NetSuite has two tax engines. SuiteTax is the newer one and the only engine supported by the Spain Localization SuiteApp. Legacy Tax accounts rely on older SuiteApps (International Tax Reports, Supplementary Tax Calculation and Tax Audit Files), which can produce the Spanish VAT return, EU sales list and Intrastat, but not the SII.

Two cautions: enabling SuiteTax can't be undone, so always test it in a sandbox first. And moving an existing account from Legacy Tax to SuiteTax is a project in itself, not a checkbox.

How to implement Spanish localization in NetSuite, step by step

This is the path we follow for Oracle's localization. A partner solution changes some details, but not the logic.

1. Check prerequisites. Confirm OneWorld and SuiteTax. Enable the required features (Custom Records, Advanced PDF/HTML Templates, client and server SuiteScript, SuiteAnalytics Workbook, CRM and Inline Editing). Install the SuiteTax Engine, Tax Reporting Framework and Localization Assistant SuiteApps, then the Spain Localization SuiteApp.
2. Set up the Spanish subsidiary. Country and nexus Spain, currency EUR, and the Enable SII box on the Spain Localization subtab if you are in the SII. Load your PGC chart of accounts so the Spanish reports display correctly.
3. Map tax codes to form boxes. Set the default tax code for each transaction type on the Spain nexus. Then review Oracle's "what goes into each box" pages for Modelos 303, 349, 390 and 347 with your tax advisor, so every typical transaction lands in the right box.
4. Install the AEAT digital certificate. Upload the company's certificate under Setup > Company > Certificates, assign it to the Spanish subsidiary, give the Tax Filing permission to the right roles, and assign the ES SII Configuration role to whoever schedules SII submissions.
5. Test in sandbox with your tax advisor. Run a real month of transactions. Compare the Modelo 303 from NetSuite with the advisor's own calculation, and review the SII files before any live submission.
6. Go live with a supported first period. Run the first filing period together with your advisor and implementation partner, fix any rejected SII records, and only then hand the process over to the finance team.

Planning a new rollout? See our NetSuite implementation services.

How to migrate from a partner localization to the official one (or the other way round)

Switching localizations is common when a vendor stops updating its SuiteApp, when Oracle adds features you need, or when Oracle's version lacks something you depend on, such as TicketBAI.

The main risks are the same in both directions:

• Tax engine. If you move to Oracle's SuiteApp from a Legacy Tax account, you first need SuiteTax, and that change can't be reversed.
• Tax codes. Oracle's reports only read its own fixed tax codes. Custom codes from a partner solution must be remapped, and historical transactions keep their old codes.
• Open periods and SII records. Switch at the start of a filing period, never mid-period. Make sure every SII record sent with the old tool was accepted, so corrections don't fall between two systems.
• Parallel run. Generate the first Modelo 303 with both solutions and compare them before you turn the old one off.

See our NetSuite migration services for help planning the switch.

Common mistakes when setting up Spanish taxes in NetSuite

• Wrong box mapping. Custom or renamed tax codes are left out of Oracle's reports, so the amounts simply don't appear in the Modelo 303. Use Oracle's codes and check them box by box.
• Corrective invoices handled as plain credit notes. Spain treats corrective invoices (facturas rectificativas) as a separate invoice type in SII. If they aren't classified correctly or don't reference the original invoice, the AEAT can reject the record.
• Broken numbering series. Spanish invoice numbers must be sequential within each series. Gaps, shared series between subsidiaries or manual numbers cause problems in SII today and in Verifactu and e-invoicing tomorrow.
• Spanish subsidiaries inside OneWorld set up like any other. A currency other than EUR or a missing Spain nexus stops the Spanish reports from working. And with Multi-Book Accounting, the reports only read the primary book, so Spanish statutory figures kept in a secondary book won't appear.
• Missing tax IDs. Customers and vendors without a valid NIF or EU VAT number lead to SII rejections and incomplete Modelo 349 and 347 data.

Frequently asked questions

Does it work in NetSuite OneWorld with subsidiaries in several countries?

Yes. In fact, Oracle's Spain Localization SuiteApp only works in OneWorld. Each Spanish subsidiary needs Spain as its country and nexus and EUR as its currency. Subsidiaries in other countries are unaffected and use their own localizations.

Do I need a digital certificate to connect NetSuite with the AEAT?

For automatic SII submission, yes. You upload the company's digital certificate in NetSuite and assign it to the Spanish subsidiary. For Modelos 303, 349, 390 and 347, NetSuite generates a file and you submit it through the AEAT portal, using your usual certificate.

What happens to the localization when NetSuite is updated?

Oracle updates its localization SuiteApps alongside NetSuite releases, usually twice a year. If you copied and customized the Spanish financial reports, Oracle recommends keeping your own saved copy so a new SuiteApp version doesn't overwrite your changes. With a partner solution, check how fast the vendor tests and ships updates after each release.

Does it also cover corporate income tax (Modelo 200)?

No. Oracle's Spain Localization SuiteApp lists no corporate income tax form. Most companies prepare Modelo 200 in their tax advisor's software, starting from the trial balance and P&L that NetSuite produces under the PGC.