Last updated: 2 November 2026. Sources: BOE, AEAT and Ministry of Finance.
Coverage, 2026–2028 deadlines and Oracle versus partner options.
Transparency: BIT Technologies is an Oracle NetSuite Alliance Partner, implementing and supporting NetSuite in Spain and DACH. Sources: linked public Oracle documentation and Spanish authorities.
What is Spanish tax localization in NetSuite?
Spanish tax localization in NetSuite combines tax codes, fields, reports and AEAT connections to manage VAT, prepare Modelos 303, 349, 390 and 347, submit SII records and produce Spanish financial statements within the ERP. Oracle provides Spain Localization; partners offer alternatives whose coverage must be checked for each subsidiary.
Why NetSuite needs a localization to operate in Spain
Global NetSuite needs Spanish rules for VAT return boxes, SII XML and balance-sheet layouts.
Localization maps transactions to boxes, adds SII invoice types and produces tax files, avoiding spreadsheet reconstruction.
What Spain's NetSuite localization includes
Oracle’s Spain Localization SuiteApp covers VAT, SII and financial statements. It requires OneWorld, SuiteTax, and subsidiaries with Spain as country and nexus and EUR currency.
VAT codes in SuiteTax: rates, intra-EU transactions, reverse charge and equivalence surcharge
Reports read the fixed Spanish tax codes by name and properties: do not edit or replace them.
- 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
It generates TXT files for AEAT upload; you remain responsible for submission.
| Form | What it reports | How often |
|---|---|---|
| Modelo 303 | VAT return: output VAT minus deductible input VAT | Monthly or quarterly |
| Modelo 349 | Intra-EU supplies and acquisitions of goods and services | Monthly or quarterly |
| Modelo 390 | Annual VAT summary | Yearly, in January |
| Modelo 347 | Transactions with a single third party above €3,005.06 a year | Yearly, in February |
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
SII (Immediate Supply of Information) replaces paper VAT books with electronic records sent to AEAT within four working days. It is mandatory above €6,010,121.04 prior-year turnover, for REDEME members and VAT groups; others may opt in.
The SuiteApp generates four SII XML files: registration and correction of issued and received invoices. Submit manually or schedule by report and Spanish subsidiary; AEAT responses show accepted/rejected records.
Accounting books and reports under the Spanish General Accounting Plan (PGC)
Five Spanish financial reports cover Balance de Situación (balance sheet), Balance de Sumas y Saldos (trial balance), Cuenta de Pérdidas y Ganancias (P&L), Libro Diario (journal) and Libro Mayor (ledger). Load the PGC chart. An issued/received invoice workbook is included; Multi-Book reports read only the primary book.
VAT on EU distance sales: OSS
For EU consumer sales, the separate One Stop Shop SuiteApp reports Union, non-Union and import OSS schemes. Spain Localization itself supports only Union.
Spain-specific fields and data: tax ID (NIF), invoice series and transaction type
Maintain valid customer/vendor NIF or EU VAT IDs, sequential numbering per series and complete, simplified or corrective invoice classification in SII transaction fields. Unknown IDs cause rejections.
Spain's 2026–2028 tax calendar: what your NetSuite must comply with
Four main obligations:
| Obligation | Who it affects | Key date | Status | Official source |
|---|---|---|---|---|
| SII | Turnover above €6,010,121.04, REDEME, VAT groups, voluntary opt-ins | In force since 1 July 2017 | Mandatory now | AEAT |
| B2B e-invoicing | Companies with turnover above €8 million | 6 October 2027 | Set by Orden HAC/1028/2026 | BOE |
| B2B e-invoicing | All other companies and self-employed | 6 October 2028 | Set by Orden HAC/1028/2026 | AEAT |
| Verifactu (legal date) | Corporate income tax payers / all other users of invoicing software | 1 January 2027 / 1 July 2027 | In force (Royal Decree-law 15/2025) | BOE |
| Verifactu (announced date) | Same groups | October 2028 | Announced 5 October 2026; not yet in the BOE | Ministry of Finance |
| TicketBAI | Companies taxed in Álava, Bizkaia or Gipuzkoa | Bizkaia's phased rollout ended 1 January 2026 | Mandatory in all three territories | Álava, Gipuzkoa, Bizkaia |
B2B e-invoicing: Crea y Crece Law, Royal Decree 238/2026 and Order HAC/1028/2026
Crea y Crece (Law 18/2022) mandates Spanish B2B e-invoicing. Royal Decree 238/2026, published 31 March 2026, requires structured EN 16931 files, not PDFs, and buyer acceptance, rejection and payment reporting.
Order HAC/1028/2026, published 5 October and effective 6 October 2026, regulates AEAT’s free public platform. Businesses above €8 million get 12 months; others 24. Self-employed issuance starts 6 October 2028; invoice/payment status reporting starts 6 October 2029.
At the stated date, Oracle documents Verifactu, not this B2B obligation. Plan with Oracle or a partner; see Crea y Crece.
Verifactu: the new postponement and who is excluded because of SII
Verifactu (RD 1007/2023) requires secure, chained, traceable invoice records that can be sent to AEAT. RDL 15/2025 sets 1 January 2027 for corporate income taxpayers and 1 July 2027 for others.
On 5 October 2026, the Ministry of Finance announced October 2028 postponement plans, aligning with smaller businesses’ B2B deadline. As of 2 November 2026, BOE publication was pending: 2027 remained legally applicable.
SII excludes Verifactu for self-issued invoices (RD 1007/2023, art. 3.3). Oracle provides Verifactu through EU Electronic Invoicing with Avalara, incompatible with simultaneous Spain Localization SII use. See Verifactu and NetSuite.
TicketBAI and the Basque provincial tax offices
Álava, Bizkaia and Gipuzkoa have provincial tax offices and TicketBAI; Bizkaia incorporates it in Batuz. Subsidiaries taxed there use TicketBAI, not Verifactu. Oracle documents no support, usually requiring a partner. Navarre’s separate foral regime and invoicing rules need independent analysis.
Official Oracle localization or partner localization: which one to choose
Choose by configuration, tax jurisdiction and obligations.
Oracle's Spain Localization SuiteApp: what it covers and what it doesn't
Covers: Modelos 303, 349, 390, 347; four SII XMLs, manual/scheduled submission and AEAT responses; five PGC reports; Spanish, Latin American Spanish and English interfaces. Release 2025.2 improved SII and Modelo 347.
Excludes (Oracle documentation, November 2026): equivalence surcharge codes, non-Union OSS, TicketBAI and Modelo 200. Verifactu requires EU Electronic Invoicing.
Localization SuiteApps built by partners
Partner SuiteApps may cover Legacy Tax, TicketBAI and additional forms. Coverage, quality and price vary: request written forms, SII scenarios and B2B plans.
Comparison
| Criterion | Oracle Spain Localization | Partner localization |
|---|---|---|
| SII | Yes: XML files, manual or scheduled submission | Usually yes; confirm scenarios covered |
| AEAT forms | 303, 349, 390, 347 | Varies by vendor; ask for the list |
| PGC financial reports | 5 reports (balance sheet, trial balance, P&L, journal, ledger) | Varies by vendor |
| B2B e-invoicing (RD 238/2026) | Not documented yet (November 2026) | Ask for the roadmap and dates |
| Verifactu | Yes, via EU Electronic Invoicing SuiteApp with Avalara | Varies by vendor |
| TicketBAI | Not documented | Offered by some vendors |
| License cost | Published by Oracle; confirm costs, including the Verifactu provider, with your account manager | Usually a separate subscription |
| Maintenance | Oracle, aligned with NetSuite releases | Vendor; check update times and support terms |
| Vendor dependency | Oracle | The partner's continuity and team |
| Technical requirements | OneWorld, SuiteTax, EUR subsidiary | Depends; some support other setups |
SuiteTax or Legacy Tax: why the tax engine matters
SuiteTax is newer and the only engine compatible with Spain Localization. Legacy Tax uses International Tax Reports, Supplementary Tax Calculation and Tax Audit Files for Spanish VAT, EU sales lists and Intrastat, but not SII.
SuiteTax activation is irreversible: test in sandbox. Legacy Tax migration is a project, not a checkbox.
How to implement Spanish localization in NetSuite, step by step
Oracle steps; partner details differ, not the underlying sequence.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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)
Switch when updates stop, Oracle adds needed features or lacks required coverage such as TicketBAI.
Risks in either direction:
- 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. 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: Spanish subsidiaries use Spanish localization; others retain their own.
Do I need a digital certificate to connect NetSuite with the AEAT?
Yes for automatic SII: upload the company certificate and assign it to the subsidiary. Submit generated Modelo 303, 349, 390 and 347 files through AEAT using your usual certificate.
What happens to the localization when NetSuite is updated?
Oracle normally updates twice yearly alongside NetSuite. Save customized Spanish report copies against overwriting. For partners, check testing and release turnaround after each update.
Does it also cover corporate income tax (Modelo 200)?
No Modelo 200 is included. Advisors usually prepare it in their software from NetSuite’s PGC trial balance and P&L.
